Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]

Groups > linux.debian.kernel > #69955 > unrolled thread

Bug#985862: linux: Please enable support for NXP/Freescale iMX8

Back to article view | Back to linux.debian.kernel

Contents

  Bug#985862: linux: Please enable support for NXP/Freescale iMX8 Wookey <wookey@wookware.org> - 2021-03-25 06:20 +0100
    Bug#985862: linux: Please enable support for NXP/Freescale iMX8 Uwe Kleine-König <u.kleine-koenig@pengutronix.de> - 2021-03-25 11:30 +0100
    Processed: Re: Bug#985862: linux: Please enable support for  NXP/Freescale iMX8 "Debian Bug Tracking System" <owner@bugs.debian.org> - 2021-03-25 11:30 +0100
    Bug#985862: marked as done (linux: Please enable support for  NXP/Freescale iMX8) "Debian Bug Tracking System" <owner@bugs.debian.org> - 2021-03-27 16:30 +0100
    Bug#985862: linux: Please enable support for NXP/Freescale iMX8 Wookey <wookey@debian.org> - 2021-04-12 15:30 +0200
      Bug#985862: linux: Please enable support for NXP/Freescale iMX8 Salvatore Bonaccorso <carnil@debian.org> - 2021-04-12 16:40 +0200
        Bug#985862: linux: Please enable support for NXP/Freescale iMX8 Wookey <wookey@wookware.org> - 2021-04-12 17:30 +0200

#69955 — Bug#985862: linux: Please enable support for NXP/Freescale iMX8

Source: linux
Severity: normal

The iMX8 SoC is used on various boards, widely available to debian
users and well supported by free software, but the platform is not
enabled in debian kernels, which is a rather major omission. I don't
know why not (I guess no-one filed this bug?).

These are all avilable today and should at least mostly work with
mainline:
Nitrogen 8M 
 https://boundarydevices.com/product/nitrogen8m/
Solidrun 
 Cubox M https://shop.solid-run.com/product/SRMP8QDWB1D04GE008X00CE/
 Hummingboard Pulse https://shop.solid-run.com/product-category/embedded-computers/nxp-family/hummingboard-m/
Purism
 Librem 5 Phone https://en.wikipedia.org/wiki/Librem_5
Compulab
 SBC-iMX8X https://www.compulab.com/products/sbcs/sbc-imx8x-nxp-i-mx-8x-single-board-computer/
 (supported since 5.4.24)
Toradex
 Apalis iMX8 CoM https://www.toradex.com/computer-on-modules/apalis-arm-family/nxp-imx-8

I believe that all that is needed is adding
CONFIG_ARCH_MXC=y in debian/config/arm64/config
Which is set by default upstream.

(There may be other drivers that should enabled too for some of these
platforms?)

I just built the kernel with the above config change and it builds
fine on arm64, and installs and boots on softiron. I don't have an
iMX8 here to test on, but we can find some, I'm sure.

It seems like the timing was rather unfortunate here with some of this
hardware only becoming widely available in Q4 2020 (shortly before the
Bullseye freeze). Is there any chance of one more hardware enablement
upload for bullseye, or does this feel like too big a change? If not,
getting this into a point release would make debian stable useful on a
lot more hardware. What testing would make the kernel team reasonably
happy about doing that?

-- 
Wookey

[toc] | [next] | [standalone]

#69965

[Multipart message — attachments visible in raw view] — view raw

Control: tag -1 + pending

Hello Wookey,

On Thu, Mar 25, 2021 at 05:13:02AM +0000, Wookey wrote:
> Source: linux
> Severity: normal
> 
> The iMX8 SoC is used on various boards, widely available to debian
> users and well supported by free software, but the platform is not
> enabled in debian kernels, which is a rather major omission. I don't
> know why not (I guess no-one filed this bug?).
> 
> These are all avilable today and should at least mostly work with
> mainline:
> Nitrogen 8M 
>  https://boundarydevices.com/product/nitrogen8m/
> Solidrun 
>  Cubox M https://shop.solid-run.com/product/SRMP8QDWB1D04GE008X00CE/
>  Hummingboard Pulse https://shop.solid-run.com/product-category/embedded-computers/nxp-family/hummingboard-m/
> Purism
>  Librem 5 Phone https://en.wikipedia.org/wiki/Librem_5
> Compulab
>  SBC-iMX8X https://www.compulab.com/products/sbcs/sbc-imx8x-nxp-i-mx-8x-single-board-computer/
>  (supported since 5.4.24)
> Toradex
>  Apalis iMX8 CoM https://www.toradex.com/computer-on-modules/apalis-arm-family/nxp-imx-8
> 
> I believe that all that is needed is adding
> CONFIG_ARCH_MXC=y in debian/config/arm64/config
> Which is set by default upstream.

I enabled a few more settings in our sid branch. See
https://deb.li/3fUTV .

> (There may be other drivers that should enabled too for some of these
> platforms?)
> 
> I just built the kernel with the above config change and it builds
> fine on arm64, and installs and boots on softiron. I don't have an
> iMX8 here to test on, but we can find some, I'm sure.

