Received: by 2002:a5b:505:0:0:0:0:0 with SMTP id o5csp6895222ybp; Wed, 16 Oct 2019 00:10:45 -0700 (PDT) X-Google-Smtp-Source: APXvYqyNCOzZfYWv3djIxYFaIfZ/LBMxVU6sO3As2adEEND6jvZg+5xob/PXgLNs+WyhE5YXx/tc X-Received: by 2002:a17:906:fad7:: with SMTP id lu23mr39329831ejb.211.1571209845309; Wed, 16 Oct 2019 00:10:45 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; t=1571209845; cv=none; d=google.com; s=arc-20160816; b=eP3Xw9d6SJwyxgRZ27gFqFFtbpVE9nuZlx4V2iX8tEwKLWjTLS1zccdMvLso2skv5K 3dn3zPri1H8wMKWnv/cIZDkcyn4Gog808EnXUH3iyb2ET7sJdJOqvDj/l6IJGwKe5QNG ZoHQRv8IpdKwBKEDkn8w/TCJKKsfyFG463EgsBKGds/MxkgtUHYAN/1WdYKSthpKEWbo KzXsgPdq3xrm6x4dcrP6XYvh5thjNhjQpnrlSwDScp/oOUn/F7c1vKlJgugMTGMMybxU BUteE5fPuygoeGI7lP+NNjimrxX0PDCDpwbgaAHoQyCBPp/yKQz69ILGsjAj7/bpSGHw hzWw== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:sender:cc:to:subject:message-id:date:from :in-reply-to:references:mime-version:dkim-signature; bh=FjTzov0ZWMBRnnkfLydTowwTTWaZQQMz8GLbYd2DoJY=; b=ICgyvxlVdv0vg2O20VblYso6y6v9bwYRqy1voWcOb6/BZ6nVQ26OR9sFVgrQ1wTAm1 L4hVNsOxpMk22mOxBB1dS3tbZaERHK0ULJpvS4Sa9P9RUNMaBFpOmcMvZlOHduvoDBOl Paq6c8fWhqx21f5F60dVAaO/8+T61kqCO4LoqjEDYOufimLcZs69mGpkDfy9+NMZKlIK fJ5C0sNp4H+7SO28/jb+9tlqG/o8JgnoznEwhWkaZp+YdEwYp6PRNI81PQ1up3ohHMrD bzdNFoDPVwhJ8ZZ+BCYnoTyepf0549RS7kLIIF8kMNF3bWkX6ZfLnc/6x9bqRLaLIWUC rnbA== ARC-Authentication-Results: i=1; mx.google.com; dkim=pass header.i=@intel-com.20150623.gappssmtp.com header.s=20150623 header.b=sseX6QWU; spf=pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org; dmarc=fail (p=NONE sp=NONE dis=NONE) header.from=intel.com Return-Path: Received: from vger.kernel.org (vger.kernel.org. [209.132.180.67]) by mx.google.com with ESMTP id k1si16562712ede.255.2019.10.16.00.10.21; Wed, 16 Oct 2019 00:10:45 -0700 (PDT) Received-SPF: pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) client-ip=209.132.180.67; Authentication-Results: mx.google.com; dkim=pass header.i=@intel-com.20150623.gappssmtp.com header.s=20150623 header.b=sseX6QWU; spf=pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org; dmarc=fail (p=NONE sp=NONE dis=NONE) header.from=intel.com Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1729024AbfJOV0n (ORCPT + 99 others); Tue, 15 Oct 2019 17:26:43 -0400 Received: from mail-oi1-f195.google.com ([209.85.167.195]:41227 "EHLO mail-oi1-f195.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1728653AbfJOV0m (ORCPT ); Tue, 15 Oct 2019 17:26:42 -0400 Received: by mail-oi1-f195.google.com with SMTP id w65so18162252oiw.8 for ; Tue, 15 Oct 2019 14:26:41 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=intel-com.20150623.gappssmtp.com; s=20150623; h=mime-version:references:in-reply-to:from:date:message-id:subject:to :cc; bh=FjTzov0ZWMBRnnkfLydTowwTTWaZQQMz8GLbYd2DoJY=; b=sseX6QWUP9CFA63813y5OMpaVx25163OITn2IzLP24ux6NTGMBFIsckkEKwagWvAJq 9yXBTSntSikoMBdORY8eLAPlVHulfEOthNtwXgw3Sxy1X0v3CvRKlAM22m0WLC13KAQp tg6hf/IYvnxhoNNhrcZUre5exfMwHVc6OOcnJDanCqFhPXEtxsOU7604QOyRVekBGf/Q 9oSMyaDTlrnjKheT8DHhUuWZEeR6Oy7YrH0suqKEP5N4kQAF/FgyjxnX/IZEYuMutYqA 9mlugtK7Tvhu+3kjPcR3vG4lbWby8JiJigfNzpb6QFeE7MNKOctL3kyENkpQV1UpzU3Z sZuQ== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to:cc; bh=FjTzov0ZWMBRnnkfLydTowwTTWaZQQMz8GLbYd2DoJY=; b=VOIvC47BXNmNwcuqeb0eGwlQayQdBvlBk7XM4Xb1DjGmHuQqth5kPvZZvXV7C3Z6Cl T6wQHcPQUIao0ztwQAi6DFHvsez8lOGuVOiBiT/0afKcbyQpXSPPwZZe8K1teGeUqK87 B67fL76Jb+SSTfLcoh1bG/YZv1VaQsnF6aUSUpcXvXjEOM+yorn8iwbWmjlaQ7AKz/HB 6RF5iCYt2IvvyJBcAAJPh0R982AiH5jTj1VXlB/V7OfyNYWAvsqaT1KCWIjL44Z4IaJ/ PCCBFAVROmzqyIpLy1fC/R2WTSefVd5v1PhIA82yPhhA892DtDoSs0/osCK/KmOD63/K S5FQ== X-Gm-Message-State: APjAAAVKMYJI28JjR7bU0N0oUBY6KW9xnagolRX+1Tsrn7+nYYw6ecpF oW5jvTZ8wvOshoWaecUQ/BU6QtZQNMrKNtsjD/oR3w== X-Received: by 2002:a05:6808:7cd:: with SMTP id f13mr551315oij.70.1571174801334; Tue, 15 Oct 2019 14:26:41 -0700 (PDT) MIME-Version: 1.0 References: <157116925749.1211205.12806062056189943042.stgit@dwillia2-desk3.amr.corp.intel.com> In-Reply-To: From: Dan Williams Date: Tue, 15 Oct 2019 14:26:29 -0700 Message-ID: Subject: Re: [PATCH] libata/ahci: Fix PCS quirk application To: Stephen Douthit Cc: "axboe@kernel.dk" , Andreas Friedrich , "stable@vger.kernel.org" , "linux-ide@vger.kernel.org" , "linux-kernel@vger.kernel.org" Content-Type: text/plain; charset="UTF-8" Sender: linux-kernel-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Tue, Oct 15, 2019 at 2:02 PM Stephen Douthit wrote: > > On 10/15/19 3:54 PM, Dan Williams wrote: > > Commit c312ef176399 "libata/ahci: Drop PCS quirk for Denverton and > > beyond" got the polarity wrong on the check for which board-ids should > > have the quirk applied. The board type board_ahci_pcs7 is defined at the > > end of the list such that "pcs7" boards can be special cased in the > > future if they need the quirk. All prior Intel board ids "< > > board_ahci_pcs7" should proceed with applying the quirk. > > > > Reported-by: Andreas Friedrich > > Reported-by: Stephen Douthit > > Fixes: c312ef176399 ("libata/ahci: Drop PCS quirk for Denverton and beyond") > > Cc: > > Signed-off-by: Dan Williams > > --- > > drivers/ata/ahci.c | 4 +++- > > 1 file changed, 3 insertions(+), 1 deletion(-) > > > > diff --git a/drivers/ata/ahci.c b/drivers/ata/ahci.c > > index dd92faf197d5..05c2b32dcc4d 100644 > > --- a/drivers/ata/ahci.c > > +++ b/drivers/ata/ahci.c > > @@ -1600,7 +1600,9 @@ static void ahci_intel_pcs_quirk(struct pci_dev *pdev, struct ahci_host_priv *hp > > */ > > if (!id || id->vendor != PCI_VENDOR_ID_INTEL) > > return; > > Unless I'm missing something this will short-circuit if there are any > older Intel controllers not explicitly listed with a PCI_VDEVICE entry > in ahci_pci_tbl. Those will match on: > > /* Generic, PCI class code for AHCI */ > { PCI_ANY_ID, PCI_ANY_ID, PCI_ANY_ID, PCI_ANY_ID, > PCI_CLASS_STORAGE_SATA_AHCI, 0xffffff, board_ahci }, You're not missing anything, but I think we should stick with explicit mapping as only newer controllers tend to match on class id rather than pci-id, and there's no way to know if that class-id match is for PCS_6 or PCS_7. Hopefully newer controllers are tested with Linux and the BIOS fixed prior to the breakage leaking into the wild.