public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Baolin Wang <baolin.wang@linaro.org>
To: balbi@kernel.org, gregkh@linuxfoundation.org, sre@kernel.org,
	dbaryshkov@gmail.com, dwmw2@infradead.org
Cc: peter.chen@freescale.com, stern@rowland.harvard.edu,
	r.baldyga@samsung.com, yoshihiro.shimoda.uh@renesas.com,
	lee.jones@linaro.org, broonie@kernel.org,
	ckeepax@opensource.wolfsonmicro.com,
	patches@opensource.wolfsonmicro.com, baolin.wang@linaro.org,
	linux-pm@vger.kernel.org, linux-usb@vger.kernel.org,
	device-mainlining@lists.linuxfoundation.org,
	linux-kernel@vger.kernel.org
Subject: [PATCH v8 0/4] Introduce usb charger framework to deal with the usb gadget power negotation
Date: Thu, 24 Mar 2016 20:35:53 +0800	[thread overview]
Message-ID: <cover.1458822334.git.baolin.wang@linaro.org> (raw)

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.

Now introduce one user with wm831x_power to support and test the usb charger,
which is pending testing. Moreover there may be other potential users will use
it in future.

Changes since v7:
 - Add documentations for sysfs attributes.

Other prominent improvements since v5:
 - Remove the notifier chain things from the gadget and introduce one callback
 function to report to the usb charger when the gadget state is changed.
 - Flesh out the port type detection which combines the USB negotiation and
 PMICs detection.
 - Supply the notification mechanism to userspace when charger state is changed.
 - Integrate with the vbus staff in the gadget API.

Baolin Wang (4):
  gadget: Introduce the usb charger framework
  gadget: Support for the usb charger framework
  gadget: Integrate with the usb gadget supporting for usb charger
  power: wm831x_power: Support USB charger current limit management

 drivers/power/wm831x_power.c      |   69 ++++
 drivers/usb/gadget/Kconfig        |    7 +
 drivers/usb/gadget/Makefile       |    1 +
 drivers/usb/gadget/charger.c      |  714 +++++++++++++++++++++++++++++++++++++
 drivers/usb/gadget/udc/udc-core.c |   11 +
 include/linux/mfd/wm831x/pdata.h  |    3 +
 include/linux/usb/gadget.h        |   11 +
 include/linux/usb/usb_charger.h   |  164 +++++++++
 8 files changed, 980 insertions(+)
 create mode 100644 drivers/usb/gadget/charger.c
 create mode 100644 include/linux/usb/usb_charger.h

-- 
1.7.9.5

             reply	other threads:[~2016-03-24 12:36 UTC|newest]

Thread overview: 41+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-03-24 12:35 Baolin Wang [this message]
2016-03-24 12:35 ` [PATCH v8 1/4] gadget: Introduce the usb charger framework Baolin Wang
2016-04-23 19:53   ` Pavel Machek
2016-04-24  5:32     ` Baolin Wang
2016-03-24 12:35 ` [PATCH v8 2/4] gadget: Support for " Baolin Wang
2016-03-27  1:29   ` kbuild test robot
2016-03-24 12:35 ` [PATCH v8 3/4] gadget: Integrate with the usb gadget supporting for usb charger Baolin Wang
2016-03-24 12:35 ` [PATCH v8 4/4] power: wm831x_power: Support USB charger current limit management Baolin Wang
2016-03-27  2:08   ` kbuild test robot
2016-03-27  8:22   ` Geert Uytterhoeven
2016-03-28  6:45     ` Baolin Wang
2016-03-25  7:09 ` [PATCH v8 0/4] Introduce usb charger framework to deal with the usb gadget power negotation Peter Chen
2016-03-28  6:51   ` Baolin Wang
2016-03-28  7:13     ` Peter Chen
2016-03-28  9:09       ` Baolin Wang
2016-03-29  0:32         ` Peter Chen
2016-03-29  2:05           ` Baolin Wang
2016-03-29 17:14             ` Mark Brown
2016-03-29 17:23       ` Mark Brown
2016-03-30  2:05         ` Peter Chen
2016-03-30  7:07           ` Baolin Wang
2016-03-30  7:42             ` Peter Chen
2016-03-30  8:40               ` Baolin Wang
2016-03-30  9:19                 ` Peter Chen
2016-03-30  9:32                   ` Baolin Wang
2016-03-29  8:45     ` Jun Li
2016-03-29  9:48       ` Baolin Wang
2016-03-30  2:54         ` Jun Li
2016-03-30  6:15           ` Baolin Wang
2016-03-30  8:07             ` Jun Li
2016-03-30  9:30               ` Baolin Wang
2016-03-30 10:58                 ` Jun Li
2016-03-30 11:24                   ` Felipe Balbi
2016-03-31  5:33                     ` Baolin Wang
2016-03-31  6:18                       ` Felipe Balbi
2016-03-31  6:35                         ` Baolin Wang
2016-03-31  5:22                   ` Baolin Wang
2016-03-31  6:12                     ` Jun Li
2016-03-31  6:37                       ` Baolin Wang
2016-03-31  8:15                         ` Felipe Balbi
2016-03-31  8:24                           ` 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=cover.1458822334.git.baolin.wang@linaro.org \
    --to=baolin.wang@linaro.org \
    --cc=balbi@kernel.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=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