From: "Heiko Stübner" <heiko@sntech.de>
To: Anton Vorontsov <cbouatmailru@gmail.com>
Cc: Vasily Khoruzhick <anarsoul@gmail.com>,
David Woodhouse <dwmw2@infradead.org>,
linux-kernel@vger.kernel.org,
Linux PM mailing list <linux-pm@lists.linux-foundation.org>
Subject: Re: [PATCH] s3c-adc-battery: Add naive POWER_SUPPLY_PROP_PRESENT implementation
Date: Fri, 11 Nov 2011 16:18:56 +0100 [thread overview]
Message-ID: <201111111619.00388.heiko@sntech.de> (raw)
In-Reply-To: <20111110133052.GA31381@oksana.dev.rtsoft.ru>
Am Donnerstag, 10. November 2011, 14:30:52 schrieb Anton Vorontsov:
> On Thu, Nov 10, 2011 at 02:05:06PM +0300, Vasily Khoruzhick wrote:
> > On Thu, 2011-11-10 at 09:56 +0100, Heiko Stübner wrote:
> > > Userspace programs like upower seem to depend on the presence of the
> > > POWER_SUPPLY_PROP_PRESENT property.
> > >
> > > The real presence of the battery cannot be sensed and all other
> > > routines of s3c-adc-battery simply expect it to be present.
> > >
> > > Therefore we simply return 1, unless the battery struct is not present
> > > at all.
> >
> > Looks OK for me,
> >
> > > Signed-off-by: Heiko Stuebner <heiko@sntech.de>
> >
> > Acked-by: Vasily Khoruzhick <anarsoul@gmail.com>
>
> I disagree. If the driver behaves like the hardware does not support
> hot-pluggable cells, then present property is not necessary.
>
> Upowerd should look at the 'present' only if it is there; and if it
> is not, cells assumed to be always present.
[..]
> So, the problem is in upowerd, not this driver.
Thanks for your comment. I will therefore take this matter up with the upower-
guys.
Thanks
Heiko
prev parent reply other threads:[~2011-11-11 15:19 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-11-10 8:56 [PATCH] s3c-adc-battery: Add naive POWER_SUPPLY_PROP_PRESENT implementation Heiko Stübner
2011-11-10 11:05 ` Vasily Khoruzhick
2011-11-10 13:30 ` Anton Vorontsov
2011-11-11 15:18 ` Heiko Stübner [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=201111111619.00388.heiko@sntech.de \
--to=heiko@sntech.de \
--cc=anarsoul@gmail.com \
--cc=cbouatmailru@gmail.com \
--cc=dwmw2@infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pm@lists.linux-foundation.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