From: Matthias Kaehlcke <mka@chromium.org>
To: Doug Anderson <dianders@chromium.org>
Cc: Andy Gross <agross@kernel.org>,
Bjorn Andersson <bjorn.andersson@linaro.org>,
Rob Herring <robh+dt@kernel.org>,
Mark Rutland <mark.rutland@arm.com>,
Dikshita Agarwal <dikshita@codeaurora.org>,
linux-arm-msm <linux-arm-msm@vger.kernel.org>,
LKML <linux-kernel@vger.kernel.org>,
"open list:OPEN FIRMWARE AND FLATTENED DEVICE TREE BINDINGS"
<devicetree@vger.kernel.org>
Subject: Re: [PATCH] arm64: dts: sc7180: Move venus node to the correct position
Date: Wed, 26 Feb 2020 12:44:36 -0800 [thread overview]
Message-ID: <20200226204436.GG24720@google.com> (raw)
In-Reply-To: <CAD=FV=UMptkb9ni0KFWp96BycU32kchYs9+uS-7H+Q9ounHy2g@mail.gmail.com>
On Wed, Feb 26, 2020 at 12:40:23PM -0800, Doug Anderson wrote:
> Hi,
>
> On Wed, Feb 26, 2020 at 11:40 AM Matthias Kaehlcke <mka@chromium.org> wrote:
> >
> > Per convention device nodes for SC7180 should be ordered by address.
> > This is currently not the case for the venus node, move it to the
> > correct position.
> >
> > Signed-off-by: Matthias Kaehlcke <mka@chromium.org>
> > ---
> >
> > arch/arm64/boot/dts/qcom/sc7180.dtsi | 52 ++++++++++++++--------------
> > 1 file changed, 26 insertions(+), 26 deletions(-)
> >
> > diff --git a/arch/arm64/boot/dts/qcom/sc7180.dtsi b/arch/arm64/boot/dts/qcom/sc7180.dtsi
> > index 253274d5f04c..5f97945e16a4 100644
> > --- a/arch/arm64/boot/dts/qcom/sc7180.dtsi
> > +++ b/arch/arm64/boot/dts/qcom/sc7180.dtsi
> > @@ -1332,6 +1332,32 @@ system-cache-controller@9200000 {
> > interrupts = <GIC_SPI 582 IRQ_TYPE_LEVEL_HIGH>;
> > };
> >
> > + venus: video-codec@aa00000 {
> > + compatible = "qcom,sc7180-venus";
> > + reg = <0 0x0aa00000 0 0xff000>;
> > + interrupts = <GIC_SPI 174 IRQ_TYPE_LEVEL_HIGH>;
> > + power-domains = <&videocc VENUS_GDSC>,
> > + <&videocc VCODEC0_GDSC>;
> > + power-domain-names = "venus", "vcodec0";
> > + clocks = <&videocc VIDEO_CC_VENUS_CTL_CORE_CLK>,
> > + <&videocc VIDEO_CC_VENUS_AHB_CLK>,
> > + <&videocc VIDEO_CC_VENUS_CTL_AXI_CLK>,
> > + <&videocc VIDEO_CC_VCODEC0_CORE_CLK>,
> > + <&videocc VIDEO_CC_VCODEC0_AXI_CLK>;
> > + clock-names = "core", "iface", "bus",
> > + "vcodec0_core", "vcodec0_bus";
> > + iommus = <&apps_smmu 0x0c00 0x60>;
> > + memory-region = <&venus_mem>;
> > +
> > + video-decoder {
> > + compatible = "venus-decoder";
> > + };
> > +
> > + video-encoder {
> > + compatible = "venus-encoder";
> > + };
> > + };
> > +
> > usb_1: usb@a6f8800 {
> > compatible = "qcom,sc7180-dwc3", "qcom,dwc3";
> > reg = <0 0x0a6f8800 0 0x400>;
>
> Maybe try one more time?
>
> >>> print [hex(x) for x in sorted([0x0aa00000, 0x0a6f8800])]
> ['0xa6f8800', '0xaa00000']
>
> ...makes me convinced that the codec should come _after_ the USB node, no?
indeed, thanks for catching it!
prev parent reply other threads:[~2020-02-26 20:44 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-02-26 19:40 [PATCH] arm64: dts: sc7180: Move venus node to the correct position Matthias Kaehlcke
2020-02-26 20:40 ` Doug Anderson
2020-02-26 20:44 ` Matthias Kaehlcke [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=20200226204436.GG24720@google.com \
--to=mka@chromium.org \
--cc=agross@kernel.org \
--cc=bjorn.andersson@linaro.org \
--cc=devicetree@vger.kernel.org \
--cc=dianders@chromium.org \
--cc=dikshita@codeaurora.org \
--cc=linux-arm-msm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mark.rutland@arm.com \
--cc=robh+dt@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 NNTP newsgroup(s).