[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <20160919190242.wx2enmdqblbcvzqm@earth>
Date: Mon, 19 Sep 2016 21:02:45 +0200
From: Sebastian Reichel <sre@...nel.org>
To: Guenter Roeck <linux@...ck-us.net>
Cc: Dmitry Eremin-Solenikov <dbaryshkov@...il.com>,
David Woodhouse <dwmw2@...radead.org>,
linux-pm@...r.kernel.org, linux-kernel@...r.kernel.org,
Brian Norris <briannorris@...omium.org>
Subject: Re: [PATCH] sbs-battery: make writes to ManufacturerAccess optional
Hi,
On Thu, Sep 08, 2016 at 07:10:00PM -0700, Guenter Roeck wrote:
> According to the Smart Battery Data Specification, the use
> of ManufacturerAcess (register 0x0) is implementation-defined.
> It appears that some batteries use writes to this register
> in order to implement certain functionality, but others may
> simply NAK all writes to it. As a result, write failures to
> ManufacturerAccess should not be used as an indicator of
> battery presence, nor as a failure to enter sleep mode.
>
> The failed write access was seen with SANYO AP13J3K.
>
> Cc: Brian Norris <briannorris@...omium.org>
> Signed-off-by: Guenter Roeck <linux@...ck-us.net>
Thanks, queued.
-- Sebastian
Download attachment "signature.asc" of type "application/pgp-signature" (820 bytes)
Powered by blists - more mailing lists