[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-id: <5460109E.9060603@samsung.com>
Date: Mon, 10 Nov 2014 10:10:54 +0900
From: jonghwa3.lee@...sung.com
To: "Tc, Jenny" <jenny.tc@...el.com>
Cc: "linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>,
"linux-pm@...r.kernel.org" <linux-pm@...r.kernel.org>,
"sre@...nel.org" <sre@...nel.org>,
"dbaryshkov@...il.com" <dbaryshkov@...il.com>,
"dwmw2@...radead.org" <dwmw2@...radead.org>,
"anton@...msg.org" <anton@...msg.org>,
"pavel@....cz" <pavel@....cz>
Subject: Re: [PATCH 1/3] power: core: Add generic interface to get battery
specification.
On 2014년 11월 08일 19:13, Tc, Jenny wrote:
>> +ATOMIC_NOTIFIER_HEAD(psy_battery_info_notifier);
>
> Isn't it good to reuse the existing power_supply_notifier for this?
>
>> +enum battery_info_notifier_events {
>> + PSY_BATT_INFO_REGISTERED,
>> + PSY_BATT_INFO_UNREGISTERED,
>> +};
>
> If we use the power_supply_notifier, then this can be moved to
> enum power_supply_notifier_events
>
It doesn't use power_supply_notifier, rather than it uses newly introduced
notifier for battery information. Intention of making of new notifier block here
is to extinguish event from power_supply_changed which might be noisy for
battery information consumer. However, If it looks wasteful code, it's not a big
deal to use existed power_supply_notifier.
Thanks,
Jonghwa
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists