>
> >> +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_noti
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
> +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
In power supply system, battery specification's dealt as static
information regardless of battery chainging. And it often assumed
fuelgauge's role to hold battery specification even same driver is
used with different batteries. To make subsystem handles above cases
properly, this patch adds helper
4 matches
Mail list logo