archive mirror
 help / color / mirror / Atom feed
From: "Pali Rohár" <>
Cc:, Sebastian Reichel <>,,
Subject: Re: BQ27xxx registers
Date: Tue, 20 Dec 2016 12:34:19 +0100	[thread overview]
Message-ID: <201612201234.19759@pali> (raw)
In-Reply-To: <>

[-- Attachment #1: Type: Text/Plain, Size: 458 bytes --]

On Tuesday 20 December 2016 07:00:41 Chris Lapa wrote:
> I can generate a patch to fix this issue, however the bigger problem
> exists as to which revision fuel gauge the bq27xxx_battery.c driver
> is intended to support for each family.

Hi! I think driver should support all revisions. There can be (and 
probably really is) hardware which uses old revision and such hardware 
should be still supported...

Pali Rohár

[-- Attachment #2: This is a digitally signed message part. --]
[-- Type: application/pgp-signature, Size: 198 bytes --]

  reply	other threads:[~2016-12-20 11:34 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-12-20  6:00 BQ27xxx registers Chris Lapa
2016-12-20 11:34 ` Pali Rohár [this message]
2016-12-21  2:49   ` Chris Lapa
2016-12-21 12:46     ` Pali Rohár
2016-12-21 13:19       ` Sebastian Reichel
2016-12-21 23:37       ` Chris Lapa
2017-01-16 17:43         ` Andrew F. Davis
2017-01-17  4:47           ` Chris Lapa

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:

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=201612201234.19759@pali \ \ \ \ \ \ \

* 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).