From: Matthias Brugger <matthias.bgg@gmail.com>
To: Rick Chang <rick.chang@mediatek.com>,
Hans Verkuil <hans.verkuil@cisco.com>,
Laurent Pinchart <laurent.pinchart+renesas@ideasonboard.com>,
Mauro Carvalho Chehab <mchehab@kernel.org>,
Rob Herring <robh+dt@kernel.org>
Cc: linux-kernel@vger.kernel.org, linux-media@vger.kernel.org,
srv_heupstream@mediatek.com, linux-mediatek@lists.infradead.org,
linux-arm-kernel@lists.infradead.org, devicetree@vger.kernel.org,
Minghsiu Tsai <minghsiu.tsai@mediatek.com>,
Bin Liu <bin.liu@mediatek.com>
Subject: Re: [PATCH v9 3/4] arm: dts: mt2701: Add node for Mediatek JPEG Decoder
Date: Wed, 10 May 2017 13:02:19 +0200 [thread overview]
Message-ID: <492cfa38-aff0-f7c9-72f9-94e53adc198c@gmail.com> (raw)
In-Reply-To: <1481702690-10476-4-git-send-email-rick.chang@mediatek.com>
On 14/12/16 09:04, Rick Chang wrote:
> Signed-off-by: Rick Chang <rick.chang@mediatek.com>
> Signed-off-by: Minghsiu Tsai <minghsiu.tsai@mediatek.com>
> ---
> This patch depends on:
> CCF "Add clock support for Mediatek MT2701"[1]
> iommu and smi "Add the dtsi node of iommu and smi for mt2701"[2]
>
> [1] http://lists.infradead.org/pipermail/linux-mediatek/2016-October/007271.html
> [2] https://patchwork.kernel.org/patch/9164013/
Now queued for v4.12-next/dts32
Thanks and sorry for the delay.
Matthias
> ---
> arch/arm/boot/dts/mt2701.dtsi | 14 ++++++++++++++
> 1 file changed, 14 insertions(+)
>
> diff --git a/arch/arm/boot/dts/mt2701.dtsi b/arch/arm/boot/dts/mt2701.dtsi
> index 8f13c70..4dd5048 100644
> --- a/arch/arm/boot/dts/mt2701.dtsi
> +++ b/arch/arm/boot/dts/mt2701.dtsi
> @@ -298,6 +298,20 @@
> power-domains = <&scpsys MT2701_POWER_DOMAIN_ISP>;
> };
>
> + jpegdec: jpegdec@15004000 {
> + compatible = "mediatek,mt2701-jpgdec";
> + reg = <0 0x15004000 0 0x1000>;
> + interrupts = <GIC_SPI 143 IRQ_TYPE_LEVEL_LOW>;
> + clocks = <&imgsys CLK_IMG_JPGDEC_SMI>,
> + <&imgsys CLK_IMG_JPGDEC>;
> + clock-names = "jpgdec-smi",
> + "jpgdec";
> + power-domains = <&scpsys MT2701_POWER_DOMAIN_ISP>;
> + mediatek,larb = <&larb2>;
> + iommus = <&iommu MT2701_M4U_PORT_JPGDEC_WDMA>,
> + <&iommu MT2701_M4U_PORT_JPGDEC_BSDMA>;
> + };
> +
> vdecsys: syscon@16000000 {
> compatible = "mediatek,mt2701-vdecsys", "syscon";
> reg = <0 0x16000000 0 0x1000>;
>
next prev parent reply other threads:[~2017-05-10 11:02 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-12-14 8:04 [PATCH v9 0/4] Add Mediatek JPEG Decoder Rick Chang
2016-12-14 8:04 ` [PATCH v9 1/4] dt-bindings: mediatek: Add a binding for " Rick Chang
2016-12-14 8:04 ` [PATCH v9 2/4] vcodec: mediatek: Add Mediatek JPEG Decoder Driver Rick Chang
2016-12-18 6:53 ` Ricky Liang
2016-12-14 8:04 ` [PATCH v9 3/4] arm: dts: mt2701: Add node for Mediatek JPEG Decoder Rick Chang
2017-05-10 11:02 ` Matthias Brugger [this message]
2017-05-31 13:04 ` Matthias Brugger
2016-12-14 8:04 ` [PATCH v9 4/4] vcodec: mediatek: Add Maintainers entry for Mediatek JPEG driver Rick Chang
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=492cfa38-aff0-f7c9-72f9-94e53adc198c@gmail.com \
--to=matthias.bgg@gmail.com \
--cc=bin.liu@mediatek.com \
--cc=devicetree@vger.kernel.org \
--cc=hans.verkuil@cisco.com \
--cc=laurent.pinchart+renesas@ideasonboard.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-media@vger.kernel.org \
--cc=linux-mediatek@lists.infradead.org \
--cc=mchehab@kernel.org \
--cc=minghsiu.tsai@mediatek.com \
--cc=rick.chang@mediatek.com \
--cc=robh+dt@kernel.org \
--cc=srv_heupstream@mediatek.com \
/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).