From: Sebastian Reichel <sre@kernel.org>
To: Liam Breck <liam@networkimprov.net>
Cc: "Andrew F. Davis" <afd@ti.com>,
linux-pm@vger.kernel.org,
Matt Ranostay <matt@ranostay.consulting>,
Liam Breck <kernel@networkimprov.net>
Subject: Re: [PATCH v11 07/10] power: bq27xxx_battery: Keep track of specific chip id
Date: Thu, 23 Mar 2017 13:30:54 +0100 [thread overview]
Message-ID: <20170323123054.jyngk44mea435cal@earth> (raw)
In-Reply-To: <CAKvHMgQsuTNcGUXZL7qk_YZ+qcdcLJ1+1xPB0zP97DqiitHJXA@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 1032 bytes --]
Hi,
On Thu, Mar 23, 2017 at 03:35:33AM -0700, Liam Breck wrote:
> On Thu, Mar 23, 2017 at 3:28 AM, Sebastian Reichel <sre@kernel.org> wrote:
> > Hi,
> >
> > On Mon, Mar 20, 2017 at 02:43:32AM -0700, Liam Breck wrote:
> >> From: Liam Breck <kernel@networkimprov.net>
> >>
> >> Pass actual chip ID into _setup(), which translates it to a group ID,
> >> to allow support for all chips by the power_supply_battery_info code.
> >> There are no functional changes to the driver.
> >>
> >> Signed-off-by: Liam Breck <kernel@networkimprov.net>
> >
> > This is really ugly. If we need chip ID and group ID let's store
> > them in different variables. For example put the detailed chipid
> > into di->realchip and then do
>
> I tried this in a previous version, and Andrew rejected it as
> confusing to have two IDs. That was while you were away on business
> :-)
now we have two IDs in the same variable.
That definitely more confusing. We can name the second variable
group to reduce confusion.
-- Sebastian
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 833 bytes --]
next prev parent reply other threads:[~2017-03-23 12:31 UTC|newest]
Thread overview: 44+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-03-20 9:43 [PATCH v11 0/10] devicetree battery support and client bq27xxx_battery Liam Breck
2017-03-20 9:43 ` [PATCH v11 02/10] devicetree: property-units: Add uWh and uAh units Liam Breck
2017-05-01 15:06 ` Sebastian Reichel
[not found] ` <20170320094335.19224-1-liam-RYWXG+zxWwBdeoIcmNTgJF6hYfS7NtTn@public.gmane.org>
2017-03-20 9:43 ` [PATCH v11 01/10] devicetree: power: Add battery.txt Liam Breck
2017-03-24 15:55 ` Rob Herring
2017-03-24 21:11 ` Liam Breck
[not found] ` <20170320094335.19224-2-liam-RYWXG+zxWwBdeoIcmNTgJF6hYfS7NtTn@public.gmane.org>
2017-03-23 10:20 ` Sebastian Reichel
2017-03-23 10:30 ` Liam Breck
2017-03-23 12:18 ` Sebastian Reichel
2017-04-07 19:23 ` Liam Breck
[not found] ` <CAKvHMgTxRJXgfpDgqQ_+=ErFEZAh9CodjVn5ZOoCfqPqSZWetA-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2017-04-14 0:33 ` Sebastian Reichel
2017-05-01 15:09 ` Sebastian Reichel
2017-03-20 9:43 ` [PATCH v11 03/10] devicetree: power: bq27xxx: Add monitored-battery documentation Liam Breck
2017-05-01 15:10 ` Sebastian Reichel
2017-03-20 9:43 ` [PATCH v11 04/10] power: power_supply: Add power_supply_battery_info and API Liam Breck
2017-03-20 20:59 ` Liam Breck
2017-03-23 10:17 ` Sebastian Reichel
2017-03-25 23:19 ` Liam Breck
2017-03-29 13:50 ` Sebastian Reichel
2017-05-01 15:11 ` Sebastian Reichel
2017-03-20 9:43 ` [PATCH v11 05/10] power: bq27xxx_battery: Make error reporting consistent Liam Breck
2017-03-20 16:57 ` Andrew F. Davis
2017-03-20 17:59 ` Liam Breck
2017-03-23 10:11 ` Sebastian Reichel
2017-03-23 10:24 ` Liam Breck
2017-03-23 10:33 ` Sebastian Reichel
2017-03-23 12:49 ` Liam Breck
2017-03-20 9:43 ` [PATCH v11 06/10] power: bq27xxx_battery: Define access methods to write chip registers Liam Breck
2017-03-21 20:54 ` kbuild test robot
2017-03-22 19:56 ` Andrew F. Davis
2017-03-20 9:43 ` [PATCH v11 07/10] power: bq27xxx_battery: Keep track of specific chip id Liam Breck
2017-03-23 10:28 ` Sebastian Reichel
2017-03-23 10:35 ` Liam Breck
2017-03-23 12:30 ` Sebastian Reichel [this message]
2017-03-23 12:39 ` Liam Breck
2017-03-23 13:06 ` Sebastian Reichel
2017-03-23 14:49 ` Andrew F. Davis
2017-03-23 21:44 ` Liam Breck
2017-03-24 11:48 ` Andrew F. Davis
2017-03-24 12:20 ` Liam Breck
2017-03-20 9:43 ` [PATCH v11 08/10] power: bq27xxx_battery: Add power_supply_battery_info support Liam Breck
2017-03-20 9:43 ` [PATCH v11 09/10] power: bq27xxx_battery_i2c: Add I2C bulk read/write functions Liam Breck
2017-03-20 9:43 ` [PATCH v11 10/10] power: bq27xxx_battery: Remove duplicate register arrays Liam Breck
[not found] ` <CAKvHMgS9ajgE3ZpseSkT=BiW5yBL03s-8XNFeHE=V0gz7W7x3w@mail.gmail.com>
2017-03-21 8:58 ` Fwd: " Liam Breck
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=20170323123054.jyngk44mea435cal@earth \
--to=sre@kernel.org \
--cc=afd@ti.com \
--cc=kernel@networkimprov.net \
--cc=liam@networkimprov.net \
--cc=linux-pm@vger.kernel.org \
--cc=matt@ranostay.consulting \
/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