On 07/18/2013 03:58 AM, Mark Brown wrote: > On Wed, Jul 17, 2013 at 04:52:42PM -0600, Stephen Warren wrote: > >> The key to enable tegra30_i2s.c should really be >> ARCH_TEGRA_3x_SOC || ARCH_TEGRA_114_SOC, which gets a bit >> unwieldy once you have, say, 4 different SoCs in that list and a >> similar list starts to apply to a lot of different >> HW-modules/drivers. Even creating an ARCH_TEGRA_30_OR_LATER_SOC >> will get problematic, since defining "or later" will likely >> become progressively more complex over time, as we start putting >> our more SoCs. What are your thoughts on the best way to solve >> that? > > Can't you just say Tegra 20 or later is Tegra 20 plus Tegra 30 or > later and so on? For the chips that are supported upstream right now, that would work. However, I'm not sure that life will be quite so linear in the future. In other words, what is "or later" for, say, the SDHCI controller may not be the same as what is "or later" for, say, the I2C controller. (feel free to substitute arbitrary HW modules into that statement). -- To unsubscribe from this list: send the line "unsubscribe linux-tegra" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
