devicetree.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Pavel Machek <pavel@ucw.cz>
To: Tony Lindgren <tony@atomide.com>
Cc: linux-omap@vger.kernel.org,
	"Benoît Cousson" <bcousson@baylibre.com>,
	devicetree@vger.kernel.org, "Merlijn Wajer" <merlijn@wizzup.org>
Subject: Re: [PATCH] ARM: dts: omap4-droid4: Enable hdq for droid4 ds250x 1-wire battery nvmem
Date: Tue, 21 Jan 2020 10:17:17 +0100	[thread overview]
Message-ID: <20200121091717.GB6934@amd> (raw)
In-Reply-To: <20200119195659.18273-1-tony@atomide.com>

[-- Attachment #1: Type: text/plain, Size: 889 bytes --]

On Sun 2020-01-19 11:56:59, Tony Lindgren wrote:
> With "[PATCHv3] w1: omap-hdq: Simplify driver with PM runtime autosuspend"
> we can read the droid4 battery information over 1-wire with this patch
> with something like:
> 
> # modprobe omap_hdq
> # hd /sys/bus/w1/devices/89-*/89-*/nvmem
> ...
> 
> Unfortunately the format of the battery data seems to be Motorola specific
> and is currently unusable for battery charger unless somebody figures out
> what it means.
> 
> Note that currently keeping omap_hdq module loaded will cause extra power
> consumption as it seems to scan devices periodically.
> 
> Cc: Merlijn Wajer <merlijn@wizzup.org>

Acked-by: Pavel Machek <pavel@ucw.cz>

Not for stable.
								Pavel
								
-- 
(english) http://www.livejournal.com/~pavelmachek
(cesky, pictures) http://atrey.karlin.mff.cuni.cz/~pavel/picture/horses/blog.html

[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 181 bytes --]

      reply	other threads:[~2020-01-21  9:17 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-01-19 19:56 [PATCH] ARM: dts: omap4-droid4: Enable hdq for droid4 ds250x 1-wire battery nvmem Tony Lindgren
2020-01-21  9:17 ` Pavel Machek [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=20200121091717.GB6934@amd \
    --to=pavel@ucw.cz \
    --cc=bcousson@baylibre.com \
    --cc=devicetree@vger.kernel.org \
    --cc=linux-omap@vger.kernel.org \
    --cc=merlijn@wizzup.org \
    --cc=tony@atomide.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 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).