> > The CC/CV for each battery temperature zone is defined as part of battery
> > spec.
> This is
> > as per the JEITA/PSE standards. So IMO, this is a battery charging
> > information
> > (charging object) rather than a thermal throttling information.
> >
> > Also the battery information may not
On Tue 2014-11-11 04:56:31, Tc, Jenny wrote:
> > > The CC,CV and restart threshold would vary based on the battery
> > > temperature
> > > So I would suggest to have temperature zone table as part of battery info
> > > along with other attributes.
> > >
> > > int iterm; //charge termination curre
> > The CC,CV and restart threshold would vary based on the battery temperature
> > So I would suggest to have temperature zone table as part of battery info
> > along with other attributes.
> >
> > int iterm; //charge termination current (used to stop charging)
> > int temp_zone_count; // number
On 2014년 11월 10일 20:16, Tc, Jenny wrote:
>> @@ -241,6 +241,8 @@ struct power_supply_info {
>> int charge_empty_design;
>> int energy_full_design;
>> int energy_empty_design;
>> +int temperature_max;
>> +int temperature_min;
>> int use_for_apm;
>> };
>
>
> The CC,CV a
> @@ -241,6 +241,8 @@ struct power_supply_info {
> int charge_empty_design;
> int energy_full_design;
> int energy_empty_design;
> + int temperature_max;
> + int temperature_min;
> int use_for_apm;
> };
The CC,CV and restart threshold would vary based on the batte
To represent thermal limitation of power_supply, it adds 'temperature_max,
temperature_min' to power_supply_info structure.
Signed-off-by: Jonghwa Lee
---
include/linux/power_supply.h |2 ++
1 file changed, 2 insertions(+)
diff --git a/include/linux/power_supply.h b/include/linux/power_supp
6 matches
Mail list logo
