> What I'm saying is that in that scenario it should not be necessary to edit the > kernel to invent new SoC types, and then teach it that Tegra4 is mostly the > same as Tegra3. That information should all be encoded into the DT rather > than the C code in the kernel. > > So, I think adding this SoC type stuff is the wrong approach to the problem. What ends up happening in practice for a lot of hw blocks inside the SoC, is that tegra4 is mostly the same as tegra3 with a few new registers and bug fixes that slightly change the programming model. So either we have to add device quirks to teach device tree about the differences, and pass those in as flags to the driver, or we can do SoC detection at runtime in the driver. It sounds like the consensus from you and Olof is that the first is preferable. -Allen -- 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
