[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <e28ba03d1df1c0c5aec987411c40e44fc351ce0d.camel@codeconstruct.com.au>
Date: Wed, 26 Jun 2024 13:31:03 +0800
From: Jeremy Kerr <jk@...econstruct.com.au>
To: Aniket <aniketmaurya@...gle.com>, Alexandre Belloni
<alexandre.belloni@...tlin.com>, Joel Stanley <joel@....id.au>, Billy Tsai
<billy_tsai@...eedtech.com>, Rob Herring <robh@...nel.org>, Krzysztof
Kozlowski <krzysztof.kozlowski+dt@...aro.org>
Cc: linux-i3c@...ts.infradead.org, linux-kernel@...r.kernel.org,
devicetree@...r.kernel.org
Subject: Re: [PATCH 1/2] dt-bindings: i3c: dw: Add property to select IBI ops
Hi Aniket,
> Use this property to select IBI related ops in the base platform
> driver. Otherwise the driver defaults to return EINVAL for any IBI
> requests.
[...]
> --- a/Documentation/devicetree/bindings/i3c/snps,dw-i3c-master.yaml
> +++ b/Documentation/devicetree/bindings/i3c/snps,dw-i3c-master.yaml
> @@ -25,6 +25,10 @@ properties:
> interrupts:
> maxItems: 1
>
> + ibi-capable:
> + description: Set to select IBI ops.
> + type: boolean
> +
Wouldn't the compatible string select whether the hardware instance
supports IBI or not?
I'd imagine that each specific synthesis of the DW IP would imply
corresponding hardware settings, and so would warrant its own compatible
value.
Maybe one for the DT folks: would this work better as individual
properties? Is there a policy here?
Cheers,
Jeremy
Powered by blists - more mailing lists