Re: [PATCHv2] ARM: Push selects for TWD/SCU into machine entries
On Tuesday 09 April 2013, Arnd Bergmann wrote: > I've applied it to the next/soc branch now. > I just made up my mind again after I got a few merge conflicts. I have added it to the next/multiplatform branch now instead of next/soc, since a few of the Kconfig entries changed in this patch are moved to other files in that branch. I've also added an entry for mach-zynq, which has gained SMP support in the meantime. I assume it uses TWD/SCU as it is otherwise rather close to the ARM reference platforms. Arnd -- 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/
Re: [PATCHv2] ARM: Push selects for TWD/SCU into machine entries
On Tuesday 09 April 2013, Stephen Boyd wrote: > >>> > >>> Sneaking it in through the fixes branch would make life easier for us, > >>> but it doesn't feel right. > >> Arnd, can you pick this up into the arm-soc tree now? It would be good > >> to get this into next so that conflicts are avoided later on. > >> > > Arnd? > > > > Ping? Sorry for the long delay, you scrolled down from my unread emails twice. Three tips for you to make it more likely to get a fast reaction time: * Send the original patch to Olof and me, not just the reply to the on-list patch. * Use the a...@kernel.org alias to reach us, since that will make the email go into the right folder * Use the [GIT PULL] keyword in the subject line, ideally sending a pull request as well, instead of a separate email. While we do apply emails, It's often batch processing to apply everything and then we scan for emails that have PULL in the subject, while others can get lost. I've applied it to the next/soc branch now. Arnd -- 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/
Re: [PATCHv2] ARM: Push selects for TWD/SCU into machine entries
On 03/26/13 10:34, Stephen Boyd wrote: > On 03/16/13 12:32, Stephen Boyd wrote: >> On 3/5/2013 2:34 PM, Arnd Bergmann wrote: >>> On Tuesday 05 March 2013, Stephen Boyd wrote: On 02/27/13 15:43, Stephen Warren wrote: > Seems simple enough it doesn't really need many, but for Tegra, > Acked-by: Stephen Warren > > Which kernel is this going into? It's possible Tegra will get converted > to multi-platform in 3.10, which might move that main ARCH_TEGRA block > from arch/arm/Kconfig into arch/arm/mach-tegra/Kconfig, although I > suppose it doesn't have to move it. I think some/all(?) other > multi-platform conversions have moved their main Kconfig option like > that though. Thanks. I'm hoping that Arnd/Olof can pick this up. I'm not sure which version it will go into. >>> Hmm, it certainly looks useful to me. I think it should go into the next >>> cleanup branch as a base, so others can build on top of it. We will >>> also need it for the Exynos multiplatform patches that I hope can land >>> in 3.10 as well. >>> >>> Sneaking it in through the fixes branch would make life easier for us, >>> but it doesn't feel right. >> Arnd, can you pick this up into the arm-soc tree now? It would be good >> to get this into next so that conflicts are avoided later on. >> > Arnd? > Ping? -- Qualcomm Innovation Center, Inc. is a member of Code Aurora Forum, hosted by The Linux Foundation -- 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/
Re: [PATCHv2] ARM: Push selects for TWD/SCU into machine entries
On 03/16/13 12:32, Stephen Boyd wrote: > On 3/5/2013 2:34 PM, Arnd Bergmann wrote: >> On Tuesday 05 March 2013, Stephen Boyd wrote: >>> On 02/27/13 15:43, Stephen Warren wrote: Seems simple enough it doesn't really need many, but for Tegra, Acked-by: Stephen Warren Which kernel is this going into? It's possible Tegra will get converted to multi-platform in 3.10, which might move that main ARCH_TEGRA block from arch/arm/Kconfig into arch/arm/mach-tegra/Kconfig, although I suppose it doesn't have to move it. I think some/all(?) other multi-platform conversions have moved their main Kconfig option like that though. >>> Thanks. I'm hoping that Arnd/Olof can pick this up. I'm not sure which >>> version it will go into. >>> >> Hmm, it certainly looks useful to me. I think it should go into the next >> cleanup branch as a base, so others can build on top of it. We will >> also need it for the Exynos multiplatform patches that I hope can land >> in 3.10 as well. >> >> Sneaking it in through the fixes branch would make life easier for us, >> but it doesn't feel right. > Arnd, can you pick this up into the arm-soc tree now? It would be good > to get this into next so that conflicts are avoided later on. > Arnd? -- Qualcomm Innovation Center, Inc. is a member of Code Aurora Forum, hosted by The Linux Foundation -- 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/
Re: [PATCHv2] ARM: Push selects for TWD/SCU into machine entries
On 3/5/2013 2:34 PM, Arnd Bergmann wrote: > On Tuesday 05 March 2013, Stephen Boyd wrote: >> On 02/27/13 15:43, Stephen Warren wrote: >>> Seems simple enough it doesn't really need many, but for Tegra, >>> Acked-by: Stephen Warren >>> >>> Which kernel is this going into? It's possible Tegra will get converted >>> to multi-platform in 3.10, which might move that main ARCH_TEGRA block >>> from arch/arm/Kconfig into arch/arm/mach-tegra/Kconfig, although I >>> suppose it doesn't have to move it. I think some/all(?) other >>> multi-platform conversions have moved their main Kconfig option like >>> that though. >> Thanks. I'm hoping that Arnd/Olof can pick this up. I'm not sure which >> version it will go into. >> > Hmm, it certainly looks useful to me. I think it should go into the next > cleanup branch as a base, so others can build on top of it. We will > also need it for the Exynos multiplatform patches that I hope can land > in 3.10 as well. > > Sneaking it in through the fixes branch would make life easier for us, > but it doesn't feel right. Arnd, can you pick this up into the arm-soc tree now? It would be good to get this into next so that conflicts are avoided later on. -- Qualcomm Innovation Center, Inc. is a member of Code Aurora Forum, hosted by The Linux Foundation -- 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/
Re: [PATCHv2] ARM: Push selects for TWD/SCU into machine entries
On Tuesday 05 March 2013, Stephen Boyd wrote: > On 02/27/13 15:43, Stephen Warren wrote: > > > > Seems simple enough it doesn't really need many, but for Tegra, > > Acked-by: Stephen Warren > > > > Which kernel is this going into? It's possible Tegra will get converted > > to multi-platform in 3.10, which might move that main ARCH_TEGRA block > > from arch/arm/Kconfig into arch/arm/mach-tegra/Kconfig, although I > > suppose it doesn't have to move it. I think some/all(?) other > > multi-platform conversions have moved their main Kconfig option like > > that though. > > Thanks. I'm hoping that Arnd/Olof can pick this up. I'm not sure which > version it will go into. > Hmm, it certainly looks useful to me. I think it should go into the next cleanup branch as a base, so others can build on top of it. We will also need it for the Exynos multiplatform patches that I hope can land in 3.10 as well. Sneaking it in through the fixes branch would make life easier for us, but it doesn't feel right. Arnd -- 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/
Re: [PATCHv2] ARM: Push selects for TWD/SCU into machine entries
On 02/27/13 15:43, Stephen Warren wrote: > > Seems simple enough it doesn't really need many, but for Tegra, > Acked-by: Stephen Warren > > Which kernel is this going into? It's possible Tegra will get converted > to multi-platform in 3.10, which might move that main ARCH_TEGRA block > from arch/arm/Kconfig into arch/arm/mach-tegra/Kconfig, although I > suppose it doesn't /have/ to move it. I think some/all(?) other > multi-platform conversions have moved their main Kconfig option like > that though. Thanks. I'm hoping that Arnd/Olof can pick this up. I'm not sure which version it will go into. -- Qualcomm Innovation Center, Inc. is a member of Code Aurora Forum, hosted by The Linux Foundation -- 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/
Re: [PATCHv2] ARM: Push selects for TWD/SCU into machine entries
On 02/27/2013 04:28 PM, Stephen Boyd wrote: > The TWD and SCU configs are selected by default as long as > MSM_SCORPIONMP is false and/or MCT is false. Implementing the > logic this way certainly saves lines in the Kconfig but it > precludes those machines which select MSM_SCORPIONMP or MCT from > participating in the single zImage effort because when those > machines are combined with other SMP capable machines the TWD and > SCU are no longer selected by default. > > Push the select out to the machine entries so that we can compile > these machines together and still select the appropriate configs. > Resending to collect some more acks. Seems simple enough it doesn't really need many, but for Tegra, Acked-by: Stephen Warren Which kernel is this going into? It's possible Tegra will get converted to multi-platform in 3.10, which might move that main ARCH_TEGRA block from arch/arm/Kconfig into arch/arm/mach-tegra/Kconfig, although I suppose it doesn't /have/ to move it. I think some/all(?) other multi-platform conversions have moved their main Kconfig option like that though. -- 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/
Re: [PATCHv2] ARM: Push selects for TWD/SCU into machine entries
On Wed, Oct 24, 2012 at 10:24:35AM -0700, Stephen Boyd wrote: > The TWD and SCU configs are selected by default as long as > MSM_SCORPIONMP is false and/or MCT is false. Implementing the > logic this way certainly saves lines in the Kconfig but it > precludes those machines which select MSM_SCORPIONMP or MCT from > participating in the single zImage effort because when those > machines are combined with other SMP capable machines the TWD and > SCU are no longer selected by default. > > Push the select out to the machine entries so that we can compile > these machines together and still select the appropriate configs. > arch/arm/mach-msm/Kconfig | 7 ++- Acked-by: David Brown -- The Qualcomm Innovation Center, Inc. is a member of the Code Aurora Forum, hosted by The Linux Foundation -- 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/
Re: [PATCHv2] ARM: Push selects for TWD/SCU into machine entries
On 10/24/12 10:54, Stephen Warren wrote: > Where will this patch be merged? > > It probably won't happen for 3.8, but that config fragment will move to > arch/arm/mach-tegra/Kconfig when Tegra enables single zImage support, I > believe. So, it'd be good to make sure this patch gets merged somewhere > that could be used as a baseline for other arm-soc branches if needed, > to avoid merge conflicts. I was hoping this could go through the arm-soc tree for the 3.8 merge window. -- Qualcomm Innovation Center, Inc. is a member of Code Aurora Forum, hosted by The Linux Foundation -- 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/
Re: [PATCHv2] ARM: Push selects for TWD/SCU into machine entries
On 10/24/2012 11:24 AM, Stephen Boyd wrote: > The TWD and SCU configs are selected by default as long as > MSM_SCORPIONMP is false and/or MCT is false. Implementing the > logic this way certainly saves lines in the Kconfig but it > precludes those machines which select MSM_SCORPIONMP or MCT from > participating in the single zImage effort because when those > machines are combined with other SMP capable machines the TWD and > SCU are no longer selected by default. > > Push the select out to the machine entries so that we can compile > these machines together and still select the appropriate configs. Acked-by: Stephen Warren > diff --git a/arch/arm/Kconfig b/arch/arm/Kconfig > @@ -633,6 +633,8 @@ config ARCH_TEGRA > select GENERIC_GPIO > select HAVE_CLK > select HAVE_SMP > + select HAVE_ARM_SCU if SMP > + select HAVE_ARM_TWD if LOCAL_TIMERS > select MIGHT_HAVE_CACHE_L2X0 > select SPARSE_IRQ > select USE_OF Where will this patch be merged? It probably won't happen for 3.8, but that config fragment will move to arch/arm/mach-tegra/Kconfig when Tegra enables single zImage support, I believe. So, it'd be good to make sure this patch gets merged somewhere that could be used as a baseline for other arm-soc branches if needed, to avoid merge conflicts. -- 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/
