On Thu, 2020-10-15 at 12:14 +0100, Richard Fitzgerald wrote: > > Sadly I don't think creating a new device tree is a good solution here. If we > > were to do so for every RPi hat/usage it'd become unmanageable very fast. There > > is a way to maintain this in the open nonetheless. I suggest you build a DT > > overlay and submit it to https://github.com/raspberrypi/linux, see > > 'arch/arm/boot/dts/overlays.' The Raspberry Pi engineers have a kernel branch > > We want something in mainline so that it can be used by people > developing on mainline and taken as a starting point for configuring > the codecs for other host platforms. The RPi is a convenient platform to > use as the base because it is widely available and low-cost. If what you want to convey is the proper way of configuring your specific device the way to go is writing a devicetree binding. See Documentation/devicetree. It's even possible to validate a given devicetree against the bindings (given they are written in yaml format). Regards, Nicolas
Attachment:
signature.asc
Description: This is a digitally signed message part
