From: Dylan Van Assche <me@dylanvanassche.be>
To: Krzysztof Kozlowski <krzysztof.kozlowski@linaro.org>,
Andy Gross <agross@kernel.org>,
Bjorn Andersson <andersson@kernel.org>,
Rob Herring <robh+dt@kernel.org>,
Krzysztof Kozlowski <krzysztof.kozlowski+dt@linaro.org>
Cc: Konrad Dybcio <konrad.dybcio@linaro.org>,
linux-arm-msm@vger.kernel.org, devicetree@vger.kernel.org,
linux-kernel@vger.kernel.org,
~postmarketos/upstreaming@lists.sr.ht,
phone-devel@vger.kernel.org
Subject: Re: [PATCH v4 4/6] dts: qcom: arm64: qcom: sdm845: use defines for VMIDs
Date: Mon, 03 Apr 2023 18:22:21 +0200 [thread overview]
Message-ID: <744f2ddc80ba9d9216ecd90b97e08aa5bd5452cd.camel@dylanvanassche.be> (raw)
In-Reply-To: <bf7b5218-56ba-5525-fcb8-7be71b114a79@linaro.org>
Hi,
On Mon, 2023-04-03 at 17:47 +0200, Krzysztof Kozlowski wrote:
> On 03/04/2023 17:32, Dylan Van Assche wrote:
> > Hi Krzysztof,
> >
> > On Mon, 2023-04-03 at 11:20 +0200, Krzysztof Kozlowski wrote:
> > > On 01/04/2023 19:35, Dylan Van Assche wrote:
> > > > Use VMID defines for SLPI's FastRPC node in the Qualcomm SDM845
> > > > DTS
> > > > instead of hardcoded magic values.
> > > >
> > > > Signed-off-by: Dylan Van Assche <me@dylanvanassche.be>
> > > > ---
> > > > arch/arm64/boot/dts/qcom/sdm845.dtsi | 4 +++-
> > > > 1 file changed, 3 insertions(+), 1 deletion(-)
> > > >
> > > > diff --git a/arch/arm64/boot/dts/qcom/sdm845.dtsi
> > > > b/arch/arm64/boot/dts/qcom/sdm845.dtsi
> > > > index 1f25a7f4e02b..dc4b553cbe2e 100644
> > > > --- a/arch/arm64/boot/dts/qcom/sdm845.dtsi
> > > > +++ b/arch/arm64/boot/dts/qcom/sdm845.dtsi
> > > > @@ -13,6 +13,7 @@
> > > > #include <dt-bindings/clock/qcom,rpmh.h>
> > > > #include <dt-bindings/clock/qcom,videocc-sdm845.h>
> > > > #include <dt-bindings/dma/qcom-gpi.h>
> > > > +#include <dt-bindings/firmware/qcom,scm.h>
> > > > #include <dt-bindings/gpio/gpio.h>
> > > > #include <dt-bindings/interconnect/qcom,osm-l3.h>
> > > > #include <dt-bindings/interconnect/qcom,sdm845.h>
> > > > @@ -3372,7 +3373,8 @@ fastrpc {
> > > > qcom,glink-channels =
> > > > "fastrpcglink-apps-dsp";
> > > > label = "sdsp";
> > > > qcom,non-secure-domain;
> > > > - qcom,vmids = <0x3 0xF
> > > > 0x5
> > > > 0x6>;
> > >
> > > Didn't you just add it in previous patch? Don't add incorrect
> > > code
> > > which
> > > you immediately change.
> > >
> >
> > Both are similar, the code is in fact the same. I followed what
> > Konrad
> > suggested in v3 to make a patch on top:
>
> I don't understand. Device nodes are similar, but they are different?
> If
> you add a line in patch X and change it in patch X+1, then something
> is
> wrong. Isn't this the case here or these are different device nodes?
>
They are the same node.
In the original patch the values are hex values, but Konrad asked to
make a patch on top depending on the qcom scm header which has these
magic hex values with defines.
I can make the defines as default, no problem. Will do in v5.
Kind regards,
Dylan
>
> Best regards,
> Krzysztof
>
next prev parent reply other threads:[~2023-04-03 16:22 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-04-01 17:35 [PATCH v4 0/6] dts: qcom: arm64: sdm845: SLPI DSP enablement Dylan Van Assche
2023-04-01 17:35 ` [PATCH v4 1/6] dts: arm64: qcom: sdm845: add SLPI remoteproc Dylan Van Assche
2023-04-01 17:35 ` [PATCH v4 2/6] dts: arm64: qcom: sdm845: add SLPI FastRPC support Dylan Van Assche
2023-04-01 17:35 ` [PATCH v4 3/6] dt-bindings: firmware: qcom: scm: add SSC_Q6 and ADSP_Q6 VMIDs Dylan Van Assche
2023-04-03 9:19 ` Krzysztof Kozlowski
2023-04-01 17:35 ` [PATCH v4 4/6] dts: qcom: arm64: qcom: sdm845: use defines for VMIDs Dylan Van Assche
2023-04-03 9:20 ` Krzysztof Kozlowski
2023-04-03 15:32 ` Dylan Van Assche
2023-04-03 15:47 ` Krzysztof Kozlowski
2023-04-03 16:22 ` Dylan Van Assche [this message]
2023-04-04 18:29 ` Konrad Dybcio
2023-04-01 17:35 ` [PATCH v4 5/6] dts: arm64: qcom: sdm845-oneplus: enable SLPI Dylan Van Assche
2023-04-01 17:35 ` [PATCH v4 6/6] dts: arm64: qcom: sdm845-shift-axolotl: " Dylan Van Assche
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=744f2ddc80ba9d9216ecd90b97e08aa5bd5452cd.camel@dylanvanassche.be \
--to=me@dylanvanassche.be \
--cc=agross@kernel.org \
--cc=andersson@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=konrad.dybcio@linaro.org \
--cc=krzysztof.kozlowski+dt@linaro.org \
--cc=krzysztof.kozlowski@linaro.org \
--cc=linux-arm-msm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=phone-devel@vger.kernel.org \
--cc=robh+dt@kernel.org \
--cc=~postmarketos/upstreaming@lists.sr.ht \
/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).