| Message ID | 1499853805-5915-4-git-send-email-chris.paterson2@renesas.com (mailing list archive) |
|---|---|
| State | Changes Requested |
| Commit | 44c6e5ceef305650bc120987513bdee8b924192b |
| Headers | show |
Hi Chris, On Wed, Jul 12, 2017 at 12:03 PM, Chris Paterson <chris.paterson2@renesas.com> wrote: > Define the iwg20m board dependent part of the MMCIF0 device node. > > Signed-off-by: Chris Paterson <chris.paterson2@renesas.com> > > diff --git a/arch/arm/boot/dts/r8a7743-iwg20m.dtsi b/arch/arm/boot/dts/r8a7743-iwg20m.dtsi > index 001ca91..ffce1b6 100644 > --- a/arch/arm/boot/dts/r8a7743-iwg20m.dtsi > +++ b/arch/arm/boot/dts/r8a7743-iwg20m.dtsi > +&pfc { > + mmcif0_pins: mmc { > + groups = "mmc_data8", "mmc_ctrl"; "mmc_data8" is not correct, as D6/D7 of the eMMC are not connected to GP6_28 resp. GP6_29, but to GP6_6 resp. GP6_7. So it should be "mmc_data8_b". Unfortunately the latter pin group isn't supported by the PFC driver yet. Cooking a patch... Gr{oetje,eeting}s, Geert -- Geert Uytterhoeven -- There's lots of Linux beyond ia32 -- geert@linux-m68k.org In personal conversations with technical people, I call myself a hacker. But when I'm talking to journalists I just say "programmer" or something like that. -- Linus Torvalds
Hi Chris,
[auto build test ERROR on renesas/next]
[also build test ERROR on next-20170712]
[cannot apply to v4.12]
[if your patch is applied to the wrong git tree, please drop us a note to help improve the system]
url: https://github.com/0day-ci/linux/commits/Chris-Paterson/Add-MMCIF0-support-for-r8a7743-iwg20m/20170713-042814
base: https://git.kernel.org/pub/scm/linux/kernel/git/horms/renesas.git next
config: arm-at91_dt_defconfig (attached as .config)
compiler: arm-linux-gnueabi-gcc (Debian 6.1.1-9) 6.1.1 20160705
reproduce:
wget https://raw.githubusercontent.com/01org/lkp-tests/master/sbin/make.cross -O ~/bin/make.cross
chmod +x ~/bin/make.cross
# save the attached .config to linux build tree
make.cross ARCH=arm
All errors (new ones prefixed by >>):
>> Error: arch/arm/boot/dts/r8a7743-iwg20m.dtsi:40.1-5 Label or path pfc not found
FATAL ERROR: Syntax error parsing input tree
---
0-DAY kernel test infrastructure Open Source Technology Center
https://lists.01.org/pipermail/kbuild-all Intel Corporation
On Thu, Jul 13, 2017 at 08:25:56AM +0800, kbuild test robot wrote: > Hi Chris, > > [auto build test ERROR on renesas/next] > [also build test ERROR on next-20170712] > [cannot apply to v4.12] > [if your patch is applied to the wrong git tree, please drop us a note to help improve the system] > > url: https://github.com/0day-ci/linux/commits/Chris-Paterson/Add-MMCIF0-support-for-r8a7743-iwg20m/20170713-042814 > base: https://git.kernel.org/pub/scm/linux/kernel/git/horms/renesas.git next > config: arm-at91_dt_defconfig (attached as .config) > compiler: arm-linux-gnueabi-gcc (Debian 6.1.1-9) 6.1.1 20160705 > reproduce: > wget https://raw.githubusercontent.com/01org/lkp-tests/master/sbin/make.cross -O ~/bin/make.cross > chmod +x ~/bin/make.cross > # save the attached .config to linux build tree > make.cross ARCH=arm > > All errors (new ones prefixed by >>): > > >> Error: arch/arm/boot/dts/r8a7743-iwg20m.dtsi:40.1-5 Label or path pfc not found > FATAL ERROR: Syntax error parsing input tree This seems to be a false positive. The node in question is present in the devel branch which is the base of these changes.
On Wed, Jul 12, 2017 at 01:52:49PM +0200, Geert Uytterhoeven wrote: > Hi Chris, > > On Wed, Jul 12, 2017 at 12:03 PM, Chris Paterson > <chris.paterson2@renesas.com> wrote: > > Define the iwg20m board dependent part of the MMCIF0 device node. > > > > Signed-off-by: Chris Paterson <chris.paterson2@renesas.com> > > > > diff --git a/arch/arm/boot/dts/r8a7743-iwg20m.dtsi b/arch/arm/boot/dts/r8a7743-iwg20m.dtsi > > index 001ca91..ffce1b6 100644 > > --- a/arch/arm/boot/dts/r8a7743-iwg20m.dtsi > > +++ b/arch/arm/boot/dts/r8a7743-iwg20m.dtsi > > > +&pfc { > > + mmcif0_pins: mmc { > > + groups = "mmc_data8", "mmc_ctrl"; > > "mmc_data8" is not correct, as D6/D7 of the eMMC are not connected to GP6_28 > resp. GP6_29, but to GP6_6 resp. GP6_7. > So it should be "mmc_data8_b". > > Unfortunately the latter pin group isn't supported by the PFC driver yet. > Cooking a patch... The above notwithstanding I have applied this patch for v4.14. This is under the assumption that: a) the relevant (pfc) driver changes will appear in v4.14 and; b) there is no regression introduced in having this change present without the driver changes An implication of the above is that the new feature will not work until both the driver and DTS changes are in the same tree. But that the trees with each of those changes continue to work at least as well as they did before. Please test the devel branch that I push later today to make sure there are no regressions.
On Thu, Jul 13, 2017 at 10:02:29AM +0200, Simon Horman wrote: > On Wed, Jul 12, 2017 at 01:52:49PM +0200, Geert Uytterhoeven wrote: > > Hi Chris, > > > > On Wed, Jul 12, 2017 at 12:03 PM, Chris Paterson > > <chris.paterson2@renesas.com> wrote: > > > Define the iwg20m board dependent part of the MMCIF0 device node. > > > > > > Signed-off-by: Chris Paterson <chris.paterson2@renesas.com> > > > > > > diff --git a/arch/arm/boot/dts/r8a7743-iwg20m.dtsi b/arch/arm/boot/dts/r8a7743-iwg20m.dtsi > > > index 001ca91..ffce1b6 100644 > > > --- a/arch/arm/boot/dts/r8a7743-iwg20m.dtsi > > > +++ b/arch/arm/boot/dts/r8a7743-iwg20m.dtsi > > > > > +&pfc { > > > + mmcif0_pins: mmc { > > > + groups = "mmc_data8", "mmc_ctrl"; > > > > "mmc_data8" is not correct, as D6/D7 of the eMMC are not connected to GP6_28 > > resp. GP6_29, but to GP6_6 resp. GP6_7. > > So it should be "mmc_data8_b". > > > > Unfortunately the latter pin group isn't supported by the PFC driver yet. > > Cooking a patch... > > The above notwithstanding I have applied this patch for v4.14. ... Sorry, I think I need more coffee. I misread Geert's comment above. I have dropped this patch. Please post a corrected v2 of this patch.
On 07/13, Simon Horman wrote: >On Thu, Jul 13, 2017 at 08:25:56AM +0800, kbuild test robot wrote: >> Hi Chris, >> >> [auto build test ERROR on renesas/next] >> [also build test ERROR on next-20170712] >> [cannot apply to v4.12] >> [if your patch is applied to the wrong git tree, please drop us a note to help improve the system] >> >> url: https://github.com/0day-ci/linux/commits/Chris-Paterson/Add-MMCIF0-support-for-r8a7743-iwg20m/20170713-042814 >> base: https://git.kernel.org/pub/scm/linux/kernel/git/horms/renesas.git next >> config: arm-at91_dt_defconfig (attached as .config) >> compiler: arm-linux-gnueabi-gcc (Debian 6.1.1-9) 6.1.1 20160705 >> reproduce: >> wget https://raw.githubusercontent.com/01org/lkp-tests/master/sbin/make.cross -O ~/bin/make.cross >> chmod +x ~/bin/make.cross >> # save the attached .config to linux build tree >> make.cross ARCH=arm >> >> All errors (new ones prefixed by >>): >> >> >> Error: arch/arm/boot/dts/r8a7743-iwg20m.dtsi:40.1-5 Label or path pfc not found >> FATAL ERROR: Syntax error parsing input tree > >This seems to be a false positive. The node in question is present in >the devel branch which is the base of these changes. Thanks for the feedback, we'll update 0day's configuration accordingly. Thanks, Xiaolong > > >_______________________________________________ >kbuild-all mailing list >kbuild-all@lists.01.org >https://lists.01.org/mailman/listinfo/kbuild-all
> From: Simon Horman [mailto:horms@verge.net.au] > Sent: 13 July 2017 09:12 > > On Thu, Jul 13, 2017 at 10:02:29AM +0200, Simon Horman wrote: > > On Wed, Jul 12, 2017 at 01:52:49PM +0200, Geert Uytterhoeven wrote: > > > Hi Chris, > > > > > > On Wed, Jul 12, 2017 at 12:03 PM, Chris Paterson > > > <chris.paterson2@renesas.com> wrote: > > > > Define the iwg20m board dependent part of the MMCIF0 device node. > > > > > > > > Signed-off-by: Chris Paterson <chris.paterson2@renesas.com> > > > > > > > > diff --git a/arch/arm/boot/dts/r8a7743-iwg20m.dtsi > > > > b/arch/arm/boot/dts/r8a7743-iwg20m.dtsi > > > > index 001ca91..ffce1b6 100644 > > > > --- a/arch/arm/boot/dts/r8a7743-iwg20m.dtsi > > > > +++ b/arch/arm/boot/dts/r8a7743-iwg20m.dtsi > > > > > > > +&pfc { > > > > + mmcif0_pins: mmc { > > > > + groups = "mmc_data8", "mmc_ctrl"; > > > > > > "mmc_data8" is not correct, as D6/D7 of the eMMC are not connected > > > to GP6_28 resp. GP6_29, but to GP6_6 resp. GP6_7. > > > So it should be "mmc_data8_b". > > > > > > Unfortunately the latter pin group isn't supported by the PFC driver yet. > > > Cooking a patch... Thanks for your review Geert. Sorry I missed this. > > > > The above notwithstanding I have applied this patch for v4.14. > > ... > > Sorry, I think I need more coffee. No worries! > > I misread Geert's comment above. I have dropped this patch. > Please post a corrected v2 of this patch. Will do.
diff --git a/arch/arm/boot/dts/r8a7743-iwg20m.dtsi b/arch/arm/boot/dts/r8a7743-iwg20m.dtsi index 001ca91..ffce1b6 100644 --- a/arch/arm/boot/dts/r8a7743-iwg20m.dtsi +++ b/arch/arm/boot/dts/r8a7743-iwg20m.dtsi @@ -22,8 +22,34 @@ device_type = "memory"; reg = <2 0x00000000 0 0x20000000>; }; + + reg_3p3v: 3p3v { + compatible = "regulator-fixed"; + regulator-name = "3P3V"; + regulator-min-microvolt = <3300000>; + regulator-max-microvolt = <3300000>; + regulator-always-on; + regulator-boot-on; + }; }; &extal_clk { clock-frequency = <20000000>; }; + +&pfc { + mmcif0_pins: mmc { + groups = "mmc_data8", "mmc_ctrl"; + function = "mmc"; + }; +}; + +&mmcif0 { + pinctrl-0 = <&mmcif0_pins>; + pinctrl-names = "default"; + + vmmc-supply = <®_3p3v>; + bus-width = <8>; + non-removable; + status = "okay"; +};
Define the iwg20m board dependent part of the MMCIF0 device node. Signed-off-by: Chris Paterson <chris.paterson2@renesas.com>