linux-next: build failure after merge of the imx-mxs tree

linux-next: build failure after merge of the imx-mxs tree

[Stephen Rothwell]

[-- Attachment #1: Type: text/plain, Size: 546 bytes --]

Hi all,

After merging the imx-mxs tree, today's linux-next build (arm
multi_v7_defconfig) failed like this:

arch/arm/mach-imx/mmdc.c: In function 'imx_mmdc_remove':
arch/arm/mach-imx/mmdc.c:465:24: error: 'mmdc_ipg_clk' undeclared (first use in this function)
  465 |  clk_disable_unprepare(mmdc_ipg_clk);
      |                        ^~~~~~~~~~~~

Caused by commit

  52172fdbc3a3 ("ARM: imx: add missing clk_disable_unprepare() when remove imx_mmdc")

I have reverted that commit for today.

-- 
Cheers,
Stephen Rothwell

[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 488 bytes --]

Re: linux-next: build failure after merge of the imx-mxs tree

[Shawn Guo]

On Tue, Nov 03, 2020 at 12:00:08PM +1100, Stephen Rothwell wrote:
> Hi all,
> 
> After merging the imx-mxs tree, today's linux-next build (arm
> multi_v7_defconfig) failed like this:
> 
> arch/arm/mach-imx/mmdc.c: In function 'imx_mmdc_remove':
> arch/arm/mach-imx/mmdc.c:465:24: error: 'mmdc_ipg_clk' undeclared (first use in this function)
>   465 |  clk_disable_unprepare(mmdc_ipg_clk);
>       |                        ^~~~~~~~~~~~
> 
> Caused by commit
> 
>   52172fdbc3a3 ("ARM: imx: add missing clk_disable_unprepare() when remove imx_mmdc")
> 
> I have reverted that commit for today.

Sorry for the breakage, Stephen.  I dropped the commit from my branch.

Shawn

linux-next: build failure after merge of the imx-mxs tree

[Stephen Rothwell]

[-- Attachment #1: Type: text/plain, Size: 415 bytes --]

Hi all,

After merging the imx-mxs tree, today's linux-next build (arm64 defconfig)
failed like this:

Error: /home/sfr/next/next/arch/arm64/boot/dts/freescale/imx8mm-evkb.dts:22.2-7 syntax error
FATAL ERROR: Unable to parse input tree

Caused by commit

  c288f420e3c6 ("arm64: dts: imx8mm-evkb: add support for i.MX8MM-EVKB")

I have reverted that commit for today.

-- 
Cheers,
Stephen Rothwell

[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 488 bytes --]

linux-next: build failure after merge of the imx-mxs tree

[Stephen Rothwell]

[-- Attachment #1: Type: text/plain, Size: 532 bytes --]

Hi all,

After merging the imx-mxs tree, today's linux-next build (arm
multi_v7_defconfig) failed like this:

arch/arm/boot/dts/imx7d-remarkable2.dts:26.15-44.5: ERROR (phandle_references): /thermal-zones/epd-thermal: Reference to non-existent node or label "epd_pmic"

ERROR: Input tree has errors, aborting (use -f to force output)

Caused by commit

  b725fda78895 ("ARM: dts: imx7d-remarkable2: Enable silergy,sy7636a")

I have used the imx-mxs tree from next-20221028 for today.

-- 
Cheers,
Stephen Rothwell

[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 488 bytes --]

Re: linux-next: build failure after merge of the imx-mxs tree

[Alistair]

On Mon, 31 Oct 2022, at 8:09 AM, Stephen Rothwell wrote:
> Hi all,
> 
> After merging the imx-mxs tree, today's linux-next build (arm
> multi_v7_defconfig) failed like this:
> 
> arch/arm/boot/dts/imx7d-remarkable2.dts:26.15-44.5: ERROR (phandle_references): /thermal-zones/epd-thermal: Reference to non-existent node or label "epd_pmic"
> 
> ERROR: Input tree has errors, aborting (use -f to force output)

Sorry, that's completely my fault. Apparently I had a local change
that didn't get committed. I'll send a new version of this patch.

Alistair

> 
> Caused by commit
> 
>   b725fda78895 ("ARM: dts: imx7d-remarkable2: Enable silergy,sy7636a")
> 
> I have used the imx-mxs tree from next-20221028 for today.
> 
> -- 
> Cheers,
> Stephen Rothwell
> 

Re: linux-next: build failure after merge of the imx-mxs tree

[Shawn Guo]

