Re: [PATCH v4 2/7] dt-bindings: serial: 8250: aspeed: add aspeed,vuart-over-pci bool prop
Grégoire Layet <[email protected]> Tue, 14 Jul 2026 09:14:17 +0200
| Newsgroups | org.ozlabs.lists.linux-aspeed,org.infradead.lists.linux-arm-kernel,org.kernel.vger.linux-devicetree,org.kernel.vger.linux-kernel,org.kernel.vger.linux-serial |
|---|---|
| Message-ID | <CAFi2wKZqHsEa3B9KMDyVk+1Ef42u4TqWzqf6O4SXtamRnWD8Yw@mail.gmail.com> |
Hi Krzysztof. On Thu, 9 Jul 2026 at 10:54, Krzysztof Kozlowski <[email protected]> wrote: > > ... > > @@ -27,6 +27,16 @@ allOf: > > enum: > > - aspeed,ast2500-vuart > > - aspeed,ast2600-vuart > > + - if: > > + required: > > + - aspeed,vuart-over-pci > > + then: > > + required: > > + - syscon > > + properties: > > + compatible: > > + contains: > > + const: aspeed,ast2600-vuart > > else: > ... > disallow new properties (see example-schema) Yes it was missing. Acknowledged. > > > - if: > > properties: > > compatible: > > @@ -223,6 +233,12 @@ properties: > > - const: uartclk > > - const: reg > > > > + syscon: > > That's explicitly forbidden by writing bindings (and mentioned as the > antipattern in my older talks about DT). Missed that. Should it be named to 'aspeed,scu-syscon' as the aspeed SCU is used for all the peripherals. Or should it be named to 'aspeed,pci-syscon' to specify its purpose in this context. From what I have gathered, current convention would use the specific name 'aspeed,pci-syscon'. Would like some feedback on this! > > + $ref: /schemas/types.yaml#/definitions/phandle > > + description: > > + Phandle to the SCU syscon, used to enable the VUART over the BMC PCI > > + device. Only applicable to aspeed,ast2600-vuart. > > + > > ... Thanks Regards, Grégoire