| Message ID | 20230720075731.20816-2-quic_harihk@quicinc.com (mailing list archive) |
|---|---|
| State | Superseded |
| Headers | show |
| Series | Add initial support for RDP434 of IPQ5018 family | expand |
On 20/07/2023 09:57, Hariharan K wrote: > Document the MP03.6-C2 (Reference Design Platform 434) board > based on IPQ5018 family of SoCs. > > Signed-off-by: Hariharan K <quic_harihk@quicinc.com> > --- > Documentation/devicetree/bindings/arm/qcom.yaml | 2 ++ > 1 file changed, 2 insertions(+) > > diff --git a/Documentation/devicetree/bindings/arm/qcom.yaml b/Documentation/devicetree/bindings/arm/qcom.yaml > index 922feb912594..2a18bb881624 100644 > --- a/Documentation/devicetree/bindings/arm/qcom.yaml > +++ b/Documentation/devicetree/bindings/arm/qcom.yaml > @@ -98,6 +98,7 @@ description: | > ap-mi01.6 > ap-mi01.9 > ap-mp03.5-c2 > + ap-mp03.6-c2 > cdp > cp01-c1 > dragonboard > @@ -344,6 +345,7 @@ properties: > - items: > - enum: > - qcom,ipq5018-ap-mp03.5-c2 > + - qcom,ipq5018-ap-mp03.6-c2 Really, how do you see it being applied? You sent multiple conflicting patches. Now, clone the kernel tree and use b4 to apply one patchset. Then apply next one. Then next and next. Did it succeed? Best regards, Krzysztof
On 7/20/2023 2:30 PM, Krzysztof Kozlowski wrote: > On 20/07/2023 09:57, Hariharan K wrote: >> Document the MP03.6-C2 (Reference Design Platform 434) board >> based on IPQ5018 family of SoCs. >> >> Signed-off-by: Hariharan K <quic_harihk@quicinc.com> >> --- >> Documentation/devicetree/bindings/arm/qcom.yaml | 2 ++ >> 1 file changed, 2 insertions(+) >> >> diff --git a/Documentation/devicetree/bindings/arm/qcom.yaml b/Documentation/devicetree/bindings/arm/qcom.yaml >> index 922feb912594..2a18bb881624 100644 >> --- a/Documentation/devicetree/bindings/arm/qcom.yaml >> +++ b/Documentation/devicetree/bindings/arm/qcom.yaml >> @@ -98,6 +98,7 @@ description: | >> ap-mi01.6 >> ap-mi01.9 >> ap-mp03.5-c2 >> + ap-mp03.6-c2 >> cdp >> cp01-c1 >> dragonboard >> @@ -344,6 +345,7 @@ properties: >> - items: >> - enum: >> - qcom,ipq5018-ap-mp03.5-c2 >> + - qcom,ipq5018-ap-mp03.6-c2 > > Really, how do you see it being applied? You sent multiple conflicting > patches. Now, clone the kernel tree and use b4 to apply one patchset. > Then apply next one. Then next and next. > > Did it succeed? > Sorry, will logically group the patches and post in next series. Best regards, Hariharan K > Best regards, > Krzysztof >
diff --git a/Documentation/devicetree/bindings/arm/qcom.yaml b/Documentation/devicetree/bindings/arm/qcom.yaml index 922feb912594..2a18bb881624 100644 --- a/Documentation/devicetree/bindings/arm/qcom.yaml +++ b/Documentation/devicetree/bindings/arm/qcom.yaml @@ -98,6 +98,7 @@ description: | ap-mi01.6 ap-mi01.9 ap-mp03.5-c2 + ap-mp03.6-c2 cdp cp01-c1 dragonboard @@ -344,6 +345,7 @@ properties: - items: - enum: - qcom,ipq5018-ap-mp03.5-c2 + - qcom,ipq5018-ap-mp03.6-c2 - const: qcom,ipq5018 - items:
Document the MP03.6-C2 (Reference Design Platform 434) board based on IPQ5018 family of SoCs. Signed-off-by: Hariharan K <quic_harihk@quicinc.com> --- Documentation/devicetree/bindings/arm/qcom.yaml | 2 ++ 1 file changed, 2 insertions(+)