Received: by 2002:a6b:500f:0:0:0:0:0 with SMTP id e15csp964638iob; Wed, 4 May 2022 11:36:49 -0700 (PDT) X-Google-Smtp-Source: ABdhPJxrCwyPYTPPllk433/Y1opbtmTbwOn7e+ut9JN2Y8HPCe1sqUrFPfDhPH2Ycb/7AnUl045I X-Received: by 2002:a05:6402:40c5:b0:427:af77:c10c with SMTP id z5-20020a05640240c500b00427af77c10cmr22234145edb.387.1651689409647; Wed, 04 May 2022 11:36:49 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; t=1651689409; cv=none; d=google.com; s=arc-20160816; b=p5rZBms2+I31xC8lODa0k2M0P9lWfOEHDA9LasQi3XL96jPxhTiuhnuP1sUZKjNpue YnFaj+K+2COlDCsQqWeyXWHYgtCfgusKI9pxJcqYZwq/TKfckFMIx9mqfqWJnrp75p+z mQE5sZLOscqHHDID77VxCRbZ83iMKjw9J/22NMV/ISrViQPZMkEYyE3eeJ/y5UNJmMZs DrVhXmh97YJvN+YSrJqbFGoHD4ptg/1wGskGvxEbdD6RliOEq0m+B0NbW8BypvCPHGTq dJTquARsfdL20ezryF5kkDi3YZqUmwLvPrPDkzSoGd+KbLvO7GBg0K57i4Rb5mYF114G qYFQ== 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:references:message-id :in-reply-to:subject:cc:to:from:date; bh=U20XmpN/+dkOzT134eo1Jt8kDrJNW0UXrR1M9onnph8=; b=hfexQr6y/Z1jbUcF0BIUQLzNGYnC/QTlZlajnb2CLfr796X41wRMIP4uXt6NKRiBZC n7KKyrfUQawpAjtOJXqgJBeColHpLchjbfUnLe9inar52C2Qt5WfTPl5QjDwZpReKBQ1 G3YfQRz+fYDdCsKplbJ+DD1zO8PV/P4fF7PTTMn1OOF0PghgIibTqU5hWEEzqWD485KT yo395GR3mG1YWPQWoFjhmke2m53ytdEnfE95BGhz6Q4V9lcfSSVoI80UePU9iSXC3Yyn WDqR3mZ3btwMwUWnFHg0VIhG/SDesWpbkqhQMsLRdqEzPPCo651Z5PMyCskxzxXpi/ec hRfw== ARC-Authentication-Results: i=1; mx.google.com; spf=pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 2620:137:e000::1:20 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org Return-Path: Received: from out1.vger.email (out1.vger.email. [2620:137:e000::1:20]) by mx.google.com with ESMTP id ka16-20020a170907991000b006e89b5401casi17107283ejc.831.2022.05.04.11.36.03; Wed, 04 May 2022 11:36:49 -0700 (PDT) Received-SPF: pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 2620:137:e000::1:20 as permitted sender) client-ip=2620:137:e000::1:20; Authentication-Results: mx.google.com; spf=pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 2620:137:e000::1:20 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1349820AbiEDMmV (ORCPT + 99 others); Wed, 4 May 2022 08:42:21 -0400 Received: from lindbergh.monkeyblade.net ([23.128.96.19]:56466 "EHLO lindbergh.monkeyblade.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1349822AbiEDMmS (ORCPT ); Wed, 4 May 2022 08:42:18 -0400 Received: from angie.orcam.me.uk (angie.orcam.me.uk [78.133.224.34]) by lindbergh.monkeyblade.net (Postfix) with ESMTP id 4376233A3B; Wed, 4 May 2022 05:38:36 -0700 (PDT) Received: by angie.orcam.me.uk (Postfix, from userid 500) id 6A2FD92009C; Wed, 4 May 2022 14:38:35 +0200 (CEST) Received: from localhost (localhost [127.0.0.1]) by angie.orcam.me.uk (Postfix) with ESMTP id 5C9E092009B; Wed, 4 May 2022 13:38:35 +0100 (BST) Date: Wed, 4 May 2022 13:38:35 +0100 (BST) From: "Maciej W. Rozycki" To: Arnd Bergmann cc: Bjorn Helgaas , Niklas Schnelle , Arnd Bergmann , Greg Kroah-Hartman , Linux Kernel Mailing List , linux-arch , linux-pci , Dominik Brodowski Subject: Re: [RFC v2 25/39] pcmcia: add HAS_IOPORT dependencies In-Reply-To: Message-ID: References: <20220429135108.2781579-44-schnelle@linux.ibm.com> <20220503233802.GA420374@bhelgaas> User-Agent: Alpine 2.21 (DEB 202 2017-01-01) MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII X-Spam-Status: No, score=-1.9 required=5.0 tests=BAYES_00,SPF_HELO_NONE, SPF_NONE,T_SCC_BODY_TEXT_LINE autolearn=ham autolearn_force=no version=3.4.6 X-Spam-Checker-Version: SpamAssassin 3.4.6 (2021-04-09) on lindbergh.monkeyblade.net Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Wed, 4 May 2022, Arnd Bergmann wrote: > Almost all architectures that support CONFIG_PCI also provide > HAS_IOPORT today (at least at compile time, if not at runtime), > with s390 as a notable exception. Any machines that have legacy > PCI device support will also have I/O ports because a lot of > legacy PCI cards used it, and any machine with a pc-card slot > should also support legacy PCI devices. > > If we get new architectures without I/O space in the future, they > would certainly not care about supporting old cardbus devices. POWER9 is another architecture with no port I/O space[1]: Table 3-2. PCIe TLP command summary -----------+-----------------------------+------------------------------- Class | Type Name | Notes ===========+=============================+=============================== Completion | Completion without Data | For PCI CFG Writes (nonposted) | | or for error responses. Completion | Completion with Data | CI load responses. Nonposted | Configuration Read Request | Outbound only. Nonposted | Configuration Write Request | Outbound only. Posted | Message Request | Inbound only. Nonposted | Memory Read Request | Posted | Memory Write Request | ===========+=============================+=============================== 1. All other valid PCIe command types are ignored and dropped. 2. Invalid PCIe request command types will result in a completion response of Unsupported Request. ------------------------------------+------------------------------------ that we do support -- I have such a system. And I guess POWER10 is the same, as will be all future architecture updates. References: [1] "Power Systems Host Bridge 4 (PHB4) Specification", Version 1.0, International Business Machines Corporation, 27 July 2018, Section 3.1 "PHB4 Command Details", p.29 Maciej