From: Sebastian Reichel <sre@kernel.org>
To: Jenny TC <jenny.tc@intel.com>
Cc: linux-pm@vger.kernel.org, linux-kernel@vger.kernel.org,
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>
Subject: Re: [RFC 3/4] power_supply: Introduce charger control interface
Date: Sun, 8 Mar 2015 02:55:16 +0100 [thread overview]
Message-ID: <20150308015515.GB25160@earth> (raw)
In-Reply-To: <1425638007-9411-4-git-send-email-jenny.tc@intel.com>
[-- Attachment #1: Type: text/plain, Size: 2726 bytes --]
Hi,
On Fri, Mar 06, 2015 at 04:03:26PM +0530, Jenny TC wrote:
> Introduce power_supply charger control interfaces to control
> charging from charging framework like charger-manager. The interfaces
> are similar to the existing power supply get/set interfaces, but
> introduce a different set of properties in order to differentiate
> itself from other power supply properties which exposed in sysfs
>
> Signed-off-by: Jenny TC <jenny.tc@intel.com>
> ---
> include/linux/power_supply.h | 28 ++++++++++++++++++++++++++++
> 1 file changed, 28 insertions(+)
>
> diff --git a/include/linux/power_supply.h b/include/linux/power_supply.h
> index 30145d8e..a80a3ef 100644
> --- a/include/linux/power_supply.h
> +++ b/include/linux/power_supply.h
> @@ -176,6 +176,32 @@ union power_supply_propval {
> struct device;
> struct device_node;
>
> +enum psy_charger_control_property {
> + PSY_CHARGER_PROP_ENABLE_CHARGING = 0,
> + PSY_CHARGER_PROP_ENABLE_CHARGER,
> + PSY_CHARGER_PROP_RESET_WDT,
> +};
> +
> +/**
> + * struct power_supply_charger - power supply charger driver
> + * @get_property: get property function to retrieve charger properties defined
> + * in enum power_supply_charger_property
> + * @set_property: get property function to retrieve charger properties defined
> + * in enum power_supply_charger_property
> + *
> + * This structure is used by charger drivers to register with power supply
> + * charging driver
> + */
> +
> +struct power_supply_charger {
> + int (*get_property)(struct power_supply_charger *psyc,
> + enum psy_charger_control_property pspc,
> + union power_supply_propval *val);
The charging framework can simply call the same get_property
as used by sysfs. This is already done by all kind of drivers.
> + int (*set_property)(struct power_supply_charger *psyc,
> + enum psy_charger_control_property pspc,
> + const union power_supply_propval *val);
I guess this is needed for values, which are supposed to be
writable by the kernel / charging framework, but non-writable
by the sysfs. I suggest to add set_property_kernel() instead
(and make the above properties part of enum power_supply_property)
> +};
> +
> struct power_supply {
> const char *name;
> enum power_supply_type type;
> @@ -200,6 +226,8 @@ struct power_supply {
> void (*external_power_changed)(struct power_supply *psy);
> void (*set_charged)(struct power_supply *psy);
>
> + struct power_supply_charger *psy_charger;
Why is this a pointer?
> +
> /*
> * Set if thermal zone should not be created for this power supply.
> * For example for virtual supplies forwarding calls to actual
-- Sebastian
[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 819 bytes --]
next prev parent reply other threads:[~2015-03-08 1:55 UTC|newest]
Thread overview: 15+ 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 ` [RFC 1/4] power_supply: Introduce charging object table Jenny TC
2015-03-06 11:12 ` 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 [this message]
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
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=20150308015515.GB25160@earth \
--to=sre@kernel.org \
--cc=anton.vorontsov@linaro.org \
--cc=dwmw2@infradead.org \
--cc=jenny.tc@intel.com \
--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 \
/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).