On Mon, Oct 31, 2022 at 08:11:57AM +1000, Alistair wrote:
> On Mon, 31 Oct 2022, at 8:09 AM, Stephen Rothwell wrote:
> > Hi all,
> > 
> > After merging the imx-mxs tree, today's linux-next build (arm
> > multi_v7_defconfig) failed like this:
> > 
> > arch/arm/boot/dts/imx7d-remarkable2.dts:26.15-44.5: ERROR (phandle_references): /thermal-zones/epd-thermal: Reference to non-existent node or label "epd_pmic"
> > 
> > ERROR: Input tree has errors, aborting (use -f to force output)
> 
> Sorry, that's completely my fault. Apparently I had a local change
> that didn't get committed. I'll send a new version of this patch.

Alistair,

I have fixed it up with the change below.

Shawn

diff --git a/arch/arm/boot/dts/imx7d-remarkable2.dts b/arch/arm/boot/dts/imx7d-remarkable2.dts
index 2314f68f3c86..8b2f11e85e05 100644
--- a/arch/arm/boot/dts/imx7d-remarkable2.dts
+++ b/arch/arm/boot/dts/imx7d-remarkable2.dts
@@ -24,7 +24,7 @@ memory@80000000 {
 
        thermal-zones {
                epd-thermal {
-                       thermal-sensors = <&epd_pmic>;
+                       thermal-sensors = <&sy7636a>;
                        polling-delay-passive = <30000>;
                        polling-delay = <30000>;
 

linux-next: build failure after merge of the imx-mxs tree

[Stephen Rothwell]

[-- Attachment #1: Type: text/plain, Size: 752 bytes --]

Hi all,

After merging the imx-mxs tree, today's linux-next build (arm
multi_v7_defconfig) failed like this:

Error: arch/arm/boot/dts/imx6q-yapp4-crux.dts:24.1-7 Label or path codec not found
Error: arch/arm/boot/dts/imx6q-yapp4-crux.dts:52.1-7 Label or path sound not found
FATAL ERROR: Syntax error parsing input tree
Error: arch/arm/boot/dts/imx6qp-yapp4-crux-plus.dts:24.1-7 Label or path codec not found 
Error: arch/arm/boot/dts/imx6qp-yapp4-crux-plus.dts:52.1-7 Label or path sound not found 
FATAL ERROR: Syntax error parsing input tree

Caused by commit

  a4d744ac2bab ("ARM: dts: imx6dl-yapp4: Add Y Soft IOTA Crux/Crux+ board")

I have used the imx-mxs tree from next-20211206 for today.

-- 
Cheers,
Stephen Rothwell

[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 488 bytes --]

Re: linux-next: build failure after merge of the imx-mxs tree

[Michal Vokáč]

On 06. 12. 21 23:10, Stephen Rothwell wrote:
> Hi all,
> 
> After merging the imx-mxs tree, today's linux-next build (arm
> multi_v7_defconfig) failed like this:
> 
> Error: arch/arm/boot/dts/imx6q-yapp4-crux.dts:24.1-7 Label or path codec not found
> Error: arch/arm/boot/dts/imx6q-yapp4-crux.dts:52.1-7 Label or path sound not found
> FATAL ERROR: Syntax error parsing input tree
> Error: arch/arm/boot/dts/imx6qp-yapp4-crux-plus.dts:24.1-7 Label or path codec not found
> Error: arch/arm/boot/dts/imx6qp-yapp4-crux-plus.dts:52.1-7 Label or path sound not found
> FATAL ERROR: Syntax error parsing input tree
> 
> Caused by commit
> 
>    a4d744ac2bab ("ARM: dts: imx6dl-yapp4: Add Y Soft IOTA Crux/Crux+ board")
> 
> I have used the imx-mxs tree from next-20211206 for today.
> 

Hi Stephen,
I already send a patch for this yesterday short time after
the kernel test robot reported the same failure. It is on
the devicetree mailing list:

https://www.spinics.net/lists/devicetree/msg461729.html

Sorry for my mistake though,
Michal

linux-next: build failure after merge of the imx-mxs tree

[Stephen Rothwell]

[-- Attachment #1: Type: text/plain, Size: 638 bytes --]

Hi all,

After merging the imx-mxs tree, today's linux-next build (powerpc
allyesconfig) failed like this:

ld: drivers/soc/imx/soc-imx-scu.o: in function `.imx_scu_soc_probe':
soc-imx-scu.c:(.text.imx_scu_soc_probe+0x44): undefined reference to `.imx_scu_get_handle'
ld: soc-imx-scu.c:(.text.imx_scu_soc_probe+0x134): undefined reference to `.imx_scu_call_rpc'
ld: soc-imx-scu.c:(.text.imx_scu_soc_probe+0x20c): undefined reference to `.imx_scu_call_rpc'

Caused by commit

  68c189e3a93c ("soc: imx: increase build coverage for imx8m soc driver")

I have reverted that commit for today.

-- 
Cheers,
Stephen Rothwell

[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 488 bytes --]

RE: linux-next: build failure after merge of the imx-mxs tree

[Peng Fan]

> Subject: linux-next: build failure after merge of the imx-mxs tree

Sorry for this. I'll fix it. It should be the functions not defined when
IMX_SCU not defined.

Thanks,
Peng.

> 
> Hi all,
> 
> After merging the imx-mxs tree, today's linux-next build (powerpc
> allyesconfig) failed like this:
> 
> ld: drivers/soc/imx/soc-imx-scu.o: in function `.imx_scu_soc_probe':
> soc-imx-scu.c:(.text.imx_scu_soc_probe+0x44): undefined reference to
> `.imx_scu_get_handle'
> ld: soc-imx-scu.c:(.text.imx_scu_soc_probe+0x134): undefined reference to
> `.imx_scu_call_rpc'
> ld: soc-imx-scu.c:(.text.imx_scu_soc_probe+0x20c): undefined reference to
> `.imx_scu_call_rpc'
> 
> Caused by commit
> 
>   68c189e3a93c ("soc: imx: increase build coverage for imx8m soc driver")
> 
> I have reverted that commit for today.
> 
> --
> Cheers,
> Stephen Rothwell

Re: linux-next: build failure after merge of the imx-mxs tree

[Shawn Guo]

On Tue, Feb 18, 2020 at 02:18:00AM +0000, Peng Fan wrote:
> 
> > Subject: linux-next: build failure after merge of the imx-mxs tree
> 
> Sorry for this. I'll fix it. It should be the functions not defined when
> IMX_SCU not defined.

I'm dropping the patch from my branch for now.

Shawn

linux-next: build failure after merge of the imx-mxs tree

[Stephen Rothwell]

[-- Attachment #1: Type: text/plain, Size: 1296 bytes --]

Hi all,

After merging the imx-mxs tree, today's linux-next build (arm
multi_v7_defconfig) failed like this:

Error: arch/arm/boot/dts/imx6ull-colibri.dtsi:536.4-5 syntax error
FATAL ERROR: Unable to parse input tree
make[2]: *** [scripts/Makefile.lib:285: arch/arm/boot/dts/imx6ull-colibri-wifi-eval-v3.dtb] Error 1
Error: arch/arm/boot/dts/imx6ull-colibri.dtsi:536.4-5 syntax error
FATAL ERROR: Unable to parse input tree
make[2]: *** [scripts/Makefile.lib:285: arch/arm/boot/dts/imx6ull-colibri-eval-v3.dtb] Error 1
arch/arm/boot/dts/imx6qdl-zii-rdu2.dtsi:422.28-424.7: Warning (graph_endpoint): /soc/aips-bus@2100000/i2c@21a0000/edp-bridge@68/ports/port@2/endpoint: graph connection to node '/panel/port/endpoint' is not bidirectional
arch/arm/boot/dts/imx6qdl-zii-rdu2.dtsi:422.28-424.7: Warning (graph_endpoint): /soc/aips-bus@2100000/i2c@21a0000/edp-bridge@68/ports/port@2/endpoint: graph connection to node '/panel/port/endpoint' is not bidirectional

Caused by commit

  e7ebb215cb78 ("ARM: dts: colibri-imx6ull: correct wrong pinmuxing and add comments")

The warning was (probably) introduced by commit

  e79295edf1df ("ARM: dts: imx6: RDU2: link eDP bridge to panel")

I have used the imx-mxs tree from next-20191211 for today.
-- 
Cheers,
Stephen Rothwell

[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 488 bytes --]

Re: linux-next: build failure after merge of the imx-mxs tree

[Shawn Guo]

Hi Stephen,

On Thu, Dec 12, 2019 at 08:35:56AM +1100, Stephen Rothwell wrote:
> Hi all,
> 
> After merging the imx-mxs tree, today's linux-next build (arm
> multi_v7_defconfig) failed like this:

