From: Lee Jones <lee.jones@linaro.org>
To: Baolin Wang <baolin.wang@linaro.org>
Cc: Felipe Balbi <balbi@kernel.org>,
Greg KH <gregkh@linuxfoundation.org>,
Sebastian Reichel <sre@kernel.org>,
Dmitry Eremin-Solenikov <dbaryshkov@gmail.com>,
David Woodhouse <dwmw2@infradead.org>,
robh@kernel.org, Jun Li <jun.li@nxp.com>,
Marek Szyprowski <m.szyprowski@samsung.com>,
Ruslan Bilovol <ruslan.bilovol@gmail.com>,
Peter Chen <peter.chen@freescale.com>,
Alan Stern <stern@rowland.harvard.edu>,
grygorii.strashko@ti.com,
Yoshihiro Shimoda <yoshihiro.shimoda.uh@renesas.com>,
Mark Brown <broonie@kernel.org>,
John Stultz <john.stultz@linaro.org>, NeilBrown <neilb@suse.com>,
Charles Keepax <ckeepax@opensource.wolfsonmicro.com>,
patches@opensource.wolfsonmicro.com,
Linux PM list <linux-pm@vger.kernel.org>,
USB <linux-usb@vger.kernel.org>
Subject: Re: [PATCH v19 0/4] Introduce usb charger framework to deal with the usb gadget power negotation
Date: Tue, 14 Mar 2017 12:14:16 +0000 [thread overview]
Message-ID: <20170314121416.lfd5mb6hg5mllk4c@dell> (raw)
In-Reply-To: <CAMz4kuLVtY-rEgDv7RWDP55DEt8bVa99He39DRmGzQeUYZkukA@mail.gmail.com>
On Tue, 14 Mar 2017, Baolin Wang wrote:
> Hi,
>
> On 14 March 2017 at 17:57, Lee Jones <lee.jones@linaro.org> wrote:
> > On Mon, 20 Feb 2017, Baolin Wang wrote:
> >
> > [...]
> >
> >> drivers/power/supply/wm831x_power.c | 63 +++
> >> drivers/usb/gadget/Kconfig | 8 +
> >> drivers/usb/gadget/udc/Makefile | 1 +
> >> drivers/usb/gadget/udc/charger.c | 865 +++++++++++++++++++++++++++++++++++
> >> drivers/usb/gadget/udc/core.c | 19 +-
> >> include/linux/usb/charger.h | 176 +++++++
> >> include/linux/usb/gadget.h | 3 +
> >> include/uapi/linux/usb/charger.h | 31 ++
> >> 8 files changed, 1165 insertions(+), 1 deletion(-)
> >> create mode 100644 drivers/usb/gadget/udc/charger.c
> >> create mode 100644 include/linux/usb/charger.h
> >> create mode 100644 include/uapi/linux/usb/charger.h
> >
> > Why have you sent this set to me?
>
> Since you have one ack on patch 4, I think I need CC you. But If you
> are not interested in this patchset, I will not CC you next time.
> Sorry.
I Acked one of the patches 9 months ago since it contained an MFD
change.
Yes, if you could drop me from any new submissions, that'd be great,
thanks.
> [PATCH v19 4/4] power: wm831x_power: Support USB charger current limit
> management
>
> Integrate with the newly added USB charger interface to limit the current
> we draw from the USB input based on the input device configuration
> identified by the USB stack, allowing us to charge more quickly from high
> current inputs without drawing more current than specified from others.
>
> Signed-off-by: Mark Brown <broonie@kernel.org>
> Signed-off-by: Baolin Wang <baolin.wang@linaro.org>
> Acked-by: Lee Jones <lee.jones@linaro.org>
> Acked-by: Charles Keepax <ckeepax@opensource.wolfsonmicro.com>
> Acked-by: Peter Chen <peter.chen@freescale.com>
> Acked-by: Sebastian Reichel <sre@kernel.org>
> .......
>
--
Lee Jones
Linaro STMicroelectronics Landing Team Lead
Linaro.org │ Open source software for ARM SoCs
Follow Linaro: Facebook | Twitter | Blog
prev parent reply other threads:[~2017-03-14 12:14 UTC|newest]
Thread overview: 27+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-02-20 8:51 [PATCH v19 0/4] Introduce usb charger framework to deal with the usb gadget power negotation Baolin Wang
2017-02-20 8:51 ` [PATCH v19 2/4] usb: gadget: Support for the usb charger framework Baolin Wang
2017-02-20 10:08 ` kbuild test robot
2017-02-20 10:18 ` Baolin Wang
2017-02-20 8:51 ` [PATCH v19 3/4] usb: gadget: Integrate with the usb gadget supporting for usb charger Baolin Wang
[not found] ` <cover.1487578977.git.baolin.wang-QSEj5FYQhm4dnm+yROfE0A@public.gmane.org>
2017-02-20 8:51 ` [PATCH v19 1/4] usb: gadget: Introduce the usb charger framework Baolin Wang
2017-02-20 8:51 ` [PATCH v19 4/4] power: wm831x_power: Support USB charger current limit management Baolin Wang
2017-02-20 10:20 ` kbuild test robot
2017-03-03 2:23 ` [PATCH v19 0/4] Introduce usb charger framework to deal with the usb gadget power negotation NeilBrown
[not found] ` <87zih3m73h.fsf-wvvUuzkyo1HefUI2i7LXDhCRmIWqnp/j@public.gmane.org>
2017-03-07 9:38 ` Baolin Wang
2017-03-09 1:50 ` Jun Li
2017-03-09 6:10 ` Baolin Wang
2017-03-09 10:34 ` Jun Li
2017-03-09 11:22 ` Baolin Wang
2017-03-10 6:30 ` Jun Li
2017-03-10 7:15 ` Baolin Wang
2017-03-10 8:27 ` Jun Li
2017-03-10 10:52 ` Baolin Wang
2017-03-13 1:09 ` Jun Li
2017-03-13 8:43 ` Baolin Wang
2017-03-14 1:10 ` Jun Li
[not found] ` <HE1PR04MB2972189B0532136078A5221D89240-6LN7OEpIatUyGO52j9nQIM9NdZoXdze2vxpqHgZTriW3zl9H0oFU5g@public.gmane.org>
2017-03-14 2:03 ` Baolin Wang
2017-03-28 23:04 ` NeilBrown
2017-03-30 3:16 ` Baolin Wang
2017-03-14 9:57 ` Lee Jones
2017-03-14 10:39 ` Baolin Wang
2017-03-14 12:14 ` Lee Jones [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=20170314121416.lfd5mb6hg5mllk4c@dell \
--to=lee.jones@linaro.org \
--cc=balbi@kernel.org \
--cc=baolin.wang@linaro.org \
--cc=broonie@kernel.org \
--cc=ckeepax@opensource.wolfsonmicro.com \
--cc=dbaryshkov@gmail.com \
--cc=dwmw2@infradead.org \
--cc=gregkh@linuxfoundation.org \
--cc=grygorii.strashko@ti.com \
--cc=john.stultz@linaro.org \
--cc=jun.li@nxp.com \
--cc=linux-pm@vger.kernel.org \
--cc=linux-usb@vger.kernel.org \
--cc=m.szyprowski@samsung.com \
--cc=neilb@suse.com \
--cc=patches@opensource.wolfsonmicro.com \
--cc=peter.chen@freescale.com \
--cc=robh@kernel.org \
--cc=ruslan.bilovol@gmail.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