From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: X-Spam-Checker-Version: SpamAssassin 3.4.0 (2014-02-07) on aws-us-west-2-korg-lkml-1.web.codeaurora.org X-Spam-Level: X-Spam-Status: No, score=-2.6 required=3.0 tests=DKIMWL_WL_HIGH,DKIM_SIGNED, DKIM_VALID,DKIM_VALID_AU,MAILING_LIST_MULTI,SPF_HELO_NONE,SPF_PASS, URIBL_BLOCKED,USER_AGENT_SANE_1 autolearn=no autolearn_force=no version=3.4.0 Received: from mail.kernel.org (mail.kernel.org [198.145.29.99]) by smtp.lore.kernel.org (Postfix) with ESMTP id F2EE5C41514 for ; Tue, 30 Jul 2019 21:33:59 +0000 (UTC) Received: from vger.kernel.org (vger.kernel.org [209.132.180.67]) by mail.kernel.org (Postfix) with ESMTP id B360E205C9 for ; Tue, 30 Jul 2019 21:33:59 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=kernel.org; s=default; t=1564522439; bh=PBEeq/uBUjX4+8wHRQuOVFEZ1PEDG4JdG/NfWEoqhSI=; h=Date:From:To:Cc:Subject:References:In-Reply-To:List-ID:From; b=VUopQXdcAz+GIQi1fndwptTrCRATGSLc1u0mzoZbErvvXt9YQBN639Dx55jue0E7S 2g8maz590Q9Ig0euqYwowXgvKDaNUgJMNnsaFEJUAfcTaHFb8a15CGZ440Hvh6qe03 gwDDEUoIvMzZWyN7/uEeUz26kP9sqHUJ9S+BYEzY= Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1728739AbfG3Vd6 (ORCPT ); Tue, 30 Jul 2019 17:33:58 -0400 Received: from mga01.intel.com ([192.55.52.88]:56890 "EHLO mga01.intel.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1726426AbfG3Vd6 (ORCPT ); Tue, 30 Jul 2019 17:33:58 -0400 X-Amp-Result: UNKNOWN X-Amp-Original-Verdict: FILE UNKNOWN X-Amp-File-Uploaded: False Received: from fmsmga001.fm.intel.com ([10.253.24.23]) by fmsmga101.fm.intel.com with ESMTP/TLS/DHE-RSA-AES256-GCM-SHA384; 30 Jul 2019 14:33:57 -0700 X-ExtLoop1: 1 X-IronPort-AV: E=Sophos;i="5.64,327,1559545200"; d="scan'208";a="191033426" Received: from unknown (HELO localhost.localdomain) ([10.232.112.69]) by fmsmga001.fm.intel.com with ESMTP; 30 Jul 2019 14:33:57 -0700 Date: Tue, 30 Jul 2019 15:31:14 -0600 From: Keith Busch To: Mario.Limonciello@dell.com Cc: kai.heng.feng@canonical.com, rjw@rjwysocki.net, keith.busch@intel.com, hch@lst.de, sagi@grimberg.me, linux-nvme@lists.infradead.org, linux-pm@vger.kernel.org, linux-kernel@vger.kernel.org, rajatja@google.com Subject: Re: [Regression] Commit "nvme/pci: Use host managed power state for suspend" has problems Message-ID: <20190730213114.GK13948@localhost.localdomain> References: <2332799.izEFUvJP67@kreacher> <4323ed84dd07474eab65699b4d007aaf@AUSX13MPC105.AMER.DELL.COM> <47415939.KV5G6iaeJG@kreacher> <20190730144134.GA12844@localhost.localdomain> <100ba4aff1c6434a81e47774ab4acddc@AUSX13MPC105.AMER.DELL.COM> <8246360B-F7D9-42EB-94FC-82995A769E28@canonical.com> <20190730191934.GD13948@localhost.localdomain> <7d3e0b8ba1444194a153c93faa1cabb3@AUSX13MPC105.AMER.DELL.COM> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <7d3e0b8ba1444194a153c93faa1cabb3@AUSX13MPC105.AMER.DELL.COM> User-Agent: Mutt/1.9.1 (2017-09-22) Sender: linux-kernel-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Tue, Jul 30, 2019 at 09:05:22PM +0000, Mario.Limonciello@dell.com wrote: > > -----Original Message----- > > From: Keith Busch > > Sent: Tuesday, July 30, 2019 2:20 PM > > To: Kai-Heng Feng > > Cc: Limonciello, Mario; rjw@rjwysocki.net; keith.busch@intel.com; hch@lst.de; > > sagi@grimberg.me; linux-nvme@lists.infradead.org; linux-pm@vger.kernel.org; > > linux-kernel@vger.kernel.org; rajatja@google.com > > Subject: Re: [Regression] Commit "nvme/pci: Use host managed power state for > > suspend" has problems > > > > > > [EXTERNAL EMAIL] > > > > On Wed, Jul 31, 2019 at 02:50:01AM +0800, Kai-Heng Feng wrote: > > > > > > Just did a quick test, this patch regress SK Hynix BC501, the SoC stays at > > > PC3 once the patch is applied. > > > > Okay, I'm afraid device/platform quirks may be required unless there are > > any other ideas out there. > > I think if a quirk goes in for Rafael's SSD it would have to be a quirk specific to this > device and FW version per the findings on KH checking the same device with the > older FW version. That's fine, we have the infrastructure in place for fw specific quirks. See drivers/nvme/host/core.c:nvme_core_quirk_entry