From: Mark Brown <broonie@kernel.org>
To: Baolin Wang <baolin.wang@linaro.org>
Cc: balbi@kernel.org, gregkh@linuxfoundation.org, sre@kernel.org,
dbaryshkov@gmail.com, dwmw2@infradead.org,
peter.chen@freescale.com, stern@rowland.harvard.edu,
r.baldyga@samsung.com, yoshihiro.shimoda.uh@renesas.com,
lee.jones@linaro.org, ckeepax@opensource.wolfsonmicro.com,
patches@opensource.wolfsonmicro.com, linux-pm@vger.kernel.org,
linux-usb@vger.kernel.org,
device-mainlining@lists.linuxfoundation.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH v7 0/4] Introduce usb charger framework to deal with the usb gadget power negotation
Date: Tue, 15 Mar 2016 16:39:18 +0000 [thread overview]
Message-ID: <20160315163918.GQ2566@sirena.org.uk> (raw)
In-Reply-To: <20160229142212.GB18327@sirena.org.uk>
[-- Attachment #1: Type: text/plain, Size: 1345 bytes --]
On Mon, Feb 29, 2016 at 11:22:12PM +0900, Mark Brown wrote:
> On Mon, Jan 04, 2016 at 11:04:26AM +0800, Baolin Wang wrote:
I see Felipe is no longer at TI so his e-mail was bouncing - let's
resend this with his kernel.org address:
> > Currently the Linux kernel does not provide any standard integration of this
> > feature that integrates the USB subsystem with the system power regulation
> > provided by PMICs meaning that either vendors must add this in their kernels
> > or USB gadget devices based on Linux (such as mobile phones) may not behave
> > as they should. Thus provide a standard framework for doing this in kernel.
> So, the review of this seems to have ground to a bit of a halt - we're
> really not seeing any engagement or comments here, people aren't raising
> any problems or suggesting alternative approaches but this isn't moving
> forwards either. This means that nothing running mainline that isn't
> totally offloaded to hardware can charge at even 500mA, let alone more,
> which seems like a failure to me. What do we need to move this
> forwards?
> If there are concerns around ABI we could either make sure it's as basic
> as possible (so that it'll be easy to maintain compatibility if we think
> of something better) or just hide things from userspace so that we just
> have the in kernel implementation.
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 473 bytes --]
next prev parent reply other threads:[~2016-03-15 16:40 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-01-04 3:04 [PATCH v7 0/4] Introduce usb charger framework to deal with the usb gadget power negotation Baolin Wang
2016-01-04 3:04 ` [PATCH v7 1/4] gadget: Introduce the usb charger framework Baolin Wang
2016-01-04 3:04 ` [PATCH v7 2/4] gadget: Support for " Baolin Wang
2016-01-04 3:04 ` [PATCH v7 3/4] gadget: Integrate with the usb gadget supporting for usb charger Baolin Wang
2016-01-04 3:04 ` [PATCH v7 4/4] power: wm831x_power: Support USB charger current limit management Baolin Wang
2016-01-04 5:21 ` kbuild test robot
[not found] ` <CAGjg+kHzt7pxxU=OdTd3sLWETiA7P6iMBmNs6dNvSCzFZiwv4w@mail.gmail.com>
2016-01-07 11:54 ` [PATCH v7 0/4] Introduce usb charger framework to deal with the usb gadget power negotation Baolin Wang
2016-01-25 3:44 ` Greg KH
2016-01-25 4:14 ` Baolin Wang
2016-02-29 14:22 ` Mark Brown
2016-03-15 16:39 ` Mark Brown [this message]
2016-03-16 11:05 ` Felipe Balbi
2016-03-16 11:20 ` Mark Brown
2016-03-16 11:27 ` Baolin Wang
-- strict thread matches above, loose matches on Subject: below --
2016-03-16 11:46 Baolin Wang
2016-03-16 11:48 ` Felipe Balbi
2016-03-16 11:56 ` Baolin Wang
2015-12-08 8:36 Baolin Wang
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=20160315163918.GQ2566@sirena.org.uk \
--to=broonie@kernel.org \
--cc=balbi@kernel.org \
--cc=baolin.wang@linaro.org \
--cc=ckeepax@opensource.wolfsonmicro.com \
--cc=dbaryshkov@gmail.com \
--cc=device-mainlining@lists.linuxfoundation.org \
--cc=dwmw2@infradead.org \
--cc=gregkh@linuxfoundation.org \
--cc=lee.jones@linaro.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pm@vger.kernel.org \
--cc=linux-usb@vger.kernel.org \
--cc=patches@opensource.wolfsonmicro.com \
--cc=peter.chen@freescale.com \
--cc=r.baldyga@samsung.com \
--cc=sre@kernel.org \
--cc=stern@rowland.harvard.edu \
--cc=yoshihiro.shimoda.uh@renesas.com \
/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;
as well as URLs for NNTP newsgroup(s).