From: Thomas Weber <thomas.weber.linux@googlemail.com>
To: NeilBrown <neilb@suse.de>
Cc: Evgeniy Polyakov <zbr@ioremap.net>, GregKH <greg@kroah.com>,
Thomas Weber <weber@corscience.de>,
Dan Carpenter <dan.carpenter@oracle.com>,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH 0/3] Small fixes for w1_bq27000 driver
Date: Sun, 19 Feb 2012 07:50:23 +0100 [thread overview]
Message-ID: <4F409BAF.9070809@gmail.com> (raw)
In-Reply-To: <20120219020910.4958.46866.stgit@notabene.brown>
On 02/19/2012 03:10 AM, NeilBrown wrote:
> The following three patches fix a problem with the w1 interface for
> the bq27000 battery charge meter, and remove some unnecessary code.
>
> thanks,
> NeilBrown
>
>
> ---
>
> NeilBrown (3):
> w1_bq27000: Only one thread can access the bq27000 at a time.
> w1_bq27000 - remove w1_bq27000_write
> w1_bq27000: remove unnecessary NULL test.
>
>
> drivers/w1/slaves/w1_bq27000.c | 19 ++-----------------
> 1 files changed, 2 insertions(+), 17 deletions(-)
>
Hello Neil,
I have the following problem. The board not correctly reads the values
from the bq27000. It also doesn't detects if the bq27000 is connected. I
think it always reads 0xFF.
Do you have an omap3 board and a bq27000 battery?
Regards,
Thomas
next prev parent reply other threads:[~2012-02-19 6:49 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-02-19 2:10 [PATCH 0/3] Small fixes for w1_bq27000 driver NeilBrown
2012-02-19 2:10 ` [PATCH 2/3] w1_bq27000 - remove w1_bq27000_write NeilBrown
2012-02-19 2:10 ` [PATCH 1/3] w1_bq27000: remove unnecessary NULL test NeilBrown
2012-02-19 2:10 ` [PATCH 3/3] w1_bq27000: Only one thread can access the bq27000 at a time NeilBrown
2012-02-19 6:50 ` Thomas Weber [this message]
2012-02-19 7:06 ` [PATCH 0/3] Small fixes for w1_bq27000 driver NeilBrown
2012-02-20 11:19 ` Thomas Weber
2012-02-20 13:56 ` [PATCH] OMAP: hdq: software-supervised control of HDQ_ICLK Thomas Weber
2012-02-20 15:22 ` Evgeniy Polyakov
2012-02-20 12:04 ` [PATCH 0/3] Small fixes for w1_bq27000 driver Evgeniy Polyakov
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=4F409BAF.9070809@gmail.com \
--to=thomas.weber.linux@googlemail.com \
--cc=dan.carpenter@oracle.com \
--cc=greg@kroah.com \
--cc=linux-kernel@vger.kernel.org \
--cc=neilb@suse.de \
--cc=weber@corscience.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;
as well as URLs for NNTP newsgroup(s).