[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <d45b05fb-e98b-4df8-a33f-37ecdd23f67d@roeck-us.net>
Date: Mon, 3 Feb 2025 08:36:39 -0800
From: Guenter Roeck <linux@...ck-us.net>
To: Avri Altman <avri.altman@....com>,
"Martin K . Petersen" <martin.petersen@...cle.com>
Cc: linux-scsi@...r.kernel.org, linux-kernel@...r.kernel.org,
Bart Van Assche <bvanassche@....org>
Subject: Re: [PATCH 2/2] scsi: ufs: Add support for critical health
notification
On 2/3/25 07:27, Avri Altman wrote:
> The UFS 4.1 standard, released on January 8, 2025, introduces several
> new features, including a new exception event: HEALTH_CRITICAL. This
> event notifies the host of a device's critical health condition,
> indicating that the device is approaching the end of its lifetime based
> on the number of program/erase cycles performed.
>
> We utilize the hwmon (hardware monitoring) subsystem to propagate this
> information via the chip alarm channel.
>
That is outside the scope of the hardware monitoring subsystem,
the "alarms" attribute is deprecated and must not be used
in new drivers, and it isn't actually implemented by this code.
I can't control what is submitted into the ufs code, bu from hardware
monitoring perspective this is a NACK.
Guenter
Powered by blists - more mailing lists