From: NeilBrown <neilb@suse.de>
To: Thomas Weber <thomas.weber.linux@googlemail.com>
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, Paul Walmsley <paul@pwsan.com>
Subject: Re: [PATCH 0/3] Small fixes for w1_bq27000 driver
Date: Sun, 19 Feb 2012 18:06:08 +1100 [thread overview]
Message-ID: <20120219180608.342a8877@notabene.brown> (raw)
In-Reply-To: <4F409BAF.9070809@gmail.com>
[-- Attachment #1: Type: text/plain, Size: 1700 bytes --]
On Sun, 19 Feb 2012 07:50:23 +0100 Thomas Weber
<thomas.weber.linux@googlemail.com> wrote:
> 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?
Yes, I have an OMAP3 with the HDQ line connected to a battery with a bq27000
in it. It now works fine.
When I first started working on it I would sometimes get problems with lots
of 0xFF being read, usually with lots of delays.
One problem was that during boot there would often be multiple threads
accessing the battery and tripping over each other.
The third patch of this set fixes that.
The other problem was power saving issues in the OMAP3 drivers. These
we address with lots of help from Paul Walmsley.
You can find my current set of HDQ patches here:
http://neil.brown.name/git?p=gta04;a=shortlog;h=refs/heads/hdq
(or git://neil.brown.name/gta04 hdq)
Most of these are from Paul.
Please let me know if they help.
NeilBrown
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 828 bytes --]
next prev parent reply other threads:[~2012-02-19 7:06 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 3/3] w1_bq27000: Only one thread can access the bq27000 at a time NeilBrown
2012-02-19 2:10 ` [PATCH 1/3] w1_bq27000: remove unnecessary NULL test NeilBrown
2012-02-19 6:50 ` [PATCH 0/3] Small fixes for w1_bq27000 driver Thomas Weber
2012-02-19 7:06 ` NeilBrown [this message]
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=20120219180608.342a8877@notabene.brown \
--to=neilb@suse.de \
--cc=dan.carpenter@oracle.com \
--cc=greg@kroah.com \
--cc=linux-kernel@vger.kernel.org \
--cc=paul@pwsan.com \
--cc=thomas.weber.linux@googlemail.com \
--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).