From: NeilBrown <neilb@suse.de>
To: Evgeniy Polyakov <zbr@ioremap.net>, Lars-Peter Clausen <lars@metafoo.de>
To: "Rodolfo Giometti" <giometti@linux.it>,
"Pali =?utf-8?b?Um9ow6FyIg==?=
<pali.rohar@gmail.com>@suse.de"@suse.de
To: Anton Vorontsov <cbouatmailru@gmail.com>,
Madhusudhan Chikkature <madhu.cr@ti.com>
Cc: Andrew Morton <akpm@linux-foundation.org>
Cc: linux-omap@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: [PATCH 0/5] Improvements to bq27000 management on OMAP
Date: Fri, 30 Dec 2011 11:58:49 +1100 [thread overview]
Message-ID: <20111230004947.11559.81184.stgit@notabene.brown> (raw)
[re-sent with multiple To: headers to placate vger.kernel.org]
This series makes the bq27000 battery monitor work well
when driven by the HDQ bus on OMAP devices.
I realise that there could be separate maintainers for each
file but figured that the series makes most sense as a whole
and am sending it as such. If people could take or ACK the
patches relevant to them I would appreciate it.
The first 3 should be uncontroversial.
The fourth:
omap_hdq: handle case where isr sees a 0 status byte.
fixes a problem that I have experienced, but I don't understand
why it happens. As the commentary in that patch says, the interrupt
service routine sometimes sees the status as '0' meaning that nothing
caused an interrupt (Inconceivable!!). This seems to happen in batches
resulting in timeouts that produce many-second delays in reading
battery status from /sys/class/bq27x00_battery/*.
The fifth:
bq27x00 - don't report power-supply change so often.
Causes the driver to be less noisy to udev. udev events should be
"uncommon" but the current code triggers a change event (almost) every
time the battery status is read, or every 6 minutes, as it is almost
certain that some value has changed (typically capacity but even
VOLTAGE_NOW can change a little bit).
Thanks,
NeilBrown
---
NeilBrown (5):
bq27x00 - don't report power-supply change so often.
omap_hdq: handle case where isr sees a 0 status byte.
omap_hdq: use wait_event_timeout to wait for read to complete.
omap_hdq: Fix some error/debug handling.
Fix w1_bq27000
drivers/power/bq27x00_battery.c | 15 ++++++++--
drivers/w1/masters/omap_hdq.c | 56 +++++++++++++++++++++++++++------------
drivers/w1/slaves/w1_bq27000.c | 17 ++++++++----
3 files changed, 63 insertions(+), 25 deletions(-)
--
Signature
next reply other threads:[~2011-12-30 1:45 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-12-30 0:58 NeilBrown [this message]
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 3/5] omap_hdq: use wait_event_timeout to wait for read to complete NeilBrown
2011-12-30 0:58 ` [PATCH 1/5] Fix w1_bq27000 NeilBrown
2012-02-15 15:36 ` Thomas Weber
2012-02-16 2:18 ` 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 2/5] omap_hdq: Fix some error/debug handling 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=20111230004947.11559.81184.stgit@notabene.brown \
--to=neilb@suse.de \
--cc=akpm@linux-foundation.org \
--cc=lars@metafoo.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).