On 12/07/18 14:50, Mikko Perttunen wrote:
On 07/12/2018 04:36 PM, Ben Dooks wrote:Hello, we are looking at up-streaming some of the work we have done on the tegra2 and tegra3 automotive devices. The automotive grade devices are close the commercial parts so we would like to discuss the core changes before submitting. The changes are mostly with things like the clock setup and a few peripheral quirks (IIRC these are mostly MMC). We are proposing to change the device-tree properties for the root node and any other affected devices from "nvidia,tegraXX" to a new "nvidia,tegraXXa". We would welcome discussion on whether to update all the devices at the start An example of tegra30a.dtsi: #include "tegra30.dtsi" / { compatible = "nvidia,tegra30a"; clock@60006000 { compatible = "nvidia,tegra30a-car"; }; } We don't think the changes are big enough to warrant their own Kconfig/defconfig updates.What kind of changes do you have? Tegra30a would point to a separate SoC revision of Tegra3 the existence of which I'm not aware of. If you can show some of the changes it would be easier to say how the system should be specified.
I'm just working on the core clock initialisation patches as our original work was just patching the tegra20 and tegra30 clock init tables. As far as we can see the tegra30 automotive grade silicon is mostly compatible with the tegra30 but has some clock restrictions and initialisation changes. -- Ben Dooks http://www.codethink.co.uk/ Senior Engineer Codethink - Providing Genius https://www.codethink.co.uk/privacy.html -- To unsubscribe from this list: send the line "unsubscribe devicetree" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
