From: Matthias Brugger <matthias.bgg@gmail.com>
To: Irui Wang <irui.wang@mediatek.com>,
Hans Verkuil <hverkuil-cisco@xs4all.nl>,
Rob Herring <robh+dt@kernel.org>,
Krzysztof Kozlowski <krzysztof.kozlowski+dt@linaro.org>,
Mauro Carvalho Chehab <mchehab@kernel.org>,
angelogioacchino.delregno@collabora.com,
nicolas.dufresne@collabora.com, kyrie wu <kyrie.wu@mediatek.com>
Cc: Project_Global_Chrome_Upstream_Group@mediatek.com,
devicetree@vger.kernel.org, linux-media@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
Subject: Re: [V1,0/2] Add jpeg enc & dec device node for MT8195
Date: Wed, 25 Jan 2023 16:22:11 +0100 [thread overview]
Message-ID: <892229a2-01b9-f4cc-95fb-980107166715@gmail.com> (raw)
In-Reply-To: <20230112084503.4277-1-irui.wang@mediatek.com>
Applied, thanks!
On 12/01/2023 09:45, Irui Wang wrote:
> From: kyrie wu <kyrie.wu@mediatek.com>
>
> This series add jpeg enc and dec device node to dts file
> for the purpose of supporting multi hardwares jpeg
> enc & dec of MT8195.
>
> This series has been tested with MT8195 Gstreamer.
> Encoding and decoding worked for this chip.
>
> Patches 1 Adds jpeg encoder device node for mt8195.
>
> Patches 2 Adds jpeg decoder device node for mt8195.
>
> kyrie wu (2):
> arm64: dts: mt8195: add jpeg encode device node
> arm64: dts: mt8195: add jpeg decode device node
>
> arch/arm64/boot/dts/mediatek/mt8195.dtsi | 100 +++++++++++++++++++++++
> 1 file changed, 100 insertions(+)
>
prev parent reply other threads:[~2023-01-25 15:22 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-01-12 8:45 [V1,0/2] Add jpeg enc & dec device node for MT8195 Irui Wang
2023-01-12 8:45 ` [V1,1/2] arm64: dts: mt8195: add jpeg encode device node Irui Wang
2023-01-12 8:45 ` [V1,2/2] arm64: dts: mt8195: add jpeg decode " Irui Wang
2023-01-25 15:22 ` 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=892229a2-01b9-f4cc-95fb-980107166715@gmail.com \
--to=matthias.bgg@gmail.com \
--cc=Project_Global_Chrome_Upstream_Group@mediatek.com \
--cc=angelogioacchino.delregno@collabora.com \
--cc=devicetree@vger.kernel.org \
--cc=hverkuil-cisco@xs4all.nl \
--cc=irui.wang@mediatek.com \
--cc=krzysztof.kozlowski+dt@linaro.org \
--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=mchehab@kernel.org \
--cc=nicolas.dufresne@collabora.com \
--cc=robh+dt@kernel.org \
--cc=tfiga@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).