From: Argus Lin <argus.lin@mediatek.com>
To: Matthias Brugger <matthias.bgg@gmail.com>
Cc: Rob Herring <robh+dt@kernel.org>,
Mark Rutland <mark.rutland@arm.com>,
Catalin Marinas <catalin.marinas@arm.com>,
Will Deacon <will.deacon@arm.com>,
Chenglin Xu <chenglin.xu@mediatek.com>,
Sean Wang <sean.wang@mediatek.com>,
wsd_upstream@mediatek.com, henryc.chen@mediatek.com,
flora.fu@mediatek.com, Chen Zhong <chen.zhong@mediatek.com>,
Christophe Jaillet <christophe.jaillet@wanadoo.fr>,
"shailendra . v" <shailendra.v@samsung.com>,
devicetree@vger.kernel.org, linux-kernel@vger.kernel.org,
linux-arm-kernel@lists.infradead.org,
linux-mediatek@lists.infradead.org
Subject: Re: [PATCH V3 3/4] soc: mediatek: pwrap: add mt6351 for mt6797 SoCs
Date: Mon, 30 Apr 2018 15:53:41 +0800 [thread overview]
Message-ID: <1525074821.22276.6.camel@mtkswgap22> (raw)
In-Reply-To: <427130f0-9f7e-22cc-3679-2a8d22124515@gmail.com>
[-- Attachment #1.1: Type: text/html, Size: 7027 bytes --]
[-- Attachment #1.2: Type: text/plain, Size: 3784 bytes --]
On Tue, 2018-04-17 at 23:10 +0200, Matthias Brugger wrote:
> Please update the subject line, we don't add mt5797 here.
Dear matthias:
I can't find where I wrote mt5797 at this patch.
>
> More comments below.
>
> On 03/23/2018 09:32 AM, argus.lin@mediatek.com wrote:
> > From: Argus Lin <argus.lin@mediatek.com>
> >
> > mt6351 is a new power management IC and it is
> > used for mt6797 SoCs. We need to add mt6351_regs for
> > pmic register mapping and pmic_mt6351 for
> > register accessing by regmap.
> >
> > Signed-off-by: Argus Lin <argus.lin@mediatek.com>
> > ---
> > drivers/soc/mediatek/mtk-pmic-wrap.c | 31 +++++++++++++++++++++++++++++--
> > 1 file changed, 29 insertions(+), 2 deletions(-)
> >
> > diff --git a/drivers/soc/mediatek/mtk-pmic-wrap.c b/drivers/soc/mediatek/mtk-pmic-wrap.c
> > index d0a0a3d7e88d..d81a585fadf5 100644
> > --- a/drivers/soc/mediatek/mtk-pmic-wrap.c
> > +++ b/drivers/soc/mediatek/mtk-pmic-wrap.c
> > @@ -153,6 +153,21 @@ static const u32 mt6397_regs[] = {
> > [PWRAP_DEW_CIPHER_SWRST] = 0xbc24,
> > };
> >
> > +static const u32 mt6351_regs[] = {
> > + [PWRAP_DEW_DIO_EN] = 0x02F2,
> > + [PWRAP_DEW_READ_TEST] = 0x02F4,
> > + [PWRAP_DEW_WRITE_TEST] = 0x02F6,
> > + [PWRAP_DEW_CRC_EN] = 0x02FA,
> > + [PWRAP_DEW_CRC_VAL] = 0x02FC,
> > + [PWRAP_DEW_CIPHER_KEY_SEL] = 0x0300,
> > + [PWRAP_DEW_CIPHER_IV_SEL] = 0x0302,
> > + [PWRAP_DEW_CIPHER_EN] = 0x0304,
> > + [PWRAP_DEW_CIPHER_RDY] = 0x0306,
> > + [PWRAP_DEW_CIPHER_MODE] = 0x0308,
> > + [PWRAP_DEW_CIPHER_SWRST] = 0x030A,
> > + [PWRAP_DEW_RDDMY_NO] = 0x030C,
> > +};
> > +
> > enum pwrap_regs {
> > PWRAP_MUX_SEL,
> > PWRAP_WRAP_EN,
> > @@ -721,6 +736,7 @@ static int mt8135_regs[] = {
> >
> > enum pmic_type {
> > PMIC_MT6323,
> > + PMIC_MT6351,
> > PMIC_MT6380,
> > PMIC_MT6397,
> > };
> > @@ -1179,8 +1195,6 @@ static int pwrap_init_cipher(struct pmic_wrapper *wrp)
> > pwrap_write(wrp, wrp->slave->dew_regs[PWRAP_DEW_CIPHER_SWRST], 0x0);
> > pwrap_write(wrp, wrp->slave->dew_regs[PWRAP_DEW_CIPHER_KEY_SEL], 0x1);
> > pwrap_write(wrp, wrp->slave->dew_regs[PWRAP_DEW_CIPHER_IV_SEL], 0x2);
> > - pwrap_write(wrp, wrp->slave->dew_regs[PWRAP_DEW_CIPHER_LOAD], 0x1);
> > - pwrap_write(wrp, wrp->slave->dew_regs[PWRAP_DEW_CIPHER_START], 0x1);
>
> That might break the driver for other devices. You can't just delete these lines
> without explanation. If you think these lines are not needed, then please put
> the deletion in another patch explaining why.
>
Dear matthias:
It is really a bug here. Below is the comment from you by patch V1.
The register of PWRAP_DEW_CIPHER_LOAD and PWRAP_DEW_CIPHER_START only
exist at mt6397.
But I think I can still separate those lines to another patch and
declare the reason.
> }
>
> /* Config cipher mode @PMIC */
> @@ -1080,8 +1158,6 @@ static int pwrap_init_cipher(struct pmic_wrapper
*wrp)
> pwrap_write(wrp, wrp->slave->dew_regs[PWRAP_DEW_CIPHER_SWRST],
0x0);
> pwrap_write(wrp, wrp->slave->dew_regs[PWRAP_DEW_CIPHER_KEY_SEL],
0x1);
> pwrap_write(wrp, wrp->slave->dew_regs[PWRAP_DEW_CIPHER_IV_SEL],
0x2);
> - pwrap_write(wrp, wrp->slave->dew_regs[PWRAP_DEW_CIPHER_LOAD],
0x1);
> - pwrap_write(wrp, wrp->slave->dew_regs[PWRAP_DEW_CIPHER_START],
0x1);
>
Ok, it looks like these two lines are actually a bug, which shouldn't be
here.
Adding John, as he added these calls twice in
5ae48040aa47 ("soc: mediatek: PMIC wrap: add mt6323 slave support")
@John, this is an oversight in your commit, right?
If so, we should fix this in a separate patch, concerning to send it to
stable
as well.
> Other then these two comments, patch looks fine.
>
> Regards,
> Matthias
next prev parent reply other threads:[~2018-04-30 7:53 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-03-23 8:32 [PATCH V3 0/4] Pwrap: Mediatek pwrap driver for mt6797 argus.lin
2018-03-23 8:32 ` [PATCH V3 1/4] dt-bindings: pwrap: mediatek: add MT6351 PMIC support for MT6797 argus.lin
2018-03-23 8:32 ` [PATCH V3 2/4] soc: mediatek: pwrap: add pwrap for mt6797 SoCs argus.lin
[not found] ` <20180323083238.13569-3-argus.lin-NuS5LvNUpcJWk0Htik3J/w@public.gmane.org>
2018-04-17 15:22 ` Matthias Brugger
2018-03-23 8:32 ` [PATCH V3 3/4] soc: mediatek: pwrap: add mt6351 " argus.lin
2018-04-17 21:10 ` Matthias Brugger
2018-04-30 7:53 ` Argus Lin [this message]
2018-04-30 9:14 ` Matthias Brugger
2018-03-23 8:32 ` [PATCH V3 4/4] arm64: dts: mt6797: add pwrap support for mt6797 argus.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=1525074821.22276.6.camel@mtkswgap22 \
--to=argus.lin@mediatek.com \
--cc=catalin.marinas@arm.com \
--cc=chen.zhong@mediatek.com \
--cc=chenglin.xu@mediatek.com \
--cc=christophe.jaillet@wanadoo.fr \
--cc=devicetree@vger.kernel.org \
--cc=flora.fu@mediatek.com \
--cc=henryc.chen@mediatek.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mediatek@lists.infradead.org \
--cc=mark.rutland@arm.com \
--cc=matthias.bgg@gmail.com \
--cc=robh+dt@kernel.org \
--cc=sean.wang@mediatek.com \
--cc=shailendra.v@samsung.com \
--cc=will.deacon@arm.com \
--cc=wsd_upstream@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).