[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <ww2npib4iyivjqp4l4rdilry2iz2svtidue34v4bebkfmuzpnv@o6ujlbilrtw6>
Date: Mon, 9 Dec 2024 10:28:36 +0100
From: Krzysztof Kozlowski <krzk@...nel.org>
To: Chen Wang <unicornxw@...il.com>
Cc: u.kleine-koenig@...libre.com, aou@...s.berkeley.edu, arnd@...db.de,
unicorn_wang@...look.com, conor+dt@...nel.org, guoren@...nel.org, inochiama@...look.com,
krzk+dt@...nel.org, palmer@...belt.com, paul.walmsley@...ive.com, robh@...nel.org,
tglx@...utronix.de, devicetree@...r.kernel.org, linux-kernel@...r.kernel.org,
linux-riscv@...ts.infradead.org, chao.wei@...hgo.com, xiaoguang.xing@...hgo.com,
fengchun.li@...hgo.com
Subject: Re: [PATCH v2 1/3] dt-bindings: interrupt-controller: Add Sophgo
SG2042 MSI
On Mon, Dec 09, 2024 at 03:11:29PM +0800, Chen Wang wrote:
> + msi-controller: true
> +
> + msi-ranges:
> + maxItems: 1
> +
> + sophgo,msi-doorbell-addr:
> + description:
> + u64 value of the MSI doorbell address
> + $ref: /schemas/types.yaml#/definitions/uint64
reg, as asked last time. 'reg' does not mean you need to ioremap it.
> +
> +required:
> + - compatible
> + - reg
> + - reg-names
> + - msi-controller
> + - msi-ranges
> + - sophgo,msi-doorbell-addr
> +
> +additionalProperties: true
Nope, this cannot be true. There is no single device binding like that,
so do not introduce your own conventions.
> +
> +examples:
> + - |
> + #include <dt-bindings/interrupt-controller/irq.h>
> + msi: msi-controller@...00000 {
Drop unused label.
Best regards,
Krzysztof
Powered by blists - more mailing lists