linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Matthias Kaehlcke <mka@chromium.org>
To: Peter Chen <peter.chen@nxp.com>
Cc: gregkh@linuxfoundation.org, stern@rowland.harvard.edu,
	ulf.hansson@linaro.org, broonie@kernel.org, sre@kernel.org,
	robh+dt@kernel.org, shawnguo@kernel.org, dbaryshkov@gmail.com,
	dwmw3@infradead.org, k.kozlowski@samsung.com,
	linux-arm-kernel@lists.infradead.org, p.zabel@pengutronix.de,
	devicetree@vger.kernel.org, pawel.moll@arm.com,
	mark.rutland@arm.com, linux-usb@vger.kernel.org, arnd@arndb.de,
	s.hauer@pengutronix.de, mail@maciej.szmigiero.name,
	troy.kisky@boundarydevices.com, festevam@gmail.com,
	oscar@naiandei.net, stephen.boyd@linaro.org,
	linux-pm@vger.kernel.org, stillcompiling@gmail.com,
	linux-kernel@vger.kernel.org
Subject: Re: [PATCH v5 2/6] power: add power sequence library
Date: Mon, 8 Aug 2016 17:25:01 -0700	[thread overview]
Message-ID: <20160809002501.GA125064@google.com> (raw)
In-Reply-To: <1470646331-23227-3-git-send-email-peter.chen@nxp.com>

El Mon, Aug 08, 2016 at 04:52:07PM +0800 Peter Chen ha dit:

> We have an well-known problem that the device needs to do some power
> sequence before it can be recognized by related host, the typical
> example like hard-wired mmc devices and usb devices.
> 
> This power sequence is hard to be described at device tree and handled by
> related host driver, so we have created a common power sequence
> library to cover this requirement. The core code has supplied
> some common helpers for host driver, and individual power sequence
> libraries handle kinds of power sequence for devices.
> 
> pwrseq_generic is intended for general purpose of power sequence, which
> handles gpios and clocks currently, and can cover regulator and pinctrl
> in future. The host driver calls pwrseq_alloc_generic to create
> an generic pwrseq instance.
> 
> Signed-off-by: Peter Chen <peter.chen@nxp.com>
> Tested-by Joshua Clayton <stillcompiling@gmail.com>

Reviewed-by: Matthias Kaehlcke <mka@chromium.org>
Tested-by: Matthias Kaehlcke <mka@chromium.org>

  reply	other threads:[~2016-08-09  0:25 UTC|newest]

Thread overview: 21+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-08-08  8:52 [PATCH v5 0/6] power: add power sequence library Peter Chen
2016-08-08  8:52 ` [PATCH v5 1/6] binding-doc: power: pwrseq-generic: add binding doc for generic " Peter Chen
2016-08-08  8:52 ` [PATCH v5 2/6] power: add " Peter Chen
2016-08-09  0:25   ` Matthias Kaehlcke [this message]
2016-08-08  8:52 ` [PATCH v5 3/6] binding-doc: usb: usb-device: add optional properties for power sequence Peter Chen
2016-08-08  8:52 ` [PATCH v5 4/6] usb: core: add power sequence handling for USB devices Peter Chen
2016-08-08  8:52 ` [PATCH v5 5/6] usb: chipidea: let chipidea core device of_node equal's glue layer device of_node Peter Chen
2016-08-10  0:15   ` Stephen Boyd
2016-08-10  3:11     ` Peter Chen
2016-08-10  9:00       ` Jun Li
2016-08-10  9:19         ` Peter Chen
2016-08-08  8:52 ` [PATCH v5 6/6] ARM: dts: imx6qdl-udoo.dtsi: fix onboard USB HUB property Peter Chen
2016-08-09 23:33   ` Joshua Clayton
2016-08-10  3:02     ` Peter Chen
2016-08-11 16:40       ` [PATCHES] ARM: dts: update udoo and evi hubs to use pwrseq Joshua Clayton
2016-08-11 16:40         ` [PATCH 1/3] ARM: dts: imx6qdl: Enable usb node children with <reg> Joshua Clayton
2016-08-11 16:40         ` [PATCH 2/3] ARM: dts: imx6qdl-udoo.dtsi: fix onboard USB HUB property Joshua Clayton
2016-08-11 16:40         ` [PATCH 3/3] ARM: dts: imx6q-evi: Fix onboard hub reset line Joshua Clayton
2016-08-12  3:11           ` Peter Chen
2016-08-12 15:20             ` Joshua Clayton
2016-08-12  3:09         ` [PATCHES] ARM: dts: update udoo and evi hubs to use pwrseq Peter Chen

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=20160809002501.GA125064@google.com \
    --to=mka@chromium.org \
    --cc=arnd@arndb.de \
    --cc=broonie@kernel.org \
    --cc=dbaryshkov@gmail.com \
    --cc=devicetree@vger.kernel.org \
    --cc=dwmw3@infradead.org \
    --cc=festevam@gmail.com \
    --cc=gregkh@linuxfoundation.org \
    --cc=k.kozlowski@samsung.com \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-kernel@vger.kernel.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=peter.chen@nxp.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).