From: Rob Herring <robh@kernel.org>
To: Irui Wang <irui.wang@mediatek.com>
Cc: Hans Verkuil <hverkuil-cisco@xs4all.nl>,
maoguang.meng@mediatek.com, linux-mediatek@lists.infradead.org,
Mauro Carvalho Chehab <mchehab@kernel.org>,
linux-arm-kernel@lists.infradead.org,
Tzung-Bi Shih <tzungbi@chromium.org>,
Matthias Brugger <matthias.bgg@gmail.com>,
Tomasz Figa <tfiga@chromium.org>,
Rob Herring <robh+dt@kernel.org>,
devicetree@vger.kernel.org, kyrie wu <kyrie.wu@mediatek.com>,
Hsin-Yi Wang <hsinyi@chromium.org>,
xia.jiang@mediatek.com, linux-media@vger.kernel.org,
Project_Global_Chrome_Upstream_Group@mediatek.com,
linux-kernel@vger.kernel.org, srv_heupstream@mediatek.com
Subject: Re: [RESEND V1,1/2] media: media: jpegenc: add mediatek,mt8186-jpgenc compatible
Date: Wed, 1 Jun 2022 16:20:32 -0500 [thread overview]
Message-ID: <20220601212032.GA476431-robh@kernel.org> (raw)
In-Reply-To: <20220520085910.28839-2-irui.wang@mediatek.com>
On Fri, 20 May 2022 16:59:09 +0800, Irui Wang wrote:
> From: kyrie wu <kyrie.wu@mediatek.com>
>
> Add mediatek,mt8186-jpgenc compatible to binding document.
>
> MT8186 iommu support 0~16GB iova. We separate it to four banks:
> 0~4G; 4G~8G; 8G~12G; 12G~16G.
>
> The "dma-ranges" could be used to adjust the bank we locate.
> If we don't set this property. The default range always is 0~4G.
>
> Signed-off-by: kyrie wu <kyrie.wu@mediatek.com>
> ---
> .../devicetree/bindings/media/mediatek-jpeg-encoder.yaml | 6 ++++++
> 1 file changed, 6 insertions(+)
>
Reviewed-by: Rob Herring <robh@kernel.org>
next prev parent reply other threads:[~2022-06-01 21:20 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-05-20 8:59 [RESEND V1,0/2] Enable hardware jpeg encoder for MT8186 Irui Wang
2022-05-20 8:59 ` [RESEND V1,1/2] media: media: jpegenc: add mediatek,mt8186-jpgenc compatible Irui Wang
2022-06-01 21:20 ` Rob Herring [this message]
2022-05-20 8:59 ` [RESEND V1,2/2] media: media: jpegenc: set bit mask for jpegenc Irui Wang
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=20220601212032.GA476431-robh@kernel.org \
--to=robh@kernel.org \
--cc=Project_Global_Chrome_Upstream_Group@mediatek.com \
--cc=devicetree@vger.kernel.org \
--cc=hsinyi@chromium.org \
--cc=hverkuil-cisco@xs4all.nl \
--cc=irui.wang@mediatek.com \
--cc=kyrie.wu@mediatek.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=maoguang.meng@mediatek.com \
--cc=matthias.bgg@gmail.com \
--cc=mchehab@kernel.org \
--cc=robh+dt@kernel.org \
--cc=srv_heupstream@mediatek.com \
--cc=tfiga@chromium.org \
--cc=tzungbi@chromium.org \
--cc=xia.jiang@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).