From: Krzysztof Kozlowski <krzysztof.kozlowski@linaro.org>
To: Varadarajan Narayanan <quic_varada@quicinc.com>
Cc: agross@kernel.org, andersson@kernel.org,
konrad.dybcio@linaro.org, amitk@kernel.org,
thara.gopinath@gmail.com, rafael@kernel.org,
daniel.lezcano@linaro.org, rui.zhang@intel.com,
robh+dt@kernel.org, krzysztof.kozlowski+dt@linaro.org,
conor+dt@kernel.org, linux-arm-msm@vger.kernel.org,
linux-pm@vger.kernel.org, devicetree@vger.kernel.org,
linux-kernel@vger.kernel.org,
Praveenkumar I <quic_ipkumar@quicinc.com>
Subject: Re: [PATCH v3 2/4] dt-bindings: thermal: tsens: Add ipq9574 compatible
Date: Thu, 18 May 2023 13:06:49 +0200 [thread overview]
Message-ID: <24b60ca3-b6b9-662f-03c8-df1536b52bc9@linaro.org> (raw)
In-Reply-To: <20230518090503.GA9173@varda-linux.qualcomm.com>
On 18/05/2023 11:05, Varadarajan Narayanan wrote:
> On Thu, May 18, 2023 at 09:09:12AM +0200, Krzysztof Kozlowski wrote:
>> On 18/05/2023 07:40, Varadarajan Narayanan wrote:
>>> On Wed, May 17, 2023 at 09:00:49AM +0200, Krzysztof Kozlowski wrote:
>>>> On 17/05/2023 07:57, Varadarajan Narayanan wrote:
>>>>> Part-1 is adding the 'const' entries at the beginning i.e.
>>>>>
>>>>> + - const: qcom,tsens-v0_1
>>>>> + - const: qcom,tsens-v1
>>>>> + - const: qcom,tsens-v2
>>>>> + - const: qcom,ipq8074-tsens
>>>>>
>>>>> Part-2 is changing from one valid syntax to another i.e.
>>>>>
>>>>> + items:
>>>>> + - enum:
>>>>> + - qcom,ipq9574-tsens
>>>>> + - const: qcom,ipq8074-tsens
>>>>>
>>>>> Without both of the above changes, either or both of dtbs_check
>>>>> & dt_binding_check fails. So, it is not possible to just add the
>>>>> "valid hunk" (part-2) alone.
>>>>
>>>> Of course it is. All schema files work like that...
>>>>>
>>>>> If having both part-1 and part-2 in the same patch is not
>>>>> acceptable, shall I split them into two patches? Please let me know.
>>>>
>>>> No, hunk one is not justified.
>>>
>>> For the other compatibles, the enum entries and const/fallback
>>> entries are different. For the 9574 & 8074 case, we want to have
>>> qcom,ipq8074-tsens as both enum and const/fallback entry. Hence,
>>> if we don't have the first hunk, dtbs_check fails for 8074
>>> related dtbs
>>>
>>> ipq8074-hk01.dtb: thermal-sensor@4a9000: compatible: 'oneOf' condition
>>> ['qcom,ipq8074-tsens'] is too short
>>
>> Why? It is already there. Open the file and you will see that this is
>> already covered.
>
> I guess dtbs_check doesn't like the same value being a const and
> a oneof entry.
I don't understand.
> Have attached the file, please see if something is
> not in order.
I don't know what changed there. Please work on patches.
>
>> If you remove it, then yes, you will see errors and the answer is: do
>> not remove it.
>
> I haven't removed it.
You did. Look:
- description: v2 of TSENS with combined interrupt
- enum:
- - qcom,ipq8074-tsens
The first character in the diff (-) means removal.
> For this patch, ipq8074-tsens changed from
> being an oneof enum entry to a const entry. Probably, that is why
> dtbs_check is giving these errors.
You removed the entry which you should not have touched.
>
>>> ipq8074-hk10-c2.dtb: thermal-sensor@4a9000: compatible: 'oneOf' condition
>>> ['qcom,ipq8074-tsens'] is too short
>>>
>>> ipq8074-hk10-c1.dtb: thermal-sensor@4a9000: compatible: 'oneOf' condition
>>> ['qcom,ipq8074-tsens'] is too short
>>>
>>> I'm not sure of the correct solution. Having the first hunk
>>> solves the above dtbs_check errors, so went with it. I'm able to
>>> avoid dtbs_check errors with just one entry in the first hunk.
>>
>> You made multiple changes in one patch which is not correct. Your goal
>> is to add only one change - ipq9574 followed by ipq8074. Add this one.
>> Don't touch others.
>
> But that breaks dtbs_check.
All other cases, hundreds of other binding files, do not have problem.
Only this one "breaks dtbs_check". No, it does not.
Whatever is broken is result of your removal of unrelated pieces.
>
>>> + - const: qcom,ipq8074-tsens
>>>
>>> Please let me know if there is a better way to resolve this or we
>>> can have just the 8074 entry in the first hunk.
>>
>> You only need to add new item on the oneOf list:
>> - enum
>> - ipq9574
>> - const: ipq8074
>
> The "['qcom,ipq8074-tsens'] is too short" errors were generated
> with the above snippet only. Please see the attachment
It's not true. The error you see is result because you removed something
you should not. I did not ask you to remove anything. So repeating -
"add new item". Adding is not "removal and adding". Adding is just "adding".
Best regards,
Krzysztof
next prev parent reply other threads:[~2023-05-18 11:06 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-05-15 10:13 [PATCH v3 0/4] Enable IPQ9574 TSENS support Varadarajan Narayanan
2023-05-15 10:13 ` [PATCH v3 1/4] dt-bindings: thermal: tsens: Fix "make dtbs_check" error Varadarajan Narayanan
2023-05-15 16:09 ` Krzysztof Kozlowski
2023-05-16 1:07 ` Konrad Dybcio
2023-05-15 10:13 ` [PATCH v3 2/4] dt-bindings: thermal: tsens: Add ipq9574 compatible Varadarajan Narayanan
2023-05-15 16:10 ` Krzysztof Kozlowski
2023-05-16 12:04 ` Varadarajan Narayanan
2023-05-16 13:06 ` Krzysztof Kozlowski
2023-05-17 5:57 ` Varadarajan Narayanan
2023-05-17 7:00 ` Krzysztof Kozlowski
2023-05-18 5:40 ` Varadarajan Narayanan
2023-05-18 7:09 ` Krzysztof Kozlowski
2023-05-18 9:05 ` Varadarajan Narayanan
2023-05-18 11:06 ` Krzysztof Kozlowski [this message]
2023-05-23 10:19 ` Varadarajan Narayanan
2023-05-23 16:44 ` Conor Dooley
2023-05-24 6:43 ` Varadarajan Narayanan
2023-05-30 11:25 ` Krzysztof Kozlowski
2023-05-15 10:13 ` [PATCH v3 3/4] arm64: dts: qcom: ipq9574: add tsens node Varadarajan Narayanan
2023-05-15 10:13 ` [PATCH v3 4/4] arm64: dts: qcom: ipq9574: add thermal zone nodes Varadarajan Narayanan
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=24b60ca3-b6b9-662f-03c8-df1536b52bc9@linaro.org \
--to=krzysztof.kozlowski@linaro.org \
--cc=agross@kernel.org \
--cc=amitk@kernel.org \
--cc=andersson@kernel.org \
--cc=conor+dt@kernel.org \
--cc=daniel.lezcano@linaro.org \
--cc=devicetree@vger.kernel.org \
--cc=konrad.dybcio@linaro.org \
--cc=krzysztof.kozlowski+dt@linaro.org \
--cc=linux-arm-msm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pm@vger.kernel.org \
--cc=quic_ipkumar@quicinc.com \
--cc=quic_varada@quicinc.com \
--cc=rafael@kernel.org \
--cc=robh+dt@kernel.org \
--cc=rui.zhang@intel.com \
--cc=thara.gopinath@gmail.com \
/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).