From: Randy Dunlap <rdunlap@infradead.org>
To: Gene Chen <gene.chen.richtek@gmail.com>, matthias.bgg@gmail.com
Cc: gene_chen@richtek.com, lgirdwood@gmail.com,
linux-kernel@vger.kernel.org, cy_huang@richtek.com,
benjamin.chao@mediatek.com, broonie@kernel.org,
linux-mediatek@lists.infradead.org, Wilma.Wu@mediatek.com,
linux-arm-kernel@lists.infradead.org, shufan_lee@richtek.com
Subject: Re: [PATCH] regulator: mt6360: Add support for MT6360 regulator
Date: Thu, 4 Jun 2020 08:06:15 -0700 [thread overview]
Message-ID: <4135d264-6758-301a-0f19-ba2f229301c3@infradead.org> (raw)
In-Reply-To: <1591254387-10304-1-git-send-email-gene.chen.richtek@gmail.com>
On 6/4/20 12:06 AM, Gene Chen wrote:
> diff --git a/drivers/regulator/Kconfig b/drivers/regulator/Kconfig
> index f4b72cb..05a3b14 100644
> --- a/drivers/regulator/Kconfig
> +++ b/drivers/regulator/Kconfig
> @@ -680,6 +680,16 @@ config REGULATOR_MT6358
> This driver supports the control of different power rails of device
> through regulator interface.
>
> +config REGULATOR_MT6360
> + tristate "MT6360 SubPMIC Regulator"
> + depends on MFD_MT6360
> + select CRC8
> + help
> + Say Y here to enable MT6360 regulator support.
> + This is support MT6360 PMIC/LDO part include
This supports the MT6300 PMIC/LDO part, which includes
> + 2-channel buck with Thermal Shutdown and Overlord Protection
is that Overload ?
Yes, it could be Overlord.
> + 6-channel High PSRR and Low Dropout LDO.
> +
> config REGULATOR_MT6380
> tristate "MediaTek MT6380 PMIC"
> depends on MTK_PMIC_WRAP
--
~Randy
_______________________________________________
Linux-mediatek mailing list
Linux-mediatek@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-mediatek
next prev parent reply other threads:[~2020-06-04 15:06 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-06-04 7:06 [PATCH] regulator: mt6360: Add support for MT6360 regulator Gene Chen
2020-06-04 13:39 ` Mark Brown
2020-06-15 9:48 ` Gene Chen
2020-06-18 11:35 ` Gene Chen
2020-06-04 15:06 ` Randy Dunlap [this message]
2020-06-18 11:38 ` Gene Chen
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=4135d264-6758-301a-0f19-ba2f229301c3@infradead.org \
--to=rdunlap@infradead.org \
--cc=Wilma.Wu@mediatek.com \
--cc=benjamin.chao@mediatek.com \
--cc=broonie@kernel.org \
--cc=cy_huang@richtek.com \
--cc=gene.chen.richtek@gmail.com \
--cc=gene_chen@richtek.com \
--cc=lgirdwood@gmail.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mediatek@lists.infradead.org \
--cc=matthias.bgg@gmail.com \
--cc=shufan_lee@richtek.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).