Received: by 2002:a05:6a10:f3d0:0:0:0:0 with SMTP id a16csp4898775pxv; Tue, 29 Jun 2021 19:31:02 -0700 (PDT) X-Google-Smtp-Source: ABdhPJwNHUgoaa9m84p2qMvEP5eTSoe4WXqV05v+f8J32OTGvf86Qw+q9/nyNAtwPlWeyEo/EaQc X-Received: by 2002:a05:6638:3594:: with SMTP id v20mr6800284jal.25.1625020262776; Tue, 29 Jun 2021 19:31:02 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; t=1625020262; cv=none; d=google.com; s=arc-20160816; b=U/ZrQZ/jwNRI/StiBeq8cg4XkQuxOvyHkMV4px8fC8no5hWoz9ET9CuRMx7nckGKVk KXC0wzedFO44Y+u0DgVXCBbS0MKZP0btUckjcH836pNufRkXffFkJvJaCPaAA1rF9xHB /zVfPw9z6xEBM/s3MOMt29wedSVopfpr30O3Ho0fPbKry27/olBtDoERhDQ+SeYrEfRn hsmYONT6zvoH+UtRFPGQZRT9QHYpEv4ytaA9R2bU1wioyymZHFrBXu48Ewvb9rIgbtdg D8/XlKCsbtsdcsan/teqOKw+smX5BRt5pgzSe5MkFcXDnNCOv2sKniVHIqY2SE80EwbG ePOw== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:mime-version:user-agent:message-id:subject:cc:to :from:date; bh=PLDXzwiL3TSIzXJTf5slgn47g8p3wTyYmY9EZteFzn4=; b=VoQa9i6oeFBEwXvZJquXoyQIwd5NazBSIVu4XgHft3/mcvPwkZbgSEiotllIsYSWzD FiW/GZG0cVF2KAKDfR4ENsWELHKXKThyIS2vAY9FDWIAhzLlwIcd6AdJfCunDFCcj3EU zd7TU+sNlwwly5Rzp5mbUHTNEdZnFgYwcDAPUyC3giXK6HKjjsMRA0ooTLR8itq4cFHi TAbD4vBolmq6RmJON9LvZfEkq4Fk9BcZeXRCa8jddmW7rvYYdJziFllob26TwVq3cSDN LYOnhYleURO3rxT4v+QKyj8n4uFv5N4mUIszlHvkkP5GZ4g9WBaUiJDZg8XU7SvlH4Oz LjnA== ARC-Authentication-Results: i=1; mx.google.com; spf=pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 23.128.96.18 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org Return-Path: Received: from vger.kernel.org (vger.kernel.org. [23.128.96.18]) by mx.google.com with ESMTP id v22si21717910jap.98.2021.06.29.19.30.51; Tue, 29 Jun 2021 19:31:02 -0700 (PDT) Received-SPF: pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 23.128.96.18 as permitted sender) client-ip=23.128.96.18; Authentication-Results: mx.google.com; spf=pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 23.128.96.18 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S232067AbhF3CcM (ORCPT + 99 others); Tue, 29 Jun 2021 22:32:12 -0400 Received: from lindbergh.monkeyblade.net ([23.128.96.19]:35664 "EHLO lindbergh.monkeyblade.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S231938AbhF3CcL (ORCPT ); Tue, 29 Jun 2021 22:32:11 -0400 Received: from angie.orcam.me.uk (angie.orcam.me.uk [IPv6:2001:4190:8020::34]) by lindbergh.monkeyblade.net (Postfix) with ESMTP id 93F48C061760; Tue, 29 Jun 2021 19:29:43 -0700 (PDT) Received: by angie.orcam.me.uk (Postfix, from userid 500) id 348A892009C; Wed, 30 Jun 2021 04:29:40 +0200 (CEST) Received: from localhost (localhost [127.0.0.1]) by angie.orcam.me.uk (Postfix) with ESMTP id 2D5D292009B; Wed, 30 Jun 2021 04:29:40 +0200 (CEST) Date: Wed, 30 Jun 2021 04:29:40 +0200 (CEST) From: "Maciej W. Rozycki" To: Bjorn Helgaas , Thomas Gleixner , Ingo Molnar , Borislav Petkov , "H. Peter Anvin" cc: linux-pci@vger.kernel.org, linux-kernel@vger.kernel.org Subject: [PATCH v2] x86/PCI: Add support for the Intel 82378ZB/82379AB (SIO/SIO.A) PIRQ router Message-ID: User-Agent: Alpine 2.21 (DEB 202 2017-01-01) MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org The Intel 82378ZB System I/O (SIO) and 82379AB System I/O APIC (SIO.A) ISA bridges implement PCI interrupt steering with a PIRQ router[1][2] that is exactly the same as that of the PIIX and ICH southbridges (or actually the other way round, given that the SIO ASIC was there first). An earlier version of the SIO, the 82378IB[3][4], does not implement PCI interrupt steering however, so we need to exclude it by checking the low nibble of the PCI Revision Identification Register[5][6] for being at least 3. There is a note in the 82379AB specification update[7] saying that the device ID for that chip is 0x7, rather than 0x484 as stated in the datasheet[8]. It looks like a red herring however, for no report has been ever seen with that value quoted and it matches the documented default value of the PCI Command Register, which comes next after the PCI Device Identification Register, so it looks like a copy-&-paste editorial mistake. NB the 82378ZB has been commonly used with smaller DEC Alpha systems with the contents of the Revision Identification Register reported as one of 0x3, 0x43, or 0x84, so the masking of the high nibble seems indeed right by empirical observation. The value in the high nibble might be either random, or depend on the batch, or correspond to some other state such as reset straps. References: [1] "82378 System I/O (SIO)", Intel Corporation, Order Number: 290473-004, December 1994, Section 4.1.26 "PIRQ[3:0]#--PIRQ Route Control Registers" [2] "82378ZB System I/O (SIO) and 82379AB System I/O APIC (SIO.A)", Intel Corporation, Order Number: 290571-001, March 1996, Section 3.1.25. "PIRQ[3:0]#--PIRQ Route Control Registers", p. 48 [3] "82378IB System I/O (SIO)", Intel Corporation, Order Number: 290473-002, April 1993, Section 5.8.7.7 "Edge and Level Triggered Modes" [4] "82378IB to 82378ZB Errata Fix and Feature Enhancement Conversion FOL933002-01", [5] "82378 System I/O (SIO)", Intel Corporation, Order Number: 290473-004, December 1994, Section 4.1.5. "RID--Revision Identification Register" [6] "82378ZB System I/O (SIO) and 82379AB System I/O APIC (SIO.A)", Intel Corporation, Order Number: 290571-001, March 1996, Section 3.1.5. "RID--Revision Identification Register", p. 34 [7] "Intel 82379AB (SIO.A) System I/O Component Specification Update", Intel Corporation, Order Number: 297734-001, May, 1996, "Component Identification via Programming Interface", p. 5 [8] "82378ZB System I/O (SIO) and 82379AB System I/O APIC (SIO.A)", Intel Corporation, Order Number: 290571-001, March 1996, Section 3.1.2. "DID--Device Identification Register", p. 33 Signed-off-by: Maciej W. Rozycki --- Changes from v1: - Add [PATCH] annotation (umm...). - Fix RID values listed to include 0x84 rather than 0x83 (braino). --- arch/x86/pci/irq.c | 11 +++++++++-- 1 file changed, 9 insertions(+), 2 deletions(-) linux-x86-pirq-router-sio.diff Index: linux-macro-ide/arch/x86/pci/irq.c =================================================================== --- linux-macro-ide.orig/arch/x86/pci/irq.c +++ linux-macro-ide/arch/x86/pci/irq.c @@ -627,6 +627,13 @@ static __init int intel_router_probe(str return 0; switch (device) { + u8 rid; + case PCI_DEVICE_ID_INTEL_82378: + pci_read_config_byte(router, PCI_REVISION_ID, &rid); + /* Tell 82378IB (rev < 3) and 82378ZB/82379AB apart. */ + if ((rid & 0xfu) < 3) + break; + fallthrough; case PCI_DEVICE_ID_INTEL_82371FB_0: case PCI_DEVICE_ID_INTEL_82371SB_0: case PCI_DEVICE_ID_INTEL_82371AB_0: @@ -668,7 +675,7 @@ static __init int intel_router_probe(str case PCI_DEVICE_ID_INTEL_ICH10_3: case PCI_DEVICE_ID_INTEL_PATSBURG_LPC_0: case PCI_DEVICE_ID_INTEL_PATSBURG_LPC_1: - r->name = "PIIX/ICH"; + r->name = "SIO/PIIX/ICH"; r->get = pirq_piix_get; r->set = pirq_piix_set; return 1; @@ -682,7 +689,7 @@ static __init int intel_router_probe(str device <= PCI_DEVICE_ID_INTEL_DH89XXCC_LPC_MAX) || (device >= PCI_DEVICE_ID_INTEL_PANTHERPOINT_LPC_MIN && device <= PCI_DEVICE_ID_INTEL_PANTHERPOINT_LPC_MAX)) { - r->name = "PIIX/ICH"; + r->name = "SIO/PIIX/ICH"; r->get = pirq_piix_get; r->set = pirq_piix_set; return 1;