From: CK Hu <ck.hu@mediatek.com>
To: Moudy Ho <moudy.ho@mediatek.com>,
Mauro Carvalho Chehab <mchehab@kernel.org>,
Rob Herring <robh+dt@kernel.org>,
Matthias Brugger <matthias.bgg@gmail.com>,
Krzysztof Kozlowski <krzysztof.kozlowski+dt@linaro.org>,
Hans Verkuil <hverkuil-cisco@xs4all.nl>
Cc: Chun-Kuang Hu <chunkuang.hu@kernel.org>,
Rob Landley <rob@landley.net>,
Laurent Pinchart <laurent.pinchart@ideasonboard.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>,
Alexandre Courbot <acourbot@chromium.org>, <tfiga@chromium.org>,
<drinkcat@chromium.org>, <pihsun@chromium.org>,
<hsinyi@google.com>,
Benjamin Gaignard <benjamin.gaignard@collabora.com>,
AngeloGioacchino Del Regno
<angelogioacchino.delregno@collabora.com>,
daoyuan huang <daoyuan.huang@mediatek.com>,
Ping-Hsun Wu <ping-hsun.wu@mediatek.com>,
<allen-kh.cheng@mediatek.com>, <xiandong.wang@mediatek.com>,
<randy.wu@mediatek.com>, <jason-jh.lin@mediatek.com>,
<roy-cw.yeh@mediatek.com>, <river.cheng@mediatek.com>,
<Project_Global_Chrome_Upstream_Group@mediatek.com>,
<cellopoint.kai@gmail.com>
Subject: Re: [PATCH v18 1/6] soc: mediatek: mutex: add common interface for modules setting
Date: Wed, 25 May 2022 11:27:41 +0800 [thread overview]
Message-ID: <05ad616704053c3f9b3275cd557b99bd56b3f40f.camel@mediatek.com> (raw)
In-Reply-To: <20220512084139.15086-2-moudy.ho@mediatek.com>
Hi, Moudy:
On Thu, 2022-05-12 at 16:41 +0800, Moudy Ho wrote:
> In order to allow multiple modules to operate MUTEX hardware through
> a common interfrace, a flexible index "mtk_mutex_table_index" needs
> to
> be added to replace original component ID so that like DDP and MDP
> can add their own MUTEX table settings independently.
>
> In addition, 4 generic interface "mtk_mutex_set_mod",
> "mtk_mutex_set_sof",
> "mtk_mutex_clear_mod" and "mtk_mutex_clear_sof" have been added,
> which is
> expected to replace the "mtk_mutex_add_comp" and
> "mtk_mutex_remove_comp"
> pair originally dedicated to DDP in the future.
>
> Signed-off-by: Moudy Ho <moudy.ho@mediatek.com>
> Reviewed-by: AngeloGioacchino Del Regno <
> angelogioacchino.delregno@collabora.com>
> ---
> drivers/soc/mediatek/mtk-mutex.c | 88
> ++++++++++++++++++++++++++
> include/linux/soc/mediatek/mtk-mutex.h | 22 +++++++
> 2 files changed, 110 insertions(+)
>
> diff --git a/drivers/soc/mediatek/mtk-mutex.c
> b/drivers/soc/mediatek/mtk-mutex.c
> index aaf8fc1abb43..a62ac1811419 100644
> --- a/drivers/soc/mediatek/mtk-mutex.c
> +++ b/drivers/soc/mediatek/mtk-mutex.c
> @@ -156,6 +156,8 @@ struct mtk_mutex_data {
> const unsigned int *mutex_sof;
> const unsigned int mutex_mod_reg;
> const unsigned int mutex_sof_reg;
> + const unsigned int *mutex_table_mod;
> + const unsigned int *mutex_table_sof;
> const bool no_clk;
> };
>
> @@ -530,6 +532,92 @@ void mtk_mutex_release(struct mtk_mutex *mutex)
> }
> EXPORT_SYMBOL_GPL(mtk_mutex_release);
>
> +static int mtk_mutex_write_mod(struct mtk_mutex *mutex,
> + enum mtk_mutex_table_index idx, bool
> clear)
> +{
> + struct mtk_mutex_ctx *mtx = container_of(mutex, struct
> mtk_mutex_ctx,
> + mutex[mutex->id]);
> + unsigned int reg;
> + unsigned int offset;
> +
> + WARN_ON(&mtx->mutex[mutex->id] != mutex);
> +
> + if (idx < MUTEX_TABLE_IDX_MDP_RDMA0 ||
> + idx >= MUTEX_TABLE_IDX_MAX) {
> + dev_err(mtx->dev, "Not supported MOD table index : %d",
> idx);
> + return -EINVAL;
> + }
> +
> + offset = DISP_REG_MUTEX_MOD(mtx->data->mutex_mod_reg,
> + mutex->id);
> + reg = readl_relaxed(mtx->regs + offset);
> +
> + if (clear)
> + reg &= ~BIT(mtx->data->mutex_table_mod[idx]);
> + else
> + reg |= BIT(mtx->data->mutex_table_mod[idx]);
> +
> + writel_relaxed(reg, mtx->regs + offset);
> +
> + return 0;
> +}
> +
> +int mtk_mutex_set_mod(struct mtk_mutex *mutex,
> + enum mtk_mutex_table_index idx)
> +{
> + return mtk_mutex_write_mod(mutex, idx, false);
> +}
> +EXPORT_SYMBOL_GPL(mtk_mutex_set_mod);
Why not just export symbol of mtk_mutex_write_mod() and drop
mtk_mutex_set_mod()/mtk_mutex_clear_mod()?
> +
> +int mtk_mutex_clear_mod(struct mtk_mutex *mutex,
> + enum mtk_mutex_table_index idx)
> +{
> + return mtk_mutex_write_mod(mutex, idx, true);
> +}
> +EXPORT_SYMBOL_GPL(mtk_mutex_clear_mod);
> +
> +int mtk_mutex_write_sof(struct mtk_mutex *mutex,
> + enum mtk_mutex_table_index idx, bool clear)
> +{
> + struct mtk_mutex_ctx *mtx = container_of(mutex, struct
> mtk_mutex_ctx,
> + mutex[mutex->id]);
> + unsigned int sof_id, val;
> +
> + WARN_ON(&mtx->mutex[mutex->id] != mutex);
> +
> + if (idx < MUTEX_TABLE_IDX_MDP_RDMA0 ||
> + idx >= MUTEX_TABLE_IDX_MAX) {
> + dev_err(mtx->dev, "Not supported SOF table index : %d",
> idx);
> + return -EINVAL;
> + }
> +
> + sof_id = mtx->data->mutex_table_sof[idx];
Why do you map each idx to a sof? For each idx, we could choose sof by
different application. I would like to change parameter
mtk_mutex_table_index to mtk_mutex_sof_index.
Regards,
CK
> +
> + if (clear)
> + val = MUTEX_SOF_SINGLE_MODE;
> + else
> + val = mtx->data->mutex_sof[sof_id];
> +
> + writel_relaxed(val, mtx->regs +
> + DISP_REG_MUTEX_SOF(mtx->data->mutex_sof_reg,
> mutex->id));
> +
> + return 0;
> +}
> +
> +int mtk_mutex_set_sof(struct mtk_mutex *mutex,
> + enum mtk_mutex_table_index idx)
> +{
> + return mtk_mutex_write_sof(mutex, idx, false);
> +}
> +EXPORT_SYMBOL_GPL(mtk_mutex_set_sof);
> +
> +int mtk_mutex_clear_sof(struct mtk_mutex *mutex,
> + enum mtk_mutex_table_index idx)
> +{
> + return mtk_mutex_write_sof(mutex, idx, true);
> +}
> +EXPORT_SYMBOL_GPL(mtk_mutex_clear_sof);
> +
> static int mtk_mutex_probe(struct platform_device *pdev)
> {
> struct device *dev = &pdev->dev;
> diff --git a/include/linux/soc/mediatek/mtk-mutex.h
> b/include/linux/soc/mediatek/mtk-mutex.h
> index 6fe4ffbde290..f174452212d6 100644
> --- a/include/linux/soc/mediatek/mtk-mutex.h
> +++ b/include/linux/soc/mediatek/mtk-mutex.h
> @@ -10,6 +10,20 @@ struct regmap;
> struct device;
> struct mtk_mutex;
>
> +enum mtk_mutex_table_index {
> + /* MDP table index */
> + MUTEX_TABLE_IDX_MDP_RDMA0,
> + MUTEX_TABLE_IDX_MDP_RSZ0,
> + MUTEX_TABLE_IDX_MDP_RSZ1,
> + MUTEX_TABLE_IDX_MDP_TDSHP0,
> + MUTEX_TABLE_IDX_MDP_WROT0,
> + MUTEX_TABLE_IDX_MDP_WDMA,
> + MUTEX_TABLE_IDX_MDP_AAL0,
> + MUTEX_TABLE_IDX_MDP_CCORR0,
> +
> + MUTEX_TABLE_IDX_MAX /* ALWAYS keep at the end */
> +};
> +
> struct mtk_mutex *mtk_mutex_get(struct device *dev);
> int mtk_mutex_prepare(struct mtk_mutex *mutex);
> void mtk_mutex_add_comp(struct mtk_mutex *mutex,
> @@ -22,5 +36,13 @@ void mtk_mutex_unprepare(struct mtk_mutex *mutex);
> void mtk_mutex_put(struct mtk_mutex *mutex);
> void mtk_mutex_acquire(struct mtk_mutex *mutex);
> void mtk_mutex_release(struct mtk_mutex *mutex);
> +int mtk_mutex_set_mod(struct mtk_mutex *mutex,
> + enum mtk_mutex_table_index idx);
> +int mtk_mutex_clear_mod(struct mtk_mutex *mutex,
> + enum mtk_mutex_table_index idx);
> +int mtk_mutex_set_sof(struct mtk_mutex *mutex,
> + enum mtk_mutex_table_index idx);
> +int mtk_mutex_clear_sof(struct mtk_mutex *mutex,
> + enum mtk_mutex_table_index idx);
>
> #endif /* MTK_MUTEX_H */
next prev parent reply other threads:[~2022-05-25 3:28 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-05-12 8:41 [PATCH v18 0/6] Add mutex support for MDP Moudy Ho
2022-05-12 8:41 ` [PATCH v18 1/6] soc: mediatek: mutex: add common interface for modules setting Moudy Ho
2022-05-12 10:30 ` Rex-BC Chen
2022-05-25 3:27 ` CK Hu [this message]
2022-05-12 8:41 ` [PATCH v18 2/6] soc: mediatek: mutex: add 8183 MUTEX MOD settings for MDP Moudy Ho
2022-05-12 10:31 ` Rex-BC Chen
2022-05-12 8:41 ` [PATCH v18 3/6] dt-bindings: soc: mediatek: move out common module from display folder Moudy Ho
2022-05-12 8:41 ` [PATCH v18 4/6] dt-bindings: soc: mediatek: add gce-client-reg for MUTEX Moudy Ho
2022-05-12 8:41 ` [PATCH v18 5/6] dts: arm64: mt8183: add GCE client property for Mediatek MUTEX Moudy Ho
2022-05-12 8:41 ` [PATCH v18 6/6] soc: mediatek: mutex: add functions that operate registers by CMDQ Moudy Ho
2022-05-12 10:32 ` Rex-BC Chen
2022-05-27 9:30 ` CK Hu
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=05ad616704053c3f9b3275cd557b99bd56b3f40f.camel@mediatek.com \
--to=ck.hu@mediatek.com \
--cc=Project_Global_Chrome_Upstream_Group@mediatek.com \
--cc=acourbot@chromium.org \
--cc=allen-kh.cheng@mediatek.com \
--cc=angelogioacchino.delregno@collabora.com \
--cc=benjamin.gaignard@collabora.com \
--cc=cellopoint.kai@gmail.com \
--cc=chunkuang.hu@kernel.org \
--cc=daoyuan.huang@mediatek.com \
--cc=devicetree@vger.kernel.org \
--cc=drinkcat@chromium.org \
--cc=hsinyi@google.com \
--cc=hverkuil-cisco@xs4all.nl \
--cc=jason-jh.lin@mediatek.com \
--cc=krzysztof.kozlowski+dt@linaro.org \
--cc=laurent.pinchart@ideasonboard.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=mchehab@kernel.org \
--cc=moudy.ho@mediatek.com \
--cc=pihsun@chromium.org \
--cc=ping-hsun.wu@mediatek.com \
--cc=randy.wu@mediatek.com \
--cc=river.cheng@mediatek.com \
--cc=rob@landley.net \
--cc=robh+dt@kernel.org \
--cc=roy-cw.yeh@mediatek.com \
--cc=tfiga@chromium.org \
--cc=xiandong.wang@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
all inboxes | Powered by JetHome®