From: "Andrew F. Davis" <afd@ti.com>
To: "Pali Rohár" <pali.rohar@gmail.com>,
"Sebastian Reichel" <sre@kernel.org>,
"Dmitry Eremin-Solenikov" <dbaryshkov@gmail.com>,
"David Woodhouse" <dwmw2@infradead.org>
Cc: linux-pm@vger.kernel.org, linux-kernel@vger.kernel.org,
"Andrew F. Davis" <afd@ti.com>
Subject: [PATCH v5 6/6] power: bq27xxx_battery: Add interrupt handling support
Date: Tue, 22 Sep 2015 14:35:11 -0500 [thread overview]
Message-ID: <1442950511-16122-7-git-send-email-afd@ti.com> (raw)
In-Reply-To: <1442950511-16122-1-git-send-email-afd@ti.com>
Some devices have a pin that can generate an interrupt when
the battery's status changes. Add an interrupt handler to
read the new battery status.
Signed-off-by: Andrew F. Davis <afd@ti.com>
---
drivers/power/bq27xxx_battery.c | 23 +++++++++++++++++++++++
1 file changed, 23 insertions(+)
diff --git a/drivers/power/bq27xxx_battery.c b/drivers/power/bq27xxx_battery.c
index fe18a2d..473aa2f 100644
--- a/drivers/power/bq27xxx_battery.c
+++ b/drivers/power/bq27xxx_battery.c
@@ -48,6 +48,7 @@
#include <linux/idr.h>
#include <linux/i2c.h>
#include <linux/slab.h>
+#include <linux/interrupt.h>
#include <asm/unaligned.h>
#include <linux/power/bq27xxx_battery.h>
@@ -761,6 +762,15 @@ static void bq27xxx_battery_update(struct bq27xxx_device_info *di)
di->last_update = jiffies;
}
+static irqreturn_t bq27xxx_battery_irq_handler_thread(int irq, void *data)
+{
+ struct bq27xxx_device_info *di = data;
+
+ bq27xxx_battery_update(di);
+
+ return IRQ_HANDLED;
+}
+
static void bq27xxx_battery_poll(struct work_struct *work)
{
struct bq27xxx_device_info *di =
@@ -1128,6 +1138,19 @@ static int bq27xxx_battery_i2c_probe(struct i2c_client *client,
i2c_set_clientdata(client, di);
+ if (client->irq) {
+ retval = devm_request_threaded_irq(&client->dev, client->irq,
+ NULL, bq27xxx_battery_irq_handler_thread,
+ IRQF_ONESHOT,
+ name, di);
+ if (retval) {
+ dev_err(&client->dev,
+ "Unable to register IRQ %d error %d\n",
+ client->irq, retval);
+ return retval;
+ }
+ }
+
return 0;
batt_failed:
--
1.9.1
next prev parent reply other threads:[~2015-09-22 19:35 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-09-22 19:35 [PATCH v5 0/6] Add support for additional bq27xxx devices Andrew F. Davis
2015-09-22 19:35 ` [PATCH v5 1/6] power: bq27x00_battery: Renaming for consistency Andrew F. Davis
2015-09-22 21:00 ` Sebastian Reichel
2015-09-23 1:07 ` Tony Lindgren
2015-09-23 6:03 ` 答复: " GUAN Xuetao
2015-09-22 19:35 ` [PATCH v5 2/6] power: bq27xxx_battery: Platform initialization must declare a device Andrew F. Davis
2015-09-22 19:35 ` [PATCH v5 3/6] power: bq27xxx_battery: Fix typos and change naming for state of charge functions Andrew F. Davis
2015-09-22 19:35 ` [PATCH v5 4/6] power: bq27xxx_battery: Add support for additional bq27xxx family devices Andrew F. Davis
2015-09-22 19:35 ` [PATCH v5 5/6] power: bq27xxx_battery: Cleanup health checking Andrew F. Davis
2015-09-22 19:35 ` Andrew F. Davis [this message]
2015-09-23 16:42 ` [PATCH v5 0/6] Add support for additional bq27xxx devices Sebastian Reichel
2015-09-23 18:41 ` Andrew F. Davis
2015-09-23 22:43 ` Sebastian Reichel
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=1442950511-16122-7-git-send-email-afd@ti.com \
--to=afd@ti.com \
--cc=dbaryshkov@gmail.com \
--cc=dwmw2@infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pm@vger.kernel.org \
--cc=pali.rohar@gmail.com \
--cc=sre@kernel.org \
/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).