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>,
devicetree@vger.kernel.org, linux-kernel@vger.kernel.org,
linux-arm-kernel@lists.infradead.org,
linux-mediatek@lists.infradead.org
Subject: Re: [PATCH 3/3] soc: mediatek: pwrap: add support for MT6359 PMIC
Date: Mon, 14 Oct 2019 13:17:44 +0800 [thread overview]
Message-ID: <1571030264.19600.2.camel@mtkswgap22> (raw)
In-Reply-To: <5ec86287-2a90-ca07-c9a6-262420a68fd3@gmail.com>
On Fri, 2019-10-04 at 01:27 +0200, Matthias Brugger wrote:
>
> On 03/10/2019 09:48, Argus Lin wrote:
> > MT6359 is a new power management IC and it is used for
> > MT6779 SoCs. To define mt6359_regs for pmic register mapping
> > and pmic_mt6359 for accessing register.
> >
> > Signed-off-by: Argus Lin <argus.lin@mediatek.com>
> > ---
> > drivers/soc/mediatek/mtk-pmic-wrap.c | 72 ++++++++++++++++++++++++++++++++++++
> > 1 file changed, 72 insertions(+)
> >
> > diff --git a/drivers/soc/mediatek/mtk-pmic-wrap.c b/drivers/soc/mediatek/mtk-pmic-wrap.c
> > index fa8daf2..dd04318 100644
> > --- a/drivers/soc/mediatek/mtk-pmic-wrap.c
> > +++ b/drivers/soc/mediatek/mtk-pmic-wrap.c
> > @@ -111,6 +111,29 @@ enum dew_regs {
> > PWRAP_RG_SPI_CON13,
> > PWRAP_SPISLV_KEY,
> >
> > + /* MT6359 only regs */
> > + PWRAP_DEW_CRC_SWRST,
> > + PWRAP_DEW_RG_EN_RECORD,
> > + PWRAP_DEW_RECORD_CMD0,
> > + PWRAP_DEW_RECORD_CMD1,
> > + PWRAP_DEW_RECORD_CMD2,
> > + PWRAP_DEW_RECORD_CMD3,
> > + PWRAP_DEW_RECORD_CMD4,
> > + PWRAP_DEW_RECORD_CMD5,
> > + PWRAP_DEW_RECORD_WDATA0,
> > + PWRAP_DEW_RECORD_WDATA1,
> > + PWRAP_DEW_RECORD_WDATA2,
> > + PWRAP_DEW_RECORD_WDATA3,
> > + PWRAP_DEW_RECORD_WDATA4,
> > + PWRAP_DEW_RECORD_WDATA5,
> > + PWRAP_DEW_RG_ADDR_TARGET,
> > + PWRAP_DEW_RG_ADDR_MASK,
> > + PWRAP_DEW_RG_WDATA_TARGET,
> > + PWRAP_DEW_RG_WDATA_MASK,
> > + PWRAP_DEW_RG_SPI_RECORD_CLR,
> > + PWRAP_DEW_RG_CMD_ALERT_CLR,
> > + PWRAP_DEW_SPISLV_KEY,
>
> That looks like PWRAP_SPISLV_KEY from MT6358.
>
> Regards,
> Matthias
>
Yes, I think I can reuse the PWRAP_SPISLV_KEY of MT6358.
B.R.
Argus
> > +
> > /* MT6397 only regs */
> > PWRAP_DEW_EVENT_OUT_EN,
> > PWRAP_DEW_EVENT_SRC_EN,
> > @@ -197,6 +220,42 @@ enum dew_regs {
> > [PWRAP_SPISLV_KEY] = 0x044a,
> > };
> >
> > +static const u32 mt6359_regs[] = {
> > + [PWRAP_DEW_RG_EN_RECORD] = 0x040a,
> > + [PWRAP_DEW_DIO_EN] = 0x040c,
> > + [PWRAP_DEW_READ_TEST] = 0x040e,
> > + [PWRAP_DEW_WRITE_TEST] = 0x0410,
> > + [PWRAP_DEW_CRC_SWRST] = 0x0412,
> > + [PWRAP_DEW_CRC_EN] = 0x0414,
> > + [PWRAP_DEW_CRC_VAL] = 0x0416,
> > + [PWRAP_DEW_CIPHER_KEY_SEL] = 0x0418,
> > + [PWRAP_DEW_CIPHER_IV_SEL] = 0x041a,
> > + [PWRAP_DEW_CIPHER_EN] = 0x041c,
> > + [PWRAP_DEW_CIPHER_RDY] = 0x041e,
> > + [PWRAP_DEW_CIPHER_MODE] = 0x0420,
> > + [PWRAP_DEW_CIPHER_SWRST] = 0x0422,
> > + [PWRAP_DEW_RDDMY_NO] = 0x0424,
> > + [PWRAP_DEW_RECORD_CMD0] = 0x0428,
> > + [PWRAP_DEW_RECORD_CMD1] = 0x042a,
> > + [PWRAP_DEW_RECORD_CMD2] = 0x042c,
> > + [PWRAP_DEW_RECORD_CMD3] = 0x042e,
> > + [PWRAP_DEW_RECORD_CMD4] = 0x0430,
> > + [PWRAP_DEW_RECORD_CMD5] = 0x0432,
> > + [PWRAP_DEW_RECORD_WDATA0] = 0x0434,
> > + [PWRAP_DEW_RECORD_WDATA1] = 0x0436,
> > + [PWRAP_DEW_RECORD_WDATA2] = 0x0438,
> > + [PWRAP_DEW_RECORD_WDATA3] = 0x043a,
> > + [PWRAP_DEW_RECORD_WDATA4] = 0x043c,
> > + [PWRAP_DEW_RECORD_WDATA5] = 0x043e,
> > + [PWRAP_DEW_RG_ADDR_TARGET] = 0x0440,
> > + [PWRAP_DEW_RG_ADDR_MASK] = 0x0442,
> > + [PWRAP_DEW_RG_WDATA_TARGET] = 0x0444,
> > + [PWRAP_DEW_RG_WDATA_MASK] = 0x0446,
> > + [PWRAP_DEW_RG_SPI_RECORD_CLR] = 0x0448,
> > + [PWRAP_DEW_RG_CMD_ALERT_CLR] = 0x0448,
> > + [PWRAP_DEW_SPISLV_KEY] = 0x044a,
> > +};
> > +
> > static const u32 mt6397_regs[] = {
> > [PWRAP_DEW_BASE] = 0xbc00,
> > [PWRAP_DEW_EVENT_OUT_EN] = 0xbc00,
> > @@ -977,6 +1036,7 @@ enum pmic_type {
> > PMIC_MT6351,
> > PMIC_MT6357,
> > PMIC_MT6358,
> > + PMIC_MT6359,
> > PMIC_MT6380,
> > PMIC_MT6397,
> > };
> > @@ -1757,6 +1817,15 @@ static irqreturn_t pwrap_interrupt(int irqno, void *dev_id)
> > .pwrap_write = pwrap_write16,
> > };
> >
> > +static const struct pwrap_slv_type pmic_mt6359 = {
> > + .dew_regs = mt6359_regs,
> > + .type = PMIC_MT6359,
> > + .regmap = &pwrap_regmap_config16,
> > + .caps = PWRAP_SLV_CAP_DUALIO,
> > + .pwrap_read = pwrap_read16,
> > + .pwrap_write = pwrap_write16,
> > +};
> > +
> > static const struct pwrap_slv_type pmic_mt6380 = {
> > .dew_regs = NULL,
> > .type = PMIC_MT6380,
> > @@ -1790,6 +1859,9 @@ static irqreturn_t pwrap_interrupt(int irqno, void *dev_id)
> > .compatible = "mediatek,mt6358",
> > .data = &pmic_mt6358,
> > }, {
> > + .compatible = "mediatek,mt6359",
> > + .data = &pmic_mt6359,
> > + }, {
> > /* The MT6380 PMIC only implements a regulator, so we bind it
> > * directly instead of using a MFD.
> > */
> > --
> > 1.8.1.1.dirty
> >
WARNING: multiple messages have this Message-ID (diff)
From: Argus Lin <argus.lin@mediatek.com>
To: Matthias Brugger <matthias.bgg@gmail.com>
Cc: Mark Rutland <mark.rutland@arm.com>,
devicetree@vger.kernel.org, wsd_upstream@mediatek.com,
Chenglin Xu <chenglin.xu@mediatek.com>,
Catalin Marinas <catalin.marinas@arm.com>,
Sean Wang <sean.wang@mediatek.com>,
Will Deacon <will.deacon@arm.com>,
linux-kernel@vger.kernel.org, henryc.chen@mediatek.com,
flora.fu@mediatek.com, Rob Herring <robh+dt@kernel.org>,
Christophe Jaillet <christophe.jaillet@wanadoo.fr>,
linux-mediatek@lists.infradead.org,
Chen Zhong <chen.zhong@mediatek.com>,
linux-arm-kernel@lists.infradead.org
Subject: Re: [PATCH 3/3] soc: mediatek: pwrap: add support for MT6359 PMIC
Date: Mon, 14 Oct 2019 13:17:44 +0800 [thread overview]
Message-ID: <1571030264.19600.2.camel@mtkswgap22> (raw)
In-Reply-To: <5ec86287-2a90-ca07-c9a6-262420a68fd3@gmail.com>
On Fri, 2019-10-04 at 01:27 +0200, Matthias Brugger wrote:
>
> On 03/10/2019 09:48, Argus Lin wrote:
> > MT6359 is a new power management IC and it is used for
> > MT6779 SoCs. To define mt6359_regs for pmic register mapping
> > and pmic_mt6359 for accessing register.
> >
> > Signed-off-by: Argus Lin <argus.lin@mediatek.com>
> > ---
> > drivers/soc/mediatek/mtk-pmic-wrap.c | 72 ++++++++++++++++++++++++++++++++++++
> > 1 file changed, 72 insertions(+)
> >
> > diff --git a/drivers/soc/mediatek/mtk-pmic-wrap.c b/drivers/soc/mediatek/mtk-pmic-wrap.c
> > index fa8daf2..dd04318 100644
> > --- a/drivers/soc/mediatek/mtk-pmic-wrap.c
> > +++ b/drivers/soc/mediatek/mtk-pmic-wrap.c
> > @@ -111,6 +111,29 @@ enum dew_regs {
> > PWRAP_RG_SPI_CON13,
> > PWRAP_SPISLV_KEY,
> >
> > + /* MT6359 only regs */
> > + PWRAP_DEW_CRC_SWRST,
> > + PWRAP_DEW_RG_EN_RECORD,
> > + PWRAP_DEW_RECORD_CMD0,
> > + PWRAP_DEW_RECORD_CMD1,
> > + PWRAP_DEW_RECORD_CMD2,
> > + PWRAP_DEW_RECORD_CMD3,
> > + PWRAP_DEW_RECORD_CMD4,
> > + PWRAP_DEW_RECORD_CMD5,
> > + PWRAP_DEW_RECORD_WDATA0,
> > + PWRAP_DEW_RECORD_WDATA1,
> > + PWRAP_DEW_RECORD_WDATA2,
> > + PWRAP_DEW_RECORD_WDATA3,
> > + PWRAP_DEW_RECORD_WDATA4,
> > + PWRAP_DEW_RECORD_WDATA5,
> > + PWRAP_DEW_RG_ADDR_TARGET,
> > + PWRAP_DEW_RG_ADDR_MASK,
> > + PWRAP_DEW_RG_WDATA_TARGET,
> > + PWRAP_DEW_RG_WDATA_MASK,
> > + PWRAP_DEW_RG_SPI_RECORD_CLR,
> > + PWRAP_DEW_RG_CMD_ALERT_CLR,
> > + PWRAP_DEW_SPISLV_KEY,
>
> That looks like PWRAP_SPISLV_KEY from MT6358.
>
> Regards,
> Matthias
>
Yes, I think I can reuse the PWRAP_SPISLV_KEY of MT6358.
B.R.
Argus
> > +
> > /* MT6397 only regs */
> > PWRAP_DEW_EVENT_OUT_EN,
> > PWRAP_DEW_EVENT_SRC_EN,
> > @@ -197,6 +220,42 @@ enum dew_regs {
> > [PWRAP_SPISLV_KEY] = 0x044a,
> > };
> >
> > +static const u32 mt6359_regs[] = {
> > + [PWRAP_DEW_RG_EN_RECORD] = 0x040a,
> > + [PWRAP_DEW_DIO_EN] = 0x040c,
> > + [PWRAP_DEW_READ_TEST] = 0x040e,
> > + [PWRAP_DEW_WRITE_TEST] = 0x0410,
> > + [PWRAP_DEW_CRC_SWRST] = 0x0412,
> > + [PWRAP_DEW_CRC_EN] = 0x0414,
> > + [PWRAP_DEW_CRC_VAL] = 0x0416,
> > + [PWRAP_DEW_CIPHER_KEY_SEL] = 0x0418,
> > + [PWRAP_DEW_CIPHER_IV_SEL] = 0x041a,
> > + [PWRAP_DEW_CIPHER_EN] = 0x041c,
> > + [PWRAP_DEW_CIPHER_RDY] = 0x041e,
> > + [PWRAP_DEW_CIPHER_MODE] = 0x0420,
> > + [PWRAP_DEW_CIPHER_SWRST] = 0x0422,
> > + [PWRAP_DEW_RDDMY_NO] = 0x0424,
> > + [PWRAP_DEW_RECORD_CMD0] = 0x0428,
> > + [PWRAP_DEW_RECORD_CMD1] = 0x042a,
> > + [PWRAP_DEW_RECORD_CMD2] = 0x042c,
> > + [PWRAP_DEW_RECORD_CMD3] = 0x042e,
> > + [PWRAP_DEW_RECORD_CMD4] = 0x0430,
> > + [PWRAP_DEW_RECORD_CMD5] = 0x0432,
> > + [PWRAP_DEW_RECORD_WDATA0] = 0x0434,
> > + [PWRAP_DEW_RECORD_WDATA1] = 0x0436,
> > + [PWRAP_DEW_RECORD_WDATA2] = 0x0438,
> > + [PWRAP_DEW_RECORD_WDATA3] = 0x043a,
> > + [PWRAP_DEW_RECORD_WDATA4] = 0x043c,
> > + [PWRAP_DEW_RECORD_WDATA5] = 0x043e,
> > + [PWRAP_DEW_RG_ADDR_TARGET] = 0x0440,
> > + [PWRAP_DEW_RG_ADDR_MASK] = 0x0442,
> > + [PWRAP_DEW_RG_WDATA_TARGET] = 0x0444,
> > + [PWRAP_DEW_RG_WDATA_MASK] = 0x0446,
> > + [PWRAP_DEW_RG_SPI_RECORD_CLR] = 0x0448,
> > + [PWRAP_DEW_RG_CMD_ALERT_CLR] = 0x0448,
> > + [PWRAP_DEW_SPISLV_KEY] = 0x044a,
> > +};
> > +
> > static const u32 mt6397_regs[] = {
> > [PWRAP_DEW_BASE] = 0xbc00,
> > [PWRAP_DEW_EVENT_OUT_EN] = 0xbc00,
> > @@ -977,6 +1036,7 @@ enum pmic_type {
> > PMIC_MT6351,
> > PMIC_MT6357,
> > PMIC_MT6358,
> > + PMIC_MT6359,
> > PMIC_MT6380,
> > PMIC_MT6397,
> > };
> > @@ -1757,6 +1817,15 @@ static irqreturn_t pwrap_interrupt(int irqno, void *dev_id)
> > .pwrap_write = pwrap_write16,
> > };
> >
> > +static const struct pwrap_slv_type pmic_mt6359 = {
> > + .dew_regs = mt6359_regs,
> > + .type = PMIC_MT6359,
> > + .regmap = &pwrap_regmap_config16,
> > + .caps = PWRAP_SLV_CAP_DUALIO,
> > + .pwrap_read = pwrap_read16,
> > + .pwrap_write = pwrap_write16,
> > +};
> > +
> > static const struct pwrap_slv_type pmic_mt6380 = {
> > .dew_regs = NULL,
> > .type = PMIC_MT6380,
> > @@ -1790,6 +1859,9 @@ static irqreturn_t pwrap_interrupt(int irqno, void *dev_id)
> > .compatible = "mediatek,mt6358",
> > .data = &pmic_mt6358,
> > }, {
> > + .compatible = "mediatek,mt6359",
> > + .data = &pmic_mt6359,
> > + }, {
> > /* The MT6380 PMIC only implements a regulator, so we bind it
> > * directly instead of using a MFD.
> > */
> > --
> > 1.8.1.1.dirty
> >
_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel
WARNING: multiple messages have this Message-ID (diff)
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>,
<devicetree@vger.kernel.org>, <linux-kernel@vger.kernel.org>,
<linux-arm-kernel@lists.infradead.org>,
<linux-mediatek@lists.infradead.org>
Subject: Re: [PATCH 3/3] soc: mediatek: pwrap: add support for MT6359 PMIC
Date: Mon, 14 Oct 2019 13:17:44 +0800 [thread overview]
Message-ID: <1571030264.19600.2.camel@mtkswgap22> (raw)
In-Reply-To: <5ec86287-2a90-ca07-c9a6-262420a68fd3@gmail.com>
On Fri, 2019-10-04 at 01:27 +0200, Matthias Brugger wrote:
>
> On 03/10/2019 09:48, Argus Lin wrote:
> > MT6359 is a new power management IC and it is used for
> > MT6779 SoCs. To define mt6359_regs for pmic register mapping
> > and pmic_mt6359 for accessing register.
> >
> > Signed-off-by: Argus Lin <argus.lin@mediatek.com>
> > ---
> > drivers/soc/mediatek/mtk-pmic-wrap.c | 72 ++++++++++++++++++++++++++++++++++++
> > 1 file changed, 72 insertions(+)
> >
> > diff --git a/drivers/soc/mediatek/mtk-pmic-wrap.c b/drivers/soc/mediatek/mtk-pmic-wrap.c
> > index fa8daf2..dd04318 100644
> > --- a/drivers/soc/mediatek/mtk-pmic-wrap.c
> > +++ b/drivers/soc/mediatek/mtk-pmic-wrap.c
> > @@ -111,6 +111,29 @@ enum dew_regs {
> > PWRAP_RG_SPI_CON13,
> > PWRAP_SPISLV_KEY,
> >
> > + /* MT6359 only regs */
> > + PWRAP_DEW_CRC_SWRST,
> > + PWRAP_DEW_RG_EN_RECORD,
> > + PWRAP_DEW_RECORD_CMD0,
> > + PWRAP_DEW_RECORD_CMD1,
> > + PWRAP_DEW_RECORD_CMD2,
> > + PWRAP_DEW_RECORD_CMD3,
> > + PWRAP_DEW_RECORD_CMD4,
> > + PWRAP_DEW_RECORD_CMD5,
> > + PWRAP_DEW_RECORD_WDATA0,
> > + PWRAP_DEW_RECORD_WDATA1,
> > + PWRAP_DEW_RECORD_WDATA2,
> > + PWRAP_DEW_RECORD_WDATA3,
> > + PWRAP_DEW_RECORD_WDATA4,
> > + PWRAP_DEW_RECORD_WDATA5,
> > + PWRAP_DEW_RG_ADDR_TARGET,
> > + PWRAP_DEW_RG_ADDR_MASK,
> > + PWRAP_DEW_RG_WDATA_TARGET,
> > + PWRAP_DEW_RG_WDATA_MASK,
> > + PWRAP_DEW_RG_SPI_RECORD_CLR,
> > + PWRAP_DEW_RG_CMD_ALERT_CLR,
> > + PWRAP_DEW_SPISLV_KEY,
>
> That looks like PWRAP_SPISLV_KEY from MT6358.
>
> Regards,
> Matthias
>
Yes, I think I can reuse the PWRAP_SPISLV_KEY of MT6358.
B.R.
Argus
> > +
> > /* MT6397 only regs */
> > PWRAP_DEW_EVENT_OUT_EN,
> > PWRAP_DEW_EVENT_SRC_EN,
> > @@ -197,6 +220,42 @@ enum dew_regs {
> > [PWRAP_SPISLV_KEY] = 0x044a,
> > };
> >
> > +static const u32 mt6359_regs[] = {
> > + [PWRAP_DEW_RG_EN_RECORD] = 0x040a,
> > + [PWRAP_DEW_DIO_EN] = 0x040c,
> > + [PWRAP_DEW_READ_TEST] = 0x040e,
> > + [PWRAP_DEW_WRITE_TEST] = 0x0410,
> > + [PWRAP_DEW_CRC_SWRST] = 0x0412,
> > + [PWRAP_DEW_CRC_EN] = 0x0414,
> > + [PWRAP_DEW_CRC_VAL] = 0x0416,
> > + [PWRAP_DEW_CIPHER_KEY_SEL] = 0x0418,
> > + [PWRAP_DEW_CIPHER_IV_SEL] = 0x041a,
> > + [PWRAP_DEW_CIPHER_EN] = 0x041c,
> > + [PWRAP_DEW_CIPHER_RDY] = 0x041e,
> > + [PWRAP_DEW_CIPHER_MODE] = 0x0420,
> > + [PWRAP_DEW_CIPHER_SWRST] = 0x0422,
> > + [PWRAP_DEW_RDDMY_NO] = 0x0424,
> > + [PWRAP_DEW_RECORD_CMD0] = 0x0428,
> > + [PWRAP_DEW_RECORD_CMD1] = 0x042a,
> > + [PWRAP_DEW_RECORD_CMD2] = 0x042c,
> > + [PWRAP_DEW_RECORD_CMD3] = 0x042e,
> > + [PWRAP_DEW_RECORD_CMD4] = 0x0430,
> > + [PWRAP_DEW_RECORD_CMD5] = 0x0432,
> > + [PWRAP_DEW_RECORD_WDATA0] = 0x0434,
> > + [PWRAP_DEW_RECORD_WDATA1] = 0x0436,
> > + [PWRAP_DEW_RECORD_WDATA2] = 0x0438,
> > + [PWRAP_DEW_RECORD_WDATA3] = 0x043a,
> > + [PWRAP_DEW_RECORD_WDATA4] = 0x043c,
> > + [PWRAP_DEW_RECORD_WDATA5] = 0x043e,
> > + [PWRAP_DEW_RG_ADDR_TARGET] = 0x0440,
> > + [PWRAP_DEW_RG_ADDR_MASK] = 0x0442,
> > + [PWRAP_DEW_RG_WDATA_TARGET] = 0x0444,
> > + [PWRAP_DEW_RG_WDATA_MASK] = 0x0446,
> > + [PWRAP_DEW_RG_SPI_RECORD_CLR] = 0x0448,
> > + [PWRAP_DEW_RG_CMD_ALERT_CLR] = 0x0448,
> > + [PWRAP_DEW_SPISLV_KEY] = 0x044a,
> > +};
> > +
> > static const u32 mt6397_regs[] = {
> > [PWRAP_DEW_BASE] = 0xbc00,
> > [PWRAP_DEW_EVENT_OUT_EN] = 0xbc00,
> > @@ -977,6 +1036,7 @@ enum pmic_type {
> > PMIC_MT6351,
> > PMIC_MT6357,
> > PMIC_MT6358,
> > + PMIC_MT6359,
> > PMIC_MT6380,
> > PMIC_MT6397,
> > };
> > @@ -1757,6 +1817,15 @@ static irqreturn_t pwrap_interrupt(int irqno, void *dev_id)
> > .pwrap_write = pwrap_write16,
> > };
> >
> > +static const struct pwrap_slv_type pmic_mt6359 = {
> > + .dew_regs = mt6359_regs,
> > + .type = PMIC_MT6359,
> > + .regmap = &pwrap_regmap_config16,
> > + .caps = PWRAP_SLV_CAP_DUALIO,
> > + .pwrap_read = pwrap_read16,
> > + .pwrap_write = pwrap_write16,
> > +};
> > +
> > static const struct pwrap_slv_type pmic_mt6380 = {
> > .dew_regs = NULL,
> > .type = PMIC_MT6380,
> > @@ -1790,6 +1859,9 @@ static irqreturn_t pwrap_interrupt(int irqno, void *dev_id)
> > .compatible = "mediatek,mt6358",
> > .data = &pmic_mt6358,
> > }, {
> > + .compatible = "mediatek,mt6359",
> > + .data = &pmic_mt6359,
> > + }, {
> > /* The MT6380 PMIC only implements a regulator, so we bind it
> > * directly instead of using a MFD.
> > */
> > --
> > 1.8.1.1.dirty
> >
next prev parent reply other threads:[~2019-10-14 5:17 UTC|newest]
Thread overview: 34+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-10-03 7:48 [PATCH 0/3] Pwrap: Mediatek pwrap driver for MT6779 Argus Lin
2019-10-03 7:48 ` Argus Lin
2019-10-03 7:48 ` Argus Lin
2019-10-03 7:48 ` [PATCH 1/3] dt-bindings: pwrap: mediatek: add pwrap support " Argus Lin
2019-10-03 7:48 ` Argus Lin
2019-10-03 7:48 ` Argus Lin
2019-10-15 19:20 ` Rob Herring
2019-10-15 19:20 ` Rob Herring
2019-10-15 19:20 ` Rob Herring
2019-10-03 7:48 ` [PATCH 2/3] soc: mediatek: pwrap: add pwrap driver for MT6779 SoCs Argus Lin
2019-10-03 7:48 ` Argus Lin
2019-10-03 7:48 ` Argus Lin
2019-10-03 23:26 ` Matthias Brugger
2019-10-03 23:26 ` Matthias Brugger
2019-10-14 6:04 ` Argus Lin
2019-10-14 6:04 ` Argus Lin
2019-10-14 6:04 ` Argus Lin
2019-11-04 8:22 ` Argus Lin
2019-11-04 8:22 ` Argus Lin
2019-11-04 8:22 ` Argus Lin
2019-11-10 18:47 ` Matthias Brugger
2019-11-10 18:47 ` Matthias Brugger
2019-11-10 18:47 ` Matthias Brugger
2019-10-03 7:48 ` [PATCH 3/3] soc: mediatek: pwrap: add support for MT6359 PMIC Argus Lin
2019-10-03 7:48 ` Argus Lin
2019-10-03 7:48 ` Argus Lin
2019-10-03 23:27 ` Matthias Brugger
2019-10-03 23:27 ` Matthias Brugger
2019-10-14 5:17 ` Argus Lin [this message]
2019-10-14 5:17 ` Argus Lin
2019-10-14 5:17 ` Argus Lin
2019-11-04 8:23 ` Argus Lin
2019-11-04 8:23 ` Argus Lin
2019-11-04 8:23 ` 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=1571030264.19600.2.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=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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.