From: pavel@ucw.cz (Pavel Machek)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH v2 2/2] power: bq27xxx_battery: add poll interval property query
Date: Wed, 2 Nov 2016 09:22:06 +0100 [thread overview]
Message-ID: <20161102082206.GE21488@amd> (raw)
In-Reply-To: <CAKzfze8Bom1XYRfiix_qYFckMggUD0eJm3Fz=GhNi6H_PBFyXA@mail.gmail.com>
Hi!
> >> >> Better then previous one.
> >> >>
> >> >> But my version of bq27xxx_battery.c already contains this:
> >> >
> >> > This is for allowing udev rule to set the properties as well.
> >> > otherwise a kinda crude RUN = " echo value >
> >> > /sys/module/bq27xxx_battery/parameters/poll_interval" is required.
> >>
> >> Any thoughts on this?
> >
> > I'd say echo value >
> > /sys/module/bq27xxx_battery/parameters/poll_interval .. is quite
> > adequate solution...?
> >
> > Alternatively, convince us that something else is useful for everyone,
> > and we can do the right thing (poll more often when battery is nearly
> > empty), automatically...
>
> Ok should have had the patchset set it per device, and not use the
> global poll_interval. Of need to add some logic to see if uses the
> global poll_interval or it's own setting.
>
> There are times where you could have multiple batteries connected to
> multiple fuel gauges, and want to up the polling interval on certain
> ones that are discharging at different rates.
>
> But of course I'll let you guys let me know if this seems useful at all.
I agree per-device polling would be cleaner.
But unless you have hardware with more than one bq27xxx, I'd avoid the
work...
Now... its also possible that poll_interval should change itself
(within kernel) to do the right thing.
Best regards,
Pavel
--
(english) http://www.livejournal.com/~pavelmachek
(cesky, pictures) http://atrey.karlin.mff.cuni.cz/~pavel/picture/horses/blog.html
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 181 bytes
Desc: Digital signature
URL: <http://lists.infradead.org/pipermail/linux-arm-kernel/attachments/20161102/5f5fae4c/attachment.sig>
next prev parent reply other threads:[~2016-11-02 8:22 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <1475092512-30555-1-git-send-email-matt@ranostay.consulting>
[not found] ` <1475092512-30555-3-git-send-email-matt@ranostay.consulting>
[not found] ` <CAKzfze9uvMvrF=gWph_HKFk_cH0qzRz6Wa2VJafK+H+wdnP0rg@mail.gmail.com>
2016-10-24 20:14 ` [PATCH v2 2/2] power: bq27xxx_battery: add poll interval property query Pavel Machek
2016-10-25 18:47 ` Matt Ranostay
2016-10-31 20:22 ` Matt Ranostay
2016-10-31 20:30 ` Pali Rohár
2016-10-31 21:38 ` Pavel Machek
2016-11-01 19:58 ` Matt Ranostay
2016-11-02 8:22 ` Pavel Machek [this message]
2016-11-04 5:00 ` Matt Ranostay
2016-11-04 7:09 ` Pavel Machek
2016-11-04 14:58 ` Tony Lindgren
2016-11-04 20:29 ` Pavel Machek
2016-11-04 20:39 ` Matt Ranostay
2016-11-04 21:43 ` Pavel Machek
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=20161102082206.GE21488@amd \
--to=pavel@ucw.cz \
--cc=linux-arm-kernel@lists.infradead.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;
as well as URLs for NNTP newsgroup(s).