[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <e1d53083-82b6-d193-517e-02af281a066a@linaro.org>
Date: Wed, 22 Mar 2023 17:27:21 +0100
From: Krzysztof Kozlowski <krzysztof.kozlowski@...aro.org>
To: Souradeep Chowdhury <quic_schowdhu@...cinc.com>,
Andy Gross <agross@...nel.org>,
Konrad Dybcio <konrad.dybcio@...ainline.org>,
Krzysztof Kozlowski <krzysztof.kozlowski+dt@...aro.org>,
Bjorn Andersson <andersson@...nel.org>,
Rob Herring <robh+dt@...nel.org>
Cc: linux-arm-kernel@...ts.infradead.org, linux-kernel@...r.kernel.org,
linux-arm-msm@...r.kernel.org, devicetree@...r.kernel.org,
Sibi Sankar <quic_sibis@...cinc.com>,
Rajendra Nayak <quic_rjendra@...cinc.com>
Subject: Re: [PATCH V1 1/4] dt-bindings: sram: qcom,imem: Add Boot Stat region
within IMEM
On 22/03/2023 14:34, Souradeep Chowdhury wrote:
>>
>>> + - const: qcom,imem-boot_stats
>>
>> No underscores in compatibles. Why this is not SoC specific compatible?
>
> Ack. The boot_stats module is not specific to a device. It is written to
> read some values from this imem region which is present for almost all
> QCOM SoCs. So SoC specific compatible is not given in this case.
Yeah, but the generic rule is that we always want SoC specific
compatibles. If this is not specific to a device, then you do not need
anything in DT and just instantiate it from some soc-driver...
Best regards,
Krzysztof
Powered by blists - more mailing lists