From: Guenter Roeck <linux@roeck-us.net>
To: Andrew Lunn <andrew@lunn.ch>
Cc: Vivien Didelot <vivien.didelot@savoirfairelinux.com>,
David Miller <davem@davemloft.net>,
netdev <netdev@vger.kernel.org>,
Florian Fainelli <f.fainelli@gmail.com>
Subject: Re: [PATCH net-next 0/2] Move hwmon support out of switch and into PHYs.
Date: Wed, 11 Jan 2017 10:00:18 -0800 [thread overview]
Message-ID: <20170111180018.GC22289@roeck-us.net> (raw)
In-Reply-To: <20170111173741.GB13033@lunn.ch>
On Wed, Jan 11, 2017 at 06:37:41PM +0100, Andrew Lunn wrote:
>
> However, at the moment, there is no code to enable interrupts for
> temperature alarms. I also don't see any need to add such code, since
> there is nowhere in HWMON to actively report such an alarm condition.
>
That is not entirely correct. It is not in the hwmon core, but that is
mostly because the sysfs attributes are managed in the hwmon drivers,
at least with the legacy API, and it is thus the responsibility of
hwmon drivers to implement interrupts and to alert user space.
It is on my task list to add a callback into the core, to support
generating udev and sysfs events with the new API, but so far I don't
see a need for it because no one requested it. This makes it kind
of a circular argument (not that the dsa hwmon driver supports the
new API anyway, but still).
Guenter
next prev parent reply other threads:[~2017-01-11 18:00 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-01-11 1:03 [PATCH net-next 0/2] Move hwmon support out of switch and into PHYs Andrew Lunn
2017-01-11 1:03 ` [PATCH net-next 1/2] phy: marvell: Add support for temperature sensor Andrew Lunn
2017-01-11 15:09 ` Andrew Lunn
2017-01-11 16:29 ` Sergei Shtylyov
2017-01-11 1:03 ` [PATCH net-next 2/2] net: dsa: Remove hwmon support Andrew Lunn
2017-01-11 17:06 ` [PATCH net-next 0/2] Move hwmon support out of switch and into PHYs Vivien Didelot
2017-01-11 17:37 ` Andrew Lunn
2017-01-11 17:55 ` Florian Fainelli
2017-01-11 19:19 ` Andrew Lunn
2017-01-11 18:00 ` Guenter Roeck [this message]
2017-01-11 19:16 ` Andrew Lunn
2017-01-11 20:00 ` 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=20170111180018.GC22289@roeck-us.net \
--to=linux@roeck-us.net \
--cc=andrew@lunn.ch \
--cc=davem@davemloft.net \
--cc=f.fainelli@gmail.com \
--cc=netdev@vger.kernel.org \
--cc=vivien.didelot@savoirfairelinux.com \
/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).