Add compatible fields for QDU1000 and QRU1000 pdcs.
Signed-off-by: Melody Olvera <[email protected]>
---
.../devicetree/bindings/interrupt-controller/qcom,pdc.yaml | 1 +
1 file changed, 1 insertion(+)
diff --git a/Documentation/devicetree/bindings/interrupt-controller/qcom,pdc.yaml b/Documentation/devicetree/bindings/interrupt-controller/qcom,pdc.yaml
index b6f56cf5fbe3..afeed7b8c0fa 100644
--- a/Documentation/devicetree/bindings/interrupt-controller/qcom,pdc.yaml
+++ b/Documentation/devicetree/bindings/interrupt-controller/qcom,pdc.yaml
@@ -26,6 +26,7 @@ properties:
compatible:
items:
- enum:
+ - qcom,qdu1000-pdc
- qcom,sc7180-pdc
- qcom,sc7280-pdc
- qcom,sdm845-pdc
--
2.25.1
On 26/10/2022 15:04, Melody Olvera wrote:
> Add compatible fields for QDU1000 and QRU1000 pdcs.
>
> Signed-off-by: Melody Olvera <[email protected]>
Looks ok, except usual stuff to fix...
Best regards,
Krzysztof
Quoting Melody Olvera (2022-10-26 12:04:41)
> Add compatible fields for QDU1000 and QRU1000 pdcs.
>
> Signed-off-by: Melody Olvera <[email protected]>
> ---
Is there a reason why this patch continues to be included in what is
otherwise a clk driver patch series? Can this patch be sent separately
from the clk patches (and not Cced to clk maintainers/list) in the
future?
Quoting Melody Olvera (2022-10-27 14:31:08)
>
>
> On 10/27/2022 11:22 AM, Stephen Boyd wrote:
> > Quoting Melody Olvera (2022-10-26 12:04:41)
> >> Add compatible fields for QDU1000 and QRU1000 pdcs.
> >>
> >> Signed-off-by: Melody Olvera <[email protected]>
> >> ---
> > Is there a reason why this patch continues to be included in what is
> > otherwise a clk driver patch series? Can this patch be sent separately
> > from the clk patches (and not Cced to clk maintainers/list) in the
> > future?
> Sure thing. On reflection, this belongs with the misc support patches.
>
Thanks!
On 10/27/2022 11:22 AM, Stephen Boyd wrote:
> Quoting Melody Olvera (2022-10-26 12:04:41)
>> Add compatible fields for QDU1000 and QRU1000 pdcs.
>>
>> Signed-off-by: Melody Olvera <[email protected]>
>> ---
> Is there a reason why this patch continues to be included in what is
> otherwise a clk driver patch series? Can this patch be sent separately
> from the clk patches (and not Cced to clk maintainers/list) in the
> future?
Sure thing. On reflection, this belongs with the misc support patches.
Thanks,
Melody
On Thu, Oct 27, 2022 at 02:31:08PM -0700, Melody Olvera wrote:
>
>
> On 10/27/2022 11:22 AM, Stephen Boyd wrote:
> > Quoting Melody Olvera (2022-10-26 12:04:41)
> >> Add compatible fields for QDU1000 and QRU1000 pdcs.
> >>
> >> Signed-off-by: Melody Olvera <[email protected]>
> >> ---
> > Is there a reason why this patch continues to be included in what is
> > otherwise a clk driver patch series? Can this patch be sent separately
> > from the clk patches (and not Cced to clk maintainers/list) in the
> > future?
> Sure thing. On reflection, this belongs with the misc support patches.
>
Even better, the "misc" series goes through my tree but this patch is
unrelated. So if you send it on it's own it could just be picked up by
the PDC maintainer (or Rob).
Regards,
Bjorn
On 11/7/2022 9:16 AM, Bjorn Andersson wrote:
> On Thu, Oct 27, 2022 at 02:31:08PM -0700, Melody Olvera wrote:
>>
>> On 10/27/2022 11:22 AM, Stephen Boyd wrote:
>>> Quoting Melody Olvera (2022-10-26 12:04:41)
>>>> Add compatible fields for QDU1000 and QRU1000 pdcs.
>>>>
>>>> Signed-off-by: Melody Olvera <[email protected]>
>>>> ---
>>> Is there a reason why this patch continues to be included in what is
>>> otherwise a clk driver patch series? Can this patch be sent separately
>>> from the clk patches (and not Cced to clk maintainers/list) in the
>>> future?
>> Sure thing. On reflection, this belongs with the misc support patches.
>>
> Even better, the "misc" series goes through my tree but this patch is
> unrelated. So if you send it on it's own it could just be picked up by
> the PDC maintainer (or Rob).
>
>
Sure thing. I'll just send each on their own.
Thanks,
Melody