public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Sean Wang <sean.wang@mediatek.com>
To: Matthias Brugger <matthias.bgg@gmail.com>
Cc: <robh+dt@kernel.org>, <mark.rutland@arm.com>,
	<lgirdwood@gmail.com>, <broonie@kernel.org>,
	<jamesjj.liao@mediatek.com>, <henryc.chen@mediatek.com>,
	<devicetree@vger.kernel.org>,
	<linux-mediatek@lists.infradead.org>, <chen.zhong@mediatek.com>,
	<chenglin.xu@mediatek.com>, <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH v3 7/9] soc: mediatek: pwrap: add MediaTek MT6380 as one slave of pwrap
Date: Thu, 12 Oct 2017 11:44:57 +0800	[thread overview]
Message-ID: <1507779897.21840.19.camel@mtkswgap22> (raw)
In-Reply-To: <0491f3fc-0404-c775-70f3-8bc86b3cf6c8@gmail.com>

On Tue, 2017-10-10 at 12:02 +0200, Matthias Brugger wrote:
> 
> On 08/15/2017 11:09 AM, sean.wang@mediatek.com wrote:
> > From: Sean Wang <sean.wang@mediatek.com>
> > 
> > Add MediaTek MT6380 regulator becoming one of PMIC wrapper slave
> > and also add extra new regmap_config of 32-bit mode for MT6380
> > since old regmap_config of 16-bit mode can't be fit into the need.
> > 
> > Signed-off-by: Chenglin Xu <chenglin.xu@mediatek.com>
> > Signed-off-by: Chen Zhong <chen.zhong@mediatek.com>
> > Signed-off-by: Sean Wang <sean.wang@mediatek.com>
> > ---
> >   drivers/soc/mediatek/mtk-pmic-wrap.c | 25 ++++++++++++++++++++++---
> >   1 file changed, 22 insertions(+), 3 deletions(-)
> > 
> > diff --git a/drivers/soc/mediatek/mtk-pmic-wrap.c b/drivers/soc/mediatek/mtk-pmic-wrap.c
> > index 1f8b69a..047e3d9 100644
> > --- a/drivers/soc/mediatek/mtk-pmic-wrap.c
> > +++ b/drivers/soc/mediatek/mtk-pmic-wrap.c
> > @@ -501,6 +501,7 @@ struct pmic_wrapper;
> >   struct pwrap_slv_type {
> >   	const u32 *dew_regs;
> >   	enum pmic_type type;
> > +	const struct regmap_config *regmap;
> >   	/* pwrap operations are highly associated with the PMIC types,
> >   	 * so the pointers added increases flexibility allowing determination
> >   	 * which type is used by the detection through device tree.
> > @@ -1109,7 +1110,7 @@ static irqreturn_t pwrap_interrupt(int irqno, void *dev_id)
> >   	return IRQ_HANDLED;
> >   }
> >   
> > -static const struct regmap_config pwrap_regmap_config = {
> > +static const struct regmap_config pwrap_regmap_config16 = {
> >   	.reg_bits = 16,
> >   	.val_bits = 16,
> >   	.reg_stride = 2,
> > @@ -1118,9 +1119,19 @@ static const struct regmap_config pwrap_regmap_config = {
> >   	.max_register = 0xffff,
> >   };
> >   
> > +static const struct regmap_config pwrap_regmap_config32 = {
> > +	.reg_bits = 32,
> > +	.val_bits = 32,
> > +	.reg_stride = 4,
> > +	.reg_read = pwrap_regmap_read,
> > +	.reg_write = pwrap_regmap_write,
> > +	.max_register = 0xffff,
> > +};
> > +
> >   static const struct pwrap_slv_type pmic_mt6323 = {
> >   	.dew_regs = mt6323_regs,
> >   	.type = PMIC_MT6323,
> > +	.regmap = &pwrap_regmap_config16,
> >   	.pwrap_read = pwrap_read16,
> >   	.pwrap_write = pwrap_write16,
> >   };
> > @@ -1128,6 +1139,7 @@ static const struct pwrap_slv_type pmic_mt6323 = {
> >   static const struct pwrap_slv_type pmic_mt6380 = {
> >   	.dew_regs = NULL,
> >   	.type = PMIC_MT6380,
> > +	.regmap = &pwrap_regmap_config32,
> >   	.pwrap_read = pwrap_read32,
> >   	.pwrap_write = pwrap_write32,
> >   };
> > @@ -1135,6 +1147,7 @@ static const struct pwrap_slv_type pmic_mt6380 = {
> >   static const struct pwrap_slv_type pmic_mt6397 = {
> >   	.dew_regs = mt6397_regs,
> >   	.type = PMIC_MT6397,
> > +	.regmap = &pwrap_regmap_config16,
> >   	.pwrap_read = pwrap_read16,
> >   	.pwrap_write = pwrap_write16,
> >   };
> > @@ -1144,9 +1157,15 @@ static const struct of_device_id of_slave_match_tbl[] = {
> >   		.compatible = "mediatek,mt6323",
> >   		.data = &pmic_mt6323,
> >   	}, {
> > +		/* The MT6380 slave device is directly pointed to the regulator
> > +		 * device which is different from the cases MT6323 and MT6397
> > +		 * where they're one kind of MFDs.
> > +		 */
> > +		.compatible = "mediatek,mt6380-regulator",
> > +		.data = &pmic_mt6380,
> 
> I understand that mt6380 only provides a regulator and no other function other 
> PMICs provide, right?

> Then maybe write a comment like:
> The MT6380 PMIC only implements a regulator, so we bind it directly instead of 
> using a MFD. If so, we should state that in the pwrap bindings document, I think.
> 

You're right. It is worth making them better in both comments and the
bindings document. I'll do it in the next version.


> Regards,
> Matthias

  reply	other threads:[~2017-10-12  3:45 UTC|newest]

Thread overview: 22+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-08-15  9:09 [PATCH v3 0/9] Add PMIC support to MediaTek MT7622 SoC sean.wang
2017-08-15  9:09 ` [PATCH v3 1/9] dt-bindings: arm: mediatek: add MT7622 string to the PMIC wrapper doc sean.wang
2017-08-15  9:09 ` [PATCH v3 2/9] dt-bindings: regulator: Add document for MediaTek MT6380 regulator sean.wang
2017-08-15 11:50   ` Mark Brown
2017-08-15 15:06     ` Sean Wang
2017-08-15 15:10       ` Mark Brown
2017-08-15 15:10   ` Applied "regulator: Add document for MediaTek MT6380 regulator" to the regulator tree Mark Brown
2017-08-15  9:09 ` [PATCH v3 3/9] regulator: mt6380: Add support for MT6380 sean.wang
2017-08-15 15:11   ` Applied "regulator: mt6380: Add support for MT6380" to the regulator tree Mark Brown
2017-08-15  9:09 ` [PATCH v3 4/9] soc: mediatek: pwrap: add pwrap_read32 for reading in 32-bit mode sean.wang
2017-08-15  9:09 ` [PATCH v3 5/9] soc: mediatek: pwrap: add pwrap_write32 for writing " sean.wang
2017-10-10  9:38   ` Matthias Brugger
2017-10-12  3:19     ` Sean Wang
2017-08-15  9:09 ` [PATCH v3 6/9] soc: mediatek: pwrap: update pwrap_init without slave programming sean.wang
2017-10-10  9:53   ` Matthias Brugger
2017-08-15  9:09 ` [PATCH v3 7/9] soc: mediatek: pwrap: add MediaTek MT6380 as one slave of pwrap sean.wang
2017-10-10 10:02   ` Matthias Brugger
2017-10-12  3:44     ` Sean Wang [this message]
2017-08-15  9:09 ` [PATCH v3 8/9] soc: mediatek: pwrap: add support for MT7622 SoC sean.wang
2017-10-10  9:57   ` Matthias Brugger
2017-08-15  9:09 ` [PATCH v3 9/9] soc: mediatek: pwrap: fixup warnings from coding style sean.wang
2017-10-10 10:03   ` Matthias Brugger

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=1507779897.21840.19.camel@mtkswgap22 \
    --to=sean.wang@mediatek.com \
    --cc=broonie@kernel.org \
    --cc=chen.zhong@mediatek.com \
    --cc=chenglin.xu@mediatek.com \
    --cc=devicetree@vger.kernel.org \
    --cc=henryc.chen@mediatek.com \
    --cc=jamesjj.liao@mediatek.com \
    --cc=lgirdwood@gmail.com \
    --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 \
    /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