From: Jon Hunter <jonathanh-DDmLM1+adcrQT0dZR+AlfA@public.gmane.org>
To: Sebastian Reichel <sre-DgEjT+Ai2ygdnm+yROfE0A@public.gmane.org>,
Peter Rosin <peda-koto5C5qi+TLoDKTGw+V6w@public.gmane.org>,
linux-tegra-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
Cc: linux-pm-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
Subject: Re: bq24735 charger and ac-detect
Date: Wed, 14 Dec 2016 17:22:26 +0000 [thread overview]
Message-ID: <e053d0ca-53d0-d458-1b8c-0ecee0fa1f8b@nvidia.com> (raw)
In-Reply-To: <20161214145951.uuoijetzat2bxmbv@earth>
On 14/12/16 14:59, Sebastian Reichel wrote:
> * PGP Signed by an unknown key
>
> Hi,
>
> Ok, Darbha Sriharsha's mail address no longer works, so I Cc'd
> linux-tegra instead. Maybe some of the people there have the
> schematics for one of the Tegra boards using the bq24735 and/or
> could check if charger presence detection actually works on
> those boards with current mainline kernel.
I just gave this a quick test on my tegra124-nyan-big with v4.9 and I do
see the status for the bq24735 switching from "Charging" to "Not
charging" when plugging and unplugging the charger.
Please note for this board, the bq24735 is connected to the Google
chrome EC (embedded controller) and not directly to Tegra. If you look
at the device-tree source, tegra124-nyan.dtsi, you will see there is
this ec-i2c-tunnel that is exposing the device to the kernel.
Cheers
Jon
--
nvpublic
next prev parent reply other threads:[~2016-12-14 17:22 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <d796f6f9-1b6a-647c-100b-b3e85fc2f4c0@axentia.se>
[not found] ` <20161214142502.su4auesnlqmgxspv@earth>
2016-12-14 14:59 ` bq24735 charger and ac-detect Sebastian Reichel
2016-12-14 17:22 ` Jon Hunter [this message]
2016-12-14 17:54 ` Jon Hunter
2016-12-14 21:22 ` Peter Rosin
[not found] ` <84ede737-9e4c-b0ba-5a37-a96a7e86c3ec-koto5C5qi+TLoDKTGw+V6w@public.gmane.org>
2016-12-15 10:45 ` Jon Hunter
[not found] ` <21e09552-96b9-fb72-60be-7a4b9347b761-DDmLM1+adcrQT0dZR+AlfA@public.gmane.org>
2016-12-15 12:04 ` Peter Rosin
2016-12-15 14:04 ` Jon Hunter
[not found] ` <721122dd-dda8-1830-9224-40b5ed79e463-DDmLM1+adcrQT0dZR+AlfA@public.gmane.org>
2016-12-15 14:07 ` Jon Hunter
2016-12-15 15:34 ` Peter Rosin
[not found] ` <1316ab3d-8a75-6a03-e1d0-7dee55f2c90f-koto5C5qi+TLoDKTGw+V6w@public.gmane.org>
2016-12-15 16:10 ` Jon Hunter
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=e053d0ca-53d0-d458-1b8c-0ecee0fa1f8b@nvidia.com \
--to=jonathanh-ddmlm1+adcrqt0dzr+alfa@public.gmane.org \
--cc=linux-pm-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
--cc=linux-tegra-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
--cc=peda-koto5C5qi+TLoDKTGw+V6w@public.gmane.org \
--cc=sre-DgEjT+Ai2ygdnm+yROfE0A@public.gmane.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