From: Greg KH <gregkh@suse.de>
To: Morten CHRISTIANSEN <morten.christiansen@stericsson.com>
Cc: "Linus Walleij" <linus.walleij@linaro.org>,
NeilBrown <neilb@suse.de>, "Arnd Bergmann" <arnd@arndb.de>,
"myungjoo.ham@gmail.com" <myungjoo.ham@gmail.com>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
"Mike Lockwood" <lockwood@android.com>,
"Arve Hjønnevåg" <arve@android.com>,
"Kyungmin Park" <kyungmin.park@samsung.com>,
"Donggeun Kim" <dg77.kim@samsung.com>,
"Grant Likely" <grant.likely@secretlab.ca>,
"Karl KOMIEROWSKI" <karl.komierowski@stericsson.com>,
"Johan BJORNSTEDT" <johan.bjornstedt@stericsson.com>,
"Daniel WILLERUD" <daniel.willerud@stericsson.com>,
"Dmitry Torokhov" <dmitry.torokhov@gmail.com>,
"Mian Yousaf KAUKAB" <mian.yousaf.kaukab@stericsson.com>
Subject: Re: [RFC PATCH 0/3] introduce: Multistate Switch Class
Date: Wed, 30 Nov 2011 15:34:05 +0900 [thread overview]
Message-ID: <20111130063405.GA12052@suse.de> (raw)
In-Reply-To: <AFCDDB4A3EA003429EEF1E7B211FDBBA36EE80C928@EXDCVYMBSTM005.EQ1STM.local>
On Mon, Nov 28, 2011 at 04:09:47PM +0100, Morten CHRISTIANSEN wrote:
> Hello!
>
> Linus is correct. However some more info might be useful? Feel free to drop off whenever in the more and more detailed explanations! This is a non-trivial issue that has had some effort spent on it already.
>
> SUMMARY: Devices today charge at high current (1.5A) from a dedicated charger and 500mA max from a standard USB port, using the standard MaxPower parameter. It would have been great if devices could also charge at higher current from a host or hub port but that is not really practical due to HW issues, not SW issues. See below. A new USB Power Delivery spec is imminent that might be of interest?
>
> SHORT VERSION OF PREVIOUS EFFORTS:
> Using HID for managing USB battery charging current from the host is indeed the correct approach. And a work effort in USB Device Working Group went all the way to "ready for publication" state - and then died (for a number of reasons) some years ago. (Due to IPR reasons I cannot forward the un-released version of the spec.)
>
> I see no reason to revisit the HID approach since it will not get any device support. Even if it was the correct approach.
<snip>
thanks a lot for the information, it was very helpful.
greg k-h
next prev parent reply other threads:[~2011-11-30 6:35 UTC|newest]
Thread overview: 44+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-11-24 2:03 MyungJoo Ham
2011-11-25 14:02 ` Arnd Bergmann
2011-11-26 5:46 ` MyungJoo Ham
2011-11-26 13:23 ` Kyungmin Park
2011-11-27 22:43 ` Linus Walleij
2011-11-27 23:08 ` Greg KH
2011-11-28 0:09 ` Dmitry Torokhov
2011-11-28 0:19 ` Greg KH
2011-11-28 9:03 ` Dmitry Torokhov
2011-11-28 1:31 ` NeilBrown
2011-11-28 7:27 ` Greg KH
2011-11-28 9:04 ` Dmitry Torokhov
2011-11-30 6:35 ` Greg KH
2011-11-30 6:58 ` MyungJoo Ham
2011-11-30 9:46 ` Mark Brown
2011-11-30 13:28 ` Linus Walleij
2011-11-30 23:04 ` NeilBrown
2011-12-01 13:38 ` Linus Walleij
2011-11-28 13:04 ` Linus Walleij
2011-11-28 15:09 ` Morten CHRISTIANSEN
2011-11-30 6:34 ` Greg KH [this message]
2011-11-28 17:53 ` Arnd Bergmann
2011-11-29 9:11 ` MyungJoo Ham
2011-11-29 9:45 ` Linus Walleij
2011-11-29 13:59 ` Arnd Bergmann
2011-11-29 17:05 ` Dmitry Torokhov
2011-11-30 2:58 ` NeilBrown
2011-11-30 6:40 ` MyungJoo Ham
2011-11-30 22:56 ` NeilBrown
2011-11-30 23:17 ` Mark Brown
2011-11-30 23:25 ` Dmitry Torokhov
2011-12-01 4:51 ` MyungJoo Ham
2011-12-01 5:21 ` NeilBrown
2011-12-01 11:34 ` Mark Brown
2011-12-05 3:04 ` NeilBrown
2011-12-05 12:06 ` Mark Brown
2011-12-05 19:38 ` NeilBrown
2011-12-05 19:45 ` Mark Brown
2011-12-01 4:46 ` MyungJoo Ham
2011-12-07 9:31 ` Linus Walleij
2011-12-08 4:42 ` Kyungmin Park
2011-11-26 15:32 ` Greg KH
2011-11-29 8:18 ` MyungJoo Ham
2011-11-28 18:23 ` Mark Brown
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=20111130063405.GA12052@suse.de \
--to=gregkh@suse.de \
--cc=arnd@arndb.de \
--cc=arve@android.com \
--cc=daniel.willerud@stericsson.com \
--cc=dg77.kim@samsung.com \
--cc=dmitry.torokhov@gmail.com \
--cc=grant.likely@secretlab.ca \
--cc=johan.bjornstedt@stericsson.com \
--cc=karl.komierowski@stericsson.com \
--cc=kyungmin.park@samsung.com \
--cc=linus.walleij@linaro.org \
--cc=linux-kernel@vger.kernel.org \
--cc=lockwood@android.com \
--cc=mian.yousaf.kaukab@stericsson.com \
--cc=morten.christiansen@stericsson.com \
--cc=myungjoo.ham@gmail.com \
--cc=neilb@suse.de \
/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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
Powered by JetHome