mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Mark Rutland <mark.rutland@arm.com>
To: Matti Vaittinen <matti.vaittinen@nsn.com>
Cc: "a.zummo@towertech.it" <a.zummo@towertech.it>,
	"jason@lakedaemon.net" <jason@lakedaemon.net>,
	"linux@roeck-us.net" <linux@roeck-us.net>,
	"jic23@kernel.org" <jic23@kernel.org>,
	"arno@natisbad.org" <arno@natisbad.org>,
	"jgunthorpe@obsidianresearch.com"
	<jgunthorpe@obsidianresearch.com>,
	"san@rosetechnology.dk" <san@rosetechnology.dk>,
	"hs@denx.de" <hs@denx.de>,
	"devicetree@vger.kernel.org" <devicetree@vger.kernel.org>,
	"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
	"rtc-linux@googlegroups.com" <rtc-linux@googlegroups.com>,
	Sverdlin Alexander <alexander.sverdlin@nsn.com>
Subject: Re: [PATCH v2] rtc: ds1307: add trickle charger device tree binding
Date: Fri, 29 Aug 2014 11:49:04 +0100	[thread overview]
Message-ID: <20140829104904.GA21473@leverpostej> (raw)
In-Reply-To: <20140829112902.GA14650@fi-ourus-dhcp00977.emea.nsn-net.net>

Hi Mati,

Looks like my last reply [1] raced with this posting.

[...]

> +Optional properties:
> +- trickle : Used Trickle Charger configuration,
> +	corresponding to 4 lowest bits in trickle charger register.
> +	Following values are specified:
> +		0x5 => No diode, 250 ohm
> +		0x9 => Diode, 250 ohm
> +		0x6 => No diode, 2k ohm
> +		0xa => Diode, 2k ohm
> +		0x7 => No diode, 4k ohm
> +		0xb => Diode, 4k ohm

Optional?

For an optional property, please describe when said property should be
present, and what the absence implies.

Usually something like "should be present if $foo is not implemented in
$such_way", so it's obvious what the behaviour should be either way.

I still think this should be two proeprties and that the driver should
handle that as appropriate, as I mentioned in my last reply [1].

Mark.

[1] http://lkml.kernel.org/r/20140829104001.GB19424@leverpostej

      reply	other threads:[~2014-08-29 10:49 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-08-29 11:29 Matti Vaittinen
2014-08-29 10:49 ` Mark Rutland [this message]

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=20140829104904.GA21473@leverpostej \
    --to=mark.rutland@arm.com \
    --cc=a.zummo@towertech.it \
    --cc=alexander.sverdlin@nsn.com \
    --cc=arno@natisbad.org \
    --cc=devicetree@vger.kernel.org \
    --cc=hs@denx.de \
    --cc=jason@lakedaemon.net \
    --cc=jgunthorpe@obsidianresearch.com \
    --cc=jic23@kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux@roeck-us.net \
    --cc=matti.vaittinen@nsn.com \
    --cc=rtc-linux@googlegroups.com \
    --cc=san@rosetechnology.dk \
    /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

Powered by JetHome