From: Guenter Roeck <linux@roeck-us.net>
To: Vivien Didelot <vivien.didelot@savoirfairelinux.com>
Cc: netdev@vger.kernel.org, linux-kernel@vger.kernel.org,
"David S. Miller" <davem@davemloft.net>,
Florian Fainelli <f.fainelli@gmail.com>,
kernel@savoirfairelinux.com
Subject: Re: [PATCH 2/2] net: dsa: register hwmon for any provided function
Date: Thu, 16 Apr 2015 14:26:38 -0700 [thread overview]
Message-ID: <20150416212638.GB2587@roeck-us.net> (raw)
In-Reply-To: <1429209499-2447-2-git-send-email-vivien.didelot@savoirfairelinux.com>
On Thu, Apr 16, 2015 at 02:38:19PM -0400, Vivien Didelot wrote:
> A switch driver may only provide one of the temperature limit accessors,
> or the temperature alarm getter. So register the hwmon subsystem if any
> of the related functions is provided.
>
> Thus, check get_temp to set the visibility of temp1_input.
>
> Signed-off-by: Vivien Didelot <vivien.didelot@savoirfairelinux.com>
> ---
> net/dsa/dsa.c | 7 ++++++-
> 1 file changed, 6 insertions(+), 1 deletion(-)
>
> diff --git a/net/dsa/dsa.c b/net/dsa/dsa.c
> index 67d2983..6b68994 100644
> --- a/net/dsa/dsa.c
> +++ b/net/dsa/dsa.c
> @@ -157,6 +157,10 @@ static umode_t dsa_hwmon_attrs_visible(struct kobject *kobj,
> umode_t mode = 0;
>
> switch (index) {
> + case 0: /* temp1_input */
> + if (drv->get_temp)
> + mode |= S_IRUGO;
This should be mandatory. Sorry, I don't really understand what you are
trying to accomplish here.
Can you give me a real world example where a chip would support setting
a limit but not reading it ?
Thanks,
Guenter
> + break;
> case 1: /* temp1_max */
> if (drv->get_temp_limit)
> mode |= S_IRUGO;
> @@ -310,7 +314,8 @@ static int dsa_switch_setup_one(struct dsa_switch *ds, struct device *parent)
> * register with hardware monitoring subsystem.
> * Treat registration error as non-fatal and ignore it.
> */
> - if (drv->get_temp) {
> + if (drv->get_temp || drv->get_temp_limit || drv->set_temp_limit ||
> + drv->get_temp_alarm) {
> const char *netname = netdev_name(dst->master_netdev);
> char hname[IFNAMSIZ + 1];
> int i, j;
> --
> 2.3.5
>
next prev parent reply other threads:[~2015-04-16 21:27 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-04-16 18:38 [PATCH 1/2] net: dsa: use DEVICE_ATTR_RW to declare temp1_max Vivien Didelot
2015-04-16 18:38 ` [PATCH 2/2] net: dsa: register hwmon for any provided function Vivien Didelot
2015-04-16 21:26 ` Guenter Roeck [this message]
2015-04-16 22:05 ` Vivien Didelot
2015-04-17 2:17 ` Guenter Roeck
2015-04-17 14:45 ` Vivien Didelot
2015-04-16 18:55 ` [PATCH 1/2] net: dsa: use DEVICE_ATTR_RW to declare temp1_max Sergei Shtylyov
2015-04-16 19:13 ` Vivien Didelot
2015-04-16 21:24 ` 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=20150416212638.GB2587@roeck-us.net \
--to=linux@roeck-us.net \
--cc=davem@davemloft.net \
--cc=f.fainelli@gmail.com \
--cc=kernel@savoirfairelinux.com \
--cc=linux-kernel@vger.kernel.org \
--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