Re: linux-next: build failure after merge of the imx-mxs tree
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
Re: linux-next: build failure after merge of the imx-mxs tree
On Tue, May 21, 2019 at 02:16:47AM +, 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:s...@canb.auug.org.au]
> > Sent: Tuesday, May 21, 2019 6:38 AM
> > To: Shawn Guo
> > Cc: Linux Next Mailing List ; Linux Kernel
> > Mailing
> > List ; Anson Huang ;
> > Aisheng Dong
> > 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
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:s...@canb.auug.org.au]
> Sent: Tuesday, May 21, 2019 6:38 AM
> To: Shawn Guo
> Cc: Linux Next Mailing List ; Linux Kernel Mailing
> List ; Anson Huang ;
> Aisheng Dong
> 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
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@3040/adc@3061 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
Re: linux-next: build failure after merge of the imx-mxs tree
On Mon, Apr 22, 2019 at 7:45 PM 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@3040/adc@3061 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
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
> > 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@4008/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
Re: linux-next: build failure after merge of the imx-mxs tree
Hi Stephen,
> Hi all,
>
> On Fri, 11 Jan 2019 09:30:03 +1100 Stephen Rothwell
> 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@4008/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: lu...@denx.de
pgpgavcO_OAFi.pgp
Description: OpenPGP digital signature
Re: linux-next: build failure after merge of the imx-mxs tree
Hi all,
On Fri, 11 Jan 2019 09:30:03 +1100 Stephen Rothwell
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@4008/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
pgpP6O0S3QvNQ.pgp
Description: OpenPGP digital signature
Re: linux-next: build failure after merge of the imx-mxs tree
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
>^
>
> 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
> 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
> ---
> 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 Rothwells...@canb.auug.org.au
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majord...@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
