From: Felipe Balbi <balbi@ti.com>
To: Felipe Balbi <balbi@ti.com>
Cc: Mark Brown <broonie@kernel.org>,
Baolin Wang <baolin.wang@linaro.org>,
Greg KH <gregkh@linuxfoundation.org>, <sre@kernel.org>,
<dbaryshkov@gmail.com>, <dwmw2@infradead.org>,
<peter.chen@freescale.com>, <stern@rowland.harvard.edu>,
<r.baldyga@samsung.com>, <sojka@merica.cz>,
<yoshihiro.shimoda.uh@renesas.com>, <linux-usb@vger.kernel.org>,
<linux-kernel@vger.kernel.org>, <sameo@linux.intel.com>,
<lee.jones@linaro.org>, <ckeepax@opensource.wolfsonmicro.com>,
<patches@opensource.wolfsonmicro.com>, <linux-pm@vger.kernel.org>,
<device-mainlining@lists.linuxfoundation.org>
Subject: Re: [PATCH v4 1/5] gadget: Introduce the notifier functions
Date: Thu, 1 Oct 2015 13:01:09 -0500 [thread overview]
Message-ID: <20151001180109.GI4469@saruman.tx.rr.com> (raw)
In-Reply-To: <20151001175849.GH4469@saruman.tx.rr.com>
[-- Attachment #1: Type: text/plain, Size: 1165 bytes --]
On Thu, Oct 01, 2015 at 12:58:49PM -0500, Felipe Balbi wrote:
> Hi,
>
> On Thu, Oct 01, 2015 at 06:43:08PM +0100, Mark Brown wrote:
> > On Thu, Oct 01, 2015 at 12:29:32PM -0500, Felipe Balbi wrote:
> >
> > > Frankly, I wanted all of this to be decided in userland with the
> > > kernel just providing notification and basic safety checks (we don't
> > > want to allow a bogus userspace daemon frying anybody's devices).
> >
> > What's the advantage of pushing this to userspace? By the time we
> > provide enough discoverability to enable userspace to configure itself
> > it seems like we'd have enough information to do the job anyway.
>
> you're going to be dealing with a setup where each vendor does one thing
> differently. Some will have it all in the SoC part of a single IP (dwc3 can be
> configured that way), some will push it out to companion IC, some might even use
oh, and as for dwc3 itself: it *can* be configured that way, but all those
charging blocks are optional :-) So you will even have setups where the very
same IP works differently because SoC vendor A configured it differently from
SoC vendor B.
--
balbi
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 819 bytes --]
next prev parent reply other threads:[~2015-10-01 18:02 UTC|newest]
Thread overview: 27+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-09-24 17:39 [PATCH v4 0/5] Introduce usb charger framework to deal with the usb gadget power negotation Baolin Wang
2015-09-24 17:39 ` [PATCH v4 1/5] gadget: Introduce the notifier functions Baolin Wang
2015-10-01 17:29 ` Felipe Balbi
2015-10-01 17:43 ` Mark Brown
2015-10-01 17:58 ` Felipe Balbi
2015-10-01 18:01 ` Felipe Balbi [this message]
2015-10-02 16:47 ` Mark Brown
2015-10-02 17:23 ` Felipe Balbi
2015-10-02 18:49 ` Mark Brown
2015-10-02 19:11 ` Felipe Balbi
2015-10-04 22:55 ` Mark Brown
2015-10-05 15:15 ` Felipe Balbi
2015-10-05 16:18 ` Mark Brown
2015-10-05 16:29 ` Felipe Balbi
2015-10-07 16:44 ` [Device-mainlining] " Bjorn Andersson
2015-10-08 15:51 ` Pavel Machek
2015-10-02 5:41 ` Greg KH
2015-10-02 17:27 ` Felipe Balbi
2015-10-08 15:50 ` Pavel Machek
2015-10-09 21:17 ` Felipe Balbi
2015-10-12 16:56 ` Mark Brown
2016-04-09 16:01 ` Pavel Machek
2015-09-24 17:39 ` [PATCH v4 2/5] gadget: Introduce the usb charger framework Baolin Wang
2015-09-24 17:39 ` [PATCH v4 3/5] gadget: Support for " Baolin Wang
2015-09-24 17:39 ` [PATCH v4 4/5] gadget: Integrate with the usb gadget supporting for usb charger Baolin Wang
2015-09-24 17:39 ` [PATCH v4 5/5] power: wm831x_power: Support USB charger current limit management Baolin Wang
-- strict thread matches above, loose matches on Subject: below --
2015-08-19 9:13 [PATCH v4 0/5] Introduce usb charger framework to deal with the usb gadget power negotation Baolin Wang
2015-08-19 9:13 ` [PATCH v4 1/5] gadget: Introduce the notifier functions 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=20151001180109.GI4469@saruman.tx.rr.com \
--to=balbi@ti.com \
--cc=baolin.wang@linaro.org \
--cc=broonie@kernel.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=sameo@linux.intel.com \
--cc=sojka@merica.cz \
--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
Powered by JetHome