[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <Y+yGYycS7rrBRBPN@atomide.com>
Date: Wed, 15 Feb 2023 09:14:43 +0200
From: Tony Lindgren <tony@...mide.com>
To: Rob Herring <robh@...nel.org>
Cc: Colin Foster <colin.foster@...advantage.com>,
linux-omap@...r.kernel.org, linux-arm-kernel@...ts.infradead.org,
linux-kernel@...r.kernel.org, devicetree@...r.kernel.org,
BenoƮt Cousson <bcousson@...libre.com>,
soc@...nel.org, Olof Johansson <olof@...om.net>,
Arnd Bergmann <arnd@...db.de>,
Krzysztof Kozlowski <krzysztof.kozlowski+dt@...aro.org>,
Krzysztof Kozlowski <krzysztof.kozlowski@...aro.org>
Subject: Re: [PATCH v3 1/2] dt-bindings: arm: omap: add phytec pcm-049 som
and pcm-959 dev board
* Rob Herring <robh@...nel.org> [230209 19:35]:
> On Wed, Feb 08, 2023 at 06:55:24PM -0800, Colin Foster wrote:
> > --- a/Documentation/devicetree/bindings/arm/omap/omap.txt
> > +++ b/Documentation/devicetree/bindings/arm/omap/omap.txt
> > @@ -131,6 +131,9 @@ Boards (incomplete list of examples):
> > - OMAP4 PandaBoard : Low cost community board
> > compatible = "ti,omap4-panda", "ti,omap4430", "ti,omap4"
> >
> > +- OMAP4 PCM-959 : Commercial dev kit with PCM-049 SOM
> > + compatible = "phytec,pcm959", "phytec,pcm049", "ti,omap4460", "ti,omap4430", "ti,omap4";
Do you have both "ti,omap4460" and "ti,omap4430" SoCs variants for
these boards? If not just drop the SoC variant not in use. If you do have,
please mention it in the commit message.
> OMAP maintainers, if no one is going to convert all of omap.txt over to
> schema, can we at least start an empty schema and add to it instead of
> here...
That sounds like a good plan to me as it allows moving one device at a
time.
Colin, care to add the initial yaml binding file with your board?
Regards,
Tony
Powered by blists - more mailing lists