linux-pm.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Andy Shevchenko <andriy.shevchenko@linux.intel.com>
To: Saravanan Sekar <sravanhome@gmail.com>
Cc: lee.jones@linaro.org, robh+dt@kernel.org, jic23@kernel.org,
	knaack.h@gmx.de, lars@metafoo.de, pmeerw@pmeerw.net,
	sre@kernel.org, mchehab+huawei@kernel.org, davem@davemloft.net,
	gregkh@linuxfoundation.org, fabrice.gasnier@st.com,
	beniamin.bia@analog.com, linus.walleij@linaro.org,
	u.kleine-koenig@pengutronix.de, fabrizio.castro@bp.renesas.com,
	info@metux.net, hancock@sedsystems.ca,
	gregory.clement@bootlin.com, renatogeh@gmail.com,
	plr.vincent@gmail.com, miquel.raynal@bootlin.com,
	marcelo.schmitt1@gmail.com, paul@crapouillou.net,
	devicetree@vger.kernel.org, linux-kernel@vger.kernel.org,
	linux-iio@vger.kernel.org, linux-pm@vger.kernel.org
Subject: Re: [PATCH 2/5] mfd: mp2629: Add support for mps battery charger
Date: Thu, 12 Mar 2020 19:49:33 +0200	[thread overview]
Message-ID: <20200312174933.GJ1922688@smile.fi.intel.com> (raw)
In-Reply-To: <20200312172649.13702-3-sravanhome@gmail.com>

On Thu, Mar 12, 2020 at 06:26:46PM +0100, Saravanan Sekar wrote:
> mp2629 is a highly-integrated switching-mode battery charge management
> device for single-cell Li-ion or Li-polymer battery.
> 
> Add MFD core enables chip access for ADC driver for battery readings,
> and a power supply battery-charger driver

...

>  drivers/mfd/Kconfig        |  43 +++++----------

Why do you have unrelated changes here?

...

> +int mp2629_set_value(struct regmap *map, u8 reg, u8 mask, unsigned int val)
> +{
> +	return regmap_update_bits(map, reg, mask, val);
> +}
> +EXPORT_SYMBOL(mp2629_set_value);
> +
> +int mp2629_get_value(struct regmap *map, u8 reg, unsigned int *val)
> +{
> +	return regmap_read(map, reg, val);
> +}
> +EXPORT_SYMBOL(mp2629_get_value);

I'm wondering why a child can get access to parent's regmap?
I.o.w. why is this being exported?

...

> +static int mp2629_probe(struct i2c_client *client)
> +{
> +	struct mp2629_info *info;
> +	int ret;
> +

> +	info = devm_kzalloc(&client->dev, sizeof(struct mp2629_info),
> +					 GFP_KERNEL);

	info = devm_kzalloc(&client->dev, sizeof(*info), GFP_KERNEL);

will be shorter.

> +	if (!info)
> +		return -ENOMEM;


> +	ret = devm_mfd_add_devices(info->dev, -1, mp2629mfd,
> +				ARRAY_SIZE(mp2629mfd), NULL,
> +				0, NULL);

-1 has a defined name in this case.

> +	if (ret)
> +		dev_err(info->dev, "Failed to add mfd %d\n", ret);
> +
> +	return ret;
> +}

...

> +static const struct of_device_id mp2629_of_match[] = {
> +	{ .compatible = "mps,mp2629"},

> +	{},

Terminator line doesn't require comma.

> +};

...

> +static const struct i2c_device_id mp2629_id[] = {
> +	{ "mp2629", },

> +	{ },

Ditto.

> +};
> +MODULE_DEVICE_TABLE(i2c, mp2629_id);

...

> +		.of_match_table = of_match_ptr(mp2629_of_match),

of_match_ptr() is redundant and even might provoke compiler warning...

> +	.probe_new	= mp2629_probe,

...especially taking into consideration ->probe_new().

...

> +#include <linux/platform_device.h>

No user here. (Hint: Use forward declaration of struct device instead)

> +#include <linux/i2c.h>

Ditto.

> +#include <linux/regmap.h>

Ditto. (Hint: Use forward declaration of struct regmap instead)

But linux/types.h is actually missed.

> +int mp2629_set_value(struct regmap *map, u8 reg, u8 mask, unsigned int val);
> +int mp2629_get_value(struct regmap *map, u8 reg, unsigned int *val);

-- 
With Best Regards,
Andy Shevchenko



  reply	other threads:[~2020-03-12 17:49 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-03-12 17:26 [PATCH 0/5] Add battery charger driver support for MP2629 Saravanan Sekar
2020-03-12 17:26 ` [PATCH 1/5] dt-bindings: mfd: add document bindings for mp2629 Saravanan Sekar
2020-03-12 17:26 ` [PATCH 2/5] mfd: mp2629: Add support for mps battery charger Saravanan Sekar
2020-03-12 17:49   ` Andy Shevchenko [this message]
2020-03-12 17:26 ` [PATCH 3/5] iio: adc: mp2629: Add support for mp2629 ADC driver Saravanan Sekar
2020-03-12 17:53   ` Andy Shevchenko
2020-03-12 17:26 ` [PATCH 4/5] power: supply: Add support for mps mp2629 battery charger Saravanan Sekar
2020-03-12 18:06   ` Andy Shevchenko
2020-03-12 17:26 ` [PATCH 5/5] MAINTAINERS: Add entry for mp2629 Battery Charger driver Saravanan Sekar
2020-03-12 18:08 ` [PATCH 0/5] Add battery charger driver support for MP2629 Andy Shevchenko

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=20200312174933.GJ1922688@smile.fi.intel.com \
    --to=andriy.shevchenko@linux.intel.com \
    --cc=beniamin.bia@analog.com \
    --cc=davem@davemloft.net \
    --cc=devicetree@vger.kernel.org \
    --cc=fabrice.gasnier@st.com \
    --cc=fabrizio.castro@bp.renesas.com \
    --cc=gregkh@linuxfoundation.org \
    --cc=gregory.clement@bootlin.com \
    --cc=hancock@sedsystems.ca \
    --cc=info@metux.net \
    --cc=jic23@kernel.org \
    --cc=knaack.h@gmx.de \
    --cc=lars@metafoo.de \
    --cc=lee.jones@linaro.org \
    --cc=linus.walleij@linaro.org \
    --cc=linux-iio@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-pm@vger.kernel.org \
    --cc=marcelo.schmitt1@gmail.com \
    --cc=mchehab+huawei@kernel.org \
    --cc=miquel.raynal@bootlin.com \
    --cc=paul@crapouillou.net \
    --cc=plr.vincent@gmail.com \
    --cc=pmeerw@pmeerw.net \
    --cc=renatogeh@gmail.com \
    --cc=robh+dt@kernel.org \
    --cc=sravanhome@gmail.com \
    --cc=sre@kernel.org \
    --cc=u.kleine-koenig@pengutronix.de \
    /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).