devicetree.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: saravanan sekar <sravanhome@gmail.com>
To: Robert Marko <robimarko@gmail.com>,
	lgirdwood@gmail.com, broonie@kernel.org, robh+dt@kernel.org,
	krzysztof.kozlowski+dt@linaro.org, linux-kernel@vger.kernel.org,
	devicetree@vger.kernel.org
Subject: Re: [PATCH v2 4/4] regulator: mp5416: add support for MP5496
Date: Sun, 5 Jun 2022 12:10:28 +0200	[thread overview]
Message-ID: <326b83b5-65f8-7cd7-4732-157b978026af@gmail.com> (raw)
In-Reply-To: <20220604145816.47576-4-robimarko@gmail.com>

On 04/06/22 16:58, Robert Marko wrote:
> MP5496 is the updated version of MP5416 with the only difference being
> that now all Buck regulators have the same 0.6-2.1875V range with a 12.5mV
> step.
> 
> Signed-off-by: Robert Marko <robimarko@gmail.com>
> ---
>   drivers/regulator/mp5416.c | 13 +++++++++++++
>   1 file changed, 13 insertions(+)
> 
> diff --git a/drivers/regulator/mp5416.c b/drivers/regulator/mp5416.c
> index 011a825570ea..71e20e8d78ac 100644
> --- a/drivers/regulator/mp5416.c
> +++ b/drivers/regulator/mp5416.c
> @@ -175,6 +175,17 @@ static struct regulator_desc mp5416_regulators_desc[MP5416_MAX_REGULATORS] = {
>   	MP5416LDO("ldo4", 4, BIT(1)),
>   };
>   
> +static struct regulator_desc mp5496_regulators_desc[MP5416_MAX_REGULATORS] = {
> +	MP5416BUCK("buck1", 1, mp5416_I_limits1, MP5416_REG_CTL1, BIT(0), 1),
> +	MP5416BUCK("buck2", 2, mp5416_I_limits2, MP5416_REG_CTL1, BIT(1), 1),
> +	MP5416BUCK("buck3", 3, mp5416_I_limits1, MP5416_REG_CTL1, BIT(2), 1),
> +	MP5416BUCK("buck4", 4, mp5416_I_limits2, MP5416_REG_CTL2, BIT(5), 1),
> +	MP5416LDO("ldo1", 1, BIT(4)),
> +	MP5416LDO("ldo2", 2, BIT(3)),
> +	MP5416LDO("ldo3", 3, BIT(2)),
> +	MP5416LDO("ldo4", 4, BIT(1)),
> +};
> +
>   static int mp5416_i2c_probe(struct i2c_client *client)
>   {
>   	struct device *dev = &client->dev;
> @@ -212,12 +223,14 @@ static int mp5416_i2c_probe(struct i2c_client *client)
>   
>   static const struct of_device_id mp5416_of_match[] = {
>   	{ .compatible = "mps,mp5416", .data = &mp5416_regulators_desc },
> +	{ .compatible = "mps,mp5496", .data = &mp5496_regulators_desc },
>   	{},
>   };
>   MODULE_DEVICE_TABLE(of, mp5416_of_match);
>   
>   static const struct i2c_device_id mp5416_id[] = {
>   	{ "mp5416", },
> +	{ "mp5496", },
>   	{ },
>   };
>   MODULE_DEVICE_TABLE(i2c, mp5416_id);

Acked-by: Saravanan Sekar <sravanhome@gmail.com>

  reply	other threads:[~2022-06-05 10:10 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-06-04 14:58 [PATCH v2 1/4] regulator: dt-bindings: mps,mp5416: add MP5496 compatible Robert Marko
2022-06-04 14:58 ` [PATCH v2 2/4] regulator: mp5416: alphabetically sort header includes Robert Marko
2022-06-04 14:58 ` [PATCH v2 3/4] regulator: mp5416: use OF match data Robert Marko
2022-06-05 10:10   ` saravanan sekar
2022-06-04 14:58 ` [PATCH v2 4/4] regulator: mp5416: add support for MP5496 Robert Marko
2022-06-05 10:10   ` saravanan sekar [this message]
2022-06-06 17:28 ` [PATCH v2 1/4] regulator: dt-bindings: mps,mp5416: add MP5496 compatible Mark Brown

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=326b83b5-65f8-7cd7-4732-157b978026af@gmail.com \
    --to=sravanhome@gmail.com \
    --cc=broonie@kernel.org \
    --cc=devicetree@vger.kernel.org \
    --cc=krzysztof.kozlowski+dt@linaro.org \
    --cc=lgirdwood@gmail.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=robh+dt@kernel.org \
    --cc=robimarko@gmail.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).