Re: [PATCH 1/1] dt-bindings: arm: lpc: add missed lpc43xx board

[Rob Herring <robh@kernel.org>]

On Mon, Jun 02, 2025 at 06:09:20PM -0400, Frank Li wrote:
> On Mon, Jun 02, 2025 at 08:17:06PM +0300, Vladimir Zapolskiy wrote:
> > On 6/2/25 19:04, Frank Li wrote:
> > > On Mon, Jun 02, 2025 at 06:34:14PM +0300, Vladimir Zapolskiy wrote:
> > > > On 6/2/25 17:06, Frank Li wrote:
> > > > > Add missed legancy lpc43xx board compatible string to fix below CHECK_DTB
> > > > > warnings:
> > > > > arch/arm/boot/dts/nxp/lpc/lpc4337-ciaa.dtb: /: failed to match any schema with compatible: ['ciaa,lpc4337', 'nxp,lpc4337', 'nxp,lpc4350']
> > > > >
> > > > > Signed-off-by: Frank Li <Frank.Li@nxp.com>
> > > > > ---
> > > > >    .../devicetree/bindings/arm/fsl.yaml          | 23 +++++++++++++++++++
> > > > >    1 file changed, 23 insertions(+)
> > > >
> > > > I prefer to see NXP SoC powered boards under Documentation/devicetree/bindings/arm/nxp/
> > > >
> > > > LPC18XX/LPC43XX SoCs are not Freescale.
> > >
> > > Generally, we don't distingiush that, new s32g chip also in this files.
> > > All nxp/fsl was maintained by one person and everyone know these are one
> > > company now.
> >
> > Well, my concern is actually not about the companies, but these two SoC
> > families are totally different, the peripherals or core controllers are
> > all different, it makes little sense to mix them up.
> 
> This just collect board level compatible string, like trivial-devices.yaml,
> which collect variance devices.
> 
> Shawn:
> 	Do you like create a nxp.yaml for LPC18xx/LPC43xx boards?

Please do. We have things like PXA2xx under intel, but PXA9xx/MNP under 
marvell as that's the companies that created the lines and there's no 
overlap. In the end, aligning the lineage is more important than 
companies.

We already have nxp/lpc32xx.yaml. This should probably be merged with 
that?

Rob