From: Johnson Wang <johnson.wang@mediatek.com>
To: <lee.jones@linaro.org>, <robh+dt@kernel.org>, <broonie@kernel.org>
Cc: <devicetree@vger.kernel.org>,
<linux-arm-kernel@lists.infradead.org>,
<linux-mediatek@lists.infradead.org>,
<linux-kernel@vger.kernel.org>,
<Project_Global_Chrome_Upstream_Group@mediatek.com>
Subject: Re: [PATCH 1/4] mfd: Add support for the MediaTek MT6366 PMIC
Date: Mon, 7 Feb 2022 15:04:52 +0800 [thread overview]
Message-ID: <777a3344a7edc654548f435cc21dd9d628fe69ea.camel@mediatek.com> (raw)
In-Reply-To: <20220106065407.16036-2-johnson.wang@mediatek.com>
Hi Lee,
This patch intends to add MT6366 PMIC support and
there are some modifications in mfd subsystem.
Could you give us some suggestion for this patch?
Thanks for your support!
BRs,
Johnson Wang
On Thu, 2022-01-06 at 14:54 +0800, Johnson Wang wrote:
> This adds support for the MediaTek MT6366 PMIC. This is a
> multifunction device with the following sub modules:
>
> - Regulator
> - RTC
> - Codec
> - Interrupt
>
> It is interfaced to the host controller using SPI interface
> by a proprietary hardware called PMIC wrapper or pwrap.
> MT6366 MFD is a child device of the pwrap.
>
> Signed-off-by: Johnson Wang <johnson.wang@mediatek.com>
> ---
> drivers/mfd/mt6358-irq.c | 1 +
> include/linux/mfd/mt6358/registers.h | 7 +++++++
> include/linux/mfd/mt6397/core.h | 1 +
> 3 files changed, 9 insertions(+)
>
> diff --git a/drivers/mfd/mt6358-irq.c b/drivers/mfd/mt6358-irq.c
> index 83f3ffbdbb4c..ea5e452510eb 100644
> --- a/drivers/mfd/mt6358-irq.c
> +++ b/drivers/mfd/mt6358-irq.c
> @@ -212,6 +212,7 @@ int mt6358_irq_init(struct mt6397_chip *chip)
>
> switch (chip->chip_id) {
> case MT6358_CHIP_ID:
> + case MT6366_CHIP_ID:
> chip->irq_data = &mt6358_irqd;
> break;
>
> diff --git a/include/linux/mfd/mt6358/registers.h
> b/include/linux/mfd/mt6358/registers.h
> index 201139b12140..3d33517f178c 100644
> --- a/include/linux/mfd/mt6358/registers.h
> +++ b/include/linux/mfd/mt6358/registers.h
> @@ -94,6 +94,10 @@
> #define MT6358_BUCK_VCORE_CON0 0x1488
> #define MT6358_BUCK_VCORE_DBG0 0x149e
> #define MT6358_BUCK_VCORE_DBG1 0x14a0
> +#define MT6358_BUCK_VCORE_SSHUB_CON0 0x14a4
> +#define MT6358_BUCK_VCORE_SSHUB_CON1 0x14a6
> +#define
> MT6358_BUCK_VCORE_SSHUB_ELR0 MT6358_BUCK_VCORE_SSHUB_CON1
> +#define MT6358_BUCK_VCORE_SSHUB_DBG1 MT6358_BUCK_VCORE_DBG1
> #define MT6358_BUCK_VCORE_ELR0 0x14aa
> #define MT6358_BUCK_VGPU_CON0 0x1508
> #define MT6358_BUCK_VGPU_DBG0 0x151e
> @@ -169,6 +173,9 @@
> #define MT6358_LDO_VSRAM_OTHERS_CON0 0x1ba6
> #define MT6358_LDO_VSRAM_OTHERS_DBG0 0x1bc0
> #define MT6358_LDO_VSRAM_OTHERS_DBG1 0x1bc2
> +#define MT6358_LDO_VSRAM_OTHERS_SSHUB_CON0 0x1bc4
> +#define MT6358_LDO_VSRAM_OTHERS_SSHUB_CON1 0x1bc6
> +#define
> MT6358_LDO_VSRAM_OTHERS_SSHUB_DBG1 MT6358_LDO_VSRAM_OTHERS_DBG1
> #define MT6358_LDO_VSRAM_GPU_CON0 0x1bc8
> #define MT6358_LDO_VSRAM_GPU_DBG0 0x1be2
> #define MT6358_LDO_VSRAM_GPU_DBG1 0x1be4
> diff --git a/include/linux/mfd/mt6397/core.h
> b/include/linux/mfd/mt6397/core.h
> index 56f210eebc54..1cf78726503b 100644
> --- a/include/linux/mfd/mt6397/core.h
> +++ b/include/linux/mfd/mt6397/core.h
> @@ -14,6 +14,7 @@ enum chip_id {
> MT6323_CHIP_ID = 0x23,
> MT6358_CHIP_ID = 0x58,
> MT6359_CHIP_ID = 0x59,
> + MT6366_CHIP_ID = 0x66,
> MT6391_CHIP_ID = 0x91,
> MT6397_CHIP_ID = 0x97,
> };
next prev parent reply other threads:[~2022-02-07 7:12 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-01-06 6:54 [PATCH 0/4] Add Support for MediaTek PMIC MT6366 Johnson Wang
2022-01-06 6:54 ` [PATCH 1/4] mfd: Add support for the MediaTek MT6366 PMIC Johnson Wang
2022-02-07 7:04 ` Johnson Wang [this message]
2022-02-14 13:39 ` Lee Jones
2022-02-23 8:28 ` Johnson Wang
2022-02-23 9:02 ` Lee Jones
2022-01-06 6:54 ` [PATCH 2/4] regulator: mt6366: Add support for MT6366 regulator Johnson Wang
2022-01-06 12:59 ` Mark Brown
2022-02-23 9:58 ` Johnson Wang
2022-01-06 6:54 ` [PATCH 3/4] dt-bindings: mfd: Add compatible for the MediaTek MT6366 PMIC Johnson Wang
2022-01-12 1:44 ` Rob Herring
2022-02-14 13:39 ` Lee Jones
2022-01-06 6:54 ` [PATCH 4/4] dt-bindings: regulator: Add MT6358 regulators Johnson Wang
2022-01-06 13:09 ` Mark Brown
2022-01-12 1:45 ` Rob Herring
2022-03-03 8:18 ` Fei Shao
2022-03-08 8:28 ` [GIT PULL - FAO MARK BROWN]: Immutable branch for MediaTek MT6366 due for the v5.18 merge window Lee Jones
2022-03-08 12:49 ` Mark Brown
2022-03-08 13:09 ` Lee Jones
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=777a3344a7edc654548f435cc21dd9d628fe69ea.camel@mediatek.com \
--to=johnson.wang@mediatek.com \
--cc=Project_Global_Chrome_Upstream_Group@mediatek.com \
--cc=broonie@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=lee.jones@linaro.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mediatek@lists.infradead.org \
--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;
as well as URLs for NNTP newsgroup(s).