Received: by 2002:a05:6a10:1d13:0:0:0:0 with SMTP id pp19csp698416pxb; Thu, 2 Sep 2021 12:56:22 -0700 (PDT) X-Google-Smtp-Source: ABdhPJxtBTTfupiBUhUTC2mDsgDdDFUYlJ8dWCL+ZOsLyTU4WiatrkNSHqrbOeND82iY1ss2udZS X-Received: by 2002:a17:907:76d8:: with SMTP id kf24mr5589447ejc.404.1630612581818; Thu, 02 Sep 2021 12:56:21 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; t=1630612581; cv=none; d=google.com; s=arc-20160816; b=qCvGlXGMJf6qd01pbJXoItEz+VALpKWzxySw3twl41F3ugJ4AsTCKj656IjshZ94AA /u/P/v780wlUvE/YuiL1DHzfoJgU1SxGgJNyFwMvneb/+Laeun1H+MB2MXh9Oz1KfL4u gXAYWCgPZK0nz8O913K2tvVOfGA/+t+dcVtsFWOpic6yaY6baqkz7QxlRQ7tScoZf5lm VghxBGJjq5wiwptSoyil3WqWNTfM7EorAg/pYC0ucCdaeTS51w+aGNcgIS7+FMY7JuaD bvsJDWCsqJDyFnaqfeFQOqCa/XpPH9AXW18iYEvWwok3Uq+GNY/vWa5Ivhiq7fY5XZBA CJdA== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:user-agent:in-reply-to:content-disposition :mime-version:references:message-id:subject:cc:to:from:date; bh=B6JB516kn/1vp9JCHWkFDTCIHqvvTnhvNuOdez+MPJE=; b=F/v4daCio2E7NjEpEa6ql1byLMV/a2qg+yIaE/R+1K+yPy5OqeLHb0HWv+sPzSJGuX W2fyKbALEbOw60ECBC2Ixh3H3asvWAfLaT3JW9k/DnfuJc7Z6zU1pcHRTQWlfrNyhCgz O5LBThMINdzyKZNc5xbDcYXdR0Q0LtAGGi7hkh38lzR/0maP8Gw5KjGJhEBK2RQuHERW N5UG9f/L4R6uelDYdirvSPRz2s7EKzHQFG6u5+pEWGoFZto+Zt76LK8v5NEYCc4/3pY5 xI6UftMmManEf1FnXIzu7LhKpdmTX0SRyYCyUi/XKeyr3eAn1H/8fa75Sg0bG8vlQ3XL FvRw== 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 q2si2936013eds.540.2021.09.02.12.55.58; Thu, 02 Sep 2021 12:56:21 -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 S244445AbhIBLJu (ORCPT + 99 others); Thu, 2 Sep 2021 07:09:50 -0400 Received: from elvis.franken.de ([193.175.24.41]:60887 "EHLO elvis.franken.de" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S230256AbhIBLJp (ORCPT ); Thu, 2 Sep 2021 07:09:45 -0400 Received: from uucp (helo=alpha) by elvis.franken.de with local-bsmtp (Exim 3.36 #1) id 1mLkaL-0002IW-00; Thu, 02 Sep 2021 13:08:45 +0200 Received: by alpha.franken.de (Postfix, from userid 1000) id C1C7CC09FF; Thu, 2 Sep 2021 13:08:04 +0200 (CEST) Date: Thu, 2 Sep 2021 13:08:04 +0200 From: Thomas Bogendoerfer To: Sergio Paracuellos Cc: bhelgaas@google.com, matthias.bgg@gmail.com, gregkh@linuxfoundation.org, linux-mips@vger.kernel.org, linux-pci@vger.kernel.org, linux-staging@lists.linux.dev, neil@brown.name, linux-kernel@vger.kernel.org Subject: Re: [PATCH v2 1/3] MIPS: ralink: don't define PC_IOBASE but increase IO_SPACE_LIMIT Message-ID: <20210902110804.GA7614@alpha.franken.de> References: <20210822161005.22467-1-sergio.paracuellos@gmail.com> <20210822161005.22467-2-sergio.paracuellos@gmail.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20210822161005.22467-2-sergio.paracuellos@gmail.com> User-Agent: Mutt/1.10.1 (2018-07-13) Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Sun, Aug 22, 2021 at 06:10:03PM +0200, Sergio Paracuellos wrote: > Defining PCI_IOBASE results in pci resource handling working but the > addresses generated for IO accesses are wrong since the ioremap in the pci core > function 'pci_parse_request_of_pci_ranges' tries to remap to a fixed virtual > address (PC_IOBASE) which can't work for KSEG1 addresses. To get it working this > way, we would need to put PCI_IOBASE somewhere into KSEG2 which will result in > creating TLB entries for IO addresses, which most of the time isn't needed on > MIPS because of access via KSEG1. So avoid to define PCI_IOBASE and increase > IO_SPACE_LIMIT resource for ralink MIPS platform instead, to get valid IO > addresses for resources from pci core 'pci_address_to_pio' function. > > Fixes: 222b27713d7f ("MIPS: ralink: Define PCI_IOBASE) > Signed-off-by: Sergio Paracuellos > --- > arch/mips/include/asm/mach-ralink/spaces.h | 4 +--- > 1 file changed, 1 insertion(+), 3 deletions(-) > > diff --git a/arch/mips/include/asm/mach-ralink/spaces.h b/arch/mips/include/asm/mach-ralink/spaces.h > index 87d085c9ad61..31a3525213cf 100644 > --- a/arch/mips/include/asm/mach-ralink/spaces.h > +++ b/arch/mips/include/asm/mach-ralink/spaces.h > @@ -2,9 +2,7 @@ > #ifndef __ASM_MACH_RALINK_SPACES_H_ > #define __ASM_MACH_RALINK_SPACES_H_ > > -#define PCI_IOBASE _AC(0xa0000000, UL) > -#define PCI_IOSIZE SZ_16M > -#define IO_SPACE_LIMIT (PCI_IOSIZE - 1) > +#define IO_SPACE_LIMIT 0x1fffffff > > #include > #endif > -- > 2.25.1 Acked-by: Thomas Bogendoerfer -- Crap can work. Given enough thrust pigs will fly, but it's not necessarily a good idea. [ RFC1925, 2.3 ]