Sorry for the breakage.

> 
> Error: arch/arm/boot/dts/imx6ull-colibri.dtsi:536.4-5 syntax error
> FATAL ERROR: Unable to parse input tree
> make[2]: *** [scripts/Makefile.lib:285: arch/arm/boot/dts/imx6ull-colibri-wifi-eval-v3.dtb] Error 1
> Error: arch/arm/boot/dts/imx6ull-colibri.dtsi:536.4-5 syntax error
> FATAL ERROR: Unable to parse input tree
> make[2]: *** [scripts/Makefile.lib:285: arch/arm/boot/dts/imx6ull-colibri-eval-v3.dtb] Error 1
> arch/arm/boot/dts/imx6qdl-zii-rdu2.dtsi:422.28-424.7: Warning (graph_endpoint): /soc/aips-bus@2100000/i2c@21a0000/edp-bridge@68/ports/port@2/endpoint: graph connection to node '/panel/port/endpoint' is not bidirectional
> arch/arm/boot/dts/imx6qdl-zii-rdu2.dtsi:422.28-424.7: Warning (graph_endpoint): /soc/aips-bus@2100000/i2c@21a0000/edp-bridge@68/ports/port@2/endpoint: graph connection to node '/panel/port/endpoint' is not bidirectional
> 
> Caused by commit
> 
>   e7ebb215cb78 ("ARM: dts: colibri-imx6ull: correct wrong pinmuxing and add comments")
> 
> The warning was (probably) introduced by commit
> 
>   e79295edf1df ("ARM: dts: imx6: RDU2: link eDP bridge to panel")

