lists.openwall.net   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  linux-cve-announce  PHC 
Open Source and information security mailing list archives
 
Hash Suite: Windows password security audit tool. GUI, reports in PDF.
[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <D854C92F57B1B347B57E531E78D05EAD142B57@BGSMSX102.gar.corp.intel.com>
Date:	Wed, 9 May 2012 06:47:54 +0000
From:	"Pallala, Ramakrishna" <ramakrishna.pallala@...el.com>
To:	"Tc, Jenny" <jenny.tc@...el.com>,
	"myungjoo.ham@...sung.com" <myungjoo.ham@...sung.com>,
	"linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>
CC:	Anton Vorontsov <cbouatmailru@...il.com>,
	Anton Vorontsov <anton.vorontsov@...aro.org>,
	??? <cw00.choi@...sung.com>
Subject: RE: [PATCH v2] charger_manager: update charge profile upon
 temperature zone change

> >
> > As part of charge enablement we generally program charge current,
> > charge voltage into the charger chip.
> >
> > We can pass the charging parameters CC and CV in two ways.
> > 1. Add these params in charger_desc struct and the  charger regulator
> > can get these params using container_of() call? but becomes complex.
> >
> > 2. use regulator_set_voltage()/regulator_set_current_limit() functions
> > to set the CV and CC params.
> > but not suitable as is, we have add support in regulator framework
> >
> 
> regulator_ops has support for set_current_limit and set_voltage. Can we use the same for
> setting CC and CV?

I feel set_voltage()/set_current_limit() is more suitable to control input source current and
voltage, but CC and CV are more like output parameters from charger.

Thanks,
Ram

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