mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Michael Mrozek <EvilDragon@openpandora.org>
To: "H. Nikolaus Schaller" <hns@goldelico.com>
Cc: kernel@pyra-handheld.com, Liam Breck <kernel@networkimprov.net>,
	Sebastian Reichel <sre@kernel.org>,
	Discussions about the Letux Kernel 
	<letux-kernel@openphoenux.org>,
	LKML <linux-kernel@vger.kernel.org>
Subject: Re: dt-bindings: power: supply: bq27xxx: Add monitored-battery documentation
Date: Tue, 29 Aug 2017 19:31:14 +0200	[thread overview]
Message-ID: <1504027874.1404.4.camel@openpandora.org> (raw)
In-Reply-To: <295D5DC5-7385-425B-847B-5AF9F93F85F7@goldelico.com>

Am Dienstag, den 29.08.2017, 15:33 +0200 schrieb H. Nikolaus Schaller:

Yes, they were just quick fixes for us, not to be used directly for
something else.

I just thought those might help finding the issue for you :)

> Hi,
> 
> > Am 29.08.2017 um 15:25 schrieb Michael Mrozek <EvilDragon@openpando
> > ra.org>:
> > 
> > The battery monitor has been fixed by notaz.
> > Find the commits here:
> > 
> > https://dev.pyra-handheld.com/notaz/pyra-kernel/commits/pyra-4.10 <
> > https://dev.pyra-handheld.com/notaz/pyra-kernel/commits/pyra-4.10>
> 
> yes, I have seen it.
> 
> Anyways the patches from Liam seem to work on 4.13-rc7 and are a much
> more general solution.
> I am just starting to test a little.
> 
> BR,
> Nikolaus
> 
> 
> > 
> > On August 29, 2017 11:43:43 AM GMT+02:00, "H. Nikolaus Schaller" <h
> > ns@goldelico.com> wrote:
> > Hi,
> > I am trying to get this working on our bq27421.
> > 
> > But the only message I get is:
> > 
> > [    6.086407] bq27xxx-battery 1-0055: data memory update not
> > supported for chip
> > 
> > A little research shows that this message comes from
> > 
> >  http://elixir.free-electrons.com/linux/v4.13-rc7/source/drivers/po
> > wer/supply/bq27xxx_battery.c#L1279 <http://elixir.free-electrons.co
> > m/linux/v4.13-
> > rc7/source/drivers/power/supply/bq27xxx_battery.c#L1279>
> > 
> > So di->dm_regs is NULL.
> > 
> > But doing an fgrep for dm_regs shows no line of code where the
> > pointer is set to a non-null value:
> > 
> > master hns$ fgrep -R dm_regs *
> > drivers/power/supply/bq27xxx_battery.c: .class = (di)-
> > >dm_regs[i].subclass_id, \
> > drivers/power/supply/bq27xxx_battery.c: .block = (di)-
> > >dm_regs[i].offset / BQ27XXX_DM_SZ, \
> > drivers/power/supply/bq27xxx_battery.c: struct bq27xxx_dm_reg *reg
> > = &di->dm_regs[reg_id];
> > drivers/power/supply/bq27xxx_battery.c: if (!di->dm_regs) {
> > drivers/power/supply/bq27xxx_battery.c: max = di-
> > >dm_regs[BQ27XXX_DM_DESIGN_ENERGY].max;
> > drivers/power/supply/bq27xxx_battery.c: max = di-
> > >dm_regs[BQ27XXX_DM_DESIGN_CAPACITY].max;
> > drivers/power/supply/bq27xxx_battery.c: min = di-
> > >dm_regs[BQ27XXX_DM_TERMINATE_VOLTAGE].min;
> > drivers/power/supply/bq27xxx_battery.c: max = di-
> > >dm_regs[BQ27XXX_DM_TERMINATE_VOLTAGE].max;
> > Binary file drivers/power/supply/bq27xxx_battery.ko matches
> > Binary file drivers/power/supply/bq27xxx_battery.o matches
> > Binary file drivers/power/supply/bq27xxx_battery_i2c.ko matches
> > Binary file drivers/power/supply/bq27xxx_battery_i2c.o matches
> > include/linux/power/bq27xxx_battery.h: struct bq27xxx_dm_reg
> > *dm_regs;
> > master hns$ 
> > 
> > What am I doing wrong here?
> > 
> > BR and thanks,
> > Nikolaus
> > 
> > 
> > Kernel mailing list
> > Kernel@pyra-handheld.com
> > http://pyra-handheld.com/cgi-bin/mailman/listinfo/kernel <http://py
> > ra-handheld.com/cgi-bin/mailman/listinfo/kernel>
> > 
> > -- 
> > Sent from my Android device with K-9 Mail. Please excuse my
> > brevity.
> 
> 
-- 
Mit freundlichen Grüßen,

Michael Mrozek

-----------------------
OpenPandora GmbH
Geschäftsführer: Michael Mrozek

Schäffbräustr. 11
85049 Ingolstadt
Deutschland
Tel.: 0841 / 990 5548
http://www.openpandora.de/
HRB 4879, Amtsgericht Ingolstadt
-----------------------
eMail: mrozek@openpandora.org

      parent reply	other threads:[~2017-08-29 17:31 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-08-29  9:43 H. Nikolaus Schaller
2017-08-29 10:40 ` Liam Breck
2017-08-29 14:24   ` H. Nikolaus Schaller
2017-08-29 18:18     ` Liam Breck
2017-08-29 19:50       ` H. Nikolaus Schaller
2017-08-29 20:05         ` Liam Breck
2017-08-29 20:09           ` H. Nikolaus Schaller
2017-09-10 20:50       ` Pavel Machek
     [not found] ` <0AB88D4C-1F05-4B4A-909E-7DBBD6FD0B13@openpandora.org>
     [not found]   ` <295D5DC5-7385-425B-847B-5AF9F93F85F7@goldelico.com>
2017-08-29 17:31     ` Michael Mrozek [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=1504027874.1404.4.camel@openpandora.org \
    --to=evildragon@openpandora.org \
    --cc=hns@goldelico.com \
    --cc=kernel@networkimprov.net \
    --cc=kernel@pyra-handheld.com \
    --cc=letux-kernel@openphoenux.org \
    --cc=linux-kernel@vger.kernel.org \
    --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

all inboxes | Powered by JetHome®