From: Dmitry Torokhov <dmitry.torokhov@gmail.com>
To: Daniel Kurtz <djkurtz@chromium.org>
Cc: Mark Rutland <mark.rutland@arm.com>,
Ulf Hansson <ulf.hansson@linaro.org>,
Heiko Stuebner <heiko@sntech.de>,
linux-doc@vger.kernel.org, linus.walleij@linaro.org,
Douglas Anderson <dianders@chromium.org>,
Caesar Wang <caesar.wang@rock-chips.com>,
Russell King <linux@arm.linux.org.uk>,
"open list:ARM/Rockchip SoC..."
<linux-rockchip@lists.infradead.org>,
Grant Likely <grant.likely@linaro.org>,
Jack Dai <jack.dai@rock-chips.com>,
"open list:OPEN FIRMWARE AND..." <devicetree@vger.kernel.org>,
Pawel Moll <pawel.moll@arm.com>,
Ian Campbell <ijc+devicetree@hellion.org.uk>,
"jinkun.hong" <jinkun.hong@rock-chips.com>,
Rob Herring <robh+dt@kernel.org>,
"linux-arm-kernel@lists.infradead.org"
<linux-arm-kernel@lists.infradead.org>,
Randy Dunlap <rdunlap@infradead.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
ZhenFu Fang <fzf@rock-chips.com>, Kumar Gala <galak@>
Subject: Re: [PATCH v11 2/3] power-domain: rockchip: add power doamin driver
Date: Thu, 13 Nov 2014 12:20:02 -0800 (PST) [thread overview]
Message-ID: <2914846.96jvVdAmYN@dtor-glaptop> (raw)
In-Reply-To: <CAGS+omCxtvk7VNr7_tJkDCwZpbW-ocFm2VL4ngujxbS5remmVA@mail.gmail.com>
On Friday, November 14, 2014 03:35:44 AM Daniel Kurtz wrote:
> On Thu, Nov 13, 2014 at 6:01 AM, Caesar Wang <caesar.wang@rock-chips.com> wrote:
> > +
> > + error = -ENXIO;
> > +
> > + for_each_available_child_of_node(np, node) {
> > + error = rockchip_pm_add_one_domain(pmu, node);
> > + if (error) {
> > + dev_err(dev, "failed to handle node %s: %d\n",
> > + node->name, error);
> > + goto err_out;
> > + }
> > + }
> > +
> > + if (error) {
> > + dev_dbg(dev, "no power domains defined\n");
>
> Perhaps dev_err() or dev_warn(), to ensure this message is seen.
> But, not have defined power domains doesn't seem like a fatal error.
> Perhaps just return 0?
As far as the driver concerned it is a fatal error - the driver can't do
anything when no domain is defined.
Thanks.
--
Dmitry
next prev parent reply other threads:[~2014-11-13 20:20 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-11-12 22:01 [PATCH v11 0/3] ARM: rk3288: Add PM Domain support Caesar Wang
2014-11-12 22:01 ` [PATCH v11 1/3] dt-bindings: add document of Rockchip power domain Caesar Wang
2014-11-12 22:01 ` [PATCH v11 2/3] power-domain: rockchip: add power doamin driver Caesar Wang
2014-11-13 17:29 ` Doug Anderson
2014-11-13 19:35 ` Daniel Kurtz
2014-11-13 20:20 ` Dmitry Torokhov [this message]
2014-11-17 3:53 ` Caesar Wang
2014-11-14 2:57 ` Daniel Kurtz
2014-11-14 3:18 ` wxt
2014-11-12 22:01 ` [PATCH v11 3/3] ARM: dts: add rk3288 power-domain node Caesar Wang
2014-11-13 17:33 ` Doug Anderson
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=2914846.96jvVdAmYN@dtor-glaptop \
--to=dmitry.torokhov@gmail.com \
--cc=caesar.wang@rock-chips.com \
--cc=devicetree@vger.kernel.org \
--cc=dianders@chromium.org \
--cc=djkurtz@chromium.org \
--cc=fzf@rock-chips.com \
--cc=grant.likely@linaro.org \
--cc=heiko@sntech.de \
--cc=ijc+devicetree@hellion.org.uk \
--cc=jack.dai@rock-chips.com \
--cc=jinkun.hong@rock-chips.com \
--cc=linus.walleij@linaro.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-doc@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-rockchip@lists.infradead.org \
--cc=linux@arm.linux.org.uk \
--cc=mark.rutland@arm.com \
--cc=pawel.moll@arm.com \
--cc=rdunlap@infradead.org \
--cc=robh+dt@kernel.org \
--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