All of lore.kernel.org
 help / color / mirror / Atom feed
From: Guenter Roeck <linux@roeck-us.net>
To: lm-sensors@vger.kernel.org
Subject: Re: [lm-sensors] [PATCH 0/3] First shot at a hwmon device name mapper
Date: Mon, 12 May 2014 01:50:12 +0000	[thread overview]
Message-ID: <537028D4.9070907@roeck-us.net> (raw)
In-Reply-To: <20140509100104.3dcdb46d@endymion.delvare>

On 05/09/2014 01:01 AM, Jean Delvare wrote:
> Hi all,
>
> As discussed lately on this list, here is a first shot at a helper
> binary that resolves libsensors chip names to kernel device names and
> back.
>
> This is really a proof of concept at this point. Everything can still
> be discussed and changed, just speak up if you see any problem or to
> ask for improvements. Specifically I have no preference for the tool's
> name or its command line interface, so if you can think of anything
> better, just let me know.
>

I tried with udev, but that doesn't work - if I understand corretly,
device rename support needs explicit kernel support per subsystem.
The networking subsystem does it with dev_change_name(). Other than that
there is device_rename(), which is hardly used.

So I guess we have no other choice than something like this, unless we go
radical and start using per-driver names (coretemp0 instead of hwmonX).
But I think even that would not be reboot-safe, for example on a system
with multiple sensors of the same type connected to different i2c busses.
Anyway, not sure if that would be a good idea to start with.

Guenter


_______________________________________________
lm-sensors mailing list
lm-sensors@lm-sensors.org
http://lists.lm-sensors.org/mailman/listinfo/lm-sensors

      reply	other threads:[~2014-05-12  1:50 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-05-09  8:01 [lm-sensors] [PATCH 0/3] First shot at a hwmon device name mapper Jean Delvare
2014-05-12  1:50 ` Guenter Roeck [this message]

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=537028D4.9070907@roeck-us.net \
    --to=linux@roeck-us.net \
    --cc=lm-sensors@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.