Re: [PATCH v2 1/2] dt-bindings: arm: qcom: Add monaco-evk-ac support

[Dmitry Baryshkov]

On Fri, Apr 03, 2026 at 04:14:28PM +0530, Umang Chheda wrote:
> Hello Dmitry,
> 
> On 4/1/2026 5:06 PM, Dmitry Baryshkov wrote:
> > On Wed, Apr 01, 2026 at 12:14:42AM +0530, Umang Chheda wrote:
> >> Introduce bindings for the monaco-evk-ac IoT board, which is
> >> based on the monaco-ac (QCS8300-AC) SoC variant.
> > 
> > If it is a different SoC SKU, should it be reflected in the SoC compat
> > strings?
> 
> Monaco‑AC does not introduce any S/W differences compared to Monaco SoC
> -- All IP blocks and bindings remain identical from S/W PoV, Hence
> haven't included the SoC SKU in the SoC compat strings.
> 
> Hope this is okay ? Your view on this ?

You are descibing -AC as the main difference between the kits, but then
you say that -AC doesn't bring new software interfaces. What is the
difference then between monako-evk and the -ac variant?

Also, from the naming point of view, it is monako-ac-evk, not the other
way.

> 
> > 
> >>
> >> Signed-off-by: Umang Chheda <umang.chheda@xxxxxxxxxxxxxxxx>
> >> ---
> >>  Documentation/devicetree/bindings/arm/qcom.yaml | 1 +
> >>  1 file changed, 1 insertion(+)
> >>
> >> diff --git a/Documentation/devicetree/bindings/arm/qcom.yaml b/Documentation/devicetree/bindings/arm/qcom.yaml
> >> index ca880c105f3b..c76365a89687 100644
> >> --- a/Documentation/devicetree/bindings/arm/qcom.yaml
> >> +++ b/Documentation/devicetree/bindings/arm/qcom.yaml
> >> @@ -918,6 +918,7 @@ properties:
> >>            - enum:
> >>                - arduino,monza
> >>                - qcom,monaco-evk
> >> +              - qcom,monaco-evk-ac
> >>                - qcom,qcs8300-ride
> >>            - const: qcom,qcs8300
> >>  
> >>
> >> -- 
> >> 2.34.1
> >>
> > 
> 
> Thanks,
> Umang

-- 
With best wishes
Dmitry