From: Pavel Machek <pavel@ucw.cz>
To: "Pali Rohár" <pali.rohar@gmail.com>
Cc: sre@kernel.org, kernel list <linux-kernel@vger.kernel.org>,
linux-arm-kernel <linux-arm-kernel@lists.infradead.org>,
linux-omap@vger.kernel.org, tony@atomide.com, khilman@kernel.org,
aaro.koskinen@iki.fi, ivo.g.dimitrov.75@gmail.com,
patrikbachan@gmail.com, serge@hallyn.com, abcloriens@gmail.com,
clayton@craftyguy.net, martijn@brixit.nl,
sakari.ailus@linux.intel.com
Subject: linux-next on Nokia N900: discharging on charger
Date: Thu, 7 Dec 2017 12:17:29 +0100 [thread overview]
Message-ID: <20171207111729.GA27036@amd> (raw)
In-Reply-To: <20171207101651.GA23691@amd>
[-- Attachment #1: Type: text/plain, Size: 1005 bytes --]
On Thu 2017-12-07 11:16:51, Pavel Machek wrote:
> On Sat 2017-12-02 12:19:54, Pali Rohár wrote:
> > On Saturday 02 December 2017 11:14:56 Pavel Machek wrote:
> > > Hi!
> > >
> > > next from 2017-12-01 was tested.
> > >
> > > MMC is detected, but then I see wtl4030_bci: .. battery temperature
> > > out of range, and machine halts. This is just before userspace would
> > > be started.
> > >
> > > 4.15-rc1 seems to work ok on the box.
> > >
> > > Any ideas?
> >
> > twl4030_bci is not available on Nokia N900, so we should not try to read
> > its registers.
>
> Today's git boots on N900; good. What is going on with twl4030_bci I
> don't have time to investigate at the moment.
Hmm. Today's next boots, but does not charge battery. Battery is less
than 80%, 3.94V, still status is fill and discharging at 600mA.
Pavel
--
(english) http://www.livejournal.com/~pavelmachek
(cesky, pictures) http://atrey.karlin.mff.cuni.cz/~pavel/picture/horses/blog.html
[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 181 bytes --]
prev parent reply other threads:[~2017-12-07 11:17 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-12-02 10:14 linux-next on Nokia N900: hang on boot Pavel Machek
2017-12-02 11:19 ` Pali Rohár
2017-12-07 10:16 ` Pavel Machek
2017-12-07 11:17 ` Pavel Machek [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=20171207111729.GA27036@amd \
--to=pavel@ucw.cz \
--cc=aaro.koskinen@iki.fi \
--cc=abcloriens@gmail.com \
--cc=clayton@craftyguy.net \
--cc=ivo.g.dimitrov.75@gmail.com \
--cc=khilman@kernel.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-omap@vger.kernel.org \
--cc=martijn@brixit.nl \
--cc=pali.rohar@gmail.com \
--cc=patrikbachan@gmail.com \
--cc=sakari.ailus@linux.intel.com \
--cc=serge@hallyn.com \
--cc=sre@kernel.org \
--cc=tony@atomide.com \
/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;
as well as URLs for NNTP newsgroup(s).