On Mon, Mar 28, 2016 at 09:16:51AM -0400, Rich Felker wrote: > On Wed, Mar 02, 2016 at 09:25:54AM +0100, Geert Uytterhoeven wrote: > > Hi Simon, > > > > On Wed, Mar 2, 2016 at 2:43 AM, Simon Horman <[email protected]> > > wrote: > > > Make use of ARCH_RENESAS in place of ARCH_SHMOBILE. > > > > > > This is part of an ongoing process to migrate from ARCH_SHMOBILE to > > > ARCH_RENESAS the motivation for which being that RENESAS seems to be a > > > more > > > appropriate name than SHMOBILE for the majority of Renesas ARM based SoCs. > > > > > > ARCH_RENESAS should cover all cases where both CONFIG_OF and > > > ARCH_SHMOBILE are enabled. > > > > > > Signed-off-by: Simon Horman <[email protected]> > > > > Acked-by: Geert Uytterhoeven <[email protected]> > > > > If you intend to drop ARCH_SHMOBILE from arch/arm/mach-shmobile/Kconfig > > before > > dropping the whole "if (...) { ... }" block below" (cfr. "drivers: sh: Stop > > using the legacy clock domain on ARM", > > http://www.spinics.net/lists/linux-renesas-soc/msg00869.html). > > > > Note that the SH-people may resurrect (a variant of) the block when they > > start > > migrating to DT and CCF. > > I can't say for sure at this point, but I think instead of searching > for a node by compatible I would want to represent the relationship > between the nodes semantically in the device tree. We can address that > when we get there, though. If we're stuck with device-provided device > trees that don't fully represent the relationships we might have to > keep kludges for searching.
Thanks for the feedback. At this point I think it would be best to drop the block in question. It should not be difficult to add it back if and when it is needed again.
