From: Thomas Weber <weber@corscience.de>
To: NeilBrown <neilb@suse.de>, zbr@ioremap.net
Cc: linux-omap@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH 1/5] Fix w1_bq27000
Date: Wed, 15 Feb 2012 16:36:09 +0100 [thread overview]
Message-ID: <4F3BD0E9.5070305@corscience.de> (raw)
In-Reply-To: <20111230005849.11559.79397.stgit@notabene.brown>
Hello Neil,
On 30.12.2011 01:58, NeilBrown wrote:
> w1_bq27000 adds a bq27000-battery platform device but does not provide
> platform data for it. This causes the bq27x00 driver to dereference a NULL
> pointer.
> So provide the appropriate platform data. This requires modifying
> w1_bq27000_read so that it find the w1 device as the parent of the bq device.
>
> Also there is no point exporting w1_bq27000_read as nothing else uses it
> or could use it. So make it static.
>
> Finally, as there is no way to track how many batteries have been found, and
> we will probably only find one, use an id number of '-1' to assert that this
> is a unique instance.
>
> Signed-off-by: NeilBrown <neilb@suse.de>
> ---
>
> drivers/w1/slaves/w1_bq27000.c | 17 ++++++++++++-----
> 1 files changed, 12 insertions(+), 5 deletions(-)
>
> diff --git a/drivers/w1/slaves/w1_bq27000.c b/drivers/w1/slaves/w1_bq27000.c
> index 8f4c91f..8f10fd2 100644
> --- a/drivers/w1/slaves/w1_bq27000.c
> +++ b/drivers/w1/slaves/w1_bq27000.c
> @@ -15,6 +15,7 @@
> #include <linux/types.h>
> #include <linux/platform_device.h>
> #include <linux/mutex.h>
> +#include <linux/power/bq27x00_battery.h>
>
> #include "../w1.h"
> #include "../w1_int.h"
> @@ -39,10 +40,10 @@ void w1_bq27000_write(struct device *dev, u8 buf, u8 reg)
> }
> EXPORT_SYMBOL(w1_bq27000_write);
>
> -int w1_bq27000_read(struct device *dev, u8 reg)
> +static int w1_bq27000_read(struct device *dev, unsigned int reg)
> {
> u8 val;
> - struct w1_slave *sl = container_of(dev, struct w1_slave, dev);
> + struct w1_slave *sl = container_of(dev->parent, struct w1_slave, dev);
>
> if (!dev)
> return 0;
> @@ -52,19 +53,25 @@ int w1_bq27000_read(struct device *dev, u8 reg)
>
> return val;
> }
> -EXPORT_SYMBOL(w1_bq27000_read);
> +
> +static struct bq27000_platform_data bq27000_battery_info = {
> + .read = w1_bq27000_read,
> + .name = "bq27000-battery",
> +};
>
> static int w1_bq27000_add_slave(struct w1_slave *sl)
> {
> int ret;
> - int id = 1;
> struct platform_device *pdev;
>
> - pdev = platform_device_alloc("bq27000-battery", id);
> + pdev = platform_device_alloc("bq27000-battery", -1);
> if (!pdev) {
> ret = -ENOMEM;
> return ret;
> }
> + ret = platform_device_add_data(pdev,
> + &bq27000_battery_info,
> + sizeof(bq27000_battery_info));
> pdev->dev.parent = &sl->dev;
>
> ret = platform_device_add(pdev);
>
>
Tested-by: Thomas Weber <weber@corscience.de>
Thanks for the patch, now the platform data of the bq27000 are found.
before:
omap_hdq omap_hdq.0: OMAP HDQ Hardware Rev 0.5. Driver in Interrupt mode
w1_master_driver w1_bus_master1: Family 1 for 01.000000000000.3d is not
registered.
bq27000-battery bq27000-battery.1: no platform_data supplied
bq27000-battery: probe of bq27000-battery.1 failed with error -22
after:
omap_hdq omap_hdq.0: OMAP HDQ Hardware Rev 0.5. Driver in Interrupt mode
w1_master_driver w1_bus_master1: Family 1 for 01.000000000000.3d is not
registered.
bq27000-battery bq27000-battery: support ver. 1.2.0 enabled
Regards,
Thomas
next prev parent reply other threads:[~2012-02-15 15:37 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-12-30 0:58 [PATCH 0/5] Improvements to bq27000 management on OMAP NeilBrown
2011-12-30 0:58 ` [PATCH 5/5] bq27x00 - don't report power-supply change so often NeilBrown
2011-12-30 11:13 ` Grazvydas Ignotas
2011-12-31 11:27 ` Lars-Peter Clausen
2012-01-03 1:02 ` NeilBrown
2011-12-30 0:58 ` [PATCH 3/5] omap_hdq: use wait_event_timeout to wait for read to complete NeilBrown
2011-12-30 0:58 ` [PATCH 4/5] omap_hdq: handle case where isr sees a 0 status byte NeilBrown
2011-12-30 0:58 ` [PATCH 2/5] omap_hdq: Fix some error/debug handling NeilBrown
2011-12-30 0:58 ` [PATCH 1/5] Fix w1_bq27000 NeilBrown
2012-02-15 15:36 ` Thomas Weber [this message]
2012-02-16 2:18 ` NeilBrown
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=4F3BD0E9.5070305@corscience.de \
--to=weber@corscience.de \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-omap@vger.kernel.org \
--cc=neilb@suse.de \
--cc=zbr@ioremap.net \
/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
Powered by JetHome