I have just taken these two commits out.

> 
> I have used the imx-mxs tree from next-20191211 for today.

Thanks.

Shawn

Re: linux-next: build failure after merge of the imx-mxs tree

[Lucas Stach]

Hi Shawn,

On Do, 2019-12-12 at 09:33 +0800, Shawn Guo wrote:
> Hi Stephen,
> 
> On Thu, Dec 12, 2019 at 08:35:56AM +1100, Stephen Rothwell wrote:
> > Hi all,
> > 
> > After merging the imx-mxs tree, today's linux-next build (arm
> > multi_v7_defconfig) failed like this:
> 
> Sorry for the breakage.
> 
[...]
> > The warning was (probably) introduced by commit
> > 
> >   e79295edf1df ("ARM: dts: imx6: RDU2: link eDP bridge to panel")
> 
> I have just taken these two commits out.

The commit message of this change should maybe have been clearer, but
the warning is expected. The bootloader fixes the DT before passing it
on to Linux by completing the other direction of link if eDP is
enabled.

How do we want to handle this? If you totally dislike the warning I can
get around it by not adding the link and adding some more complexity to
the bootloader, but given the choice I would like to keep the
incomplete link in the Linux DT and keep bootloader complexity down.

Regards,
Lucas

Re: linux-next: build failure after merge of the imx-mxs tree

[Shawn Guo]

On Thu, Dec 12, 2019 at 10:45:34AM +0100, Lucas Stach wrote:
> Hi Shawn,
> 
> On Do, 2019-12-12 at 09:33 +0800, Shawn Guo wrote:
> > Hi Stephen,
> > 
> > On Thu, Dec 12, 2019 at 08:35:56AM +1100, Stephen Rothwell wrote:
> > > Hi all,
> > > 
> > > After merging the imx-mxs tree, today's linux-next build (arm
> > > multi_v7_defconfig) failed like this:
> > 
> > Sorry for the breakage.
> > 
> [...]
> > > The warning was (probably) introduced by commit
> > > 
> > >   e79295edf1df ("ARM: dts: imx6: RDU2: link eDP bridge to panel")
> > 
> > I have just taken these two commits out.
> 
> The commit message of this change should maybe have been clearer, but
> the warning is expected. The bootloader fixes the DT before passing it
> on to Linux by completing the other direction of link if eDP is
> enabled.
> 
> How do we want to handle this? If you totally dislike the warning I can
> get around it

Yes, please.  I do not like the warning.

Shawn

linux-next: build failure after merge of the imx-mxs tree

[Stephen Rothwell]

[-- Attachment #1: Type: text/plain, Size: 850 bytes --]

Hi Shawn,

After merging the imx-mxs tree, today's linux-next build (arm
multi_v7_defconfig) failed like this:

drivers/clk/imx/clk.c: In function 'imx_mmdc_mask_handshake':
drivers/clk/imx/clk.c:20:8: error: implicit declaration of function 'readl_relaxed'; did you mean 'xchg_relaxed'? [-Werror=implicit-function-declaration]
  reg = readl_relaxed(ccm_base + CCM_CCDR);
        ^~~~~~~~~~~~~
        xchg_relaxed
drivers/clk/imx/clk.c:22:2: error: implicit declaration of function 'writel_relaxed'; did you mean 'xchg_relaxed'? [-Werror=implicit-function-declaration]
  writel_relaxed(reg, ccm_base + CCM_CCDR);
  ^~~~~~~~~~~~~~
  xchg_relaxed

