From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from smtp.kernel.org (aws-us-west-2-korg-mail-1.web.codeaurora.org [10.30.226.201]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by smtp.subspace.kernel.org (Postfix) with ESMTPS id B0A21770E2 for ; Fri, 24 Jan 2025 16:31:45 +0000 (UTC) Authentication-Results: smtp.subspace.kernel.org; arc=none smtp.client-ip=10.30.226.201 ARC-Seal:i=1; a=rsa-sha256; d=subspace.kernel.org; s=arc-20240116; t=1737736305; cv=none; b=ghsl9IO5APJNxEtnkZ6Ub3gVOT7VaUXMCbC5F6q/WhNcuZ8S9HmVgvqFbDmxnVYJ+Z2qVqzGepXhf43lN2wFgTRw3Ihbguig8eXeXPKLho885BcZ5B+fzLjqsTXQvjF+60EWFaEn8fN+GvN3ydXyu67qY71aBukJyakRDt04u+8= ARC-Message-Signature:i=1; a=rsa-sha256; d=subspace.kernel.org; s=arc-20240116; t=1737736305; c=relaxed/simple; bh=EUyfHwb9lv3xB513S78TNVQ3Fp0DkOb+zWH8cEEAir4=; h=Date:From:To:Cc:Subject:Message-ID:References:MIME-Version: Content-Type:Content-Disposition:In-Reply-To; b=PSAmcpntZlGWywfkRPHHRdJCqkgOHa5N08l0vOhvCd/Vdygq8MYsr5wmI8HlPjKRyWgKcQVBMQ34kgNqELRGEN2MMOI1/cFHLrJvFB3t1K1+xnV83CyEZVXkYqoiN/gYOS8GTOT5yddjbpQL9a4/idErKChDxH3rfm9Q1U3mB1o= ARC-Authentication-Results:i=1; smtp.subspace.kernel.org; dkim=pass (2048-bit key) header.d=kernel.org header.i=@kernel.org header.b=nlwUv/aN; arc=none smtp.client-ip=10.30.226.201 Authentication-Results: smtp.subspace.kernel.org; dkim=pass (2048-bit key) header.d=kernel.org header.i=@kernel.org header.b="nlwUv/aN" Received: by smtp.kernel.org (Postfix) with ESMTPSA id B91C2C4CED2; Fri, 24 Jan 2025 16:31:44 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=kernel.org; s=k20201202; t=1737736305; bh=EUyfHwb9lv3xB513S78TNVQ3Fp0DkOb+zWH8cEEAir4=; h=Date:From:To:Cc:Subject:References:In-Reply-To:From; b=nlwUv/aNh00YxVmL4SCDAk5syOKEO/rLwityHKcDzBkd/8US91uM4/s3TaAxeCDKi 71PkIADg5j9GZ8m8HCA/tFMdQiH+k4B5rGKccoaN2gagZ7cO959LrzvPr4UU4fOAYO iSykBaXCw3KykLYVL52FPECKrEA5/ppaFUEvnKqPqB57m26Pz9kLakXCqDNGi02MAF ggyYGtfJQPqUErngvF+la1itsmPlcrQ3xuTZ9EgGMowq8t9BKaDZxiFIXtxLGuW+NP 6WF7q50DcAf+apRjg9ERGTzYIdxC9fylHLmYT8QXk45fUh7bidoLsVgxfHodNdQqX9 Zzikx0XezmM9A== Date: Fri, 24 Jan 2025 09:31:42 -0700 From: Keith Busch To: =?iso-8859-1?Q?Sa=FAl?= Valdelvira Cc: axboe@kernel.dk, hch@lst.de, sagi@grimberg.me, linux-nvme@lists.infradead.org, linux-kernel@vger.kernel.org Subject: Re: [PATCH] nvme-pci: Avoid the deepest sleep state on Wester Digital SSD Message-ID: References: <20250117164653.1751-1-saul@saulv.es> Precedence: bulk X-Mailing-List: linux-kernel@vger.kernel.org List-Id: List-Subscribe: List-Unsubscribe: MIME-Version: 1.0 Content-Type: text/plain; charset=iso-8859-1 Content-Disposition: inline Content-Transfer-Encoding: 8bit In-Reply-To: <20250117164653.1751-1-saul@saulv.es> On Fri, Jan 17, 2025 at 05:46:53PM +0100, Saśl Valdelvira wrote: > This [1] page from Dell's web mentions a firmware update for this SSD > with number 20240012 that seems to address the issue. > The problem is that, as far as i know, Western Digital doesn't offer > official firmware updates for Linux. At least, I haven't been able to > update it. We would definitely prefer the firmware solution. Quirking devices in the driver would force everyone to subscribe to the less aggressive power savings even if they're not affected. How do they offer their firmware update? I think it's common for vendors to provide some kind of bootable USB image that does the update if they don't provide a standalone firmware binary or other tooling.