From: Mark Brown <broonie@opensource.wolfsonmicro.com>
To: rklein@nvidia.com
Cc: cbouatmailru@gmail.com, linux-i2c@vger.kernel.org,
linux-kernel@vger.kernel.org, olof@lixom.net, achew@nvidia.com
Subject: Re: [PATCH 1/1] power supply: add driver for TI BQ20Z75 gas gauge IC
Date: Tue, 31 Aug 2010 14:13:24 +0100 [thread overview]
Message-ID: <20100831131323.GA16671@sirena.org.uk> (raw)
In-Reply-To: <1282949443-8052-1-git-send-email-rklein@nvidia.com>
On Fri, Aug 27, 2010 at 03:50:43PM -0700, rklein@nvidia.com wrote:
> + case POWER_SUPPLY_PROP_STATUS:
> + case POWER_SUPPLY_PROP_CYCLE_COUNT:
> + case POWER_SUPPLY_PROP_VOLTAGE_NOW:
> + case POWER_SUPPLY_PROP_CURRENT_NOW:
> + case POWER_SUPPLY_PROP_TEMP:
> + case POWER_SUPPLY_PROP_TIME_TO_EMPTY_AVG:
> + case POWER_SUPPLY_PROP_TIME_TO_FULL_AVG:
> + case POWER_SUPPLY_PROP_SERIAL_NUMBER:
> + for (count = 0; count < REG_MAX; count++) {
> + if (psp == bq20z75_data[count].psp)
> + break;
> + }
Rather than using REG_MAX it'd seem safer to use ARRAY_SIZE() to make
sure you're within the array.
> + if (bq20z75_get_battery_property(count, psp, val))
> + return -EINVAL;
> + break;
Indentation is messed up here.
> + printk(KERN_INFO "%s: property = %d, value = %d\n", __func__,
> + psp, val->intval);
Remove unconditional logging like this, make it dev_dbg() if you want to
keep it in so it's only visible when explicitly requested.
> + bq20z75_device = kzalloc(sizeof(*bq20z75_device), GFP_KERNEL);
> + if (!bq20z75_device)
> + return -ENOMEM;
> +
> +memset(bq20z75_device, 0, sizeof(*bq20z75_device));
Indentation again.
> +/* any smbus transaction will wake up bq20z75 */
> +static int bq20z75_resume(struct i2c_client *client)
> +{
> + return 0;
> +}
No need for null functions like this.
> +#if defined CONFIG_PM
> + .suspend = bq20z75_suspend,
> + .resume = bq20z75_resume,
> +#endif
The standard way to do this is with the suspend/resume functions -
#define them to NULL which turns their assignments into noops.
> +MODULE_AUTHOR("NVIDIA Graphics Pvt Ltd");
This only makes sense if it's an actual person (or other contact
address); there's already copyright statements on the file, the author
information is more there to help find someone who might know something
about the driver.
next prev parent reply other threads:[~2010-08-31 13:13 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-08-27 22:50 [PATCH 1/1] power supply: add driver for TI BQ20Z75 gas gauge IC rklein
2010-08-31 8:24 ` Jean Delvare
2010-09-01 17:54 ` Rhyland Klein
2010-08-31 13:13 ` Mark Brown [this message]
2010-09-01 17:53 ` Rhyland Klein
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=20100831131323.GA16671@sirena.org.uk \
--to=broonie@opensource.wolfsonmicro.com \
--cc=achew@nvidia.com \
--cc=cbouatmailru@gmail.com \
--cc=linux-i2c@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=olof@lixom.net \
--cc=rklein@nvidia.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