mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: AngeloGioacchino Del Regno  <angelogioacchino.delregno@collabora.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>,
	Hans Verkuil <hverkuil-cisco@xs4all.nl>,
	Jernej Skrabec <jernej.skrabec@siol.net>
Cc: Chun-Kuang Hu <chunkuang.hu@kernel.org>,
	Geert Uytterhoeven <geert+renesas@glider.be>,
	Rob Landley <rob@landley.net>,
	Laurent Pinchart <laurent.pinchart@ideasonboard.com>,
	linux-media@vger.kernel.org, devicetree@vger.kernel.org,
	linux-arm-kernel@lists.infradead.org,
	linux-mediatek@lists.infradead.org, linux-kernel@vger.kernel.org,
	Alexandre Courbot <acourbot@chromium.org>,
	tfiga@chromium.org, drinkcat@chromium.org, pihsun@chromium.org,
	hsinyi@google.com,
	Benjamin Gaignard <benjamin.gaignard@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,
	srv_heupstream@mediatek.com,
	Project_Global_Chrome_Upstream_Group@mediatek.com
Subject: Re: [PATCH v14 1/6] soc: mediatek: mutex: add common interface to accommodate multiple modules operationg MUTEX
Date: Wed, 13 Apr 2022 10:27:17 +0200	[thread overview]
Message-ID: <0193f6b6-0019-3080-2615-02225eb4bf3b@collabora.com> (raw)
In-Reply-To: <20220411072403.24016-2-moudy.ho@mediatek.com>

Il 11/04/22 09:23, Moudy Ho ha scritto:
> 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>
> Change-Id: I6a2ab74fccf36248165ce4a6b268d82a1177afc9
> ---
>   drivers/soc/mediatek/mtk-mutex.c       | 89 ++++++++++++++++++++++++++
>   include/linux/soc/mediatek/mtk-mutex.h | 21 ++++++
>   2 files changed, 110 insertions(+)
> 
> diff --git a/drivers/soc/mediatek/mtk-mutex.c b/drivers/soc/mediatek/mtk-mutex.c
> index aaf8fc1abb43..48a04dce50d5 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;
>   };
>   
> @@ -445,6 +447,54 @@ void mtk_mutex_add_comp(struct mtk_mutex *mutex,
>   }
>   EXPORT_SYMBOL_GPL(mtk_mutex_add_comp);
>   

Hello Moudy,

Some critical things, and one cleanup.

First of all, the commit title is very long, and it also contains a typo.
I would go for something like
"soc: mediatek: mutex: Add common interface for modules setting".

Also, please remove your internal "Change-Id" tag, this is meaningless on
upstream, hence not applicable here.

Now for the cleanup: I have an idea to make this a bit shorter (and please
feel free to change function names with something more appropriate, if needed):

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;

		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])

> +	reg |= 1 << mtx->data->mutex_table_mod[idx];
> +	writel_relaxed(reg, mtx->regs + offset);
> +}

int mtk_mutex_set_mod(struct mtk_mutex *mutex,
		      enum mtk_mutex_table_index idx)
{
	return mtk_mutex_write_mod(mutex, idx, false);
}

int mtk_mutex_clear_mod(struct mtk_mutex *mutex,
			enum mtk_mutex_table_index idx)
{
	return mtk_mutex_clear_mod(mutex, idx, true);
}

> +EXPORT_SYMBOL_GPL(mtk_mutex_set_mod);
> +
> +void mtk_mutex_set_sof(struct mtk_mutex *mutex,
> +		       enum mtk_mutex_table_index idx)
> +{
> +	struct mtk_mutex_ctx *mtx = container_of(mutex, struct mtk_mutex_ctx,
> +						 mutex[mutex->id]);
> +	unsigned int sof_id;
> +
> +	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;
> +	}
> +
> +	sof_id = mtx->data->mutex_table_sof[idx];

... same changes here, except we'd have something like

if (clear)
	val = MUTEX_SOF_SINGLE_MODE;
else
	val = mtx->data->mutex_sof[sof_id];

	writel_relaxed(val, ...etc)

but feel free to give me valid reasons to not use this approach.

In any case, the code looks ok to me.


Regards,
Angelo

  reply	other threads:[~2022-04-13  8:27 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-04-11  7:23 [PATCH v14 0/6] Add mutex support for MDP Moudy Ho
2022-04-11  7:23 ` [PATCH v14 1/6] soc: mediatek: mutex: add common interface to accommodate multiple modules operationg MUTEX Moudy Ho
2022-04-13  8:27   ` AngeloGioacchino Del Regno [this message]
2022-04-11  7:23 ` [PATCH v14 2/6] soc: mediatek: mutex: add 8183 MUTEX MOD settings for MDP Moudy Ho
2022-04-13  8:28   ` AngeloGioacchino Del Regno
2022-04-11  7:24 ` [PATCH v14 3/6] dt-bindings: soc: mediatek: move out common module from display folder Moudy Ho
2022-04-13  8:28   ` AngeloGioacchino Del Regno
2022-04-11  7:24 ` [PATCH v14 4/6] dt-bindings: soc: mediatek: add gce-client-reg for MUTEX Moudy Ho
2022-04-11  7:24 ` [PATCH v14 5/6] dts: arm64: mt8183: add GCE client property for Mediatek MUTEX Moudy Ho
2022-04-13  8:29   ` AngeloGioacchino Del Regno
2022-04-11  7:24 ` [PATCH v14 6/6] soc: mediatek: mutex: add functions that operate registers by CMDQ Moudy Ho
2022-04-13  8:41   ` AngeloGioacchino Del Regno
  -- strict thread matches above, loose matches on Subject: below --
2022-03-17 14:39 [PATCH v14 0/6] Add mutex support for MDP Moudy Ho
2022-03-17 14:39 ` [PATCH v14 1/6] soc: mediatek: mutex: add common interface to accommodate multiple modules operationg MUTEX Moudy Ho
2022-03-22  9:37   ` 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=0193f6b6-0019-3080-2615-02225eb4bf3b@collabora.com \
    --to=angelogioacchino.delregno@collabora.com \
    --cc=Project_Global_Chrome_Upstream_Group@mediatek.com \
    --cc=acourbot@chromium.org \
    --cc=allen-kh.cheng@mediatek.com \
    --cc=benjamin.gaignard@collabora.com \
    --cc=chunkuang.hu@kernel.org \
    --cc=daoyuan.huang@mediatek.com \
    --cc=devicetree@vger.kernel.org \
    --cc=drinkcat@chromium.org \
    --cc=geert+renesas@glider.be \
    --cc=hsinyi@google.com \
    --cc=hverkuil-cisco@xs4all.nl \
    --cc=jason-jh.lin@mediatek.com \
    --cc=jernej.skrabec@siol.net \
    --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=srv_heupstream@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®