Caused by commit

  0dc6b492b6e0 ("clk: imx: Add common API for masking MMDC handshake")

I have used the imx-mxs tree from next-20190520 for today.

-- 
Cheers,
Stephen Rothwell

[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 488 bytes --]

RE: linux-next: build failure after merge of the imx-mxs tree

[Anson Huang]

Hi, Stephen/Shawn
	I realized this issue last week when I updated my Linux-next tree (NOT sure why I did NOT meet such issue when I did the patch), so I resent the patch series of adding head file "io.h" to fix this issue, please apply below V2 patch series instead, sorry for the inconvenience.

https://patchwork.kernel.org/patch/10944681/

thanks,
Anson.

> -----Original Message-----
> From: Stephen Rothwell [mailto:sfr@canb.auug.org.au]
> Sent: Tuesday, May 21, 2019 6:38 AM
> To: Shawn Guo <shawnguo@kernel.org>
> Cc: Linux Next Mailing List <linux-next@vger.kernel.org>; Linux Kernel Mailing
> List <linux-kernel@vger.kernel.org>; Anson Huang <anson.huang@nxp.com>;
> Aisheng Dong <aisheng.dong@nxp.com>
> Subject: linux-next: build failure after merge of the imx-mxs tree
> 
> Hi Shawn,
> 
> After merging the imx-mxs tree, today's linux-next build (arm
> multi_v7_defconfig) failed like this:
> 
> drivers/clk/imx/clk.c: In function 'imx_mmdc_mask_handshake':
> drivers/clk/imx/clk.c:20:8: error: implicit declaration of function
> 'readl_relaxed'; did you mean 'xchg_relaxed'? [-Werror=implicit-function-
> declaration]
>   reg = readl_relaxed(ccm_base + CCM_CCDR);
>         ^~~~~~~~~~~~~
>         xchg_relaxed
> drivers/clk/imx/clk.c:22:2: error: implicit declaration of function
> 'writel_relaxed'; did you mean 'xchg_relaxed'? [-Werror=implicit-function-
> declaration]
>   writel_relaxed(reg, ccm_base + CCM_CCDR);
>   ^~~~~~~~~~~~~~
>   xchg_relaxed
> 
> Caused by commit
> 
>   0dc6b492b6e0 ("clk: imx: Add common API for masking MMDC handshake")
> 
> I have used the imx-mxs tree from next-20190520 for today.
> 
> --
> Cheers,
> Stephen Rothwell

Re: linux-next: build failure after merge of the imx-mxs tree

[Shawn Guo]

On Tue, May 21, 2019 at 02:16:47AM +0000, Anson Huang wrote:
> Hi, Stephen/Shawn
> 	I realized this issue last week when I updated my Linux-next tree (NOT sure why I did NOT meet such issue when I did the patch), so I resent the patch series of adding head file "io.h" to fix this issue, please apply below V2 patch series instead, sorry for the inconvenience.
> 
> https://patchwork.kernel.org/patch/10944681/

Okay, fixed.  Sorry for the breakage, Stephen.

Shawn

> > -----Original Message-----
> > From: Stephen Rothwell [mailto:sfr@canb.auug.org.au]
> > Sent: Tuesday, May 21, 2019 6:38 AM
> > To: Shawn Guo <shawnguo@kernel.org>
> > Cc: Linux Next Mailing List <linux-next@vger.kernel.org>; Linux Kernel Mailing
> > List <linux-kernel@vger.kernel.org>; Anson Huang <anson.huang@nxp.com>;
> > Aisheng Dong <aisheng.dong@nxp.com>
> > Subject: linux-next: build failure after merge of the imx-mxs tree
> > 
> > Hi Shawn,
> > 
> > After merging the imx-mxs tree, today's linux-next build (arm
> > multi_v7_defconfig) failed like this:
> > 
> > drivers/clk/imx/clk.c: In function 'imx_mmdc_mask_handshake':
> > drivers/clk/imx/clk.c:20:8: error: implicit declaration of function
> > 'readl_relaxed'; did you mean 'xchg_relaxed'? [-Werror=implicit-function-
> > declaration]
> >   reg = readl_relaxed(ccm_base + CCM_CCDR);
> >         ^~~~~~~~~~~~~
> >         xchg_relaxed
> > drivers/clk/imx/clk.c:22:2: error: implicit declaration of function
> > 'writel_relaxed'; did you mean 'xchg_relaxed'? [-Werror=implicit-function-
> > declaration]
> >   writel_relaxed(reg, ccm_base + CCM_CCDR);
> >   ^~~~~~~~~~~~~~
> >   xchg_relaxed
> > 
> > Caused by commit
> > 
> >   0dc6b492b6e0 ("clk: imx: Add common API for masking MMDC handshake")
> > 
> > I have used the imx-mxs tree from next-20190520 for today.
> > 
> > --
> > Cheers,
> > Stephen Rothwell

