From: "Andrew F. Davis" <afd@ti.com>
To: Krzysztof Kozlowski <k.kozlowski@samsung.com>,
"Pallala, Ramakrishna" <ramakrishna.pallala@intel.com>
Cc: "linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
"linux-pm@vger.kernel.org" <linux-pm@vger.kernel.org>,
"devicetree@vger.kernel.org" <devicetree@vger.kernel.org>,
Sebastian Reichel <sre@kernel.org>,
"Tc, Jenny" <jenny.tc@intel.com>,
Andreas Dannenberg <dannenberg@ti.com>
Subject: Re: [PATCH] power: bq24261_charger: Add support for TI BQ24261 charger
Date: Thu, 10 Sep 2015 11:42:37 -0500 [thread overview]
Message-ID: <55F1B2FD.4020608@ti.com> (raw)
In-Reply-To: <55F0C522.6070705@samsung.com>
On 09/09/2015 06:47 PM, Krzysztof Kozlowski wrote:
>>>> +- ti,enable-user-write: boolean, if present driver will allow the user space
>>>> + to control the charging current and voltage through sysfs;
>>>
>>> This is not DT property. It does not describe hardware.
>> We needed a mechanism to enable the sysfs writes on certain properties.
>> If DT is not the place where should it go?
>
> DT is not the place. As I discussed later with Andreas, if you really
> need this and if mainline is a place for that then probably this should
> be compile option (a Kconfig symbol).
>
I think this would actually be a good use for module parameters, this way
it could still be set at boot without re-compiling.
I think compile-time disabling sysfs properties because they are "dangerous" is
a little bit too artificially restricting and controlling, you can set permissions
so only root can change them already. The kernel should not be restricting root,
I understand the fear of someone rooting a machine and remotely over charging
a LiPo[1], but these physical limits are hardware descriptions and can and should
be set by DT, beyond this root should have full control over their machine.
Besides root can already just unbind your driver and issue raw I2C commands to do
the same thing. </rant>
[1] http://i.imgur.com/vszJJ.jpg
Regards,
Andrew
next prev parent reply other threads:[~2015-09-10 16:42 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-09-06 17:23 [PATCH] power: bq24261_charger: Add support for TI BQ24261 charger Ramakrishna Pallala
2015-09-07 3:57 ` Krzysztof Kozlowski
2015-09-09 2:26 ` Andreas Dannenberg
2015-09-09 4:17 ` Krzysztof Kozlowski
2015-09-09 17:31 ` Andreas Dannenberg
2015-09-09 23:49 ` Krzysztof Kozlowski
2015-09-10 14:50 ` Laurentiu Palcu
2015-09-09 18:11 ` Pallala, Ramakrishna
2015-09-09 23:47 ` Krzysztof Kozlowski
2015-09-10 16:42 ` Andrew F. Davis [this message]
2015-09-11 0:58 ` Krzysztof Kozlowski
2015-09-22 15:37 ` Sebastian Reichel
2015-09-22 15:43 ` Pallala, Ramakrishna
[not found] ` <1441560187-23611-1-git-send-email-ramakrishna.pallala-ral2JQCrhuEAvxtiuMwx3w@public.gmane.org>
2015-09-09 3:01 ` Fabio Estevam
2015-09-09 22:27 ` Andreas Dannenberg
2015-10-19 17:34 ` Pallala, Ramakrishna
-- strict thread matches above, loose matches on Subject: below --
2015-09-09 22:47 Alexey Klimov
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=55F1B2FD.4020608@ti.com \
--to=afd@ti.com \
--cc=dannenberg@ti.com \
--cc=devicetree@vger.kernel.org \
--cc=jenny.tc@intel.com \
--cc=k.kozlowski@samsung.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pm@vger.kernel.org \
--cc=ramakrishna.pallala@intel.com \
--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;
as well as URLs for NNTP newsgroup(s).