[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <d42990af-78e4-e6c4-37ae-8043d27e565a@roeck-us.net>
Date: Tue, 7 Jan 2020 05:00:39 -0800
From: Guenter Roeck <linux@...ck-us.net>
To: "Martin K. Petersen" <martin.petersen@...cle.com>
Cc: linux-hwmon@...r.kernel.org, Jean Delvare <jdelvare@...e.com>,
Linus Walleij <linus.walleij@...aro.org>,
Bart Van Assche <bvanassche@....org>,
linux-doc@...r.kernel.org, linux-kernel@...r.kernel.org,
linux-scsi@...r.kernel.org, linux-ide@...r.kernel.org,
Chris Healy <cphealy@...il.com>
Subject: Re: [PATCH v2] hwmon: Driver for temperature sensors on SATA drives
On 1/6/20 8:10 PM, Martin K. Petersen wrote:
>
> Hi Guenter!
>
>>> - I still think sensor naming needs work. How and where are the
>>> "drivetemp-scsi-8-140" names generated?
>>>
>> Quick one: In libsensors, outside the kernel. The naming is generic,
>> along the line of <driver name>-<bus name>-<bus index>-<slot>.
>
> I understand that there are sensors that may not have an obvious
> associated topology and therefore necessitate coming up with a suitable
> naming or enumeration scheme. But in this case we already have a
> well-defined SCSI device name. Any particular reason you don't shift the
> chip.addr back and print the H:C:T:L format that you used as input?
>
> However arcane H:C:T:L may seem, I think that predictable naming would
> make things a lot easier for users that need to identify which device
> matches which sensor...
>
Not sure I understand. Do you mean to add "H:C:T:L" to "drivetemp" ?
That would make it something like "drivetemp:H:C:T:L-scsi-8-140".
Not sure if that is really useful, and it would at least be partially
redundant.
"scsi-8-140" is created by libsensors, so any change in that would
have to be made there, not in the kernel driver.
Guenter
Powered by blists - more mailing lists