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 90E57C433EF for ; Fri, 22 Jul 2022 22:28:09 +0000 (UTC) Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S236788AbiGVW2I (ORCPT ); Fri, 22 Jul 2022 18:28:08 -0400 Received: from lindbergh.monkeyblade.net ([23.128.96.19]:49650 "EHLO lindbergh.monkeyblade.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S234255AbiGVW2I (ORCPT ); Fri, 22 Jul 2022 18:28:08 -0400 Received: from angie.orcam.me.uk (angie.orcam.me.uk [IPv6:2001:4190:8020::34]) by lindbergh.monkeyblade.net (Postfix) with ESMTP id 26D109362E; Fri, 22 Jul 2022 15:28:07 -0700 (PDT) Received: by angie.orcam.me.uk (Postfix, from userid 500) id 0E55392009D; Sat, 23 Jul 2022 00:28:06 +0200 (CEST) Received: from localhost (localhost [127.0.0.1]) by angie.orcam.me.uk (Postfix) with ESMTP id 0992892009C; Fri, 22 Jul 2022 23:28:06 +0100 (BST) Date: Fri, 22 Jul 2022 23:28:05 +0100 (BST) From: "Maciej W. Rozycki" To: Rob Herring cc: Palmer Dabbelt , Bjorn Helgaas , Stafford Horne , "linux-kernel@vger.kernel.org" , Arnd Bergmann , Catalin Marinas , Will Deacon , Guo Ren , Paul Walmsley , Albert Ou , Richard Weinberger , Anton Ivanov , Johannes Berg , linux-arm-kernel , linux-csky@vger.kernel.org, linux-riscv , linux-um@lists.infradead.org, PCI , "open list:GENERIC INCLUDE/ASM HEADER FILES" Subject: Re: [PATCH v3 2/2] asm-generic: Add new pci.h and use it In-Reply-To: Message-ID: References: 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-csky@vger.kernel.org On Fri, 22 Jul 2022, Rob Herring wrote: > > > So again, how does one get a 0 address handed out when that's not even > > > a valid region according to DT? Is there some legacy stuff that > > > ignores the bridge windows? > > > > It doesn't matter as just sets it as a generic parameter for > > the platform, reflecting the limitation of PCI core, which in the course > > of the discussion referred was found rather infeasible to remove. The > > FU740 does not decode to PCI at 0, but another RISC-V device could. And I > > think that DT should faithfully describe hardware and not our software > > limitations. > > Let me ask this another way. When would a 0 memory or i/o address ever > work? It doesn't seem this s/w limitation has anything specific to > Risc-V. Given pci_iomap_range() rejects 0, I can't see how it could > ever work. Maybe only for legacy ISA? So should the generic defaults > just be what Risc-V is using instead of 0? Absolutely, cf.: . Maciej