[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <d1a852e1-c4c2-b7c4-ddeb-7fbcfd9b4e58@canonical.com>
Date: Thu, 13 Jan 2022 13:31:57 +0100
From: Krzysztof Kozlowski <krzysztof.kozlowski@...onical.com>
To: Alim Akhtar <alim.akhtar@...sung.com>,
linux-arm-kernel@...ts.infradead.org, linux-kernel@...r.kernel.org
Cc: soc@...nel.org, linux-clk@...r.kernel.org,
devicetree@...r.kernel.org, olof@...om.net,
linus.walleij@...aro.org, catalin.marinas@....com,
robh+dt@...nel.org, s.nawrocki@...sung.com,
linux-samsung-soc@...r.kernel.org, pankaj.dubey@...sung.com
Subject: Re: [PATCH 00/23] Add support for Tesla Full Self-Driving (FSD) SoC
On 13/01/2022 13:11, Alim Akhtar wrote:
> This patch set adds basic support for the Tesla Full Self-Driving (FSD)
> SoC. This SoC contains three clusters of four Cortex-A72 CPUs,
> as well as several IPs.
>
> Patches 1 to 8 provide support for the clock controller
> (which is designed similarly to Exynos SoCs).
>
> The remaining changes provide pinmux support, initial device tree support,
> and SPI, ADC, and MCT IP functionality.
Does FSD have some version number? The FDS, especially in compatibles,
looks quite generic, so what will happen if a newer SoC comes later? You
would have:
- tesla,fsd-pinctrl
- tesla,fsd-xxxx-pinctrl (where xxxx could be some new version)
This will be extra confusing, because fsd-pinctrl looks like the generic
one, while it is specific...
Best regards,
Krzysztof
Powered by blists - more mailing lists