devicetree.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Krzysztof Kozlowski <krzysztof.kozlowski@linaro.org>
To: Ninad Naik <quic_ninanaik@quicinc.com>,
	andersson@kernel.org, konrad.dybcio@linaro.org,
	robh+dt@kernel.org, krzysztof.kozlowski+dt@linaro.org,
	conor+dt@kernel.org
Cc: linux-arm-msm@vger.kernel.org, devicetree@vger.kernel.org,
	quic_psodagud@quicinc.com, quic_kprasan@quicinc.com,
	quic_ymg@quicinc.com, kernel@quicinc.com
Subject: Re: [PATCH] arm64: dts: qcom: sa8775p: Add new memory map updates to SA8775P
Date: Tue, 23 Jan 2024 09:26:47 +0100	[thread overview]
Message-ID: <e4fe77d6-2762-4fe1-a68b-e7d152d22efd@linaro.org> (raw)
In-Reply-To: <20240118155711.7601-1-quic_ninanaik@quicinc.com>

On 18/01/2024 16:57, Ninad Naik wrote:
> New memory map layout changes (by Qualcomm firmware) have brought
> in updates to base addresses and/or size for different memory regions
> like cpcucp_fw, tz-stat, and also introduces new memory regions for
> resource manager firmware. This change brings in these corresponding
> memory map updates to the SA8775P SoC device tree.
> 
> Signed-off-by: Ninad Naik <quic_ninanaik@quicinc.com>
> ---
>  arch/arm64/boot/dts/qcom/sa8775p.dtsi | 103 +++++++++++++++++++++++---
>  1 file changed, 94 insertions(+), 9 deletions(-)
> 
> diff --git a/arch/arm64/boot/dts/qcom/sa8775p.dtsi b/arch/arm64/boot/dts/qcom/sa8775p.dtsi
> index a7eaca33d326..20b16fb5f537 100644
> --- a/arch/arm64/boot/dts/qcom/sa8775p.dtsi
> +++ b/arch/arm64/boot/dts/qcom/sa8775p.dtsi
> @@ -356,13 +356,18 @@ uefi_log: uefi-log@908b0000 {
>  			no-map;
>  		};
>  
> +		ddr_training_checksum: ddr_training_checksum@908c0000 {

Underscores are not allowed. Please rewrite downstream patches to match
upstream code.

Also, useful is to run basic tests/tools on your patches, like W=1
builds, before posting.

Best regards,
Krzysztof


  parent reply	other threads:[~2024-01-23  8:26 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-01-18 15:57 [PATCH] arm64: dts: qcom: sa8775p: Add new memory map updates to SA8775P Ninad Naik
2024-01-18 20:28 ` Brian Masney
2024-01-23  8:25   ` Krzysztof Kozlowski
2024-01-18 23:58 ` Eric Chanudet
2024-01-19 19:11   ` Bjorn Andersson
2024-01-19 20:35     ` Dmitry Baryshkov
2024-01-22 13:45       ` Brian Masney
2024-01-22 20:02         ` Bjorn Andersson
2024-01-23  0:41           ` Brian Masney
2024-01-23  2:58           ` Trilok Soni
2024-01-23  6:23             ` Dmitry Baryshkov
2024-01-23 16:02               ` Bjorn Andersson
2024-01-23 16:53                 ` Dmitry Baryshkov
2024-01-25  6:05               ` Trilok Soni
2024-01-25  9:53                 ` Konrad Dybcio
2024-01-22 21:15         ` Dmitry Baryshkov
2024-01-19 23:14     ` Eric Chanudet
2024-01-23  8:26 ` Krzysztof Kozlowski [this message]
2024-01-23 10:15   ` Ninad Naik

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=e4fe77d6-2762-4fe1-a68b-e7d152d22efd@linaro.org \
    --to=krzysztof.kozlowski@linaro.org \
    --cc=andersson@kernel.org \
    --cc=conor+dt@kernel.org \
    --cc=devicetree@vger.kernel.org \
    --cc=kernel@quicinc.com \
    --cc=konrad.dybcio@linaro.org \
    --cc=krzysztof.kozlowski+dt@linaro.org \
    --cc=linux-arm-msm@vger.kernel.org \
    --cc=quic_kprasan@quicinc.com \
    --cc=quic_ninanaik@quicinc.com \
    --cc=quic_psodagud@quicinc.com \
    --cc=quic_ymg@quicinc.com \
    --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;
as well as URLs for NNTP newsgroup(s).