All of lore.kernel.org
 help / color / mirror / Atom feed
From: Stephen Warren <swarren@wwwdotorg.org>
To: Laxman Dewangan <ldewangan@nvidia.com>
Cc: akpm@linux-foundation.org, grant.likely@linaro.org,
	rob.herring@calxeda.com, rob@landley.net,
	devicetree@vger.kernel.org, linux-doc@vger.kernel.org,
	linux-kernel@vger.kernel.org, rtc-linux@googlegroups.com,
	gg@slimlogic.co.uk, kishon@ti.com,
	Stephen Warren <swarren@nvidia.com>,
	Pawel Moll <pawel.moll@arm.com>,
	Mark Rutland <Mark.Rutland@arm.com>,
	Ian Campbell <ian.campbell@citrix.com>
Subject: Re: [PATCH] drivers/rtc/rtc-palmas.c: support for backup battery charging
Date: Fri, 26 Jul 2013 09:40:15 -0600	[thread overview]
Message-ID: <51F2985F.60202@wwwdotorg.org> (raw)
In-Reply-To: <1374755343-32573-1-git-send-email-ldewangan@nvidia.com>

(CC'ing the new DT binding maintainers and mailing list on this reply,
hence quoting the whole of the DT binding)

On 07/25/2013 06:29 AM, Laxman Dewangan wrote:
> Palmas series device like TPS65913, TPS80036 supports the backup battery
> for powering the RTC when no other energy source is available.
> 
> The backup battery is optional, connected to the VBACKUP pin, and can be
> nonrechargeable or rechargeable. The rechargeable battery can be charged
> from the system supply using the backup battery charger.
> 
> Add support for enabling charging of this backup battery.  Also add the DT
> binding document and the new properties to have this support.
> 
> Signed-off-by: Laxman Dewangan <ldewangan@nvidia.com>
> ---
>  .../devicetree/bindings/rtc/rtc-palmas.txt         |   28 ++++++++++++++
>  drivers/rtc/rtc-palmas.c                           |   39 ++++++++++++++++++++
>  2 files changed, 67 insertions(+), 0 deletions(-)
>  create mode 100644 Documentation/devicetree/bindings/rtc/rtc-palmas.txt
> 
> diff --git a/Documentation/devicetree/bindings/rtc/rtc-palmas.txt b/Documentation/devicetree/bindings/rtc/rtc-palmas.txt
> new file mode 100644
> index 0000000..e4b6910
> --- /dev/null
> +++ b/Documentation/devicetree/bindings/rtc/rtc-palmas.txt
> @@ -0,0 +1,28 @@
> +Palmas RTC controller bindings
> +
> +Required properties:
> +- compatible:
> +  - "ti,palams-rtc" for palma series of the RTC controller
> +- interrupt-parent: Parent interrupt device, must be handle of palams node.
> +- interrupts: Interrupt number of RTC submodule on device.
> +
> +Optional properties:
> +- ti,back-bat-chg-enable: The palmas series device like TPS65913 or TPS80036
> +	supports the battery backup for powering the RTC when main battery is
> +	removed or in very low power state. This flag will enable the backup
> +	battery charging.
> +- ti,back-bat-chg-current: Configure charging current. Device supports the
> +	charging current as < 100mA or >100mA.

Does the HW support just two options; less-than or greater-than 100mA?
If so, a Boolean property here might be better. The code below certainly
implies this.

Given there's only 1 battery, I think "back-" is redundant in the
property names. Since that shortens the names a bit, I'd suggest
spelling everything out in full, perhaps:

battery-charge-enable
battery-charge-low-current

Both Boolean.

> +Example:
> +	palmas: tps65913@58 {
> +		:::::::::::

"..." is probably more common than lots of colons, or you could just
delete this line.

> +		palmas_rtc: rtc {
> +			compatible = "ti,palmas-rtc";
> +			interrupt-parent = <&palmas>;
> +			interrupts = <8 0>;
> +			ti,back-bat-chg-enable;
> +			ti,back-bat-chg-current = <100>;
> +		};
> +		:::::::::::
> +	};

> diff --git a/drivers/rtc/rtc-palmas.c b/drivers/rtc/rtc-palmas.c

> @@ -238,6 +238,19 @@ static int palmas_rtc_probe(struct platform_device *pdev)

> +		ret = of_property_read_u32(pdev->dev.of_node,
> +					"ti,back-bat-chg-current", &pval);
> +		if (!ret)
> +			bb_charging_current = pval;

Do you need to validate that pval is one of the legal values?

> @@ -254,6 +267,32 @@ static int palmas_rtc_probe(struct platform_device *pdev)
>  	palmas_rtc->dev = &pdev->dev;
>  	platform_set_drvdata(pdev, palmas_rtc);
>  
> +	if (enable_bb_charging) {
> +		unsigned reg = 0;
> +
> +		if (bb_charging_current < 100)
> +			reg |= PALMAS_BACKUP_BATTERY_CTRL_BBS_BBC_LOW_ICHRG;

This implies that a Boolean property would be a better representation of HW.

  reply	other threads:[~2013-07-26 15:40 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-07-25 12:29 [PATCH] drivers/rtc/rtc-palmas.c: support for backup battery charging Laxman Dewangan
2013-07-25 12:29 ` Laxman Dewangan
2013-07-26 15:40 ` Stephen Warren [this message]
2013-07-26 15:52   ` Mark Rutland
2013-07-26 16:35   ` Mark Brown
2013-07-26 16:42     ` Stephen Warren
2013-07-27  7:32       ` Laxman Dewangan
2013-07-26 20:45   ` Tomasz Figa
2013-07-27  7:38     ` Laxman Dewangan

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=51F2985F.60202@wwwdotorg.org \
    --to=swarren@wwwdotorg.org \
    --cc=Mark.Rutland@arm.com \
    --cc=akpm@linux-foundation.org \
    --cc=devicetree@vger.kernel.org \
    --cc=gg@slimlogic.co.uk \
    --cc=grant.likely@linaro.org \
    --cc=ian.campbell@citrix.com \
    --cc=kishon@ti.com \
    --cc=ldewangan@nvidia.com \
    --cc=linux-doc@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=pawel.moll@arm.com \
    --cc=rob.herring@calxeda.com \
    --cc=rob@landley.net \
    --cc=rtc-linux@googlegroups.com \
    --cc=swarren@nvidia.com \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.