From: Jenny TC <jenny.tc@intel.com>
To: linux-pm@vger.kernel.org, linux-kernel@vger.kernel.org,
Sebastian Reichel <sre@kernel.org>
Cc: Anton Vorontsov <anton.vorontsov@linaro.org>,
David Woodhouse <dwmw2@infradead.org>,
jonghwa3.lee@samsung.com, myungjoo.ham@gmail.com,
Pallala Ramakrishna <ramakrishna.pallala@intel.com>,
Jenny TC <jenny.tc@intel.com>
Subject: [RFC 1/4] power_supply: Introduce charging object table
Date: Fri, 6 Mar 2015 16:03:24 +0530 [thread overview]
Message-ID: <1425638007-9411-2-git-send-email-jenny.tc@intel.com> (raw)
In-Reply-To: <1425638007-9411-1-git-send-email-jenny.tc@intel.com>
Charging current (CC) and charging voltage (CV) may vary based on
battery temperature. To support CC and CV for different temperature
zones, defined a charging object which holds the properties related
to battery charging.
Signed-off-by: Jenny TC <jenny.tc@intel.com>
---
include/linux/power_supply.h | 27 +++++++++++++++++++++++++++
1 file changed, 27 insertions(+)
diff --git a/include/linux/power_supply.h b/include/linux/power_supply.h
index 096dbce..7aada44 100644
--- a/include/linux/power_supply.h
+++ b/include/linux/power_supply.h
@@ -252,6 +252,33 @@ struct power_supply_info {
int use_for_apm;
};
+
+struct psy_temp_mon_table {
+ int temp_max;
+ int temp_min;
+ int charging_current; /* CC */
+ int charging_voltage; /* CV */
+ /* delta voltage at which charging should restart */
+ int maint_voltage_delta;
+};
+
+#define PSY_MAX_BAT_NAME_LEN 8
+#define PSY_MAX_TEMP_ZONE 6
+
+struct psy_charging_obj {
+ char name[PSY_MAX_BAT_NAME_LEN];
+ int battery_type;
+ int temp_max;
+ int temp_min;
+ int full_condition_soc;
+ int full_condition_capacity;
+ int full_condition_voltage;
+ int iterm; /* charge termination current */
+ /* CC/CV table for different temperature range */
+ int temp_mon_count; /* number of entries in temp_mon_table */
+ struct psy_temp_mon_table temp_mon_table[PSY_MAX_TEMP_ZONE];
+};
+
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);
--
1.7.9.5
next prev parent reply other threads:[~2015-03-06 10:33 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-03-06 10:33 [RFC 0/4] Enable power supply charging control Jenny TC
2015-03-06 10:33 ` Jenny TC [this message]
2015-03-06 11:12 ` [RFC 1/4] power_supply: Introduce charging object table Oliver Neukum
2015-03-08 1:31 ` Sebastian Reichel
2015-03-08 1:00 ` Sebastian Reichel
2015-03-06 10:33 ` [RFC 2/4] power: core: Add generic interface to get battery specification Jenny TC
2015-03-06 11:16 ` Oliver Neukum
2015-03-09 11:24 ` jonghwa3.lee
2015-03-06 10:33 ` [RFC 3/4] power_supply: Introduce charger control interface Jenny TC
2015-03-08 1:55 ` Sebastian Reichel
2015-03-09 12:47 ` Tc, Jenny
2015-03-09 14:55 ` Sebastian Reichel
2015-03-06 10:33 ` [RFC 4/4] charger-manager: Enable psy based charge control Jenny TC
2015-03-08 2:14 ` Sebastian Reichel
2015-03-10 5:21 ` Tc, Jenny
2015-03-09 12:26 [RFC 1/4] power_supply: Introduce charging object table Tc, Jenny
2015-03-09 14:08 ` 'Sebastian Reichel'
2015-03-10 5:16 ` Tc, Jenny
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=1425638007-9411-2-git-send-email-jenny.tc@intel.com \
--to=jenny.tc@intel.com \
--cc=anton.vorontsov@linaro.org \
--cc=dwmw2@infradead.org \
--cc=jonghwa3.lee@samsung.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pm@vger.kernel.org \
--cc=myungjoo.ham@gmail.com \
--cc=ramakrishna.pallala@intel.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).