From: Matt Ranostay <matt@ranostay.consulting>
To: linux-pm@vger.kernel.org, devicetree@vger.kernel.org
Cc: sre@kernel.org, tony@atomide.com,
Matt Ranostay <matt@ranostay.consulting>
Subject: [PATCH v3 2/7] power: power_supply: add battery information struct
Date: Tue, 10 Jan 2017 22:19:58 -0800 [thread overview]
Message-ID: <20170111062003.10110-3-matt@ranostay.consulting> (raw)
In-Reply-To: <20170111062003.10110-1-matt@ranostay.consulting>
Add power_supply_battery_info structure that is used to
enumerate battery state machine settings.
Signed-off-by: Matt Ranostay <matt@ranostay.consulting>
---
include/linux/power_supply.h | 12 ++++++++++++
1 file changed, 12 insertions(+)
diff --git a/include/linux/power_supply.h b/include/linux/power_supply.h
index 3965503315ef..59674a257d5e 100644
--- a/include/linux/power_supply.h
+++ b/include/linux/power_supply.h
@@ -288,6 +288,18 @@ struct power_supply_info {
int use_for_apm;
};
+/*
+ * This is the recommended struct to specify static battery parameters.
+ * Power supply class itself doesn't use this, but it implements access
+ * that most platform drivers should use for consistency.
+ */
+
+struct power_supply_battery_info {
+ int energy; /* uWh */
+ int power; /* uAh */
+ int nominal_voltage; /* uV */
+};
+
extern struct atomic_notifier_head power_supply_notifier;
extern int power_supply_reg_notifier(struct notifier_block *nb);
extern void power_supply_unreg_notifier(struct notifier_block *nb);
--
2.10.2
next prev parent reply other threads:[~2017-01-11 6:20 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-01-11 6:19 [PATCH v3 0/7] power: bq27xxx: add support for NVRAM R/W access Matt Ranostay
2017-01-11 6:19 ` Matt Ranostay [this message]
2017-01-11 6:19 ` [PATCH v3 3/7] power: power_supply: add battery info platform data retrieval Matt Ranostay
[not found] ` <20170111062003.10110-1-matt-sk+viVC6FLCDq+mSdOJa79kegs52MxvZ@public.gmane.org>
2017-01-11 6:19 ` [PATCH v3 1/7] devicetree: power: add battery state machine documentation Matt Ranostay
[not found] ` <20170111062003.10110-2-matt-sk+viVC6FLCDq+mSdOJa79kegs52MxvZ@public.gmane.org>
2017-01-13 17:23 ` Rob Herring
2017-01-13 18:33 ` Sebastian Reichel
2017-01-11 6:20 ` [PATCH v3 4/7] power: bq27xxx_battery: add BQ27425 chip id Matt Ranostay
2017-01-11 6:20 ` [PATCH v3 5/7] power: bq27xxx_battery: add i2c bulk read/write functions Matt Ranostay
2017-01-11 6:20 ` [PATCH v3 7/7] power: bq27xxx_battery: add initial state machine support Matt Ranostay
2017-01-11 6:20 ` [PATCH v3 6/7] devicetree: power: bq27xxx: add monitored battery documentation Matt Ranostay
[not found] ` <20170111062003.10110-7-matt-sk+viVC6FLCDq+mSdOJa79kegs52MxvZ@public.gmane.org>
2017-01-13 17:28 ` Rob Herring
2017-01-14 6:07 ` Matt Ranostay
[not found] ` <CAJ_EiSRnU1q8QPKO43hk3ajS=RaAtQ2tVJ-060GcmPoPA6Ranw-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2017-01-17 0:59 ` 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=20170111062003.10110-3-matt@ranostay.consulting \
--to=matt@ranostay.consulting \
--cc=devicetree@vger.kernel.org \
--cc=linux-pm@vger.kernel.org \
--cc=sre@kernel.org \
--cc=tony@atomide.com \
/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).