From: Konrad Dybcio <konrad.dybcio@linaro.org>
To: Naina Mehta <quic_nainmeht@quicinc.com>,
andersson@kernel.org, mathieu.poirier@linaro.org,
robh@kernel.org, krzk+dt@kernel.org, conor+dt@kernel.org,
manivannan.sadhasivam@linaro.org
Cc: linux-arm-msm@vger.kernel.org, linux-remoteproc@vger.kernel.org,
devicetree@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH v2 3/5] arm64: dts: qcom: sdx75: add missing qlink_logging reserved memory for mpss
Date: Mon, 17 Jun 2024 19:33:22 +0200 [thread overview]
Message-ID: <a31a2f94-d125-48fa-8e57-7aedee98063e@linaro.org> (raw)
In-Reply-To: <20240617093428.3616194-4-quic_nainmeht@quicinc.com>
On 6/17/24 11:34, Naina Mehta wrote:
> The qlink_logging memory region is also used by the modem firmware,
> add it to reserved memory regions.
> Also split MPSS DSM region into 2 separate regions.
>
> Signed-off-by: Naina Mehta <quic_nainmeht@quicinc.com>
> ---
The commit message is very misleading.. You're not adding
qlink_logging, you're renaming qdss@8800000 to qlink_logging.
Then, you add qdss_mem @ 88500000 and split the dsmharq_mem into two
and shrink mpssadsp_mem.
Please rewrite the commit message.
Konrad
next prev parent reply other threads:[~2024-06-17 17:33 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-06-17 9:34 [PATCH v2 0/5] Add MPSS remoteproc support for SDX75 Naina Mehta
2024-06-17 9:34 ` [PATCH v2 1/5] dt-bindings: remoteproc: qcom,sm8550-pas: document the SDX75 PAS Naina Mehta
2024-06-17 12:22 ` Krzysztof Kozlowski
2024-06-17 9:34 ` [PATCH v2 2/5] remoteproc: qcom: pas: Add SDX75 remoteproc support Naina Mehta
2024-06-17 9:34 ` [PATCH v2 3/5] arm64: dts: qcom: sdx75: add missing qlink_logging reserved memory for mpss Naina Mehta
2024-06-17 17:33 ` Konrad Dybcio [this message]
2024-06-17 9:34 ` [PATCH v2 4/5] arm64: dts: qcom: sdx75: Add remoteproc node Naina Mehta
2024-06-17 10:02 ` Dmitry Baryshkov
2024-06-17 9:34 ` [PATCH v2 5/5] arm64: dts: qcom: sdx75-idp: enable MPSS " Naina Mehta
2024-06-17 10:02 ` Dmitry Baryshkov
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=a31a2f94-d125-48fa-8e57-7aedee98063e@linaro.org \
--to=konrad.dybcio@linaro.org \
--cc=andersson@kernel.org \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=krzk+dt@kernel.org \
--cc=linux-arm-msm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-remoteproc@vger.kernel.org \
--cc=manivannan.sadhasivam@linaro.org \
--cc=mathieu.poirier@linaro.org \
--cc=quic_nainmeht@quicinc.com \
--cc=robh@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 read-only IMAP folder(s) and NNTP newsgroup(s).