linux-next: build failure after merge of the imx-mxs tree

[Stephen Rothwell]

[-- Attachment #1: Type: text/plain, Size: 459 bytes --]

Hi all,

After merging the imx-mxs tree, today's linux-next build (arm
multi_v7_defconfig) failed like this:

arch/arm/boot/dts/imx7d-zii-rpu2.dts:46.12-50.4: Warning (io_channels_property): /iio-hwmon: Missing property '#io-channel-cells' in node /soc/aips-bus@30400000/adc@30610000 or bad phandle (referred from io-channels[0])

Caused by commit

  69ab5392f517 ("ARM: dts: Add support for ZII i.MX7 RPU2 board")

-- 
Cheers,
Stephen Rothwell

[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 488 bytes --]

Re: linux-next: build failure after merge of the imx-mxs tree

[Fabio Estevam]

On Mon, Apr 22, 2019 at 7:45 PM Stephen Rothwell <sfr@canb.auug.org.au> wrote:
>
> Hi all,
>
> After merging the imx-mxs tree, today's linux-next build (arm
> multi_v7_defconfig) failed like this:
>
> arch/arm/boot/dts/imx7d-zii-rpu2.dts:46.12-50.4: Warning (io_channels_property): /iio-hwmon: Missing property '#io-channel-cells' in node /soc/aips-bus@30400000/adc@30610000 or bad phandle (referred from io-channels[0])
>
> Caused by commit
>
>   69ab5392f517 ("ARM: dts: Add support for ZII i.MX7 RPU2 board")

Andrey has submitted a fix for this issue:
https://lkml.org/lkml/2019/4/14/168

Re: linux-next: build failure after merge of the imx-mxs tree

[Shawn Guo]

Hi Stephen,

On Tue, Apr 23, 2019 at 08:45:01AM +1000, Stephen Rothwell wrote:
> Hi all,
> 
> After merging the imx-mxs tree, today's linux-next build (arm
> multi_v7_defconfig) failed like this:
> 
> arch/arm/boot/dts/imx7d-zii-rpu2.dts:46.12-50.4: Warning (io_channels_property): /iio-hwmon: Missing property '#io-channel-cells' in node /soc/aips-bus@30400000/adc@30610000 or bad phandle (referred from io-channels[0])
> 
> Caused by commit
> 
>   69ab5392f517 ("ARM: dts: Add support for ZII i.MX7 RPU2 board")

Fixed.  Thanks for reporting.

Shawn

linux-next: build failure after merge of the imx-mxs tree

[Stephen Rothwell]

[-- Attachment #1: Type: text/plain, Size: 569 bytes --]

Hi Shawn,

After merging the imx-mxs tree, today's linux-next build (arm
multi_v7_defconfig) failed like this:

arch/arm/boot/dts/vfxxx.dtsi:550.24-563.6: Warning (spi_bus_bridge): /soc/aips-bus@40080000/spi@400ad000: incorrect #address-cells for SPI bus
  also defined at arch/arm/boot/dts/vf610-bk4.dts:130.8-142.3
arch/arm/boot/dts/vf610-bk4.dtb: Warning (spi_bus_reg): Failed prerequisite 'spi_bus_bridge'


Caused by commit

  cf91ce9696a0 ("ARM: dts: vf610-bk4: Provide support for reading ID code from MVB device")

-- 
Cheers,
Stephen Rothwell

[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 488 bytes --]

Re: linux-next: build failure after merge of the imx-mxs tree

[Stephen Rothwell]

[-- Attachment #1: Type: text/plain, Size: 718 bytes --]

Hi all,

On Fri, 11 Jan 2019 09:30:03 +1100 Stephen Rothwell <sfr@canb.auug.org.au> wrote:
>
> After merging the imx-mxs tree, today's linux-next build (arm
> multi_v7_defconfig) failed like this:

Actually this is only treated as a warning.

> arch/arm/boot/dts/vfxxx.dtsi:550.24-563.6: Warning (spi_bus_bridge): /soc/aips-bus@40080000/spi@400ad000: incorrect #address-cells for SPI bus
>   also defined at arch/arm/boot/dts/vf610-bk4.dts:130.8-142.3
> arch/arm/boot/dts/vf610-bk4.dtb: Warning (spi_bus_reg): Failed prerequisite 'spi_bus_bridge'
> 
> 
> Caused by commit
> 
>   cf91ce9696a0 ("ARM: dts: vf610-bk4: Provide support for reading ID code from MVB device")
-- 
Cheers,
Stephen Rothwell

