From: Mohammad Rafi Shaik <mohammad.rafi.shaik@oss.qualcomm.com>
To: Rob Herring <robh@kernel.org>
Cc: Bjorn Andersson <andersson@kernel.org>,
Linus Walleij <linusw@kernel.org>,
Krzysztof Kozlowski <krzk+dt@kernel.org>,
Conor Dooley <conor+dt@kernel.org>,
Srinivas Kandagatla <srini@kernel.org>,
linux-arm-msm@vger.kernel.org, linux-gpio@vger.kernel.org,
devicetree@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH v3] dt-bindings: pinctrl: qcom,sm8450-lpass-lpi-pinctrl: Add SA8775P and QCS8300 pinctrl
Date: Thu, 29 Jan 2026 16:03:37 +0530 [thread overview]
Message-ID: <81f0ee3c-a7e3-4730-a396-9599ddd45f53@oss.qualcomm.com> (raw)
In-Reply-To: <CAL_Jsq+YYxWKaD-Xo7L3VUAJ=wvpbfW9GkKn0gcj3AOvMb=Uhg@mail.gmail.com>
On 1/27/2026 11:57 PM, Rob Herring wrote:
> On Tue, Jan 27, 2026 at 12:13 PM Mohammad Rafi Shaik
> <mohammad.rafi.shaik@oss.qualcomm.com> wrote:
>>
>>
>>
>> On 1/27/2026 7:47 PM, Rob Herring wrote:
>>> On Tue, Jan 27, 2026 at 04:25:11PM +0530, Mohammad Rafi Shaik wrote:
>>>> Document compatible for Qualcomm SA8775P and QCS8300 SoC LPASS TLMM
>>>> pin controller, fully compatible with previous SM8450 generation
>>>> (same amount of pins and functions).
>>>>
>>>> Signed-off-by: Mohammad Rafi Shaik <mohammad.rafi.shaik@oss.qualcomm.com>
>>>> ---
>>>> changes in [v3]:
>>>> - Removed the duplicate driver code patch as suggested by Krzysztof.
>>>> - Reused the existing SM8490 pinctrl, which is fully compatible with SA8775P and QCS8300.
>>>> - Link to V2: https://lore.kernel.org/all/20260107192007.500995-1-mohammad.rafi.shaik@oss.qualcomm.com/
>>>>
>>>> changes in [v2]:
>>>> - Fixed dt-binding errors reported by Krzysztof and Rob.
>>>> - Added proper slew rate value for wsa2_swr_data GPIO, as suggested by Konrad.
>>>> - Documented Monaco compatible as suggested by Konrad.
>>>> - Link to V1: https://lore.kernel.org/all/20251116171656.3105461-1-mohammad.rafi.shaik@oss.qualcomm.com/
>>>> ---
>>>> .../pinctrl/qcom,sm8450-lpass-lpi-pinctrl.yaml | 10 +++++++++-
>>>> 1 file changed, 9 insertions(+), 1 deletion(-)
>>>>
>>>> diff --git a/Documentation/devicetree/bindings/pinctrl/qcom,sm8450-lpass-lpi-pinctrl.yaml b/Documentation/devicetree/bindings/pinctrl/qcom,sm8450-lpass-lpi-pinctrl.yaml
>>>> index e7565592d..354629c38 100644
>>>> --- a/Documentation/devicetree/bindings/pinctrl/qcom,sm8450-lpass-lpi-pinctrl.yaml
>>>> +++ b/Documentation/devicetree/bindings/pinctrl/qcom,sm8450-lpass-lpi-pinctrl.yaml
>>>> @@ -15,7 +15,15 @@ description:
>>>>
>>>> properties:
>>>> compatible:
>>>> - const: qcom,sm8450-lpass-lpi-pinctrl
>>>> + oneOf:
>>>> + - const: qcom,sm8450-lpass-lpi-pinctrl
>>>> + - items:
>>>> + - enum:
>>>> + - qcom,qcs8300-lpass-lpi-pinctrl
>>>> + - qcom,sa8775p-lpass-lpi-pinctrl
>>>> + - const: qcom,sm8450-lpass-lpi-pinctrl
>>>> + minItems: 1
>>>> + maxItems: 2
>>>
>>> No. You are either backwards compatible with sm8450 or you aren't. The
>>> h/w is fixed.
>>>
>>
>> ACK,
>>
>> Agree,
>>
>> Need backward compatibility with sm8450 for both sa8775p and qcs8300 as
>> they must fall back to the sm8450, so initially used enum to pick
>> between the sa8775p and qcs8300 compatibles. I see enum isn’t
>> appropriate here since fixed h/w.
>>
>> will use the const instead of enum like below.
>>
>> properties:
>> compatible:
>> - const: qcom,sm8450-lpass-lpi-pinctrl
>> + oneOf:
>> + - const: qcom,sm8450-lpass-lpi-pinctrl
>> + - items:
>> + - const: qcom,sa8775p-lpass-lpi-pinctrl
>> + - const: qcom,sm8450-lpass-lpi-pinctrl
>> +
>> + - items:
>> + - const: qcom,qcs8300-lpass-lpi-pinctrl
>> + - const: qcom,sm8450-lpass-lpi-pinctrl
>
> Sigh, no. The 2 entries can be combined like you had. Just drop
> minItems and maxItems from what you had.
>
> And test your binding before sending it.
>
Sure, I’ll take care of it going forward
Thanks & Regarding,
Rafi.
> Rob
prev parent reply other threads:[~2026-01-29 10:33 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-01-27 10:55 Mohammad Rafi Shaik
2026-01-27 12:19 ` Rob Herring (Arm)
2026-01-27 14:17 ` Rob Herring
2026-01-27 18:13 ` Mohammad Rafi Shaik
2026-01-27 18:27 ` Rob Herring
2026-01-29 10:33 ` Mohammad Rafi Shaik [this message]
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=81f0ee3c-a7e3-4730-a396-9599ddd45f53@oss.qualcomm.com \
--to=mohammad.rafi.shaik@oss.qualcomm.com \
--cc=andersson@kernel.org \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=krzk+dt@kernel.org \
--cc=linusw@kernel.org \
--cc=linux-arm-msm@vger.kernel.org \
--cc=linux-gpio@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=robh@kernel.org \
--cc=srini@kernel.org \
/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
all inboxes | Powered by JetHome®