From: Sibi Sankar <quic_sibis@quicinc.com>
To: Konrad Dybcio <konrad.dybcio@linaro.org>, <andersson@kernel.org>,
<robh+dt@kernel.org>, <krzysztof.kozlowski+dt@linaro.org>,
<catalin.marinas@arm.com>, <ulf.hansson@linaro.org>
Cc: <agross@kernel.org>, <conor+dt@kernel.org>,
<ayan.kumar.halder@amd.com>, <j@jannau.net>,
<dmitry.baryshkov@linaro.org>, <nfraprado@collabora.com>,
<m.szyprowski@samsung.com>, <u-kumar1@ti.com>, <peng.fan@nxp.com>,
<lpieralisi@kernel.org>, <quic_rjendra@quicinc.com>,
<abel.vesa@linaro.org>, <linux-arm-msm@vger.kernel.org>,
<devicetree@vger.kernel.org>, <linux-kernel@vger.kernel.org>,
<linux-arm-kernel@lists.infradead.org>, <quic_tsoni@quicinc.com>,
<neil.armstrong@linaro.org>
Subject: Re: [PATCH 3/5] arm64: dts: qcom: Add base SC8380XP dtsi and the QCP dts
Date: Fri, 17 Nov 2023 09:46:30 +0530 [thread overview]
Message-ID: <ece6fb69-b313-a47d-24b3-af4077f09cc3@quicinc.com> (raw)
In-Reply-To: <f3661605-ea2f-4681-8486-b83bd042568c@linaro.org>
Hey Konrad,
On 10/26/23 16:06, Konrad Dybcio wrote:
>
>
> On 10/25/23 16:24, Sibi Sankar wrote:
>> From: Rajendra Nayak <quic_rjendra@quicinc.com>
>>
>> Add base dtsi and QCP board (Qualcomm Compute Platform) dts file for
>> SC8380XP SoC, describing the CPUs, GCC and RPMHCC clock controllers,
>> geni UART, interrupt controller, TLMM, reserved memory, interconnects,
>> SMMU and LLCC nodes.
>>
>> Co-developed-by: Abel Vesa <abel.vesa@linaro.org>
>> Signed-off-by: Abel Vesa <abel.vesa@linaro.org>
>> Signed-off-by: Rajendra Nayak <quic_rjendra@quicinc.com>
>> Co-developed-by: Sibi Sankar <quic_sibis@quicinc.com>
>> Signed-off-by: Sibi Sankar <quic_sibis@quicinc.com>
>> ---
> [...]
>
>> +&tlmm {
>> + gpio-reserved-ranges = <33 3>, <44 4>, <238 1>;
> It would be really cool if you added an explanation on why these
> GPIOs need to be reserved, especially since you can see what's
> connected on there on schematics. So, like:
>
> gpio-reserved-ranges = <33 3>, /* something */
> <44 4>, /* something else (fp scanner?)
> <238 1>; /* UFS reset? */
will do.
>
>
> [...]
>
>> + compatible = "qcom,oryon";
> Again, this compatible won't fly unless all of these cores
> are totally identical and Oryon is only a name for this
> generation on this SoC (which I believe not to be the case).
>
>> + reg = <0x0 0x0>;
>> + enable-method = "psci";
>> + next-level-cache = <&L1_0>;
>> +
>> + L1_0: l1-cache {
>> + compatible = "cache";
> I'm not sure if L1 is supposed to be described in the DT,
> Krzysztof should know.
>
>> + next-level-cache = <&L2_0>;
>> +
>> + L2_0: l2-cache-0 {
>> + compatible = "cache";
> cache-level?
> cache-unified?
ack will remove the l1 and use ^^ appropriately.
>
> [...]
>
>> + memory@80000000 {
>> + device_type = "memory";
>> + /* We expect the bootloader to fill in the size */
>> + reg = <0 0x80000000 0 0x80000000>;
> That contradicts the comment you made above. Plus, 2 GiB seems a
> bit low for this SoC :D
will fix this.
>
> [...]
>
>> + gunyah_hyp_mem: gunyah-hyp-region@80000000 {
> you can probably strip the "-region" part, as this is implied by
> being a child of /reserved-memory
ok, will do but all the previous SoCs do it differently.
>
>> + pld_pep_mem: pld-pep-region@81f30000 {
> What's PLD?
>
> What's this region used for? PEP is a Windows invention.
>
We list all the possible reserved memory regions from the reference doc.
I can remove the unused regions in the platforms dts later once this
series lands.
> [...]
>
>> + av1_encoder_mem: av1-encoder-region@8e900000 {
> Is AV1enc hardware separate from iris?
no, it isn't separate from iris AFAIK.
>
> [...]
>
>> + gcc: clock-controller@100000 {
>> + compatible = "qcom,sc8380xp-gcc";
>> + reg = <0 0x100000 0 0x200000>;
> The address part of reg should be padded to 8 hex digits.
thanks for catching this.
>
>> +
>> + interconnects = <&clk_virt MASTER_QUP_CORE_2 0
>> &clk_virt SLAVE_QUP_CORE_2 0>,
> QCOM_ICC_TAG_ALWAYS would be nicer than 0 (see sa8775p)
will do.
>
> [...]
>
>> +
>> + interrupts = <GIC_SPI 65 IRQ_TYPE_LEVEL_HIGH>,
> One space after and before '='
ack
>
> Konrad
next prev parent reply other threads:[~2023-11-17 4:17 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-10-25 14:24 [PATCH 0/5] dts: qcom: Introduce SC8380XP platforms device tree Sibi Sankar
2023-10-25 14:24 ` [PATCH 1/5] dt-bindings: arm: cpus: Add qcom,oryon compatible Sibi Sankar
2023-10-26 10:23 ` Konrad Dybcio
2023-10-25 14:24 ` [PATCH 2/5] dt-bindings: arm: qcom: Document SC8380XP SoC and boards Sibi Sankar
2023-10-26 10:24 ` Konrad Dybcio
2023-11-17 4:05 ` Sibi Sankar
2023-10-27 8:16 ` Krzysztof Kozlowski
2023-11-17 4:07 ` Sibi Sankar
2023-10-25 14:24 ` [PATCH 3/5] arm64: dts: qcom: Add base SC8380XP dtsi and the QCP dts Sibi Sankar
2023-10-26 10:36 ` Konrad Dybcio
2023-11-17 4:16 ` Sibi Sankar [this message]
2023-10-26 18:05 ` kernel test robot
2023-10-25 14:24 ` [PATCH 4/5] arm64: dts: qcom: sc8380xp: Add Compute Reference Device Sibi Sankar
2023-10-26 10:38 ` Konrad Dybcio
2023-11-17 4:17 ` Sibi Sankar
2023-10-25 14:24 ` [PATCH 5/5] arm64: defconfig: Enable SC8380XP SoC base configs Sibi Sankar
2023-10-26 10:55 ` Konrad Dybcio
2023-11-17 4:18 ` Sibi Sankar
2023-10-27 8:18 ` Krzysztof Kozlowski
2023-11-17 4:19 ` Sibi Sankar
2023-10-30 16:00 ` [PATCH 0/5] dts: qcom: Introduce SC8380XP platforms device tree Abel Vesa
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=ece6fb69-b313-a47d-24b3-af4077f09cc3@quicinc.com \
--to=quic_sibis@quicinc.com \
--cc=abel.vesa@linaro.org \
--cc=agross@kernel.org \
--cc=andersson@kernel.org \
--cc=ayan.kumar.halder@amd.com \
--cc=catalin.marinas@arm.com \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=dmitry.baryshkov@linaro.org \
--cc=j@jannau.net \
--cc=konrad.dybcio@linaro.org \
--cc=krzysztof.kozlowski+dt@linaro.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-arm-msm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=lpieralisi@kernel.org \
--cc=m.szyprowski@samsung.com \
--cc=neil.armstrong@linaro.org \
--cc=nfraprado@collabora.com \
--cc=peng.fan@nxp.com \
--cc=quic_rjendra@quicinc.com \
--cc=quic_tsoni@quicinc.com \
--cc=robh+dt@kernel.org \
--cc=u-kumar1@ti.com \
--cc=ulf.hansson@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).