From: Miles Chen <miles.chen@mediatek.com>
To: <chun-jie.chen@mediatek.com>
Cc: <Project_Global_Chrome_Upstream_Group@mediatek.com>,
<devicetree@vger.kernel.org>, <drinkcat@chromium.org>,
<linux-arm-kernel@lists.infradead.org>,
<linux-clk@vger.kernel.org>, <linux-kernel@vger.kernel.org>,
<linux-mediatek@lists.infradead.org>, <matthias.bgg@gmail.com>,
<robh+dt@kernel.org>, <sboyd@kernel.org>,
<srv_heupstream@mediatek.com>
Subject: Re: [PATCH v3 11/15] clk: mediatek: Add MT8186 vdecsys clock support
Date: Sun, 13 Mar 2022 07:17:31 +0800 [thread overview]
Message-ID: <20220312231731.10369-1-miles.chen@mediatek.com> (raw)
In-Reply-To: <20220311114229.32504-12-chun-jie.chen@mediatek.com>
> Add MT8186 vdec clock controller which provide clock gate
> control for video decoder.
>
> Signed-off-by: Chun-Jie Chen <chun-jie.chen@mediatek.com>
> Acked-by: AngeloGioacchino Del Regno <angelogioacchino.delregno@collabora.com>
Reviewed-by: Miles Chen <miles.chen@mediatek.com>
next prev parent reply other threads:[~2022-03-12 23:17 UTC|newest]
Thread overview: 31+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-03-11 11:42 [PATCH v3 00/15] MediaTek MT8186 clock support Chun-Jie Chen
2022-03-11 11:42 ` [PATCH v3 01/15] dt-bindings: ARM: MediaTek: Add new document bindings of MT8186 clock Chun-Jie Chen
2022-03-11 11:42 ` [PATCH v3 02/15] clk: mediatek: Add MT8186 mcusys clock support Chun-Jie Chen
2022-03-12 23:00 ` Miles Chen
2022-03-17 19:47 ` Stephen Boyd
2022-03-11 11:42 ` [PATCH v3 03/15] clk: mediatek: Add MT8186 topckgen " Chun-Jie Chen
2022-03-12 23:02 ` Miles Chen
2022-03-11 11:42 ` [PATCH v3 04/15] clk: mediatek: Add MT8186 infrastructure " Chun-Jie Chen
2022-03-12 23:04 ` Miles Chen
2022-03-11 11:42 ` [PATCH v3 05/15] clk: mediatek: Add MT8186 apmixedsys " Chun-Jie Chen
2022-03-12 23:05 ` Miles Chen
2022-03-11 11:42 ` [PATCH v3 06/15] clk: mediatek: Add MT8186 imp i2c wrapper " Chun-Jie Chen
2022-03-12 23:08 ` Miles Chen
2022-03-11 11:42 ` [PATCH v3 07/15] clk: mediatek: Add MT8186 mfgsys " Chun-Jie Chen
2022-03-12 23:11 ` Miles Chen
2022-03-11 11:42 ` [PATCH v3 08/15] clk: mediatek: Add MT8186 mmsys " Chun-Jie Chen
2022-03-12 23:12 ` Miles Chen
2022-03-11 11:42 ` [PATCH v3 09/15] clk: mediatek: Add MT8186 wpesys " Chun-Jie Chen
2022-03-12 23:13 ` Miles Chen
2022-03-11 11:42 ` [PATCH v3 10/15] clk: mediatek: Add MT8186 imgsys " Chun-Jie Chen
2022-03-12 23:16 ` Miles Chen
2022-03-11 11:42 ` [PATCH v3 11/15] clk: mediatek: Add MT8186 vdecsys " Chun-Jie Chen
2022-03-12 23:17 ` Miles Chen [this message]
2022-03-11 11:42 ` [PATCH v3 12/15] clk: mediatek: Add MT8186 vencsys " Chun-Jie Chen
2022-03-12 23:21 ` Miles Chen
2022-03-11 11:42 ` [PATCH v3 13/15] clk: mediatek: Add MT8186 camsys " Chun-Jie Chen
2022-03-12 23:22 ` Miles Chen
2022-03-11 11:42 ` [PATCH v3 14/15] clk: mediatek: Add MT8186 mdpsys " Chun-Jie Chen
2022-03-12 23:25 ` Miles Chen
2022-03-11 11:42 ` [PATCH v3 15/15] clk: mediatek: Add MT8186 ipesys " Chun-Jie Chen
2022-03-12 23:26 ` Miles Chen
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=20220312231731.10369-1-miles.chen@mediatek.com \
--to=miles.chen@mediatek.com \
--cc=Project_Global_Chrome_Upstream_Group@mediatek.com \
--cc=chun-jie.chen@mediatek.com \
--cc=devicetree@vger.kernel.org \
--cc=drinkcat@chromium.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-clk@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mediatek@lists.infradead.org \
--cc=matthias.bgg@gmail.com \
--cc=robh+dt@kernel.org \
--cc=sboyd@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).