Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1751886AbdFGRkz (ORCPT ); Wed, 7 Jun 2017 13:40:55 -0400 Received: from mail-vk0-f66.google.com ([209.85.213.66]:35877 "EHLO mail-vk0-f66.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1751842AbdFGRkw (ORCPT ); Wed, 7 Jun 2017 13:40:52 -0400 MIME-Version: 1.0 X-Originating-IP: [209.133.79.7] In-Reply-To: References: <20170523004107.536-1-palmer@dabbelt.com> <20170606230007.19101-1-palmer@dabbelt.com> <20170606230007.19101-2-palmer@dabbelt.com> <20170607142558.GA21155@infradead.org> From: Olof Johansson Date: Wed, 7 Jun 2017 10:40:50 -0700 Message-ID: Subject: Re: [PATCH 01/17] drivers: support PCIe in RISCV To: Wesley Terpstra Cc: Christoph Hellwig , Palmer Dabbelt , patches@groups.riscv.org, linux-arch , albert@sifive.com, Arnd Bergmann , "linux-kernel@vger.kernel.org" Content-Type: text/plain; charset="UTF-8" Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 1730 Lines: 46 On Wed, Jun 7, 2017 at 10:09 AM, Wesley Terpstra wrote: > > > On Jun 7, 2017 7:26 AM, "Christoph Hellwig" wrote: > > On Tue, Jun 06, 2017 at 03:59:51PM -0700, Palmer Dabbelt wrote: >> From: "Wesley W. Terpstra" >> >> There are RISC-V systems that have been mapped to Xilinx FPGAs that have >> their PCIe controllers on chip. These build system changes allow RISC-V >> systems to enable the Xilinx PCIe controller, and to setup PCIe IRQs. >> >> Signed-off-by: Palmer Dabbelt >> --- >> drivers/pci/Makefile | 1 + >> drivers/pci/host/Kconfig | 2 +- >> 2 files changed, 2 insertions(+), 1 deletion(-) >> >> diff --git a/drivers/pci/Makefile b/drivers/pci/Makefile >> index 462c1f5f5546..a29d9ec05d13 100644 >> --- a/drivers/pci/Makefile >> +++ b/drivers/pci/Makefile >> @@ -41,6 +41,7 @@ obj-$(CONFIG_MIPS) += setup-irq.o >> obj-$(CONFIG_TILE) += setup-irq.o >> obj-$(CONFIG_SPARC_LEON) += setup-irq.o >> obj-$(CONFIG_M68K) += setup-irq.o >> +obj-$(CONFIG_RISCV) += setup-irq.o > > Can we do a cleanup here and add a ARCH_USE_GENERIC_PCI_SETUP Kconfig > symbol that all these architectures can select? > > > That would probably be better. I did not want to touch other arch/ folders > in our changes. I understand that approach when you're doing things in your tree early, but in this case (and at this phase in submission/merging), don't be afraid to touch other architectures and refactor/clean up. Please do the refactor in a separate preceding patch and submit it separate/soon instead of keeping it just in the series and bundled with your addition. That way it can go in when ready even if the rest of the series is spinning. -Olof