linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Ulf Hansson <ulf.hansson@linaro.org>
To: Peter Chen <peter.chen@nxp.com>
Cc: Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
	Alan Stern <stern@rowland.harvard.edu>,
	Mark Brown <broonie@kernel.org>,
	Sebastian Reichel <sre@kernel.org>,
	Rob Herring <robh+dt@kernel.org>, Shawn Guo <shawnguo@kernel.org>,
	"Rafael J. Wysocki" <rjw@rjwysocki.net>,
	Dmitry Eremin-Solenikov <dbaryshkov@gmail.com>,
	Heiko Stuebner <heiko@sntech.de>,
	"linux-arm-kernel@lists.infradead.org" 
	<linux-arm-kernel@lists.infradead.org>,
	Philipp Zabel <p.zabel@pengutronix.de>,
	"devicetree@vger.kernel.org" <devicetree@vger.kernel.org>,
	Pawel Moll <pawel.moll@arm.com>,
	Mark Rutland <mark.rutland@arm.com>,
	Linux USB List <linux-usb@vger.kernel.org>,
	Arnd Bergmann <arnd@arndb.de>,
	Sascha Hauer <s.hauer@pengutronix.de>,
	"Maciej S. Szmigiero" <mail@maciej.szmigiero.name>,
	troy.kisky@boundarydevices.com,
	Fabio Estevam <festevam@gmail.com>,
	oscar@naiandei.net, Stephen Boyd <stephen.boyd@linaro.org>,
	"linux-pm@vger.kernel.org" <linux-pm@vger.kernel.org>,
	Joshua Clayton <stillcompiling@gmail.com>,
	"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
	mka@chromium.org, Vaibhav Hiremath <vaibhav.hiremath@linaro.org>,
	Gary Bisson <gary.bisson@boundarydevices.com>,
	hverkuil@xs4all.nl, Krzysztof Kozlowski <krzk@kernel.org>,
	frank.li@nxp.com, jun.li@nxp.com
Subject: Re: [PATCH v15 2/7] power: add power sequence library
Date: Tue, 13 Jun 2017 12:24:42 +0200	[thread overview]
Message-ID: <CAPDyKFpOQWTPpdd__OBP1DcW58CbqnygGAOxiEFq5kqqvCm0QA@mail.gmail.com> (raw)
In-Reply-To: <1497319166-17287-3-git-send-email-peter.chen@nxp.com>

[...]

> +
> +/**
> + * of_pwrseq_on - Carry out power sequence on for device node
> + *
> + * @np: the device node would like to power on
> + *
> + * Carry out a single device power on.  If multiple devices
> + * need to be handled, use of_pwrseq_on_list() instead.
> + *
> + * Return a pointer to the power sequence instance on success,
> + * or an error code otherwise.
> + */
> +struct pwrseq *of_pwrseq_on(struct device_node *np)
> +{
> +       struct pwrseq *pwrseq;
> +       int ret;
> +
> +       pwrseq = pwrseq_find_available_instance(np);
> +       if (!pwrseq)
> +               return ERR_PTR(-ENOENT);

In case the pwrseq instance hasn't been registered yet, then there is
no way to deal with -EPROBE_DEFER properly here.

I haven't been following the discussions in-depth during all
iterations, so perhaps you have already discussed why doing it like
this.

Anyway, that means all pwrseq instances needs to be registered an
early boot level, to be safe. To me, that seems like poor design
choice.

[...]

Otherwise I think this looks okay to me.

Kind regards
Uffe

  reply	other threads:[~2017-06-13 10:24 UTC|newest]

Thread overview: 21+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-06-13  1:59 [PATCH v15 0/7] power: add power sequence library Peter Chen
2017-06-13  1:59 ` [PATCH v15 1/7] binding-doc: power: pwrseq-generic: add binding doc for generic " Peter Chen
2017-06-13  1:59 ` [PATCH v15 2/7] power: add " Peter Chen
2017-06-13 10:24   ` Ulf Hansson [this message]
2017-06-14  1:53     ` Peter Chen
2017-06-14  8:53       ` Ulf Hansson
2017-06-15  6:58         ` Peter Chen
2017-06-15  8:11           ` Ulf Hansson
2017-06-15  9:11             ` Peter Chen
2017-06-15  9:35               ` Ulf Hansson
2017-06-15 10:06                 ` Peter Chen
2017-06-19  0:59                   ` Peter Chen
2017-06-19  8:09                   ` Ulf Hansson
2017-06-19  9:02                     ` Peter Chen
2017-06-19  9:48                       ` Ulf Hansson
2017-06-20  2:37                         ` Peter Chen
2017-06-13  1:59 ` [PATCH v15 3/7] binding-doc: usb: usb-device: add optional properties for power sequence Peter Chen
2017-06-13  1:59 ` [PATCH v15 4/7] usb: core: add power sequence handling for USB devices Peter Chen
2017-06-13  1:59 ` [PATCH v15 5/7] ARM: dts: imx6qdl: Enable usb node children with <reg> Peter Chen
2017-06-13  1:59 ` [PATCH v15 6/7] ARM: dts: imx6qdl-udoo.dtsi: fix onboard USB HUB property Peter Chen
2017-06-13  1:59 ` [PATCH v15 7/7] ARM: dts: imx6q-evi: Fix onboard hub reset line 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=CAPDyKFpOQWTPpdd__OBP1DcW58CbqnygGAOxiEFq5kqqvCm0QA@mail.gmail.com \
    --to=ulf.hansson@linaro.org \
    --cc=arnd@arndb.de \
    --cc=broonie@kernel.org \
    --cc=dbaryshkov@gmail.com \
    --cc=devicetree@vger.kernel.org \
    --cc=festevam@gmail.com \
    --cc=frank.li@nxp.com \
    --cc=gary.bisson@boundarydevices.com \
    --cc=gregkh@linuxfoundation.org \
    --cc=heiko@sntech.de \
    --cc=hverkuil@xs4all.nl \
    --cc=jun.li@nxp.com \
    --cc=krzk@kernel.org \
    --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=mka@chromium.org \
    --cc=oscar@naiandei.net \
    --cc=p.zabel@pengutronix.de \
    --cc=pawel.moll@arm.com \
    --cc=peter.chen@nxp.com \
    --cc=rjw@rjwysocki.net \
    --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=vaibhav.hiremath@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).