[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <e7298704-5a03-0961-90a3-dab4af60c326@linaro.org>
Date: Sat, 1 Jul 2023 13:03:51 +0200
From: Krzysztof Kozlowski <krzysztof.kozlowski@...aro.org>
To: Anjelique Melendez <quic_amelende@...cinc.com>,
Rob Herring <robh@...nel.org>
Cc: pavel@....cz, lee@...nel.org, thierry.reding@...il.com,
krzysztof.kozlowski+dt@...aro.org, conor+dt@...nel.org,
agross@...nel.org, andersson@...nel.org, konrad.dybcio@...aro.org,
u.kleine-koenig@...gutronix.de, linux-leds@...r.kernel.org,
devicetree@...r.kernel.org, linux-kernel@...r.kernel.org,
linux-arm-msm@...r.kernel.org, linux-pwm@...r.kernel.org
Subject: Re: [PATCH 1/7] dt-bindings: soc: qcom: Add qcom-pbs bindings
On 29/06/2023 03:19, Anjelique Melendez wrote:
>>> +examples:
>>> + - |
>>> + pmic {
>>> + #address-cells = <1>;
>>> + #size-cells = <0>;
>>> +
>>> + qcom,pbs@...0 {
>>> + compatible = "qcom,pbs";
>>> + reg = <0x7400>;
>>> + };
>>
>> Why do you need a child node for this? Is there more than 1 instance in
>> a PMIC? Every sub-function of a PMIC doesn't have to have a DT node.
>>
>
> We currently have another downstream driver (which is planned to get upstreamed)
> which also needs a handle to a pbs device in order to properly trigger events.
I don't see how does it answer Rob's concerns. Neither mine about
incomplete binding. You don't need pbs node here for that.
Anyway, whatever you have downstream also does not justify any changes.
Either upstream these so we can see it or drop this binding.
Best regards,
Krzysztof
Powered by blists - more mailing lists