From: "Pali Rohár" <pali.rohar@gmail.com>
To: "Lars-Peter Clausen" <lars@metafoo.de>
Cc: Anton Vorontsov <cbouatmailru@gmail.com>,
David Woodhouse <dwmw2@infradead.org>,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH] power: bq27x00_battery: Export all battery registers via sysfs
Date: Tue, 26 Mar 2013 20:27:39 +0100 [thread overview]
Message-ID: <201303262027.39772@pali> (raw)
In-Reply-To: <50FBBE7D.7040102@metafoo.de>
[-- Attachment #1: Type: Text/Plain, Size: 940 bytes --]
On Sunday 20 January 2013 10:53:01 Lars-Peter Clausen wrote:
> On 01/19/2013 03:01 PM, Pali Rohár wrote:
> > bq27xxx batteries have a lot of properties, more than
> > power_supply interface. Some of them can be usefull for
> > userspace applications (like CI bit) but does not make
> > sense to add bq specified property to power_supply
> > interface. When bq27x00_battery is not loaded userspace
> > application (like i2cget) can use /dev/i2c-* interface for
> > raw access. But when kernel module is attached to i2c
> > device, userspace applications cannot access it via
> > /dev/i2c-*.
>
> You can still access it if you use the I2C_SLAVE_FORCE flag.
> This is a bit ugly, but I'd rather see an ugly hack in
> userspace than in kernel space.
>
What is I2C_SLAVE_FORCE flag doing? Isnt there some potential
hardware damage problems (like simultaneous access to i2c bus)?
--
Pali Rohár
pali.rohar@gmail.com
[-- Attachment #2: This is a digitally signed message part. --]
[-- Type: application/pgp-signature, Size: 198 bytes --]
next prev parent reply other threads:[~2013-03-26 19:27 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-01-19 14:01 [PATCH] power: bq27x00_battery: Export all battery registers via sysfs Pali Rohár
2013-01-19 18:20 ` [PATCH v2] " Pali Rohár
2013-01-20 2:00 ` [PATCH] " Anton Vorontsov
2013-01-20 9:53 ` Lars-Peter Clausen
2013-03-26 19:27 ` Pali Rohár [this message]
2013-03-26 19:52 ` Lars-Peter Clausen
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=201303262027.39772@pali \
--to=pali.rohar@gmail.com \
--cc=cbouatmailru@gmail.com \
--cc=dwmw2@infradead.org \
--cc=lars@metafoo.de \
--cc=linux-kernel@vger.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.