From: Stephen Boyd <sboyd@kernel.org>
To: Mohammad Rafi Shaik <quic_mohs@quicinc.com>,
agross@kernel.org, andersson@kernel.org, broonie@kernel.org,
konrad.dybcio@somainline.org, krzysztof.kozlowski+dt@linaro.org,
linux-arm-msm@vger.kernel.org, linux-clk@vger.kernel.org,
linux-kernel@vger.kernel.org, mturquette@baylibre.com,
quic_plai@quicinc.com, quic_rohkumar@quicinc.com,
quic_visr@quicinc.com, robh+dt@kernel.org, swboyd@chromium.org
Subject: Re: [PATCH v1 0/4] Remove the qdsp6ss register from lpasscc
Date: Tue, 28 Mar 2023 10:41:59 -0700 [thread overview]
Message-ID: <5c89937f7b208e872af58636933194a0.sboyd@kernel.org> (raw)
In-Reply-To: <fb9712fc-d103-769c-2ed7-51a08bbe76b2@quicinc.com>
Quoting Mohammad Rafi Shaik (2023-03-27 23:02:38)
>
> On 3/27/2023 11:11 PM, Stephen Boyd wrote:
> > Quoting Mohammad Rafi Shaik (2023-03-27 09:32:45)
> >> This patch set is to remove the qdsp6ss register from lpasscc to
> >> resolve memory conflict's between lpascc and ADSP remoteproc driver.
> > Is this related to the other patch series[1] ("[PATCH v9 0/4] Add resets
> > for ADSP based audio clock controller driver")? Does it supersede those?
> Thanks for comment,
>
> yes, its superseded form patch series[1] ("[PATCH v9 0/4] Add resets
> for ADSP based audio clock controller driver") which is required many
> changes.
>
> As the qdsp6ss clocks are being enabled in remoteproc driver,
> the qdsp6ss not required in lpasscc node.
>
> For audioreach solution required to create the remoteproc_adsp
> device tree node with base address 0x3000000 for remoteproc driver,
> as already this address being used in lpasscc node it's causing memory
> conflict.
Ok. Please add the details of superseded patch series to the cover
letter. It helps us understand what to do with the other patches on the
list.
prev parent reply other threads:[~2023-03-28 17:42 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-03-27 16:32 [PATCH v1 0/4] Remove the qdsp6ss register from lpasscc Mohammad Rafi Shaik
2023-03-27 16:32 ` [PATCH v1 1/4] arm64: dts: qcom: sc7280: Modify lpasscc node name Mohammad Rafi Shaik
2023-03-27 16:32 ` [PATCH v1 2/4] dt-bindings: clock: qcom,sc7280-lpasscc: Remove qdsp6ss register region Mohammad Rafi Shaik
2023-03-31 9:29 ` Krzysztof Kozlowski
2023-03-27 16:32 ` [PATCH v1 3/4] arm64: dts: qcom: sc7280: Remove qdsp6ss regmap region Mohammad Rafi Shaik
2023-03-27 16:32 ` [PATCH v1 4/4] clk: qcom: lpasscc-sc7280: Remove qdsp6ss clock registration Mohammad Rafi Shaik
2023-03-29 3:11 ` Stephen Boyd
2023-03-29 9:24 ` Mohammad Rafi Shaik
2023-03-29 17:57 ` Stephen Boyd
2023-03-31 9:30 ` Krzysztof Kozlowski
2023-03-27 17:41 ` [PATCH v1 0/4] Remove the qdsp6ss register from lpasscc Stephen Boyd
2023-03-28 6:02 ` Mohammad Rafi Shaik
2023-03-28 17:41 ` Stephen Boyd [this message]
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=5c89937f7b208e872af58636933194a0.sboyd@kernel.org \
--to=sboyd@kernel.org \
--cc=agross@kernel.org \
--cc=andersson@kernel.org \
--cc=broonie@kernel.org \
--cc=konrad.dybcio@somainline.org \
--cc=krzysztof.kozlowski+dt@linaro.org \
--cc=linux-arm-msm@vger.kernel.org \
--cc=linux-clk@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mturquette@baylibre.com \
--cc=quic_mohs@quicinc.com \
--cc=quic_plai@quicinc.com \
--cc=quic_rohkumar@quicinc.com \
--cc=quic_visr@quicinc.com \
--cc=robh+dt@kernel.org \
--cc=swboyd@chromium.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