From: Peter Chen <peter.chen@nxp.com>
To: gregkh@linuxfoundation.org, stern@rowland.harvard.edu,
ulf.hansson@linaro.org, broonie@kernel.org, sre@kernel.org,
robh+dt@kernel.org, shawnguo@kernel.org
Cc: mark.rutland@arm.com, devicetree@vger.kernel.org,
k.kozlowski@samsung.com, stephen.boyd@linaro.org,
oscar@naiandei.net, arnd@arndb.de, pawel.moll@arm.com,
linux-pm@vger.kernel.org, s.hauer@pengutronix.de,
linux-usb@vger.kernel.org, mail@maciej.szmigiero.name,
troy.kisky@boundarydevices.com, stillcompiling@gmail.com,
Peter Chen <peter.chen@nxp.com>,
p.zabel@pengutronix.de, festevam@gmail.com,
linux-arm-kernel@lists.infradead.org
Subject: [PATCH v2 0/6] power: add power sequence library
Date: Wed, 13 Jul 2016 10:06:44 +0800 [thread overview]
Message-ID: <1468375610-18625-1-git-send-email-peter.chen@nxp.com> (raw)
Hi all,
This is a follow-up for my last power sequence framework patch set [1].
According to Rob Herring and Ulf Hansson's comments[2], I use a generic
power sequence library for parsing the power sequence elements on DT,
and implement generic power sequence on library. The host driver
can allocate power sequence instance, and calls pwrseq APIs accordingly.
In future, if there are special power sequence requirements, the special
power sequence library can be created.
This patch set is tested on i.mx6 sabresx evk using a dts change, I use
two hot-plug devices to simulate this use case, the related binding
change is updated at patch[1/6], The udoo board changes were tested
using my last power sequence patch set.[3]
Except for hard-wired MMC and USB devices, I find the USB ULPI PHY also
need to power on itself before it can be found by ULPI bus.
[1] http://www.spinics.net/lists/linux-usb/msg142755.html
[2] http://www.spinics.net/lists/linux-usb/msg143106.html
[3] http://www.spinics.net/lists/linux-usb/msg142815.html
Changes for v2:
- Delete "pwrseq" prefix and clock-names for properties at dt binding
- Should use structure not but its pointer for kzalloc
- Since chipidea core has no of_node, let core's of_node equals glue
layer's at core's probe
Peter Chen (6):
binding-doc: power: pwrseq-generic: add binding doc for generic power
sequence library
power: add power sequence library
binding-doc: usb: usb-device: add optional properties for power
sequence
usb: core: add power sequence handling for USB devices
usb: chipidea: let chipidea core device of_node equal's glue layer
device of_node
ARM: dts: imx6qdl-udoo.dtsi: fix onboard USB HUB property
.../bindings/power/pwrseq/pwrseq-generic.txt | 53 ++++++++
.../devicetree/bindings/usb/usb-device.txt | 9 ++
arch/arm/boot/dts/imx6qdl-udoo.dtsi | 27 +++--
drivers/power/Kconfig | 1 +
drivers/power/Makefile | 1 +
drivers/power/pwrseq/Kconfig | 20 +++
drivers/power/pwrseq/Makefile | 2 +
drivers/power/pwrseq/core.c | 79 ++++++++++++
drivers/power/pwrseq/pwrseq_generic.c | 134 +++++++++++++++++++++
drivers/usb/chipidea/core.c | 10 ++
drivers/usb/core/Makefile | 1 +
drivers/usb/core/hub.c | 12 +-
drivers/usb/core/hub.h | 12 ++
drivers/usb/core/pwrseq.c | 102 ++++++++++++++++
include/linux/power/pwrseq.h | 55 +++++++++
15 files changed, 502 insertions(+), 16 deletions(-)
create mode 100644 Documentation/devicetree/bindings/power/pwrseq/pwrseq-generic.txt
create mode 100644 drivers/power/pwrseq/Kconfig
create mode 100644 drivers/power/pwrseq/Makefile
create mode 100644 drivers/power/pwrseq/core.c
create mode 100644 drivers/power/pwrseq/pwrseq_generic.c
create mode 100644 drivers/usb/core/pwrseq.c
create mode 100644 include/linux/power/pwrseq.h
--
1.9.1
next reply other threads:[~2016-07-13 2:06 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-07-13 2:06 Peter Chen [this message]
2016-07-13 2:06 ` [PATCH v2 1/6] binding-doc: power: pwrseq-generic: add binding doc for generic power sequence library Peter Chen
2016-07-13 7:27 ` Philipp Zabel
2016-07-13 8:42 ` Peter Chen
2016-07-13 23:20 ` Joshua Clayton
2016-07-14 6:36 ` Peter Chen
2016-07-16 22:30 ` Rob Herring
2016-07-18 3:04 ` Peter Chen
2016-07-13 2:06 ` [PATCH v2 2/6] power: add " Peter Chen
2016-07-13 2:06 ` [PATCH v2 3/6] binding-doc: usb: usb-device: add optional properties for power sequence Peter Chen
2016-07-16 22:31 ` Rob Herring
2016-07-18 2:55 ` Peter Chen
2016-07-13 2:06 ` [PATCH v2 4/6] usb: core: add power sequence handling for USB devices Peter Chen
2016-07-13 2:06 ` [PATCH v2 6/6] ARM: dts: imx6qdl-udoo.dtsi: fix onboard USB HUB property Peter Chen
[not found] ` <1468375610-18625-1-git-send-email-peter.chen-3arQi8VN3Tc@public.gmane.org>
2016-07-13 2:06 ` [PATCH v2 5/6] usb: chipidea: let chipidea core device of_node equal's glue layer device of_node Peter Chen
2016-08-23 10:22 ` [PATCH v2 0/6] power: add power sequence library Vaibhav Hiremath
2016-08-23 10:27 ` Vaibhav Hiremath
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=1468375610-18625-1-git-send-email-peter.chen@nxp.com \
--to=peter.chen@nxp.com \
--cc=arnd@arndb.de \
--cc=broonie@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=festevam@gmail.com \
--cc=gregkh@linuxfoundation.org \
--cc=k.kozlowski@samsung.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-pm@vger.kernel.org \
--cc=linux-usb@vger.kernel.org \
--cc=mail@maciej.szmigiero.name \
--cc=mark.rutland@arm.com \
--cc=oscar@naiandei.net \
--cc=p.zabel@pengutronix.de \
--cc=pawel.moll@arm.com \
--cc=robh+dt@kernel.org \
--cc=s.hauer@pengutronix.de \
--cc=shawnguo@kernel.org \
--cc=sre@kernel.org \
--cc=stephen.boyd@linaro.org \
--cc=stern@rowland.harvard.edu \
--cc=stillcompiling@gmail.com \
--cc=troy.kisky@boundarydevices.com \
--cc=ulf.hansson@linaro.org \
/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).