From: Krzysztof Kozlowski <krzysztof.kozlowski@linaro.org>
To: Luca Weiss <luca@z3ntu.xyz>, linux-arm-msm@vger.kernel.org
Cc: ~postmarketos/upstreaming@lists.sr.ht,
phone-devel@vger.kernel.org, Andy Gross <agross@kernel.org>,
Bjorn Andersson <andersson@kernel.org>,
Konrad Dybcio <konrad.dybcio@somainline.org>,
Rob Herring <robh+dt@kernel.org>,
Krzysztof Kozlowski <krzysztof.kozlowski+dt@linaro.org>,
devicetree@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH 2/2] ARM: dts: qcom: pm8941: fix iadc node
Date: Wed, 28 Sep 2022 09:26:11 +0200 [thread overview]
Message-ID: <c36a8f26-b187-9870-ebfb-caaa893f3d86@linaro.org> (raw)
In-Reply-To: <1828122.tdWV9SEqCh@g550jk>
On 26/09/2022 17:05, Luca Weiss wrote:
> Hi Krzysztof,
>
> On Montag, 26. September 2022 10:54:23 CEST Krzysztof Kozlowski wrote:
>> On 25/09/2022 18:18, Luca Weiss wrote:
>>> The iadc node name is supposed to be just 'adc' and the compatible is
>>> only supposed to be qcom,spmi-iadc according to the bindings.
>>>
>>> Adjust the node to match that.
>>>
>>> Signed-off-by: Luca Weiss <luca@z3ntu.xyz>
>>> ---
>>>
>>> arch/arm/boot/dts/qcom-pm8941.dtsi | 4 ++--
>>> 1 file changed, 2 insertions(+), 2 deletions(-)
>>>
>>> diff --git a/arch/arm/boot/dts/qcom-pm8941.dtsi
>>> b/arch/arm/boot/dts/qcom-pm8941.dtsi index 3c15eecf2f21..33517cccee01
>>> 100644
>>> --- a/arch/arm/boot/dts/qcom-pm8941.dtsi
>>> +++ b/arch/arm/boot/dts/qcom-pm8941.dtsi
>>> @@ -131,8 +131,8 @@ adc-chan@48 {
>>>
>>> };
>>>
>>> };
>>>
>>> - pm8941_iadc: iadc@3600 {
>>> - compatible = "qcom,pm8941-iadc",
> "qcom,spmi-iadc";
>>> + pm8941_iadc: adc@3600 {
>>> + compatible = "qcom,spmi-iadc";
>>
>> I am not sure this is correct. Usually specific compatibles are encouraged.
>
> I'm happy to change it the other way also.
>
> But the sibling of this compatible, qcom,spmi-vadc also only has that single
> compatible so it'd align it with that.
Ugh, there is a mess around them. Some other ADCs have specific
compatibles, some not, so there is no consistency.
I propose to have device specific compatible with qcom,spmi-iadc
fallback, so basically document the DTS in bindings. Maybe other IADC
will need some quirks, so specific compatible helps here.
Best regards,
Krzysztof
next prev parent reply other threads:[~2022-09-28 7:35 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-09-25 16:18 [PATCH 1/2] ARM: dts: qcom: pm8941: fix vadc channel node names Luca Weiss
2022-09-25 16:18 ` [PATCH 2/2] ARM: dts: qcom: pm8941: fix iadc node Luca Weiss
2022-09-26 8:45 ` Neil Armstrong
2022-09-26 8:54 ` Krzysztof Kozlowski
2022-09-26 15:05 ` Luca Weiss
2022-09-28 7:26 ` Krzysztof Kozlowski [this message]
2022-09-27 12:43 ` Konrad Dybcio
2022-09-26 8:44 ` [PATCH 1/2] ARM: dts: qcom: pm8941: fix vadc channel node names Neil Armstrong
2022-09-26 8:54 ` Krzysztof Kozlowski
2022-09-27 13:03 ` Konrad Dybcio
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=c36a8f26-b187-9870-ebfb-caaa893f3d86@linaro.org \
--to=krzysztof.kozlowski@linaro.org \
--cc=agross@kernel.org \
--cc=andersson@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=konrad.dybcio@somainline.org \
--cc=krzysztof.kozlowski+dt@linaro.org \
--cc=linux-arm-msm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=luca@z3ntu.xyz \
--cc=phone-devel@vger.kernel.org \
--cc=robh+dt@kernel.org \
--cc=~postmarketos/upstreaming@lists.sr.ht \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).