From: Phil Reid <preid@electromag.com.au>
To: Nicola Saenz Julienne <nicolas.saenz@prodys.net>, sre@kernel.org
Cc: linux-kernel@vger.kernel.org, linux-pm@vger.kernel.org
Subject: Re: [PATCH 2/2] power: supply: add sbs-charger driver
Date: Wed, 23 Nov 2016 09:17:10 +0800 [thread overview]
Message-ID: <b84c933d-6186-a67b-c35f-486335e2ed28@electromag.com.au> (raw)
In-Reply-To: <d5340efc-b3b4-a247-ed85-b8f117294f40@electromag.com.au>
On 23/11/2016 09:06, Phil Reid wrote:
> G'day Nicola,
>
> On 22/11/2016 02:04, Nicola Saenz Julienne wrote:
>> This adds support for sbs-charger compilant chips as defined here:
>> http://sbs-forum.org/specs/sbc110.pdf
>>
>
> You may want to look at the series: power: supply: sbs-manager add driver.
> http://www.spinics.net/lists/linux-i2c/msg26383.html
>
> This is the same thing that Karl-Heinz and myself particpated on.
>
> We've had some trouble getting the device tree binding approved thou.
>
> In particular it handles multiple sbs-batteries thru an i2c mux.
>
> Have a look and let me know what you think. Sebastians comment on the irq thing looks interesting
> There does look to be some nice additional features in your driver.
>
> I've been distracted with other things but if you want to progress it I'm happy to help with testing etc.
>
> Dual battery support is a must for me thou.
>
Sorry Ignore all that.
Just realised its a different device. charger vs combined manager / charger.
--
Regards
Phil Reid
prev parent reply other threads:[~2016-11-23 1:17 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-11-21 18:04 [PATCH 0/2] power: supply: add sbs-charger driver Nicola Saenz Julienne
2016-11-21 18:04 ` [PATCH 1/2] power: supply: sbs-battery: use fixed device name Nicola Saenz Julienne
2016-11-22 15:23 ` Sebastian Reichel
2016-11-22 15:31 ` Nicolas Saenz Julienne
2016-11-22 16:17 ` Sebastian Reichel
2016-11-21 18:04 ` [PATCH 2/2] power: supply: add sbs-charger driver Nicola Saenz Julienne
2016-11-22 16:11 ` Sebastian Reichel
2016-11-23 1:06 ` Phil Reid
2016-11-23 1:17 ` Phil Reid [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=b84c933d-6186-a67b-c35f-486335e2ed28@electromag.com.au \
--to=preid@electromag.com.au \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pm@vger.kernel.org \
--cc=nicolas.saenz@prodys.net \
--cc=sre@kernel.org \
/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