From: Pavan Kondeti <pkondeti@codeaurora.org>
To: balbi@ti.com
Cc: "linux-usb@vger.kernel.org" <linux-usb@vger.kernel.org>,
"linux-arm-msm@vger.kernel.org" <linux-arm-msm@vger.kernel.org>
Subject: Re: finding out the attached device current requirement
Date: Thu, 03 Mar 2011 17:01:29 +0530 [thread overview]
Message-ID: <4D6F7C11.1010807@codeaurora.org> (raw)
In-Reply-To: <20110303094512.GI2644@legolas.emea.dhcp.ti.com>
On 3/3/2011 3:15 PM, Felipe Balbi wrote:
> On Thu, Mar 03, 2011 at 02:22:34PM +0530, Pavan Kondeti wrote:
>> Hi
>>
>> I am adding ACA (Accessory Charger Adapter) detection support for MSM
>> OTG driver. Battery charging spec introduced ACA to facilitate charging
>> when acting as a host. The host does not have to supply power on VBUS
>> when ACA is connected. Host device can also draw some amount of current.
>> The amount of current is determined by subtracting the attached
>> peripheral current requirement from the charger rating current. I am
>> looking for a way to find out the attached peripheral's current
>> requirement. We already DEVICE_ADD and DEVICE_REMOVE notifications. But
>
> bMaxPower from the device descriptor ??
>
You are referring to bMaxPower in Configuration descriptor right? When a
multi configuration device is connected, configuration can be changed by
user at any time. The same can also be possible with a user claimed
port. So I am looking for a notification from USB core when a
SET_CONFIGURATION request is sent to a device connected on the root hub.
I will reduce my power (ACA rating current - bMaxpower of the config
being selected) upon this notification.
Thanks,
Pavan
--
Sent by a consultant of the Qualcomm Innovation Center, Inc.
The Qualcomm Innovation Center, Inc. is a member of the Code Aurora Forum.
prev parent reply other threads:[~2011-03-03 11:31 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-03-03 8:52 finding out the attached device current requirement Pavan Kondeti
2011-03-03 9:45 ` Felipe Balbi
2011-03-03 11:31 ` Pavan Kondeti [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=4D6F7C11.1010807@codeaurora.org \
--to=pkondeti@codeaurora.org \
--cc=balbi@ti.com \
--cc=linux-arm-msm@vger.kernel.org \
--cc=linux-usb@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.