[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 488 bytes --]

Re: linux-next: build failure after merge of the imx-mxs tree

[Lukasz Majewski]

[-- Attachment #1: Type: text/plain, Size: 1088 bytes --]

Hi Stephen,

> Hi all,
> 
> On Fri, 11 Jan 2019 09:30:03 +1100 Stephen Rothwell
> <sfr@canb.auug.org.au> wrote:
> >
> > After merging the imx-mxs tree, today's linux-next build (arm
> > multi_v7_defconfig) failed like this:  
> 
> Actually this is only treated as a warning.

Thanks for the notification. I will look on that (soon).

> 
> > arch/arm/boot/dts/vfxxx.dtsi:550.24-563.6: Warning
> > (spi_bus_bridge): /soc/aips-bus@40080000/spi@400ad000: incorrect
> > #address-cells for SPI bus also defined at
> > arch/arm/boot/dts/vf610-bk4.dts:130.8-142.3
> > arch/arm/boot/dts/vf610-bk4.dtb: Warning (spi_bus_reg): Failed
> > prerequisite 'spi_bus_bridge'
> > 
> > 
> > Caused by commit
> > 
> >   cf91ce9696a0 ("ARM: dts: vf610-bk4: Provide support for reading
> > ID code from MVB device")  




Best regards,

Lukasz Majewski

--

DENX Software Engineering GmbH,      Managing Director: Wolfgang Denk
HRB 165235 Munich, Office: Kirchenstr.5, D-82194 Groebenzell, Germany
Phone: (+49)-8142-66989-59 Fax: (+49)-8142-66989-80 Email: lukma@denx.de

[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 488 bytes --]

Re: linux-next: build failure after merge of the imx-mxs tree

[Shawn Guo]

On Fri, Jan 11, 2019 at 12:15:59AM +0100, Lukasz Majewski wrote:
> Hi Stephen,
> 
> > Hi all,
> > 
> > On Fri, 11 Jan 2019 09:30:03 +1100 Stephen Rothwell
> > <sfr@canb.auug.org.au> wrote:
> > >
> > > After merging the imx-mxs tree, today's linux-next build (arm
> > > multi_v7_defconfig) failed like this:  
> > 
> > Actually this is only treated as a warning.

Thanks for reporting, Stephen.

> 
> Thanks for the notification. I will look on that (soon).

I just sent a fix for it.

https://patchwork.kernel.org/patch/10760827/

