mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: "Allen-KH Cheng (程冠勳)" <Allen-KH.Cheng@mediatek.com>
To: "wenst@chromium.org" <wenst@chromium.org>
Cc: "linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
	"linux-mediatek@lists.infradead.org" 
	<linux-mediatek@lists.infradead.org>,
	"robh+dt@kernel.org" <robh+dt@kernel.org>,
	"devicetree@vger.kernel.org" <devicetree@vger.kernel.org>,
	"krzysztof.kozlowski@linaro.org" <krzysztof.kozlowski@linaro.org>,
	Project_Global_Chrome_Upstream_Group 
	<Project_Global_Chrome_Upstream_Group@mediatek.com>,
	"hsinyi@chromium.org" <hsinyi@chromium.org>,
	"linux-arm-kernel@lists.infradead.org" 
	<linux-arm-kernel@lists.infradead.org>,
	"matthias.bgg@gmail.com" <matthias.bgg@gmail.com>
Subject: Re: [PATCH] arm64: dts: mt8192: Add vcodec lat and core nodes
Date: Mon, 26 Sep 2022 08:29:49 +0000	[thread overview]
Message-ID: <621542e1d23a477aec9e7796da2673717db56027.camel@mediatek.com> (raw)
In-Reply-To: <CAGXv+5Hx31PWVU-uz0araW+jYX-s+_HXph-ZAPa6eMPn0LQ+Bg@mail.gmail.com>

Hi Chen-Yu,

Thanks for the suggestion and test.

The following version will fix the node's name.

BRs,
Allen

On Mon, 2022-09-26 at 14:47 +0800, Chen-Yu Tsai wrote:
> On Fri, Sep 23, 2022 at 7:47 PM Allen-KH Cheng
> <allen-kh.cheng@mediatek.com> wrote:
> > 
> > Add vcodec lat and core nodes for mt8192 SoC.
> > 
> > Signed-off-by: Allen-KH Cheng <allen-kh.cheng@mediatek.com>
> 
> Tested-by: Chen-Yu Tsai <wenst@chromium.org>
> 
> > ---
> > This patch is based on matthias.bgg/linux.git, v6.0-next/dts64
> > [Allen-KH Cheng <allen-kh.cheng@mediatek.com>]
> > ---
> > ---
> >  arch/arm64/boot/dts/mediatek/mt8192.dtsi | 60
> > ++++++++++++++++++++++++
> >  1 file changed, 60 insertions(+)
> > 
> > diff --git a/arch/arm64/boot/dts/mediatek/mt8192.dtsi
> > b/arch/arm64/boot/dts/mediatek/mt8192.dtsi
> > index 6b20376191a7..aa6524948e7c 100644
> > --- a/arch/arm64/boot/dts/mediatek/mt8192.dtsi
> > +++ b/arch/arm64/boot/dts/mediatek/mt8192.dtsi
> > @@ -1449,6 +1449,66 @@
> >                         power-domains = <&spm
> > MT8192_POWER_DOMAIN_ISP2>;
> >                 };
> > 
> > +               vcodec_dec: vcodec-dec@16000000 {
> 
> The device node name should be generic, so maybe "video-codec@"?
> 
> > +                       compatible = "mediatek,mt8192-vcodec-dec";
> > +                       reg = <0 0x16000000 0 0x1000>;
> > +                       mediatek,scp = <&scp>;
> > +                       iommus = <&iommu0 M4U_PORT_L4_VDEC_MC_EXT>;
> > +                       dma-ranges = <0x1 0x0 0x0 0x40000000 0x0
> > 0xfff00000>;
> > +                       #address-cells = <2>;
> > +                       #size-cells = <2>;
> > +                       ranges = <0 0 0 0x16000000 0 0x26000>;
> > +
> > +                       vcodec_lat: vcodec-lat@10000 {
> 
> Same here.
> 
> > +                               compatible = "mediatek,mtk-vcodec-
> > lat";
> > +                               reg = <0x0 0x10000 0 0x800>;
> > +                               interrupts = <GIC_SPI 426
> > IRQ_TYPE_LEVEL_HIGH 0>;
> > +                               iommus = <&iommu0
> > M4U_PORT_L5_VDEC_LAT0_VLD_EXT>,
> > +                                        <&iommu0
> > M4U_PORT_L5_VDEC_LAT0_VLD2_EXT>,
> > +                                        <&iommu0
> > M4U_PORT_L5_VDEC_LAT0_AVC_MV_EXT>,
> > +                                        <&iommu0
> > M4U_PORT_L5_VDEC_LAT0_PRED_RD_EXT>,
> > +                                        <&iommu0
> > M4U_PORT_L5_VDEC_LAT0_TILE_EXT>,
> > +                                        <&iommu0
> > M4U_PORT_L5_VDEC_LAT0_WDMA_EXT>,
> > +                                        <&iommu0
> > M4U_PORT_L5_VDEC_LAT0_RG_CTRL_DMA_EXT>,
> > +                                        <&iommu0
> > M4U_PORT_L5_VDEC_UFO_ENC_EXT>;
> > +                               clocks = <&topckgen
> > CLK_TOP_VDEC_SEL>,
> > +                                        <&vdecsys_soc
> > CLK_VDEC_SOC_VDEC>,
> > +                                        <&vdecsys_soc
> > CLK_VDEC_SOC_LAT>,
> > +                                        <&vdecsys_soc
> > CLK_VDEC_SOC_LARB1>,
> > +                                        <&topckgen
> > CLK_TOP_MAINPLL_D4>;
> > +                               clock-names = "sel", "soc-vdec",
> > "soc-lat", "vdec", "top";
> > +                               assigned-clocks = <&topckgen
> > CLK_TOP_VDEC_SEL>;
> > +                               assigned-clock-parents = <&topckgen
> > CLK_TOP_MAINPLL_D4>;
> > +                               power-domains = <&spm
> > MT8192_POWER_DOMAIN_VDEC>;
> > +                       };
> > +
> > +                       vcodec_core: vcodec-core@25000 {
> 
> Same here.
> 
> ChenYu

      reply	other threads:[~2022-09-26  8:30 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-09-23 11:46 Allen-KH Cheng
2022-09-26  6:47 ` Chen-Yu Tsai
2022-09-26  8:29   ` Allen-KH Cheng (程冠勳) [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=621542e1d23a477aec9e7796da2673717db56027.camel@mediatek.com \
    --to=allen-kh.cheng@mediatek.com \
    --cc=Project_Global_Chrome_Upstream_Group@mediatek.com \
    --cc=devicetree@vger.kernel.org \
    --cc=hsinyi@chromium.org \
    --cc=krzysztof.kozlowski@linaro.org \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-mediatek@lists.infradead.org \
    --cc=matthias.bgg@gmail.com \
    --cc=robh+dt@kernel.org \
    --cc=wenst@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

all inboxes | Powered by JetHome®