[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <1bc7627a-f1d7-4fee-b016-5b9cc407f170@quicinc.com>
Date: Tue, 19 Nov 2024 15:15:07 +0530
From: Raviteja Laggyshetty <quic_rlaggysh@...cinc.com>
To: Dmitry Baryshkov <dmitry.baryshkov@...aro.org>
CC: Georgi Djakov <djakov@...nel.org>, Rob Herring <robh@...nel.org>,
Krzysztof Kozlowski <krzk+dt@...nel.org>,
Conor Dooley <conor+dt@...nel.org>,
Bjorn Andersson <andersson@...nel.org>,
Konrad Dybcio
<konradybcio@...nel.org>,
Sibi Sankar <quic_sibis@...cinc.com>, <linux-arm-msm@...r.kernel.org>,
<linux-pm@...r.kernel.org>, <devicetree@...r.kernel.org>,
<linux-kernel@...r.kernel.org>,
Odelu Kukatla
<quic_okukatla@...cinc.com>,
Mike Tipton <quic_mdtipton@...cinc.com>
Subject: Re: [PATCH V4 1/3] dt-bindings: interconnect: Add EPSS L3 compatible
for SA8775P
On 11/18/2024 4:42 PM, Dmitry Baryshkov wrote:
> On Mon, 18 Nov 2024 at 13:07, Raviteja Laggyshetty
> <quic_rlaggysh@...cinc.com> wrote:
>>
>>
>>
>> On 11/12/2024 7:20 PM, Dmitry Baryshkov wrote:
>>> On Tue, Nov 12, 2024 at 07:58:24AM +0000, Raviteja Laggyshetty wrote:
>>>> Add Epoch Subsystem (EPSS) L3 interconnect provider binding on
>>>> SA8775P SoCs.
>>>>
>>>> Signed-off-by: Raviteja Laggyshetty <quic_rlaggysh@...cinc.com>
>>>> ---
>>>> Documentation/devicetree/bindings/interconnect/qcom,osm-l3.yaml | 1 +
>>>> 1 file changed, 1 insertion(+)
>>>>
>>>> diff --git a/Documentation/devicetree/bindings/interconnect/qcom,osm-l3.yaml b/Documentation/devicetree/bindings/interconnect/qcom,osm-l3.yaml
>>>> index 21dae0b92819..94f7f283787a 100644
>>>> --- a/Documentation/devicetree/bindings/interconnect/qcom,osm-l3.yaml
>>>> +++ b/Documentation/devicetree/bindings/interconnect/qcom,osm-l3.yaml
>>>> @@ -33,6 +33,7 @@ properties:
>>>> - qcom,sm6375-cpucp-l3
>>>> - qcom,sm8250-epss-l3
>>>> - qcom,sm8350-epss-l3
>>>> + - qcom,sa8775p-epss-l3
>>>> - const: qcom,epss-l3
>>>
>>> No, sa8775p isn't compatible with qcom,epss-l3. I asked you to split the
>>> driver patch, not to change the compatibles.
>>>
>>>
>> Got it, I will split the driver code changes into two patches.
>> First patch will contain the SoC-specific compatible change and multi device support.
>
> no ands, just multidev.
ok, Will split multidev support as one patch. Generic and SoC-specific compatibles addition as second patch.
>
>> Second patch will contain the generic compatible addition to of_match table.
>>
>
>
Powered by blists - more mailing lists