[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <57018287-3686-4575-8bd4-a1efd1248fe8@linaro.org>
Date: Thu, 8 Feb 2024 16:58:22 +0100
From: Krzysztof Kozlowski <krzysztof.kozlowski@...aro.org>
To: Sibi Sankar <quic_sibis@...cinc.com>, Rob Herring <robh@...nel.org>
Cc: sudeep.holla@....com, cristian.marussi@....com, andersson@...nel.org,
konrad.dybcio@...aro.org, jassisinghbrar@...il.com,
krzysztof.kozlowski+dt@...aro.org, linux-kernel@...r.kernel.org,
linux-arm-msm@...r.kernel.org, devicetree@...r.kernel.org,
quic_rgottimu@...cinc.com, quic_kshivnan@...cinc.com, conor+dt@...nel.org
Subject: Re: [RFC 1/7] dt-bindings: mailbox: qcom: Add CPUCP mailbox
controller bindings
On 08/02/2024 11:28, Sibi Sankar wrote:
>>> +properties:
>>> + compatible:
>>> + items:
>>> + - enum:
>>> + - qcom,x1e80100-cpucp-mbox
>>> + - const: qcom,cpucp-mbox
>>
>> A generic fallback implies multiple devices use the same unchanged
>> block. That seems doubtful given you have not defined any others and
>> given Konrad's comments.
>
> This mbox is expected to be used as is on a number of future SoCs,
> that's the only reason I added the generic fallback. I can drop it
> in the next re-spin if you want.
Given that, if you ever have compatible devices, just use
device-specific compatible as fallback.
Best regards,
Krzysztof
Powered by blists - more mailing lists