From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from quartz.orcorp.ca ([184.70.90.242]:60024 "EHLO quartz.orcorp.ca" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1755478Ab3JQOlR (ORCPT ); Thu, 17 Oct 2013 10:41:17 -0400 Date: Thu, 17 Oct 2013 08:41:12 -0600 From: Jason Gunthorpe To: Jason Cooper Cc: Thomas Petazzoni , linux-arm-kernel@lists.infradead.org, linux-pci@vger.kernel.org, Ezequiel Garcia Subject: Re: [PATCH v2] PCI: mvebu - Support a bridge with no IO port window Message-ID: <20131017144112.GA28343@obsidianresearch.com> References: <1381868182-8544-1-git-send-email-jgunthorpe@obsidianresearch.com> <20131017131031.GD22434@titan.lakedaemon.net> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii In-Reply-To: <20131017131031.GD22434@titan.lakedaemon.net> Sender: linux-pci-owner@vger.kernel.org List-ID: On Thu, Oct 17, 2013 at 09:10:31AM -0400, Jason Cooper wrote: > On Tue, Oct 15, 2013 at 02:16:22PM -0600, Jason Gunthorpe wrote: > > Make pcie-io-aperture and the IO port MBUS ID in ranges optional. > > If not provided the bridge reports to Linux that IO space mapping is > > not supported and refuses to configure an IO mbus window. > > > > This allows both complete disable (do not specify pcie-io-aperture) and > > per-port disable (do not specify a IO target ranges entry for the port) > > > > Most PCIE devices these days do not require IO support to function, > > so having an option to disable it in the driver is useful. > > > > Signed-off-by: Jason Gunthorpe > > drivers/pci/host/pci-mvebu.c | 64 +++++++++++++++++++++++++++++--------------- > > 1 file changed, 43 insertions(+), 21 deletions(-) > > Applied to mvebu/drivers If possible, Thomas should test this, IMHO. My hardware here completely lacks IO port windows so I cannot meaningfully test that aspect of the change. Thanks, Jason