From: Irui Wang <irui.wang@mediatek.com>
To: Hans Verkuil <hverkuil-cisco@xs4all.nl>,
Mauro Carvalho Chehab <mchehab@kernel.org>,
Rob Herring <robh+dt@kernel.org>,
Matthias Brugger <matthias.bgg@gmail.com>,
Tzung-Bi Shih <tzungbi@chromium.org>
Cc: <Project_Global_Chrome_Upstream_Group@mediatek.com>,
<linux-media@vger.kernel.org>, <devicetree@vger.kernel.org>,
<linux-kernel@vger.kernel.org>,
<linux-arm-kernel@lists.infradead.org>,
<linux-mediatek@lists.infradead.org>,
Tomasz Figa <tfiga@chromium.org>, <xia.jiang@mediatek.com>,
<maoguang.meng@mediatek.com>, kyrie wu <kyrie.wu@mediatek.com>,
<srv_heupstream@mediatek.com>
Subject: [V2,0/2] Enable hardware jpeg encoder for MT8186
Date: Wed, 8 Jun 2022 14:07:53 +0800 [thread overview]
Message-ID: <20220608060755.2213-1-irui.wang@mediatek.com> (raw)
From: kyrie wu <kyrie.wu@mediatek.com>
This series adds support for MT8186 hardware jpeg encoding.
This series has been tested with both MT8186.
Encoding worked for this chip.
Patches 1 Adds jpeg encoder dt-bindings for mt8186
Patches 2 set bit mask for jpegenc to support 34bits iova space,
which means iova rangement from 0 to 16GB.
Changes compared with v1:
--rebase on latest media_stage tree
kyrie wu (2):
media: media: jpegenc: add mediatek,mt8186-jpgenc compatible
media: media: jpegenc: set bit mask for jpegenc
.../devicetree/bindings/media/mediatek-jpeg-encoder.yaml | 6 ++++++
drivers/media/platform/mediatek/jpeg/mtk_jpeg_core.c | 3 +++
2 files changed, 9 insertions(+)
--
2.18.0
next reply other threads:[~2022-06-08 7:07 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-06-08 6:07 Irui Wang [this message]
2022-06-08 6:07 ` [V2,1/2] media: media: jpegenc: add mediatek,mt8186-jpgenc compatible Irui Wang
2022-06-08 15:00 ` Rob Herring
2022-06-08 6:07 ` [V2,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=20220608060755.2213-1-irui.wang@mediatek.com \
--to=irui.wang@mediatek.com \
--cc=Project_Global_Chrome_Upstream_Group@mediatek.com \
--cc=devicetree@vger.kernel.org \
--cc=hverkuil-cisco@xs4all.nl \
--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).