linux-kernel - RE: [PATCH 1/2] power_supply: Add charge control struct in power supply class

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Date:	Mon, 7 Jan 2013 05:23:36 +0000
From:	"Tc, Jenny" <jenny.tc@...el.com>
To:	"Pallala, Ramakrishna" <ramakrishna.pallala@...el.com>,
	Anton Vorontsov <anton@...msg.org>
CC:	"linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>,
	Myungjoo Ham <myungjoo.ham@...sung.com>
Subject: RE: [PATCH 1/2] power_supply: Add charge control struct in power
 supply class

> 
> > > +struct power_supply_charger_control {
> > > +	const char *name;
> > > +	/* get charging status */
> > > +	int (*is_charging_enabled)(void);
> > > +	int (*is_charger_enabled)(void);
> > > +
> > > +	/* set charging parameters */
> > > +	int (*set_in_current_limit)(int uA);
> > > +	int (*set_charge_current)(int uA);
> > > +	int (*set_charge_voltage)(int uV);
> > > +
> > > +	/* control battery charging */
> > > +	int (*enable_charging)(void);
> > > +	int (*disable_charging)(void);
> > > +
> > > +	/* control VSYS or system supply */
> > > +	int (*turnon_charger)(void);
> > > +	int (*turnoff_charger)(void);
> > > +};
> > > +
> >
> > I'm all for this patch, but why do you need to place it into
> > power_supply.h and power_supply_core.c? :) I see nothing generic here,
> > it's pure charger-manager stuff. So, place everything into charger-
> manager.{c,h}.
> 
> Hi Anton,
> 
> The main reason for keeping this stuff in power_supply.h and
> power_supply_core.c is to make these interfaces uniform Across multiple
> charger frameworks and to avoid each charger framework define it's own
> interfaces. If there is need for new callback They can add to the existing struct
> defined above and it will available to all the frameworks. Also the work
> required to support a new Framework will be reduced if the driver already
> support any one of the existing frameworks.
> 

Rama,

The similar functionalities are exposed by patch https://lkml.org/lkml/2012/10/18/219.
As per Anton's review comments on this patch, I'll be moving the macros to power_supply.h.
Wouldn't that be enough ?