From: Komal Bajaj <quic_kbajaj@quicinc.com>
To: Dmitry Baryshkov <dmitry.baryshkov@linaro.org>
Cc: <agross@kernel.org>, <andersson@kernel.org>,
<konrad.dybcio@linaro.org>, <robh+dt@kernel.org>,
<krzysztof.kozlowski+dt@linaro.org>, <conor+dt@kernel.org>,
<linux-arm-msm@vger.kernel.org>, <devicetree@vger.kernel.org>,
<linux-kernel@vger.kernel.org>
Subject: Re: [PATCH 1/2] arm64: dts: qcom: qdu1000-idp: Update reserved memory region
Date: Wed, 5 Jul 2023 12:36:45 +0530 [thread overview]
Message-ID: <db283531-36a2-0535-4fe2-d1571b3fa8cb@quicinc.com> (raw)
In-Reply-To: <CAA8EJpo406gV-5H8+y4SJbbRqnWFRo5wrR6a9KJ2arbN61tS2Q@mail.gmail.com>
On 7/5/2023 11:19 AM, Dmitry Baryshkov wrote:
> On Wed, 5 Jul 2023 at 08:40, Komal Bajaj <quic_kbajaj@quicinc.com> wrote:
>> Add missing reserved regions as described in QDU1000 memory map.
>>
>> Signed-off-by: Komal Bajaj <quic_kbajaj@quicinc.com>
>> ---
>> arch/arm64/boot/dts/qcom/qdu1000-idp.dts | 26 ++++++++++++++++++++++++
>> 1 file changed, 26 insertions(+)
>>
>> diff --git a/arch/arm64/boot/dts/qcom/qdu1000-idp.dts b/arch/arm64/boot/dts/qcom/qdu1000-idp.dts
>> index 1d22f87fd238..3f5512ec0a90 100644
>> --- a/arch/arm64/boot/dts/qcom/qdu1000-idp.dts
>> +++ b/arch/arm64/boot/dts/qcom/qdu1000-idp.dts
>> @@ -448,6 +448,32 @@ &qupv3_id_0 {
>> status = "okay";
>> };
>>
>> +&reserved_memory{
>> + #address-cells = <2>;
>> + #size-cells = <2>;
>> + ranges;
>> +
>> + ecc_meta_data_reserved_mem:ecc_meta_data_reserved_region@e0000000{
> no_underscores_in_node_names. Ever.
>
> Also, if you have checked other platforms, you'd have seen that other
> platforms use a much more generic node name for 'memory' nodes (which
> you should have used too).
These memory nodes are new to QDU platform, so will it be okay if I keep
these names without region suffix?
Thanks
Komal
>
>> + no-map;
>> + reg = <0x0 0xe0000000 0x0 0x20000000>;
>> + };
>> +
>> + harq_buffer_mem:harq_buffer_region@800000000{
>> + no-map;
>> + reg = <0x8 0x0 0x0 0x80000000>;
>> + };
>> +
>> + tenx_sp_buffer_mem:tenx_sp_buffer_region@880000000{
>> + no-map;
>> + reg = <0x8 0x80000000 0x0 0x50000000>;
>> + };
>> +
>> + fapi_buffer_mem:fapi_buffer_region@8d0000000{
>> + no-map;
>> + reg = <0x8 0xd0000000 0x0 0x20000000>;
>> + };
>> +};
>> +
>> &sdhc {
>> pinctrl-0 = <&sdc_on_state>;
>> pinctrl-1 = <&sdc_off_state>;
>> --
>> 2.40.1
>>
>
next prev parent reply other threads:[~2023-07-05 7:07 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-07-05 5:39 [PATCH 0/2] arm64: dts: qcom: qdu1000: " Komal Bajaj
2023-07-05 5:39 ` [PATCH 1/2] arm64: dts: qcom: qdu1000-idp: " Komal Bajaj
2023-07-05 5:49 ` Dmitry Baryshkov
2023-07-05 7:06 ` Komal Bajaj [this message]
2023-07-05 9:42 ` Dmitry Baryshkov
2023-07-05 11:02 ` Komal Bajaj
2023-07-05 11:08 ` Konrad Dybcio
2023-07-05 14:19 ` Krzysztof Kozlowski
2023-07-05 6:13 ` Krzysztof Kozlowski
2023-07-05 5:39 ` [PATCH 2/2] arm64: dts: qcom: qru1000-idp: " Komal Bajaj
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=db283531-36a2-0535-4fe2-d1571b3fa8cb@quicinc.com \
--to=quic_kbajaj@quicinc.com \
--cc=agross@kernel.org \
--cc=andersson@kernel.org \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=dmitry.baryshkov@linaro.org \
--cc=konrad.dybcio@linaro.org \
--cc=krzysztof.kozlowski+dt@linaro.org \
--cc=linux-arm-msm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=robh+dt@kernel.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
all inboxes | Powered by JetHome®