[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <00697eef-0b36-1ff5-9c7a-43c1b53b52bc@nvidia.com>
Date: Tue, 20 Sep 2016 18:40:06 +0100
From: Jon Hunter <jonathanh@...dia.com>
To: Paul Kocialkowski <contact@...lk.fr>,
<linux-kernel@...r.kernel.org>
CC: <devicetree@...r.kernel.org>,
Stephen Warren <swarren@...dotorg.org>,
Thierry Reding <thierry.reding@...il.com>,
<linux-tegra@...r.kernel.org>,
Alexandre Courbot <gnurou@...il.com>,
<linux-arm-kernel@...ts.infradead.org>
Subject: Re: [PATCH 2/4] ARM: tegra: nyan: Use external control for bq24735
charger
On 28/08/16 18:32, Paul Kocialkowski wrote:
> Nyan boards come with an embedded controller that controls when to
> enable and disable the charge. Thus, it should not be left up to the
> kernel to handle that.
>
> Using the ti,external-control property allows specifying this use-case.
So the bq24735 is populated under the EC's 'i2c-tunnel' property which
is there to specifically interface it's child devices to the host. So I
am a bit confused why this is expose to the host if it should not be used?
Again you may right and I did find the original series [0] for this
which specifically references the Acer Chromebook that needs this.
However, I am not sure why this was never populated? Is there any other
history here?
What is the actual problem you see without making this change? The
original series states ...
"On Acer Chromebook 13 (CB5-311) this module fails to load if the
charger is not inserted, and will error when it is removed."
Cheers
Jon
[0] http://marc.info/?l=linux-pm&m=145447948705686&w=2
--
nvpublic
Powered by blists - more mailing lists