From: Matthias Brugger <matthias.bgg@gmail.com>
To: Hsin-Yi Wang <hsinyi@chromium.org>, linux-arm-kernel@lists.infradead.org
Cc: linux-mediatek@lists.infradead.org, linux-kernel@vger.kernel.org,
devicetree@vger.kernel.org, Mark Rutland <mark.rutland@arm.com>,
Rob Herring <robh+dt@kernel.org>,
Daniel Kurtz <djkurtz@chromium.org>
Subject: Re: [PATCH] arm64: dts: mt8173: add Mediatek JPEG Codec
Date: Sat, 14 Dec 2019 22:40:27 +0100 [thread overview]
Message-ID: <759103c9-e090-277b-a727-1d5223caffb3@gmail.com> (raw)
In-Reply-To: <20191213045720.172738-1-hsinyi@chromium.org>
On 13/12/2019 05:57, Hsin-Yi Wang wrote:
> Add JPEG codec node in mt8173.
>
> Signed-off-by: Hsin-Yi Wang <hsinyi@chromium.org>
> ---
Applied to v5.5-next/dts64
Thanks!
> arch/arm64/boot/dts/mediatek/mt8173.dtsi | 14 ++++++++++++++
> 1 file changed, 14 insertions(+)
>
> diff --git a/arch/arm64/boot/dts/mediatek/mt8173.dtsi b/arch/arm64/boot/dts/mediatek/mt8173.dtsi
> index 15f1842f6df3..82df8940d515 100644
> --- a/arch/arm64/boot/dts/mediatek/mt8173.dtsi
> +++ b/arch/arm64/boot/dts/mediatek/mt8173.dtsi
> @@ -1401,6 +1401,20 @@ vcodec_enc: vcodec@18002000 {
> <&topckgen CLK_TOP_UNIVPLL1_D2>;
> };
>
> + jpegdec: jpegdec@18004000 {
> + compatible = "mediatek,mt8173-jpgdec";
> + reg = <0 0x18004000 0 0x1000>;
> + interrupts = <GIC_SPI 203 IRQ_TYPE_LEVEL_LOW>;
> + clocks = <&vencsys CLK_VENC_CKE0>,
> + <&vencsys CLK_VENC_CKE3>;
> + clock-names = "jpgdec-smi",
> + "jpgdec";
> + power-domains = <&scpsys MT8173_POWER_DOMAIN_VENC>;
> + mediatek,larb = <&larb3>;
> + iommus = <&iommu M4U_PORT_JPGDEC_WDMA>,
> + <&iommu M4U_PORT_JPGDEC_BSDMA>;
> + };
> +
> vencltsys: clock-controller@19000000 {
> compatible = "mediatek,mt8173-vencltsys", "syscon";
> reg = <0 0x19000000 0 0x1000>;
>
prev parent reply other threads:[~2019-12-14 21:40 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-12-13 4:57 [PATCH] arm64: dts: mt8173: add Mediatek JPEG Codec Hsin-Yi Wang
2019-12-14 21:40 ` Matthias Brugger [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=759103c9-e090-277b-a727-1d5223caffb3@gmail.com \
--to=matthias.bgg@gmail.com \
--cc=devicetree@vger.kernel.org \
--cc=djkurtz@chromium.org \
--cc=hsinyi@chromium.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mediatek@lists.infradead.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).