Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]


Groups > linux.kernel > #1486776 > unrolled thread

Re: [PATCH] sbs-battery: make writes to ManufacturerAccess optional

Started bySebastian Reichel <sre@kernel.org>
First post2016-09-19 21:10 +0200
Last post2016-09-19 21:10 +0200
Articles 1 — 1 participant

Back to article view | Back to linux.kernel

This discussion starts older than the indexed window; earlier articles aren't shown. The article labeled Started by below is the oldest one visible, not the original post.


Contents

  Re: [PATCH] sbs-battery: make writes to ManufacturerAccess optional Sebastian Reichel <sre@kernel.org> - 2016-09-19 21:10 +0200

#1486776 — Re: [PATCH] sbs-battery: make writes to ManufacturerAccess optional

FromSebastian Reichel <sre@kernel.org>
Date2016-09-19 21:10 +0200
SubjectRe: [PATCH] sbs-battery: make writes to ManufacturerAccess optional
Message-ID<sjc70-Xi-25@gated-at.bofh.it>

[Multipart message — attachments visible in raw view] — view raw

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@chromium.org>
> Signed-off-by: Guenter Roeck <linux@roeck-us.net>

Thanks, queued.

-- Sebastian

[toc] | [standalone]


Back to top | Article view | linux.kernel


csiph-web