linux-kernel - Re: [PATCH v3 0/2] *** Remove UFS_DEVICE_QUIRK_DELAY_AFTER

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [day] [month] [year] [list]

Message-ID: <yq14irr6848.fsf@ca-mkp.ca.oracle.com>
Date: Tue, 21 Oct 2025 21:25:09 -0400
From: "Martin K. Petersen" <martin.petersen@...cle.com>
To: "Bao D. Nguyen" <quic_nguyenb@...cinc.com>
Cc: <quic_cang@...cinc.com>, <quic_nitirawa@...cinc.com>, <bvanassche@....org>,
        <avri.altman@....com>, <peter.wang@...iatek.com>,
        <adrian.hunter@...el.com>, <martin.petersen@...cle.com>,
        <linux-scsi@...r.kernel.org>,
        Matthias Brugger <matthias.bgg@...il.com>,
        AngeloGioacchino Del Regno <angelogioacchino.delregno@...labora.com>,
        "open list:ARM/Mediatek SoC support:Keyword:mediatek"
 <linux-kernel@...r.kernel.org>,
        "moderated list:ARM/Mediatek SoC
 support:Keyword:mediatek" <linux-arm-kernel@...ts.infradead.org>,
        "moderated list:ARM/Mediatek SoC support:Keyword:mediatek"
 <linux-mediatek@...ts.infradead.org>
Subject: Re: [PATCH v3 0/2] *** Remove UFS_DEVICE_QUIRK_DELAY_AFTER_LPM
 quirk ***


Bao,

> Multiple ufs device manufacturers request support for the
> UFS_DEVICE_QUIRK_DELAY_AFTER_LPM quirk in the Qualcomm's platform
> driver. After checking further with the major UFS manufacturers
> engineering teams such as Samsung, Kioxia, SK Hynix and Micron, all
> the manufacturers require this quirk. Since the quirk is needed by all
> the ufs device manufacturers, remove the quirk in the ufs core driver
> and implement a universal delay for all the ufs devices.
>
> In addition to verifying with the public device's datasheets, the ufs
> device manufacturer's engineering teams confirmed the required vcc
> power-off time for the devices is a minimum of 1ms before vcc can be
> powered on again. The existing 5ms delay implemented in the ufs core
> driver seems too conservative, so replace the hard coded 5ms delay
> with a variable default to 2ms setting to improve the system resume
> latency. The platform drivers can override this setting as needed.

Applied to 6.19/scsi-staging, thanks!

-- 
Martin K. Petersen