[PATCH 0/5] Improvements to bq27000 management on OMAP

From: NeilBrown
Date: Thu Dec 29 2011 - 20:45:55 EST

[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).



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(-)


To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/