On Mon, Aug 22, 2022 at 9:29 AM Andrew Lunn <andrew@xxxxxxx> wrote: > > On Mon, Aug 22, 2022 at 08:53:23AM -0500, Rob Herring wrote: > > On Sat, Aug 20, 2022 at 09:47:53PM +0200, Andrew Lunn wrote: > > > This is the first batch of patches converting the Marvell MVEBU driver > > > bindings from .txt to .yaml. So far, kirkwood has been used for > > > testing, but these drivers apply to a range of Marvell SoCs. > > > > > > In order to reduce the number of warnings from the DT schema checking > > > tools, a few minor changes have been made to a few DT files. No actual > > > errors have been found, the changes just make the checker quiet. > > > > > > Andrew Lunn (11): > > > DT: RTC: orion-rtc: Convert to YAML > > > DT: thermal: marvell,kirkwood-thermal: Convert to YAML > > > DT: pinctrl: Convert marvell,kirkwood-pintctrl to YAML > > > DT: USB: Convert ehci-orion to YAML > > > DT: watchdog: Convert marvel.txt to YAML > > > arm: DT: kirkwood/orion5: Rename watchdog node > > > DT: nand-controller: Reflect reality of marvell,orion-nand > > > DT: mtd: Convert orion-nand to YAML > > > arm: DT: kirkwood.dtsi: Rename nand to nand-controller > > > DT: timer: Convert marvell,orion-timer.txt to YAML > > > DT: clock: Convert mvebu-gated-clock.txt to YAML > > > > Also, there's not any dependency between most of these patches and they > > all go thru different subsystems, so no need for this to be 1 series. > > My intention was for them all to go through mvebu, to arm-soc and in. > That is how all these .txt files got merged many years ago. Yes, that did happen some, but the documented path in for bindings is via subsystem maintainers (with the driver for new bindings). The 2nd preference is the DT tree as I'm about the only one testing (or continuously testing) the schemas. Rob
