Re: [PATCH v3 1/7] dt-bindings: serial: 8250: aspeed: add compatible string for ast2600
Krzysztof Kozlowski <[email protected]> Wed, 24 Jun 2026 09:15:34 +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 | <20260624-realistic-spiked-parrot-db1d9c@quoll> |
On Tue, Jun 23, 2026 at 02:25:39PM +0000, Grégoire Layet wrote: > The ast2600 was using the ast2500 vuart compatible string. > This change makes it possible to have ast2600-specific properties. > > Signed-off-by: Grégoire Layet <[email protected]> Do not attach (thread) your patchsets to some other threads (unrelated or older versions). This buries them deep in the mailbox and might interfere with applying entire sets. See also: https://elixir.bootlin.com/linux/v6.16-rc2/source/Documentation/process/submitting-patches.rst#L830 > --- > .../devicetree/bindings/serial/8250.yaml | 20 +++++++++++-------- > 1 file changed, 12 insertions(+), 8 deletions(-) > > diff --git a/Documentation/devicetree/bindings/serial/8250.yaml b/Documentation/devicetree/bindings/serial/8250.yaml > index bb7b9c87a807..3cbd0f532e15 100644 > --- a/Documentation/devicetree/bindings/serial/8250.yaml > +++ b/Documentation/devicetree/bindings/serial/8250.yaml > @@ -23,7 +23,9 @@ allOf: > then: > properties: > compatible: > - const: aspeed,ast2500-vuart > + anyOf: This should be oneOf (by convention and actually more accurate meaning). > + - const: aspeed,ast2500-vuart > + - const: aspeed,ast2600-vuart > - if: > properties: > compatible: > @@ -287,17 +289,19 @@ properties: > aspeed,sirq-polarity-sense: > $ref: /schemas/types.yaml#/definitions/phandle-array > description: | > - Phandle to aspeed,ast2500-scu compatible syscon alongside register > - offset and bit number to identify how the SIRQ polarity should be > - configured. One possible data source is the LPC/eSPI mode bit. Only > - applicable to aspeed,ast2500-vuart. > + Phandle to aspeed,ast2500-scu or aspeed,ast2600-scu compatible syscon > + alongside register offset and bit number to identify how the SIRQ > + polarity should be configured. One possible data source is the LPC/eSPI > + mode bit. Only applicable to aspeed,ast2500-vuart and > + aspeed,ast2600-vuart. > deprecated: true > > aspeed,lpc-io-reg: > $ref: /schemas/types.yaml#/definitions/uint32-array > maxItems: 1 > description: | > - The VUART LPC address. Only applicable to aspeed,ast2500-vuart. > + The VUART LPC address. Only applicable to aspeed,ast2500-vuart and > + aspeed,ast2600-vuart. > > aspeed,lpc-interrupts: > $ref: /schemas/types.yaml#/definitions/uint32-array > @@ -305,8 +309,8 @@ properties: > maxItems: 2 > description: | > A 2-cell property describing the VUART SIRQ number and SIRQ > - polarity (IRQ_TYPE_LEVEL_LOW or IRQ_TYPE_LEVEL_HIGH). Only > - applicable to aspeed,ast2500-vuart. > + polarity (IRQ_TYPE_LEVEL_LOW or IRQ_TYPE_LEVEL_HIGH). Only > + applicable to aspeed,ast2500-vuart and aspeed,ast2600-vuart. > More important, where is documenting of the actual compatible? Best regards, Krzysztof