From: Guenter Roeck <linux@roeck-us.net>
To: Avi Shchislowski <avi.shchislowski@wdc.com>
Cc: Alim Akhtar <alim.akhtar@samsung.com>,
Avri Altman <avri.altman@wdc.com>,
"James E.J. Bottomley" <jejb@linux.ibm.com>,
"Martin K. Petersen" <martin.petersen@oracle.com>,
linux-kernel@vger.kernel.org, linux-scsi@vger.kernel.org
Subject: Re: [PATCH 0/5] scsi: ufs: ufs device as a temperature sensor
Date: Sun, 2 Feb 2020 11:21:05 -0800 [thread overview]
Message-ID: <20200202192105.GA20107@roeck-us.net> (raw)
In-Reply-To: <1580640419-6703-1-git-send-email-avi.shchislowski@wdc.com>
On Sun, Feb 02, 2020 at 12:46:54PM +0200, Avi Shchislowski wrote:
> UFS3.0 allows using the ufs device as a temperature sensor. The
> purpose of this feature is to provide notification to the host of the
> UFS device case temperature. It allows reading of a rough estimate
> (+-10 degrees centigrade) of the current case temperature, And
> setting a lower and upper temperature bounds, in which the device
> will trigger an applicable exception event.
>
> We added the capability of responding to such notifications, while
> notifying the kernel's thermal core, which further exposes the thermal
> zone attributes to user space. UFS temperature attributes are all
> read-only, so only thermal read ops (.get_xxx) can be implemented.
>
Can you add an explanation why this can't be added to the just-introduced
'drivetemp' driver in the hwmon subsystem, and why it make sense to
have proprietary attributes for temperature and temperature limits ?
Thanks,
Guenter
> Avi Shchislowski (5):
> scsi: ufs: Add ufs thermal support
> scsi: ufs: export ufshcd_enable_ee
> scsi: ufs: enable thermal exception event
> scsi: ufs-thermal: implement thermal file ops
> scsi: ufs: temperature atrributes add to ufs_sysfs
attributes
next prev parent reply other threads:[~2020-02-02 19:21 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-02-02 10:46 Avi Shchislowski
2020-02-02 10:46 ` [PATCH 1/5] scsi: ufs: Add ufs thermal support Avi Shchislowski
2020-02-02 10:46 ` [PATCH 2/5] scsi: ufs: export ufshcd_enable_ee Avi Shchislowski
2020-02-02 10:46 ` [PATCH 3/5] scsi: ufs: enable thermal exception event Avi Shchislowski
2020-02-02 10:46 ` [PATCH 4/5] scsi: ufs-thermal: implement thermal file ops Avi Shchislowski
2020-02-02 10:46 ` [PATCH 5/5] scsi: ufs: temperature atrributes add to ufs_sysfs Avi Shchislowski
2020-02-02 19:21 ` Guenter Roeck [this message]
2020-02-03 11:57 ` [PATCH 0/5] scsi: ufs: ufs device as a temperature sensor Avi Shchislowski
2020-02-03 14:47 ` Guenter Roeck
2020-02-03 21:29 ` Avri Altman
2020-02-03 21:47 ` Guenter Roeck
2020-02-04 6:17 ` Avri Altman
2020-02-06 10:40 ` Avi Shchislowski
2020-02-06 11:39 ` Julian Calaby
2020-02-06 12:08 ` Avri Altman
2020-02-06 12:41 ` Julian Calaby
2020-02-06 13:40 ` Avri Altman
2020-02-06 15:49 ` Julian Calaby
2020-02-06 19:32 ` Avri Altman
2020-02-06 20:42 ` Guenter Roeck
2020-02-06 22:21 ` Avri Altman
2020-02-07 0:47 ` Julian Calaby
2020-02-03 8:51 ` [EXT] " Bean Huo (beanhuo)
-- strict thread matches above, loose matches on Subject: below --
2020-02-02 15:47 Avi Shchislowski
2020-02-02 7:41 Avi Shchislowski
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=20200202192105.GA20107@roeck-us.net \
--to=linux@roeck-us.net \
--cc=alim.akhtar@samsung.com \
--cc=avi.shchislowski@wdc.com \
--cc=avri.altman@wdc.com \
--cc=jejb@linux.ibm.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-scsi@vger.kernel.org \
--cc=martin.petersen@oracle.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
Powered by JetHome