From: Eugen Hristev <eugen.hristev@collabora.com>
To: tiffany.lin@mediatek.com, andrew-ct.chen@mediatek.com,
matthias.bgg@gmail.com, angelogioacchino.delregno@collabora.com,
linux-mediatek@lists.infradead.org
Cc: eugen.hristev@collabora.com, linux-media@vger.kernel.org,
devicetree@vger.kernel.org, linux-kernel@vger.kernel.org,
linux-arm-kernel@lists.infradead.org, robh+dt@kernel.org,
kernel@collabora.com
Subject: [PATCH v3 0/6] video encoder on mt8186
Date: Thu, 28 Dec 2023 13:32:39 +0200 [thread overview]
Message-ID: <20231228113245.174706-1-eugen.hristev@collabora.com> (raw)
Hello,
This series adds support for the video encoder on mt8186.
Few patches fix the binding, there is a patch for the DT node,
and one patch for the driver that fixes an imbalance.
Changes in v3:
- removed the patch to add dma-ranges, because this was intentionally
removed (e.g. https://patchwork.kernel.org/project/linux-media/patch/20230303013842.23259-3-allen-kh.cheng@mediatek.com/ )
also removed dma-ranges and cells from the DT node
Changes in v2:
- change log in every patch
Eugen Hristev (5):
media: mediatek: vcodec: fix possible unbalanced PM counter
dt-bindings: media: mtk-vcodec-encoder: fix non-vp8 clock name
arm64: dts: mediatek: mt8192: fix vencoder clock name
dt-bindings: media: mtk-vcodec-encoder: add compatible for mt8186
arm64: dts: mediatek: mt8186: fix VENC power domain clocks
Kyrie Wu (1):
arm64: dts: mediatek: mt8186: Add venc node
.../media/mediatek,vcodec-encoder.yaml | 31 ++++++++++---------
arch/arm64/boot/dts/mediatek/mt8186.dtsi | 23 +++++++++++++-
arch/arm64/boot/dts/mediatek/mt8192.dtsi | 2 +-
.../vcodec/encoder/mtk_vcodec_enc_pm.c | 4 ++-
.../vcodec/encoder/mtk_vcodec_enc_pm.h | 2 +-
.../mediatek/vcodec/encoder/venc_drv_if.c | 5 ++-
6 files changed, 47 insertions(+), 20 deletions(-)
--
2.34.1
next reply other threads:[~2023-12-28 11:32 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-12-28 11:32 Eugen Hristev [this message]
2023-12-28 11:32 ` [PATCH v3 1/6] media: mediatek: vcodec: fix possible unbalanced PM counter Eugen Hristev
2023-12-28 11:32 ` [PATCH v3 2/6] dt-bindings: media: mtk-vcodec-encoder: fix non-vp8 clock name Eugen Hristev
2024-01-02 9:13 ` AngeloGioacchino Del Regno
2023-12-28 11:32 ` [PATCH v3 3/6] arm64: dts: mediatek: mt8192: fix vencoder " Eugen Hristev
2024-01-02 9:13 ` AngeloGioacchino Del Regno
2023-12-28 11:32 ` [PATCH v3 4/6] dt-bindings: media: mtk-vcodec-encoder: add compatible for mt8186 Eugen Hristev
2024-01-02 9:14 ` AngeloGioacchino Del Regno
2023-12-28 11:32 ` [PATCH v3 5/6] arm64: dts: mediatek: mt8186: fix VENC power domain clocks Eugen Hristev
2024-01-02 9:14 ` AngeloGioacchino Del Regno
2023-12-28 11:32 ` [PATCH v3 6/6] arm64: dts: mediatek: mt8186: Add venc node Eugen Hristev
2024-01-02 9:14 ` AngeloGioacchino Del Regno
2024-01-29 10:41 ` (subset) [PATCH v3 0/6] video encoder on mt8186 AngeloGioacchino Del Regno
2024-01-29 10:47 ` AngeloGioacchino Del Regno
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=20231228113245.174706-1-eugen.hristev@collabora.com \
--to=eugen.hristev@collabora.com \
--cc=andrew-ct.chen@mediatek.com \
--cc=angelogioacchino.delregno@collabora.com \
--cc=devicetree@vger.kernel.org \
--cc=kernel@collabora.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=matthias.bgg@gmail.com \
--cc=robh+dt@kernel.org \
--cc=tiffany.lin@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