From: Trent Piepho <tpiepho@impinj.com>
To: "linux@roeck-us.net" <linux@roeck-us.net>,
"m.felsch@pengutronix.de" <m.felsch@pengutronix.de>
Cc: "dmitry.torokhov@gmail.com" <dmitry.torokhov@gmail.com>,
"linux-hwmon@vger.kernel.org" <linux-hwmon@vger.kernel.org>,
"jdelvare@suse.com" <jdelvare@suse.com>,
"kernel@pengutronix.de" <kernel@pengutronix.de>
Subject: Re: [PATCH v2 2/2] hwmon: add generic GPIO brownout support
Date: Tue, 30 Oct 2018 18:54:27 +0000 [thread overview]
Message-ID: <1540925667.30311.69.camel@impinj.com> (raw)
In-Reply-To: <20181030104706.dbuld7tymwcpayzd@pengutronix.de>
On Tue, 2018-10-30 at 11:47 +0100, Marco Felsch wrote:
>
> >
> > I disagree. That functionality is essential to the driver as submitted.
>
> You're right thats important for my use-case, but I got you, thats not a
> hwmon related problem. If I understood the device-model correctly there
> are absolut no problems to hot-unplug devices, this is always the case
> if we unbind a driver from user-space. So why we can't handle it
> directly in the kernel. Are there any concerns? If not can you give me
> some hints to get the logic at thr right place.
It is already common to have a userspace process that is signaled via
a hwmon alarm attribute. Is there a reason one couldn't have a
userspace process poll() on the alarm and unbind or remote devices via
sysfs when it goes off?
Seems like this might also give the opportunity to stop using the
device in a more controlled way, instead of having it just disappear.
next prev parent reply other threads:[~2018-10-30 18:54 UTC|newest]
Thread overview: 32+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-10-29 14:35 [PATCH v2 0/2] Add GPIO brownout detection support Marco Felsch
2018-10-29 14:35 ` [PATCH v2 1/2] dt-binding: hwmon: add gpio-brownout bindings Marco Felsch
2018-10-29 14:35 ` [PATCH v2 2/2] hwmon: add generic GPIO brownout support Marco Felsch
2018-10-29 19:52 ` Guenter Roeck
2018-10-29 21:16 ` Trent Piepho
2018-10-30 1:12 ` Guenter Roeck
2018-10-30 10:47 ` Marco Felsch
2018-10-30 13:13 ` Guenter Roeck
2018-10-30 17:00 ` Marco Felsch
2018-10-30 19:34 ` Trent Piepho
2018-10-30 20:11 ` Guenter Roeck
2018-11-01 10:40 ` Marco Felsch
2018-11-01 13:01 ` Guenter Roeck
2018-11-01 14:53 ` Marco Felsch
2018-11-01 15:14 ` Guenter Roeck
2018-11-01 18:21 ` Trent Piepho
2018-11-02 6:38 ` Marco Felsch
2018-11-02 23:05 ` Trent Piepho
2018-11-05 8:19 ` Marco Felsch
2018-11-06 20:50 ` Trent Piepho
2018-11-07 9:35 ` Marco Felsch
2018-11-07 18:07 ` Trent Piepho
2018-11-01 13:02 ` Guenter Roeck
2018-11-01 14:58 ` Marco Felsch
2018-11-01 15:08 ` Guenter Roeck
2018-11-01 17:41 ` Trent Piepho
2018-11-02 6:48 ` Marco Felsch
2018-10-30 19:56 ` Guenter Roeck
2018-11-01 9:44 ` Marco Felsch
2018-10-30 18:54 ` Trent Piepho [this message]
2018-10-30 18:49 ` Trent Piepho
2018-10-30 20:13 ` Guenter Roeck
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=1540925667.30311.69.camel@impinj.com \
--to=tpiepho@impinj.com \
--cc=dmitry.torokhov@gmail.com \
--cc=jdelvare@suse.com \
--cc=kernel@pengutronix.de \
--cc=linux-hwmon@vger.kernel.org \
--cc=linux@roeck-us.net \
--cc=m.felsch@pengutronix.de \
/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