devicetree.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Konrad Dybcio <konrad.dybcio@linaro.org>
To: Krzysztof Kozlowski <krzysztof.kozlowski@linaro.org>,
	Andy Gross <agross@kernel.org>,
	Bjorn Andersson <andersson@kernel.org>,
	Rob Herring <robh+dt@kernel.org>,
	Krzysztof Kozlowski <krzysztof.kozlowski+dt@linaro.org>,
	Robert Marko <robimarko@gmail.com>,
	Das Srinagesh <quic_gurus@quicinc.com>
Cc: Bhupesh Sharma <bhupesh.sharma@linaro.org>,
	Vladimir Zapolskiy <vladimir.zapolskiy@linaro.org>,
	Marijn Suijten <marijn.suijten@somainline.org>,
	linux-arm-msm@vger.kernel.org, devicetree@vger.kernel.org,
	linux-kernel@vger.kernel.org
Subject: Re: [PATCH 3/9] arm64: dts: qcom: Add initial QCM2290, PM2250 & RB1 device trees
Date: Tue, 4 Apr 2023 11:47:17 +0200	[thread overview]
Message-ID: <b99e4236-de56-95e4-f1a1-db52238e937f@linaro.org> (raw)
In-Reply-To: <e1c2605c-6976-4d3e-25c8-e71145eea518@linaro.org>



On 4.04.2023 08:06, Krzysztof Kozlowski wrote:
> On 03/04/2023 19:36, Konrad Dybcio wrote:
>> Add initial device trees for the QCM2290 SoC, QC Robotics RB1 board, as
>> well as the bundled PM2250 PMIC.
>>
>> On the SoC part, CA53 compatibles were used, as Qualcomm claims that's
>> what has been implemented, despite the cores reporting a Qualcomm Kryo
>> MIDR_EL1[PART_NUM].
>>
>> To get a successful boot on RB1, run:
>>
>> cat arch/arm64/boot/Image.gz arch/arm64/boot/dts/qcom/qrb2210-rb1.dtb >\
>> .Image.gz-dtb
>>
>> mkbootimg \
>>         --kernel .Image.gz-dtb \
>>         --ramdisk some_initrd \
>>         --output rb1-boot.img \
>>         --pagesize 4096 \
>>         --base 0x8000 \
>>         --cmdline 'some cmdline'
>>
>> fastboot boot rb1-boot.img
>>
>> There's no dtbo or other craziness to worry about.
>> For the best dev experience, you can erase boot and use fastboot boot
>> everytime, so that the bootloader doesn't mess with you.
>>
>> If you have a SoM revision 3 or older (there should be a sticker on it
>> with text like -r00, where r is the revision), you will need to apply
>> this additional diff:
>>
>>         aliases {
>> -               serial0 = &uart0;
>> +               serial0 = &uart4;
>>
>> /* UART connected to the Micro-USB port via a FTDI chip */
>> -&uart0 {
>> +&uart4 {
>>
>> That should however only concern preproduction boards.
>>
>> Signed-off-by: Konrad Dybcio <konrad.dybcio@linaro.org>
>> ---
[...]

>> @@ -0,0 +1,63 @@
>> +// SPDX-License-Identifier: (GPL-2.0+ OR BSD-3-Clause)
This I think can go BSD3

> 
> Odd license. Unless you based it on 2.0+, please use standard dual-license.

[...]
>> +	pmic@1 {
>> +		compatible = "qcom,pm2250", "qcom,spmi-pmic";
>> +		reg = <0x1 SPMI_USID>;
>> +		#address-cells = <1>;
>> +		#size-cells = <0>;
>> +	};
>> +};
>> \ No newline at end of file
> 
> Patch error to fix.
Ack.

> 
>> diff --git a/arch/arm64/boot/dts/qcom/qcm2290.dtsi b/arch/arm64/boot/dts/qcom/qcm2290.dtsi
>> new file mode 100644
>> index 000000000000..27d4742cdb19
>> --- /dev/null
>> +++ b/arch/arm64/boot/dts/qcom/qcm2290.dtsi
>> @@ -0,0 +1,848 @@
>> +// SPDX-License-Identifier: (GPL-2.0+ OR BSD-3-Clause)
> 
> Same concern. Also in DTS.
This was based off of sm6115 dtsi, which is dual-licensed.
I'm not a legal expert, not sure how much flexibility we
can get here.

Konrad
> 
> Best regards,
> Krzysztof
> 

  reply	other threads:[~2023-04-04  9:47 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-04-03 17:35 [PATCH 0/9] RB1 + QCM2290 support Konrad Dybcio
2023-04-03 17:35 ` [PATCH 1/9] dt-bindings: firmware: document Qualcomm QCM2290 SCM Konrad Dybcio
2023-04-04  6:02   ` Krzysztof Kozlowski
2023-04-03 17:36 ` [PATCH 2/9] dt-bindings: arm: qcom: Add QRB2210/QCM2290 and RB1 board Konrad Dybcio
2023-04-04  6:03   ` Krzysztof Kozlowski
2023-04-03 17:36 ` [PATCH 3/9] arm64: dts: qcom: Add initial QCM2290, PM2250 & RB1 device trees Konrad Dybcio
2023-04-04  6:06   ` Krzysztof Kozlowski
2023-04-04  9:47     ` Konrad Dybcio [this message]
2023-04-04 10:02       ` Krzysztof Kozlowski
2023-04-03 17:36 ` [PATCH 4/9] arm64: dts: qcom: qcm2290: Add most QUPs Konrad Dybcio
2023-04-03 17:36 ` [PATCH 5/9] arm64: dts: qcom: qcm2290: Add thermal zones Konrad Dybcio
2023-04-03 17:36 ` [PATCH 6/9] arm64: dts: qcom: qcm2290: Add SMP2P Konrad Dybcio
2023-04-03 17:36 ` [PATCH 7/9] arm64: dts: qcom: qcm2290: Add ADSP & modem Konrad Dybcio
2023-04-03 17:36 ` [PATCH 8/9] arm64: dts: qcom: qcm2290: Add WCN3990 Wi-Fi node Konrad Dybcio
2023-04-04  6:08   ` Krzysztof Kozlowski
2023-04-04  9:55     ` Konrad Dybcio
2023-04-04 10:04       ` Krzysztof Kozlowski
2023-04-04 10:05         ` Krzysztof Kozlowski
2023-04-03 17:36 ` [PATCH 9/9] arm64: dts: qcom: qrb2210-rb1: Enable RESIN Volume Down Konrad Dybcio

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=b99e4236-de56-95e4-f1a1-db52238e937f@linaro.org \
    --to=konrad.dybcio@linaro.org \
    --cc=agross@kernel.org \
    --cc=andersson@kernel.org \
    --cc=bhupesh.sharma@linaro.org \
    --cc=devicetree@vger.kernel.org \
    --cc=krzysztof.kozlowski+dt@linaro.org \
    --cc=krzysztof.kozlowski@linaro.org \
    --cc=linux-arm-msm@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=marijn.suijten@somainline.org \
    --cc=quic_gurus@quicinc.com \
    --cc=robh+dt@kernel.org \
    --cc=robimarko@gmail.com \
    --cc=vladimir.zapolskiy@linaro.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).