From: "Nancy Lin (林欣螢)" <Nancy.Lin@mediatek.com>
To: "matthias.bgg@gmail.com" <matthias.bgg@gmail.com>,
"nfraprado@collabora.com" <nfraprado@collabora.com>
Cc: "llvm@lists.linux.dev" <llvm@lists.linux.dev>,
"Yongqiang Niu (牛永强)" <yongqiang.niu@mediatek.com>,
"robh+dt@kernel.org" <robh+dt@kernel.org>,
"Singo Chang (張興國)" <Singo.Chang@mediatek.com>,
"nathan@kernel.org" <nathan@kernel.org>,
"linux-mediatek@lists.infradead.org"
<linux-mediatek@lists.infradead.org>,
"chunkuang.hu@kernel.org" <chunkuang.hu@kernel.org>,
"Jason-JH Lin (林睿祥)" <Jason-JH.Lin@mediatek.com>,
"linux@roeck-us.net" <linux@roeck-us.net>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
"devicetree@vger.kernel.org" <devicetree@vger.kernel.org>,
"daniel@ffwll.ch" <daniel@ffwll.ch>,
"p.zabel@pengutronix.de" <p.zabel@pengutronix.de>,
"dri-devel@lists.freedesktop.org"
<dri-devel@lists.freedesktop.org>,
Project_Global_Chrome_Upstream_Group
<Project_Global_Chrome_Upstream_Group@mediatek.com>,
"linux-arm-kernel@lists.infradead.org"
<linux-arm-kernel@lists.infradead.org>,
"wim@linux-watchdog.org" <wim@linux-watchdog.org>,
"airlied@linux.ie" <airlied@linux.ie>,
"angelogioacchino.delregno@collabora.com"
<angelogioacchino.delregno@collabora.com>,
"ndesaulniers@google.com" <ndesaulniers@google.com>
Subject: Re: [PATCH v28 05/11] soc: mediatek: refine code to use mtk_mmsys_update_bits API
Date: Thu, 24 Nov 2022 09:38:02 +0000 [thread overview]
Message-ID: <f726657c3d2b16ed18e9d24a69b736970c0cf316.camel@mediatek.com> (raw)
In-Reply-To: <aa7cab9c-8fe2-b42e-84ba-1aeb79d50190@gmail.com>
Dear Matthias,
Thanks for the review.
On Thu, 2022-11-10 at 14:12 +0100, Matthias Brugger wrote:
>
> On 08/11/2022 20:43, Nícolas F. R. A. Prado wrote:
> > On Tue, Nov 08, 2022 at 06:37:19PM +0100, Matthias Brugger wrote:
> > >
> > >
> > > On 07/11/2022 08:22, Nancy.Lin wrote:
> > > > Simplify code for update mmsys reg.
> > > >
> > > > Signed-off-by: Nancy.Lin <nancy.lin@mediatek.com>
> > > > Reviewed-by: AngeloGioacchino Del Regno <
> > > > angelogioacchino.delregno@collabora.com>
> > > > Reviewed-by: CK Hu <ck.hu@mediatek.com>
> > > > Tested-by: AngeloGioacchino Del Regno <
> > > > angelogioacchino.delregno@collabora.com>
> > > > Tested-by: Bo-Chen Chen <rex-bc.chen@mediatek.com>
> > > > Reviewed-by: Nícolas F. R. A. Prado <nfraprado@collabora.com>
> > > > ---
> > > > drivers/soc/mediatek/mtk-mmsys.c | 45 ++++++++++++--------
> > > > ------------
> > > > 1 file changed, 16 insertions(+), 29 deletions(-)
> > > >
> > > > diff --git a/drivers/soc/mediatek/mtk-mmsys.c
> > > > b/drivers/soc/mediatek/mtk-mmsys.c
> > > > index 9a327eb5d9d7..73c8bd27e6ae 100644
> > > > --- a/drivers/soc/mediatek/mtk-mmsys.c
> > > > +++ b/drivers/soc/mediatek/mtk-mmsys.c
> > > > @@ -99,22 +99,27 @@ struct mtk_mmsys {
> > > > struct reset_controller_dev rcdev;
> > > > };
> > > > +static void mtk_mmsys_update_bits(struct mtk_mmsys *mmsys, u32
> > > > offset, u32 mask, u32 val)
> > > > +{
> > > > + u32 tmp;
> > > > +
> > > > + tmp = readl_relaxed(mmsys->regs + offset);
> > > > + tmp = (tmp & ~mask) | (val & mask);
> > >
> > > I'm not sure about the change in the implementation of
> > > mtk_mmsys_update_bits(). Nicolas tried to explain it to me on IRC
> > > but I
> > > wasn't totally convincing. As we have to go for at least another
> > > round of
> > > this patches, I'd like to get a clear understanding while it is
> > > needed that
> > > val bits are set to 1 in the mask.
> >
> > The point here was to make sure that mtk_mmsys_update_bits() didn't
> > allow
> > setting bits outside of the mask, since that's never what you want:
> > the entire
> > point of having a mask is to specify the bits that should be
> > updated (and the
> > ones that should be kept unchanged). So for example if you had
> >
> > mask = 0x0ff0
> > val = 0x00ff
> >
> > the previous implementation would happily overwrite the 4 least
> > significant bits
> > on the destination register, despite them not being present in the
> > mask, which
> > is wrong.
> >
> > This wrong behavior could easily lead to hard to trace bugs as soon
> > as a badly
> > formatted/wrong val is passed and an unrelated bit updated due to
> > the mask being
> > ignored.
> >
> > For reference, _regmap_update_bits() does the same masking of the
> > value [1].
> >
> > That said, given that this function already existed and was just
> > being moved,
> > it would've been cleaner to make this change in a separate commit.
> >
>
> Would have been better, but we can leave it as it.
>
> Regards,
> Matthias
>
Do you mean to keep original one (1), or keep this (2) ?
1. tmp = (tmp & ~mask) | val;
2. tmp = (tmp & ~mask) | (val & mask);
Regards,
Nancy
> > [1]
> > https://urldefense.com/v3/__https://elixir.bootlin.com/linux/latest/source/drivers/base/regmap/regmap.c*L3122__;Iw!!CTRNKA9wMg0ARbw!xSv5xbY6cv-Mg-1xDGOf3oVZ93uyrcv4tt87DKlx5emjmwufjf2DjION7GiNAaJB$
> >
> >
> > Thanks,
> > Nícolas
> >
> > >
> > > Regards,
> > > Matthias
> > >
> > > > + writel_relaxed(tmp, mmsys->regs + offset);
> > > > +}
> >
> > [..]
> > > > -static void mtk_mmsys_update_bits(struct mtk_mmsys *mmsys, u32
> > > > offset, u32 mask, u32 val)
> > > > -{
> > > > - u32 tmp;
> > > > -
> > > > - tmp = readl_relaxed(mmsys->regs + offset);
> > > > - tmp = (tmp & ~mask) | val;
> > > > - writel_relaxed(tmp, mmsys->regs + offset);
> > > > -}
> > > > -
> >
> > [..]
>
>
next prev parent reply other threads:[~2022-11-24 9:39 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20221107072243.15748-1-nancy.lin@mediatek.com>
[not found] ` <20221107072243.15748-6-nancy.lin@mediatek.com>
2022-11-08 17:37 ` [PATCH v28 05/11] soc: mediatek: refine code to use mtk_mmsys_update_bits API Matthias Brugger
2022-11-08 19:43 ` Nícolas F. R. A. Prado
2022-11-10 13:12 ` Matthias Brugger
2022-11-24 9:38 ` Nancy Lin (林欣螢) [this message]
2022-12-01 11:44 ` Chen-Yu Tsai
2022-12-27 7:54 ` Nancy Lin (林欣螢)
[not found] ` <20221107072243.15748-7-nancy.lin@mediatek.com>
2022-11-08 17:46 ` [PATCH v28 06/11] soc: mediatek: add mtk-mmsys config API for mt8195 vdosys1 Matthias Brugger
2022-11-28 7:38 ` Nancy Lin (林欣螢)
[not found] ` <20221107072243.15748-5-nancy.lin@mediatek.com>
2022-11-08 17:46 ` [PATCH v28 04/11] soc: mediatek: add mtk-mmsys support " Matthias Brugger
2022-11-08 19:10 ` Nícolas F. R. A. Prado
2022-11-09 11:18 ` Matthias Brugger
[not found] ` <20221107072243.15748-2-nancy.lin@mediatek.com>
2022-11-08 17:46 ` [PATCH v28 01/11] dt-bindings: arm: mediatek: mmsys: add vdosys1 compatible for MT8195 Matthias Brugger
2022-11-09 5:10 ` Jason-JH Lin (林睿祥)
2022-11-10 13:10 ` Matthias Brugger
2022-11-22 10:51 ` Nancy Lin (林欣螢)
2022-11-22 15:48 ` Matthias Brugger
2022-11-23 16:06 ` Krzysztof Kozlowski
2022-11-24 7:34 ` Nancy Lin (林欣螢)
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=f726657c3d2b16ed18e9d24a69b736970c0cf316.camel@mediatek.com \
--to=nancy.lin@mediatek.com \
--cc=Jason-JH.Lin@mediatek.com \
--cc=Project_Global_Chrome_Upstream_Group@mediatek.com \
--cc=Singo.Chang@mediatek.com \
--cc=airlied@linux.ie \
--cc=angelogioacchino.delregno@collabora.com \
--cc=chunkuang.hu@kernel.org \
--cc=daniel@ffwll.ch \
--cc=devicetree@vger.kernel.org \
--cc=dri-devel@lists.freedesktop.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mediatek@lists.infradead.org \
--cc=linux@roeck-us.net \
--cc=llvm@lists.linux.dev \
--cc=matthias.bgg@gmail.com \
--cc=nathan@kernel.org \
--cc=ndesaulniers@google.com \
--cc=nfraprado@collabora.com \
--cc=p.zabel@pengutronix.de \
--cc=robh+dt@kernel.org \
--cc=wim@linux-watchdog.org \
--cc=yongqiang.niu@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).