From: jgunthorpe@obsidianresearch.com (Jason Gunthorpe)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH v2] PCI: mvebu - Support a bridge with no IO port window
Date: Thu, 17 Oct 2013 08:41:12 -0600 [thread overview]
Message-ID: <20131017144112.GA28343@obsidianresearch.com> (raw)
In-Reply-To: <20131017131031.GD22434@titan.lakedaemon.net>
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 <jgunthorpe@obsidianresearch.com>
> > 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
next prev parent reply other threads:[~2013-10-17 14:41 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-10-15 20:16 [PATCH v2] PCI: mvebu - Support a bridge with no IO port window Jason Gunthorpe
2013-10-17 13:10 ` Jason Cooper
2013-10-17 14:41 ` Jason Gunthorpe [this message]
2013-10-17 14:47 ` Jason Cooper
2013-10-31 9:13 ` Thomas Petazzoni
2013-10-31 16:48 ` Jason Gunthorpe
2013-10-31 17:10 ` Bjorn Helgaas
2013-10-31 23:32 ` Jason Gunthorpe
2013-11-01 2:44 ` Bjorn Helgaas
2013-11-01 5:28 ` Jason Gunthorpe
2013-11-01 13:50 ` Bjorn Helgaas
2013-11-01 16:56 ` Jason Gunthorpe
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20131017144112.GA28343@obsidianresearch.com \
--to=jgunthorpe@obsidianresearch.com \
--cc=linux-arm-kernel@lists.infradead.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).