I have an i.MX8 here, but didn't do any tests (yet).

Best regards
Uwe

-- 
Pengutronix e.K.                           | Uwe Kleine-König            |
Industrial Linux Solutions                 | https://www.pengutronix.de/ |

[toc] | [prev] | [next] | [standalone]

#69967 — Processed: Re: Bug#985862: linux: Please enable support for NXP/Freescale iMX8

Processing control commands:

> tag -1 + pending
Bug #985862 [src:linux] linux: Please enable support for NXP/Freescale iMX8
Added tag(s) pending.

-- 
985862: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=985862
Debian Bug Tracking System
Contact owner@bugs.debian.org with problems

[toc] | [prev] | [next] | [standalone]

#69993 — Bug#985862: marked as done (linux: Please enable support for NXP/Freescale iMX8)

[Multipart message — attachments visible in raw view] — view raw

Your message dated Sat, 27 Mar 2021 15:19:48 +0000
with message-id <E1lQAj6-0004kA-SP@fasolo.debian.org>
and subject line Bug#985862: fixed in linux 5.10.26-1
has caused the Debian Bug report #985862,
regarding linux: Please enable support for NXP/Freescale iMX8
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact owner@bugs.debian.org
immediately.)


-- 
985862: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=985862
Debian Bug Tracking System
Contact owner@bugs.debian.org with problems

[toc] | [prev] | [next] | [standalone]

#70084

Source: linux
Version: 5.10.26-1
Followup-For: Bug #985862

Testing 5.10.26-1 on a Compulab IOT-gateway board (https://www.compulab.com/products/iot-gateways/iot-gate-imx8-industrial-arm-iot-gateway/) revealed that a couple more config options are needed to support it:
 CONFIG_SERIAL_IMX_CONSOLE=y
 CONFIG_CLK_IMX8MM=y

Without these it hangs early in the boot process.

(Whilst they can be configured as modules this doesn't work
well. CONFIG_SERIAL_IMX_CONSOLE=m misses quite alot of the boot
messages and CONFIG_CLK_IMX8MM=m just makes it hang.)

(Thanks to Vincent for the testing)

Enabling these in the next upload, whenever that is, would be much appreciated.

Addendum:
There are almost certainly some other clocks needed for other hardware, but that
needs to await testing/feedback from people with access to said hardware.

Just for future reference: I believe the correspondance of config options to SOC variants is:
 IMX8MN == i.MX8M Nano
 IMX8MQ == i.MX8M Quad
IMX8QXP == i.MX8 QuadXPlus
 IMX8MP == i.MX8M Plus

--
Wookey

[toc] | [prev] | [next] | [standalone]

#70088

Hi,

On Mon, Apr 12, 2021 at 02:22:39PM +0100, Wookey wrote:
> Source: linux
> Version: 5.10.26-1
> Followup-For: Bug #985862
> 
> Testing 5.10.26-1 on a Compulab IOT-gateway board (https://www.compulab.com/products/iot-gateways/iot-gate-imx8-industrial-arm-iot-gateway/) revealed that a couple more config options are needed to support it:
>  CONFIG_SERIAL_IMX_CONSOLE=y
>  CONFIG_CLK_IMX8MM=y
> 
> Without these it hangs early in the boot process.
> 
> (Whilst they can be configured as modules this doesn't work
> well. CONFIG_SERIAL_IMX_CONSOLE=m misses quite alot of the boot
> messages and CONFIG_CLK_IMX8MM=m just makes it hang.)
> 
> (Thanks to Vincent for the testing)
> 
> Enabling these in the next upload, whenever that is, would be much appreciated.
> 
> Addendum:
> There are almost certainly some other clocks needed for other hardware, but that
> needs to await testing/feedback from people with access to said hardware.
> 
> Just for future reference: I believe the correspondance of config options to SOC variants is:
>  IMX8MN == i.MX8M Nano
>  IMX8MQ == i.MX8M Quad
> IMX8QXP == i.MX8 QuadXPlus
>  IMX8MP == i.MX8M Plus

Thanks Wookey for the testing feedback. This really starts to become
late for the bullseye release, so we need to be careful enough. We
will see what we can do.

Regards,
Salvatore

[toc] | [prev] | [next] | [standalone]

#70090

[Multipart message — attachments visible in raw view] — view raw

On 2021-04-12 16:30 +0200, Salvatore Bonaccorso wrote:
> 
> Thanks Wookey for the testing feedback. This really starts to become
> late for the bullseye release, so we need to be careful enough. We
> will see what we can do.

Understood. I see we were just 2 days too late for the 5.10.28 update,
which is unfortunate - that would have worked nicely.

I think it's fairly safe, and it's been upstream and enabled there for
a while, but of course you never know...

If this has to end up in the first point release after bullseye then that's fair enough. 


Wookey
-- 
Principal hats:  Linaro, Debian, Wookware, ARM
http://wookware.org/

[toc] | [prev] | [standalone]

Back to top | Article view | linux.debian.kernel

csiph-web