[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20ADAB092842284E95860F279283C5642ED9EDE3@BGSMSX104.gar.corp.intel.com>
Date: Mon, 10 Nov 2014 11:16:32 +0000
From: "Tc, Jenny" <jenny.tc@...el.com>
To: Jonghwa Lee <jonghwa3.lee@...sung.com>,
"linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>
CC: "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 2/3] power: core: Add variables related temperature to
power_supply_info.
> @@ -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;
};
-Jenny
--
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