devicetree.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Lee Jones <lee.jones@linaro.org>
To: Stefan Agner <stefan@agner.ch>
Cc: mark.rutland@arm.com, devicetree@vger.kernel.org,
	pawel.moll@arm.com, max.oss.09@gmail.com, khilman@baylibre.com,
	ijc+devicetree@hellion.org.uk, lgirdwood@gmail.com,
	robh+dt@kernel.org, linux@armlinux.org.uk, b.galvani@gmail.com,
	broonie@kernel.org, marcel@ziswiler.com, galak@codeaurora.org,
	carlo@caione.org, linux-amlogic@lists.infradead.org,
	linux-kernel@vger.kernel.org,
	linux-arm-kernel@lists.infradead.org
Subject: Re: [PATCH v2 4/5] mfd: rn5t618: register power off callback optionally
Date: Mon, 20 Jun 2016 10:00:46 +0100	[thread overview]
Message-ID: <20160620090046.GC1465@dell> (raw)
In-Reply-To: <876c6fc0a1e300e95eda616c8c71a3ec@agner.ch>

On Sat, 18 Jun 2016, Stefan Agner wrote:

> On 2016-06-16 07:59, Lee Jones wrote:
> > On Tue, 07 Jun 2016, Stefan Agner wrote:
> > 
> >> Only register power off if the PMIC is defined as system power
> >> controller (see Documentation/devicetree/bindings/power/
> >> power-controller.txt).
> >>
> >> Reviewed-by: Marcel Ziswiler <marcel.ziswiler@toradex.com>
> >> Signed-off-by: Stefan Agner <stefan@agner.ch>
> > 
> > These should be chronological.
> > 
> 
> Has been discussed already here:
> http://lists.infradead.org/pipermail/linux-arm-kernel/2015-May/345835.html
> 
> It's an artifact of my development process, I keep the commits in my
> local branches without signed off lines and add them before sending out
> patches. So whenever I prepare a new revision, collected acks, sobs are
> chronological, but end up before my sob.
> 
> But since you are the second maintainer which has objection to that
> style I probably should change that...

It would make your life easier in the long run. :)

> >> ---
> >>  drivers/mfd/rn5t618.c | 10 +++++++---
> >>  1 file changed, 7 insertions(+), 3 deletions(-)
> >>
> >> diff --git a/drivers/mfd/rn5t618.c b/drivers/mfd/rn5t618.c
> >> index 7607ced..d9b4d40 100644
> >> --- a/drivers/mfd/rn5t618.c
> >> +++ b/drivers/mfd/rn5t618.c
> >> @@ -103,9 +103,13 @@ static int rn5t618_i2c_probe(struct i2c_client *i2c,
> >>  		return ret;
> >>  	}
> >>
> >> -	if (!pm_power_off) {
> >> -		rn5t618_pm_power_off = priv;
> >> -		pm_power_off = rn5t618_power_off;
> >> +	if (of_device_is_system_power_controller(i2c->dev.of_node)) {
> >> +		if (!pm_power_off) {
> >> +			rn5t618_pm_power_off = priv;
> >> +			pm_power_off = rn5t618_power_off;
> >> +		} else {
> >> +			dev_err(&i2c->dev, "Failed to set poweroff capability, already defined\n");
> > 
> > This is not an error.  Please use dev_warn() instead.
> > 
> 
> Hm, I agree... FWIW, I copied the code (and that message) from here,
> where dev_err is probably also not appropriate:
> drivers/regulator/act8865-regulator.c

Mark (Regulator maintainer) also accepts patches.

> > Also, is this message actually accurate?  Your commit message would
> > indicate that it's not.
> 
> Hm, maybe we should bail out with an error in that case since DT
> explicitly asks to be power controller... Is that what you mean?

I think I misunderstood the message.  To fix this I would reword it.

"Poweroff call-back already defined"

-- 
Lee Jones
Linaro STMicroelectronics Landing Team Lead
Linaro.org │ Open source software for ARM SoCs
Follow Linaro: Facebook | Twitter | Blog

_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel

  reply	other threads:[~2016-06-20  9:00 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-06-08  1:04 [PATCH v2 0/5] regulator: add Ricoh RN5T567 PMIC support Stefan Agner
2016-06-08  1:04 ` [PATCH v2 1/5] ARM: dts: meson: minix-neo-x8: define PMIC as power controller Stefan Agner
2016-06-08  1:04 ` [PATCH v2 2/5] mfd: add Ricoh RN5T567 PMIC support Stefan Agner
     [not found]   ` <20160608010429.19618-3-stefan-XLVq0VzYD2Y@public.gmane.org>
2016-06-08 20:22     ` Rob Herring
2016-06-08 21:47       ` Stefan Agner
2016-06-16 14:55   ` Lee Jones
2016-06-19  0:57     ` Stefan Agner
2016-06-08  1:04 ` [PATCH v2 3/5] regulator: rn5t618: add " Stefan Agner
2016-06-16 14:56   ` Lee Jones
2016-06-08  1:04 ` [PATCH v2 4/5] mfd: rn5t618: register power off callback optionally Stefan Agner
2016-06-16 14:59   ` Lee Jones
2016-06-19  1:08     ` Stefan Agner
2016-06-20  9:00       ` Lee Jones [this message]
2016-06-08  1:04 ` [PATCH v2 5/5] mfd: rn5t618: register restart handler Stefan Agner
2016-06-16 15:03   ` Lee Jones

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=20160620090046.GC1465@dell \
    --to=lee.jones@linaro.org \
    --cc=b.galvani@gmail.com \
    --cc=broonie@kernel.org \
    --cc=carlo@caione.org \
    --cc=devicetree@vger.kernel.org \
    --cc=galak@codeaurora.org \
    --cc=ijc+devicetree@hellion.org.uk \
    --cc=khilman@baylibre.com \
    --cc=lgirdwood@gmail.com \
    --cc=linux-amlogic@lists.infradead.org \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux@armlinux.org.uk \
    --cc=marcel@ziswiler.com \
    --cc=mark.rutland@arm.com \
    --cc=max.oss.09@gmail.com \
    --cc=pawel.moll@arm.com \
    --cc=robh+dt@kernel.org \
    --cc=stefan@agner.ch \
    /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).