From: Arnd Bergmann <arnd@arndb.de>
To: Eric Andersson <eric.andersson@unixphere.com>
Cc: linux-kernel@vger.kernel.org, gregkh@linuxfoundation.org,
alan@lxorguk.ukuu.org.uk, zhengguang.guo@bosch-sensortec.com,
peter.moeller@cn.bosch.com
Subject: Re: [PATCHv2 1/3] misc: clean up bmp085 driver
Date: Tue, 6 Mar 2012 21:20:47 +0000 [thread overview]
Message-ID: <201203062120.47953.arnd@arndb.de> (raw)
In-Reply-To: <1331068084-17911-2-git-send-email-eric.andersson@unixphere.com>
On Tuesday 06 March 2012, Eric Andersson wrote:
> This patch includes various cleaning of the bmp085 driver including:
> - Addition of platform_data and header file
> - Implement pm functions
> - Whitespaces and alignment fixes
> - Minor typos
> - Consistency fixes
>
> Reviewed-by: Stefan Nilsson <stefan.nilsson@unixphere.com>
> Signed-off-by: Eric Andersson <eric.andersson@unixphere.com>
Most of the cleanups look good, just a few things that stick out:
> static int __devinit bmp085_probe(struct i2c_client *client,
> - const struct i2c_device_id *id)
> + const struct i2c_device_id *id)
> {
> struct bmp085_data *data;
> + struct bmp085_platform_data *pdata = client->dev.platform_data;
> + u8 chip_id = (pdata && pdata->chip_id) ? pdata->chip_id :
> + BMP085_CHIP_ID;
> int err = 0;
>
> + if (pdata && pdata->init_hw) {
> + err = pdata->init_hw(&client->dev);
> + if (err) {
> + dev_err(&client->dev, "%s: init_hw failed!\n",
> + BMP085_NAME);
> + return err;
> + }
> + }
> +
The addition of platform_data does not look like a cleanup to me,
it's a significant change in the interface to the platform, so I
would put it into a separate patch.
> + if (i2c_smbus_read_byte_data(client, BMP085_CHIP_ID_REG) != chip_id) {
> + dev_err(&client->dev, "%s: chip_id failed!\n", BMP085_NAME);
> + err = -ENODEV;
> + goto exit_free;
> + }
> +
This part looks like it belongs into the second patch where you add support
for more than one chip id.
> diff --git a/include/linux/i2c/bmp085.h b/include/linux/i2c/bmp085.h
> new file mode 100644
> index 0000000..e6fc752
> --- /dev/null
> +++ b/include/linux/i2c/bmp085.h
Since this file only adds platform_data, I think it should go into
include/linux/platform_data/, not include/linux/i2c, and it should
be in the same patch as the change to use the platform data when you
split that out.
Also, which platforms are actually using this driver? I could
not find any platform that defines a bmp085 platform_device. If this
is for new ARM platforms, I would rather not add platform_data at
all because those platforms will have to use device tree properties
rather than platform_data to pass initialization data.
Arnd
next prev parent reply other threads:[~2012-03-06 21:20 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-03-06 21:08 [PATCHv2 0/3] Add support for bmp18x to bmp085 Eric Andersson
2012-03-06 21:08 ` [PATCHv2 1/3] misc: clean up bmp085 driver Eric Andersson
2012-03-06 21:20 ` Arnd Bergmann [this message]
2012-03-12 22:53 ` Eric Andersson
2012-03-13 12:04 ` Arnd Bergmann
2012-03-06 21:08 ` [PATCHv2 2/3] misc: add support for bmp18x chips to the " Eric Andersson
2012-03-06 21:27 ` Arnd Bergmann
2012-03-06 22:17 ` Eric Andersson
2012-03-07 0:03 ` Mark Brown
2012-03-06 21:08 ` [PATCHv2 3/3] misc: rename bmp085 to bmp18x Eric Andersson
2012-03-06 21:14 ` Arnd Bergmann
2012-03-06 21:37 ` Alan Cox
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=201203062120.47953.arnd@arndb.de \
--to=arnd@arndb.de \
--cc=alan@lxorguk.ukuu.org.uk \
--cc=eric.andersson@unixphere.com \
--cc=gregkh@linuxfoundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=peter.moeller@cn.bosch.com \
--cc=zhengguang.guo@bosch-sensortec.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