From: Sibi Sankar <sibis@codeaurora.org>
To: Stephen Boyd <swboyd@chromium.org>
Cc: Bjorn Andersson <bjorn.andersson@linaro.org>,
p.zabel@pengutronix.de, robh+dt@kernel.org, agross@kernel.org,
mani@kernel.org, linux-arm-msm@vger.kernel.org,
devicetree@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH 6/6] arm64: dts: qcom: sc7280: Add nodes to boot WPSS
Date: Mon, 19 Apr 2021 15:40:56 +0530 [thread overview]
Message-ID: <92f87f0b2a080077f426b7d704314e35@codeaurora.org> (raw)
In-Reply-To: <14476306c74356a747473e820d4067a6@codeaurora.org>
On 2021-03-24 12:19, Sibi Sankar wrote:
> On 2021-03-24 03:36, Stephen Boyd wrote:
>> Quoting Bjorn Andersson (2021-03-13 20:16:39)
>>> On Sat 13 Mar 15:46 CST 2021, Stephen Boyd wrote:
>>>
>>> > Quoting Sibi Sankar (2021-03-08 21:51:51)
>>> > > Add miscellaneous nodes to boot the Wireless Processor Subsystem on
>>> >
>>> > Maybe add (WPSS) after the name so we know they're related.
>>> >
>>> > > SC7280 SoCs.
>>> > >
>>> > > Signed-off-by: Sibi Sankar <sibis@codeaurora.org>
>>> > > ---
>>> > >
>>> > > https://patchwork.kernel.org/project/linux-arm-msm/list/?series=438217
>>> > > Depends on ipcc dt node enablement from ^^
>>> > >
>>> > > arch/arm64/boot/dts/qcom/sc7280.dtsi | 143 +++++++++++++++++++++++++++++++++++
>>> > > 1 file changed, 143 insertions(+)
>>> > >
>>> > > diff --git a/arch/arm64/boot/dts/qcom/sc7280.dtsi b/arch/arm64/boot/dts/qcom/sc7280.dtsi
>>> > > index 18637c369c1d..4f03c468df51 100644
>>> > > --- a/arch/arm64/boot/dts/qcom/sc7280.dtsi
>>> > > +++ b/arch/arm64/boot/dts/qcom/sc7280.dtsi
>>> > > @@ -244,12 +251,131 @@
>>> > > reg = <0 0x80000000 0 0>;
>>> > > };
>>> > >
>>> > > + tcsr_mutex: hwlock {
>>> > > + compatible = "qcom,tcsr-mutex";
>>> > > + syscon = <&tcsr_mutex_regs 0 0x1000>;
>>> > > + #hwlock-cells = <1>;
>>> > > + };
>>> >
>>> > Is this node in the right place? I think the node above it is 'memory'?
>>> > In which case 'hwlock' comes before 'memory' alphabetically.
>>> >
>>>
>>> Thanks for spotting this, as it's no longer acceptable to have a
>>> standalone "syscon" node I was asked to rewrite the binding for this
>>> a
>>> few months ago. So the tcsr_mutex should now be represented with a
>>> reg
>>> under /soc.
>>
>> Oh nice, I wasn't aware.
>>
>>> > > + #interrupt-cells = <2>;
>>> > > + };
>>> > > + };
>>> > > +
>>> > > + smp2p-mpss {
>>> > > + compatible = "qcom,smp2p";
>>> > > + qcom,smem = <435>, <428>;
>>> > > + interrupts-extended = <&ipcc IPCC_CLIENT_MPSS
>>> > > + IPCC_MPROC_SIGNAL_SMP2P
>>> > > + IRQ_TYPE_EDGE_RISING>;
>>> > > + mboxes = <&ipcc IPCC_CLIENT_MPSS
>>> > > + IPCC_MPROC_SIGNAL_SMP2P>;
>>> > > +
>>> > > + qcom,local-pid = <0>;
>>> > > + qcom,remote-pid = <1>;
>>> > > +
>>> > > + modem_smp2p_out: master-kernel {
>>> > > + qcom,entry-name = "master-kernel";
>>> > > + #qcom,smem-state-cells = <1>;
>>> > > + };
>>> > > +
>>> > > + modem_smp2p_in: slave-kernel {
>>> > > + qcom,entry-name = "slave-kernel";
>>> >
>>> > Do these names need to have 'master' and 'slave' in them? We're trying
>>> > to avoid these terms. See Documentation/process/coding-style.rst Section
>>> > 4 naming.
>>> >
>>>
>>> They need to match the naming in the firmware, but I would welcome a
>>> future change to something in line with the coding style and simply
>>> more
>>> descriptive.
>>>
>>
>> Sibi can this be done? I think it's still pretty early days for the
>> firmware so hopefully the terms can be replaced with something
>> different.
>
> I'll discuss the ask with the modem fw team and
> get back.
Sorry for the delayed response. Looks
like it's something Qualcomm wouldn't
want to do mid-project since a number
of the fw images are re-used across
platforms. But this is something that
will be taken up on newer SoCs.
--
Qualcomm Innovation Center, Inc. is a member of Code Aurora Forum,
a Linux Foundation Collaborative Project.
prev parent reply other threads:[~2021-04-19 10:11 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-03-09 5:51 [PATCH 0/6] Enable miscellaneous hardware blocks to boot WPSS Sibi Sankar
2021-03-09 5:51 ` [PATCH 1/6] soc: qcom: smem: Update max processor count Sibi Sankar
2021-03-13 21:36 ` Stephen Boyd
2021-03-09 5:51 ` [PATCH 2/6] dt-bindings: mailbox: Add WPSS client index to IPCC Sibi Sankar
2021-03-13 21:37 ` Stephen Boyd
2021-03-16 22:07 ` Rob Herring
2021-03-09 5:51 ` [PATCH 3/6] dt-bindings: reset: aoss: Add AOSS reset controller binding Sibi Sankar
2021-03-13 21:37 ` Stephen Boyd
2021-03-16 22:07 ` Rob Herring
2021-03-09 5:51 ` [PATCH 4/6] dt-bindings: reset: pdc: Add PDC Global bindings Sibi Sankar
2021-03-13 21:37 ` Stephen Boyd
2021-04-19 10:27 ` Sibi Sankar
2021-03-16 22:08 ` Rob Herring
2021-03-09 5:51 ` [PATCH 5/6] reset: qcom: Add PDC Global reset signals for WPSS Sibi Sankar
2021-03-13 21:40 ` Stephen Boyd
2021-03-09 5:51 ` [PATCH 6/6] arm64: dts: qcom: sc7280: Add nodes to boot WPSS Sibi Sankar
2021-03-13 21:46 ` Stephen Boyd
2021-03-14 4:16 ` Bjorn Andersson
2021-03-23 22:06 ` Stephen Boyd
2021-03-24 6:49 ` Sibi Sankar
2021-04-19 10:10 ` Sibi Sankar [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=92f87f0b2a080077f426b7d704314e35@codeaurora.org \
--to=sibis@codeaurora.org \
--cc=agross@kernel.org \
--cc=bjorn.andersson@linaro.org \
--cc=devicetree@vger.kernel.org \
--cc=linux-arm-msm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mani@kernel.org \
--cc=p.zabel@pengutronix.de \
--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;
as well as URLs for NNTP newsgroup(s).