mbox series

[0/2] Add initial support for RDP434 of IPQ5018 family

Message ID 20230720075731.20816-1-quic_harihk@quicinc.com
Headers show
Series Add initial support for RDP434 of IPQ5018 family | expand

Message

Hariharan K July 20, 2023, 7:57 a.m. UTC
Add the initial device tree support for the Reference Design
Platform(RDP) 434 based on IPQ5018 family of SoC. This patch
carries the support for Console UART and eMMC.

This series is based on the below two series,
https://lore.kernel.org/lkml/20230720072938.315
46-1-quic_harihk@quicinc.com/

Hariharan K (2):
  dt-bindings: arm: qcom: Document MP03.6-C2 board based on IPQ5018
    family
  arm64: dts: qcom: ipq5018: add support for the RDP434 variant

 .../devicetree/bindings/arm/qcom.yaml         |  2 +
 arch/arm64/boot/dts/qcom/Makefile             |  1 +
 arch/arm64/boot/dts/qcom/ipq5018-rdp434.dts   | 49 +++++++++++++++++++
 3 files changed, 52 insertions(+)
 create mode 100644 arch/arm64/boot/dts/qcom/ipq5018-rdp434.dts

Comments

Krzysztof Kozlowski July 20, 2023, 9 a.m. UTC | #1
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
Hariharan K July 20, 2023, 11:23 a.m. UTC | #2
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
>