[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <yq17e233o0o.fsf@oracle.com>
Date: Mon, 06 Jan 2020 23:10:15 -0500
From: "Martin K. Petersen" <martin.petersen@...cle.com>
To: Guenter Roeck <linux@...ck-us.net>
Cc: "Martin K. Petersen" <martin.petersen@...cle.com>,
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
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...
--
Martin K. Petersen Oracle Linux Engineering
Powered by blists - more mailing lists