[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <87vb3v2nm8.fsf@intel.com>
Date: Wed, 06 Apr 2016 10:38:23 +0300
From: Felipe Balbi <balbi@...nel.org>
To: Peter Chen <hzpeterchen@...il.com>,
Baolin Wang <baolin.wang@...aro.org>
Cc: gregkh@...uxfoundation.org, sre@...nel.org, dbaryshkov@...il.com,
dwmw2@...radead.org, peter.chen@...escale.com,
stern@...land.harvard.edu, r.baldyga@...sung.com,
yoshihiro.shimoda.uh@...esas.com, lee.jones@...aro.org,
broonie@...nel.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
Subject: Re: [PATCH v9 1/4] gadget: Introduce the usb charger framework
Peter Chen <hzpeterchen@...il.com> writes:
> On Fri, Apr 01, 2016 at 03:21:49PM +0800, Baolin Wang wrote:
> +
>> +static struct attribute *usb_charger_attrs[] = {
>> + &dev_attr_sdp_current.attr,
>> + &dev_attr_dcp_current.attr,
>> + &dev_attr_cdp_current.attr,
>> + &dev_attr_aca_current.attr,
>> + &dev_attr_charger_type.attr,
>> + &dev_attr_charger_state.attr,
>> + NULL
>> +};
>
> The user may only care about current limit, type and state, why they
> need to care what type's current limit, it is the usb charger
> framework handles, the framework judge the current according to
> charger type and USB state (connect/configured/suspended).
it might be useful if we want to know that $this charger doesn't really
give us as much current as it advertises.
--
balbi
Download attachment "signature.asc" of type "application/pgp-signature" (819 bytes)
Powered by blists - more mailing lists