[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20160503105718.GL6292@sirena.org.uk>
Date: Tue, 3 May 2016 11:57:18 +0100
From: Mark Brown <broonie@...nel.org>
To: Manish Badarkhe <badarkhe.manish@...il.com>
Cc: Baolin Wang <baolin.wang@...aro.org>, balbi@...nel.org,
gregkh@...uxfoundation.org, sre@...nel.org,
Dmitry Eremin-Solenikov <dbaryshkov@...il.com>,
David Woodhouse <dwmw2@...radead.org>, robh@...nel.org,
m.szyprowski@...sung.com, ruslan.bilovol@...il.com,
peter.chen@...escale.com, stern@...land.harvard.edu,
r.baldyga@...sung.com, yoshihiro.shimoda.uh@...esas.com,
Lee Jones <lee.jones@...aro.org>,
ckeepax@...nsource.wolfsonmicro.com,
patches@...nsource.wolfsonmicro.com, linux-pm@...r.kernel.org,
linux-usb@...r.kernel.org,
device-mainlining@...ts.linuxfoundation.org,
"linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>
Subject: Re: [RESEND PATCH v10 4/4] power: wm831x_power: Support USB charger
current limit management
On Tue, May 03, 2016 at 09:30:48AM +0530, Manish Badarkhe wrote:
> On Tue, May 3, 2016 at 9:00 AM, Baolin Wang <baolin.wang@...aro.org> wrote:
> > +static const unsigned int wm831x_usb_limits[] = {
> > + 0,
> > + 2,
> > + 100,
> > + 500,
> > + 900,
> > + 1500,
> > + 1800,
> > + 550,
> > +};
> Just for curiosity, How these current limits are getting decided?
> Can we have some proper defines over here so that it can be grasped easily?
They're in the silicon, it's just a table of values that were put into
the silicon at design time. The defines would just be TABLE_ENTRY_1 or
whatever.
Download attachment "signature.asc" of type "application/pgp-signature" (474 bytes)
Powered by blists - more mailing lists