From: jonghwa3.lee@samsung.com
To: "Tc, Jenny" <jenny.tc@intel.com>
Cc: "linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
"linux-pm@vger.kernel.org" <linux-pm@vger.kernel.org>,
"sre@kernel.org" <sre@kernel.org>,
"dbaryshkov@gmail.com" <dbaryshkov@gmail.com>,
"dwmw2@infradead.org" <dwmw2@infradead.org>,
"anton@enomsg.org" <anton@enomsg.org>,
"pavel@ucw.cz" <pavel@ucw.cz>
Subject: Re: [PATCH 1/3] power: core: Add generic interface to get battery specification.
Date: Mon, 10 Nov 2014 10:10:54 +0900 [thread overview]
Message-ID: <5460109E.9060603@samsung.com> (raw)
In-Reply-To: <20ADAB092842284E95860F279283C5642ED8AE04@BGSMSX104.gar.corp.intel.com>
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
next prev parent reply other threads:[~2014-11-10 1:10 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-10-07 10:58 [RFC PATCH 0/3] power: Generic interface to get battery specification Jonghwa Lee
2014-10-07 10:58 ` [PATCH 1/3] power: core: Add generic " Jonghwa Lee
2014-11-08 10:13 ` Tc, Jenny
2014-11-10 1:10 ` jonghwa3.lee [this message]
2014-11-10 3:41 ` Tc, Jenny
2014-11-10 3:41 ` Tc, Jenny
2014-10-07 10:58 ` [PATCH 2/3] power: core: Add variables related temperature to power_supply_info Jonghwa Lee
2014-11-10 11:16 ` Tc, Jenny
2014-11-11 0:30 ` jonghwa3.lee
2014-11-11 4:56 ` Tc, Jenny
2014-11-11 4:56 ` Tc, Jenny
2014-11-11 20:42 ` Pavel Machek
2014-11-12 3:45 ` Tc, Jenny
2014-10-07 10:58 ` [PATCH 3/3] power: of_battery: Initial support for of-based battery specification driver Jonghwa Lee
2014-10-09 10:44 ` Pavel Machek
2015-01-22 0:54 ` [RFC PATCH 0/3] power: Generic interface to get battery specification 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=5460109E.9060603@samsung.com \
--to=jonghwa3.lee@samsung.com \
--cc=anton@enomsg.org \
--cc=dbaryshkov@gmail.com \
--cc=dwmw2@infradead.org \
--cc=jenny.tc@intel.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pm@vger.kernel.org \
--cc=pavel@ucw.cz \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.