[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <5c89937f7b208e872af58636933194a0.sboyd@kernel.org>
Date: Tue, 28 Mar 2023 10:41:59 -0700
From: Stephen Boyd <sboyd@...nel.org>
To: Mohammad Rafi Shaik <quic_mohs@...cinc.com>, agross@...nel.org,
andersson@...nel.org, broonie@...nel.org,
konrad.dybcio@...ainline.org, krzysztof.kozlowski+dt@...aro.org,
linux-arm-msm@...r.kernel.org, linux-clk@...r.kernel.org,
linux-kernel@...r.kernel.org, mturquette@...libre.com,
quic_plai@...cinc.com, quic_rohkumar@...cinc.com,
quic_visr@...cinc.com, robh+dt@...nel.org, swboyd@...omium.org
Subject: Re: [PATCH v1 0/4] Remove the qdsp6ss register from lpasscc
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.
Powered by blists - more mailing lists