> 
> > 
> > > arch/arm/boot/dts/vfxxx.dtsi:550.24-563.6: Warning
> > > (spi_bus_bridge): /soc/aips-bus@40080000/spi@400ad000: incorrect
> > > #address-cells for SPI bus also defined at
> > > arch/arm/boot/dts/vf610-bk4.dts:130.8-142.3
> > > arch/arm/boot/dts/vf610-bk4.dtb: Warning (spi_bus_reg): Failed
> > > prerequisite 'spi_bus_bridge'
> > > 
> > > 
> > > Caused by commit
> > > 
> > >   cf91ce9696a0 ("ARM: dts: vf610-bk4: Provide support for reading
> > > ID code from MVB device")  

I found that the warning exists even on v5.0-rc1, so it's not caused by
Lukasz's change.

Shawn

linux-next: build failure after merge of the imx-mxs tree

[Stephen Rothwell]

[-- Attachment #1: Type: text/plain, Size: 1663 bytes --]

Hi Shawn,

After merging the imx-mxs tree, today's linux-next build (powerpc
allyesconfig) failed like this:

drivers/clocksource/timer-imx-gpt.c: In function 'mxc_clocksource_init':
drivers/clocksource/timer-imx-gpt.c:173:2: error: invalid use of undefined type 'struct delay_timer'
  imx_delay_timer.read_current_timer = &imx_read_current_timer;
  ^
drivers/clocksource/timer-imx-gpt.c:174:2: error: invalid use of undefined type 'struct delay_timer'
  imx_delay_timer.freq = c;
  ^
drivers/clocksource/timer-imx-gpt.c:175:2: error: implicit declaration of function 'register_current_timer_delay' [-Werror=implicit-function-declaration]
  register_current_timer_delay(&imx_delay_timer);
  ^
drivers/clocksource/timer-imx-gpt.c: In function 'mxc_timer_init':
drivers/clocksource/timer-imx-gpt.c:458:2: error: implicit declaration of function 'clk_get_sys' [-Werror=implicit-function-declaration]
  imxtm->clk_per = clk_get_sys("imx-gpt.0", "per");
  ^
drivers/clocksource/timer-imx-gpt.c:458:17: warning: assignment makes pointer from integer without a cast
  imxtm->clk_per = clk_get_sys("imx-gpt.0", "per");
                 ^
drivers/clocksource/timer-imx-gpt.c:459:17: warning: assignment makes pointer from integer without a cast
  imxtm->clk_ipg = clk_get_sys("imx-gpt.0", "ipg");
                 ^
drivers/clocksource/timer-imx-gpt.c:461:31: error: 'SZ_4K' undeclared (first use in this function)
  imxtm->base = ioremap(pbase, SZ_4K);
                               ^

I am not quite sure what caused this ... I have disabled the driver
again today.
-- 
Cheers,
Stephen Rothwell                    sfr@canb.auug.org.au

[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 819 bytes --]

linux-next: build failure after merge of the imx-mxs tree

[Stephen Rothwell]

[-- Attachment #1: Type: text/plain, Size: 1164 bytes --]

Hi Shawn,

After merging the imx-mxs tree, today's linux-next build (powerpc
allyesconfig) failed like this:


drivers/clocksource/timer-imx-gpt.c:37:27: fatal error: asm/mach/time.h: No such file or directory
 #include <asm/mach/time.h>
                           ^

Caused by commit 77b0235b6b5c ("ARM: imx: move timer driver into
drivers/clocksource").

I have marked it as BROKEN for now:

From: Stephen Rothwell <sfr@canb.auug.org.au>
Date: Fri, 29 May 2015 21:24:03 +1000
Subject: [PATCH] ARM: imx: mark CLKSRC_IMX_GPT as BROKEN for now

Signed-off-by: Stephen Rothwell <sfr@canb.auug.org.au>
---
 drivers/clocksource/Kconfig | 1 +
 1 file changed, 1 insertion(+)

diff --git a/drivers/clocksource/Kconfig b/drivers/clocksource/Kconfig
index 3c15a49fdac9..d8fedc925864 100644
--- a/drivers/clocksource/Kconfig
+++ b/drivers/clocksource/Kconfig
@@ -279,6 +279,7 @@ config CLKSRC_PXA
 config CLKSRC_IMX_GPT
 	bool "Clocksource using i.MX GPT" if COMPILE_TEST
 	depends on OF
+	depends on BROKEN
 	select CLKSRC_MMIO
 
 config H8300_TMR16
-- 
2.1.4

-- 
Cheers,
Stephen Rothwell                    sfr@canb.auug.org.au

[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 819 bytes --]

Re: linux-next: build failure after merge of the imx-mxs tree

[Shawn Guo]

Hi Stephen,

On Fri, May 29, 2015 at 09:28:59PM +1000, Stephen Rothwell wrote:
> Hi Shawn,
> 
> After merging the imx-mxs tree, today's linux-next build (powerpc
> allyesconfig) failed like this:
> 
> 
> drivers/clocksource/timer-imx-gpt.c:37:27: fatal error: asm/mach/time.h: No such file or directory
>  #include <asm/mach/time.h>
>                            ^
> 
> Caused by commit 77b0235b6b5c ("ARM: imx: move timer driver into
> drivers/clocksource").
> 
> I have marked it as BROKEN for now:

Thanks for the report.  I just sent a fix for it, and will get it into
my for-next branch soon.

Sorry for the breakage.

Shawn

> 
> From: Stephen Rothwell <sfr@canb.auug.org.au>
> Date: Fri, 29 May 2015 21:24:03 +1000
> Subject: [PATCH] ARM: imx: mark CLKSRC_IMX_GPT as BROKEN for now
> 
> Signed-off-by: Stephen Rothwell <sfr@canb.auug.org.au>
> ---
>  drivers/clocksource/Kconfig | 1 +
>  1 file changed, 1 insertion(+)
> 
> diff --git a/drivers/clocksource/Kconfig b/drivers/clocksource/Kconfig
> index 3c15a49fdac9..d8fedc925864 100644
> --- a/drivers/clocksource/Kconfig
> +++ b/drivers/clocksource/Kconfig
> @@ -279,6 +279,7 @@ config CLKSRC_PXA
>  config CLKSRC_IMX_GPT
>  	bool "Clocksource using i.MX GPT" if COMPILE_TEST
>  	depends on OF
> +	depends on BROKEN
>  	select CLKSRC_MMIO
>  
>  config H8300_TMR16
> -- 
> 2.1.4
> 
> -- 
> Cheers,
> Stephen Rothwell                    sfr@canb.auug.org.au