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 Received: from vger.kernel.org (vger.kernel.org [23.128.96.18]) by smtp.lore.kernel.org (Postfix) with ESMTP id 0B083C433F5 for ; Wed, 4 May 2022 14:07:34 +0000 (UTC) Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S237174AbiEDOLG (ORCPT ); Wed, 4 May 2022 10:11:06 -0400 Received: from lindbergh.monkeyblade.net ([23.128.96.19]:56600 "EHLO lindbergh.monkeyblade.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1344973AbiEDOLE (ORCPT ); Wed, 4 May 2022 10:11:04 -0400 Received: from dfw.source.kernel.org (dfw.source.kernel.org [IPv6:2604:1380:4641:c500::1]) by lindbergh.monkeyblade.net (Postfix) with ESMTPS id CDBB541338; Wed, 4 May 2022 07:07:28 -0700 (PDT) Received: from smtp.kernel.org (relay.kernel.org [52.25.139.140]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by dfw.source.kernel.org (Postfix) with ESMTPS id 6890461A35; Wed, 4 May 2022 14:07:28 +0000 (UTC) Received: by smtp.kernel.org (Postfix) with ESMTPSA id D14A1C385A4; Wed, 4 May 2022 14:07:27 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=kernel.org; s=k20201202; t=1651673247; bh=AOzP1mjGIKqKOsNlo9BHb/hKxiRMov98HMlUP91rW/0=; h=References:In-Reply-To:From:Date:Subject:To:Cc:From; b=QFkrSmgCkKXjqTPEq4kQlT0ktmBYcUZhWXaNTU/xLrJiMFoy3ekEvJ76ZybZitrbT NgRYx3J2l+pWcvJHZN58Q3tlp7gXbafjbBeGHoY88sZ8VKL1H1qA4bVMMgdf+AtkAF ZIGp2V58aIKQyKmpuIXfbUPMTDLkNzL+QfKxkr08XcEVMAT4VwdM73l8HAjN97MPcc 4oEzXkI7lCXLc4Vu4LNIBC9qQ+wxT7crzjS0TbrwArlun6Px6QbG0EoqNFoNWm59XO mB+Q7vkxkSyDoRSX40CorQVysexK45CIzoRJNlKvH1zObWQr0j4dX9eSoaNZVlspNq HOfc7g1HcUzyQ== Received: by mail-wr1-f43.google.com with SMTP id d5so2181986wrb.6; Wed, 04 May 2022 07:07:27 -0700 (PDT) X-Gm-Message-State: AOAM533lI/2iybd3pb0fmsY0ib2ml2cLZqRCy1nFu8hoFrgtSI6ZSn1B Vw63GiMgW8xJ4VOV7S5gz/mPbwsD88MKQGGI968= X-Google-Smtp-Source: ABdhPJyBvuzUVHauiOOhlgsX/356BcYJrvgYX24D9gTDq9FHSvu8LBFLLUOrs+/KZcEXVCs6uf2aemiYa3pCuILeHqY= X-Received: by 2002:a5d:49cb:0:b0:20a:cee3:54fc with SMTP id t11-20020a5d49cb000000b0020acee354fcmr16094949wrs.12.1651673246077; Wed, 04 May 2022 07:07:26 -0700 (PDT) MIME-Version: 1.0 References: <20220429135108.2781579-44-schnelle@linux.ibm.com> <20220503233802.GA420374@bhelgaas> In-Reply-To: From: Arnd Bergmann Date: Wed, 4 May 2022 16:07:09 +0200 X-Gmail-Original-Message-ID: Message-ID: Subject: Re: [RFC v2 25/39] pcmcia: add HAS_IOPORT dependencies To: "Maciej W. Rozycki" Cc: Bjorn Helgaas , Niklas Schnelle , Arnd Bergmann , Greg Kroah-Hartman , Linux Kernel Mailing List , linux-arch , linux-pci , Dominik Brodowski Content-Type: text/plain; charset="UTF-8" Precedence: bulk List-ID: X-Mailing-List: linux-pci@vger.kernel.org On Wed, May 4, 2022 at 2:38 PM Maciej W. Rozycki wrote: > > 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]: POWER9 is just an implementation of the power architecture that has a particular PCI host bridge. I would assume that arch/powerpc/ would continue to set HAS_IOPORT because it knows how to access I/O ports at compile-time. If a particular host bridge does not declare an I/O port range in its DT, then of course it won't be accessible, but that is different from architectures that have no concept of I/O ports. Arnd