Message ID | 20150126012401.GA8229@verge.net.au (mailing list archive) |
---|---|
State | Superseded |
Delegated to: | Simon Horman |
Headers | show |
On Mon, Jan 26, 2015 at 10:24:04AM +0900, Simon Horman wrote: > Hi Geert, Hi Morimoto-san, > > I believe this problem is present in renesas-next-20150122-v3.19-rc1, > but not in renesas-devel-20150123-v3.19-rc5 due to the presence there of > the following in the latter: > > >From Magnus Damm <damm+renesas@opensource.se> > > ARM: shmobile: sh73a0: Add Multiplatform support > > Enable sh73a0 Multiplatform support for the generic sh73a0 > machine vector. No board support is enabled, and the board > code for KZM9G DT Reference is left by itself. > > Signed-off-by: Magnus Damm <damm+renesas@opensource.se> > Signed-off-by: Geert Uytterhoeven <geert+renesas@glider.be> > Signed-off-by: Simon Horman <horms+renesas@verge.net.au> > > diff --git a/arch/arm/mach-shmobile/Kconfig b/arch/arm/mach-shmobile/Kconfig > index 2f36c85..8ee2f28 100644 > --- a/arch/arm/mach-shmobile/Kconfig > +++ b/arch/arm/mach-shmobile/Kconfig > @@ -78,6 +78,11 @@ config ARCH_R8A7794 > bool "R-Car E2 (R8A77940)" > select ARCH_RCAR_GEN2 > > +config ARCH_SH73A0 > + bool "SH-Mobile AG5 (R8A73A00)" > + select ARCH_RMOBILE > + select RENESAS_INTC_IRQPIN > + > comment "Renesas ARM SoCs Board Type" > > config MACH_MARZEN > [patch truncated] > > > It may have been better if the defconfig problem that Morimoto-san > mentions below had not gone into next for v3.20 while the change above > ended up being deferred for v3.21. But that is how things have > played out. And the result seems to be that Morimoto-san's patch > will resolve a regression that has been queued up for v3.20. > > With the above in mind I plan to queue up the change below > as a fix for v3.20. As I would like to treat this as a fix I have made a more minimal version of Morimoto-san's patch. I have also updated the changelog to supply a bit more information. I will post the result as "[PATCH] ARM: shmobile: Select CONFIG_REGULATOR in defconfig once again". -- To unsubscribe from this list: send the line "unsubscribe linux-sh" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html
Hi Simon > I believe this problem is present in renesas-next-20150122-v3.19-rc1, > but not in renesas-devel-20150123-v3.19-rc5 due to the presence there of > the following in the latter: (snip) > It may have been better if the defconfig problem that Morimoto-san > mentions below had not gone into next for v3.20 while the change above > ended up being deferred for v3.21. But that is how things have > played out. And the result seems to be that Morimoto-san's patch > will resolve a regression that has been queued up for v3.20. > > With the above in mind I plan to queue up the change below > as a fix for v3.20. Thank you for your help. My patch is including below, because "make savedefconfig" did it -CONFIG_ARCH_SH73A0=y -CONFIG_SIMPLE_PM_BUS=y -CONFIG_RCAR_DMAC=y But, if these are based on merged branch (= Geert mentioned to it), I think I should send v2 (which includes REGURALOR only), otherwise, it will create other issues. My patch was based on renesas-devel-20150122-v3.19-rc5. but, can you show me best branch/tag for this issue ? Best regards --- Kuninori Morimoto -- To unsubscribe from this list: send the line "unsubscribe linux-sh" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html
On Mon, Jan 26, 2015 at 02:28:26AM +0000, Kuninori Morimoto wrote: > > Hi Simon > > > I believe this problem is present in renesas-next-20150122-v3.19-rc1, > > but not in renesas-devel-20150123-v3.19-rc5 due to the presence there of > > the following in the latter: > (snip) > > It may have been better if the defconfig problem that Morimoto-san > > mentions below had not gone into next for v3.20 while the change above > > ended up being deferred for v3.21. But that is how things have > > played out. And the result seems to be that Morimoto-san's patch > > will resolve a regression that has been queued up for v3.20. > > > > With the above in mind I plan to queue up the change below > > as a fix for v3.20. > > Thank you for your help. > My patch is including below, because "make savedefconfig" did it > > -CONFIG_ARCH_SH73A0=y > -CONFIG_SIMPLE_PM_BUS=y > -CONFIG_RCAR_DMAC=y > > But, if these are based on merged branch (= Geert mentioned to it), > I think I should send v2 (which includes REGURALOR only), > otherwise, it will create other issues. > > My patch was based on renesas-devel-20150122-v3.19-rc5. > but, can you show me best branch/tag for this issue ? renesas-next-20150122-v3.19-rc1 The config items above would probably also be removed by savedefconfig in renesas-next-20150122-v3.19-rc1 too. However, I think a minimal approach is best for a fix: just removing REGURALOR as you suggest. As you (now) know I have sent a patch to do that, which I suppose crossed in-flight with your email. -- To unsubscribe from this list: send the line "unsubscribe linux-sh" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html
diff --git a/arch/arm/mach-shmobile/Kconfig b/arch/arm/mach-shmobile/Kconfig index 2f36c85..8ee2f28 100644 --- a/arch/arm/mach-shmobile/Kconfig +++ b/arch/arm/mach-shmobile/Kconfig @@ -78,6 +78,11 @@ config ARCH_R8A7794 bool "R-Car E2 (R8A77940)" select ARCH_RCAR_GEN2 +config ARCH_SH73A0 + bool "SH-Mobile AG5 (R8A73A00)" + select ARCH_RMOBILE + select RENESAS_INTC_IRQPIN + comment "Renesas ARM SoCs Board Type" config MACH_MARZEN