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  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, 10 Nov 2014 11:16:32 +0000
From:	"Tc, Jenny" <>
To:	Jonghwa Lee <>,
	"" <>
CC:	"" <>,
	"" <>,
	"" <>,
	"" <>,
	"" <>,
	"" <>
Subject: RE: [PATCH 2/3] power: core: Add variables related temperature to

> @@ -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 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 of temperature zone tables present
struct batt_temp_mon_table temp_mon_tbl[MAX_TEMP_MON_TABLE]; //temperature zone table array

struct  batt_temp_mon_table {
	 short int temp_max;
	 short int cc;
	 short int cv;
	 short int vbat_vchk_drop_uv;
	 short int temp_min;


To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to
More majordomo info at
Please read the FAQ at

Powered by blists - more mailing lists