| Message ID | 1524230914-10175-8-git-send-email-geert+renesas@glider.be |
|---|---|
| State | Not Applicable, archived |
| Delegated to: | David Miller |
| Headers | show |
| Series | arm: renesas: Change platform dependency to ARCH_RENESAS | expand |
On Fri, Apr 20, 2018 at 03:28:33PM +0200, Geert Uytterhoeven wrote: > All drivers for Renesas ARM SoCs have gained proper ARCH_RENESAS > platform dependencies. Hence finish the conversion from ARCH_SHMOBILE > to ARCH_RENESAS for Renesas 32-bit ARM SoCs, as started by commit > 9b5ba0df4ea4f940 ("ARM: shmobile: Introduce ARCH_RENESAS"). > > Signed-off-by: Geert Uytterhoeven <geert+renesas@glider.be> > --- > This depends on the previous patches in this series, hence the RFC. > > JFTR, after this, the following symbols for drivers supporting only > Renesas SuperH "SH-Mobile" SoCs can no longer be selected: > - CONFIG_KEYBOARD_SH_KEYSC, > - CONFIG_VIDEO_SH_VOU, > - CONFIG_VIDEO_SH_MOBILE_CEU, > - CONFIG_DRM_SHMOBILE[*], > - CONFIG_FB_SH_MOBILE_MERAM. > (changes for a shmobile_defconfig .config) > > [*] CONFIG_DRM_SHMOBILE has a dependency on ARM, but it was never wired > up. From the use of sh_mobile_meram, I guess it was meant for > SH-Mobile AP4 on Mackerel or AP4EVB, which are long gone. > So the only remaining upstream platforms that could make use of it > are legacy SuperH SH-Mobile SoCs? That sounds about right. If there is interest I can sift through my mail archive and see if it yields any answers.
On Fri, Apr 20, 2018 at 03:28:33PM +0200, Geert Uytterhoeven wrote: > All drivers for Renesas ARM SoCs have gained proper ARCH_RENESAS > platform dependencies. Hence finish the conversion from ARCH_SHMOBILE > to ARCH_RENESAS for Renesas 32-bit ARM SoCs, as started by commit > 9b5ba0df4ea4f940 ("ARM: shmobile: Introduce ARCH_RENESAS"). > > Signed-off-by: Geert Uytterhoeven <geert+renesas@glider.be> > --- > This depends on the previous patches in this series, hence the RFC. Thanks, I have marked this and the following patch as deferred. Please repost or otherwise ping me once the dependencies are in place.
diff --git a/arch/arm/mach-shmobile/Kconfig b/arch/arm/mach-shmobile/Kconfig index 96672da02f5f17b9..d892c5b52b6f5627 100644 --- a/arch/arm/mach-shmobile/Kconfig +++ b/arch/arm/mach-shmobile/Kconfig @@ -1,6 +1,3 @@ -config ARCH_SHMOBILE - bool - config PM_RMOBILE bool select PM @@ -30,7 +27,6 @@ menuconfig ARCH_RENESAS bool "Renesas ARM SoCs" depends on ARCH_MULTI_V7 && MMU select ARCH_DMA_ADDR_T_64BIT if ARM_LPAE - select ARCH_SHMOBILE select ARM_GIC select GPIOLIB select HAVE_ARM_SCU if SMP
All drivers for Renesas ARM SoCs have gained proper ARCH_RENESAS platform dependencies. Hence finish the conversion from ARCH_SHMOBILE to ARCH_RENESAS for Renesas 32-bit ARM SoCs, as started by commit 9b5ba0df4ea4f940 ("ARM: shmobile: Introduce ARCH_RENESAS"). Signed-off-by: Geert Uytterhoeven <geert+renesas@glider.be> --- This depends on the previous patches in this series, hence the RFC. JFTR, after this, the following symbols for drivers supporting only Renesas SuperH "SH-Mobile" SoCs can no longer be selected: - CONFIG_KEYBOARD_SH_KEYSC, - CONFIG_VIDEO_SH_VOU, - CONFIG_VIDEO_SH_MOBILE_CEU, - CONFIG_DRM_SHMOBILE[*], - CONFIG_FB_SH_MOBILE_MERAM. (changes for a shmobile_defconfig .config) [*] CONFIG_DRM_SHMOBILE has a dependency on ARM, but it was never wired up. From the use of sh_mobile_meram, I guess it was meant for SH-Mobile AP4 on Mackerel or AP4EVB, which are long gone. So the only remaining upstream platforms that could make use of it are legacy SuperH SH-Mobile SoCs? --- arch/arm/mach-shmobile/Kconfig | 4 ---- 1 file changed, 4 deletions(-)