linux-arm-kernel.lists.infradead.org archive mirror
 help / color / mirror / Atom feed
From: jgunthorpe@obsidianresearch.com (Jason Gunthorpe)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH v2] bus: mvebu-mbus: Fix optional pcie-mem/io-aperture properties
Date: Tue, 1 Oct 2013 11:22:59 -0600	[thread overview]
Message-ID: <20131001172259.GA19668@obsidianresearch.com> (raw)
In-Reply-To: <20131001170918.GF31178@titan.lakedaemon.net>

On Tue, Oct 01, 2013 at 01:09:18PM -0400, Jason Cooper wrote:
> Ok, I've moved it over the mvebu/fixes and amended the commit as
> follows:
> 
> """
>     bus: mvebu-mbus: Fix optional pcie-mem/io-aperture properties
>     
>     If the property was not specified then the returned resource had a
>     resource_size(..) == 1, rather than 0. The PCI-E driver checks for 0 so it
>     blindly continues on with a corrupted resource.
>     
>     The regression was introduced into v3.12 by:
>     
>       11be654 PCI: mvebu: Adapt to the new device tree layout
>     
> """

Reads fine to me, thanks
 
> > This patch is a necessary precondition to applying:
> > 
> > https://github.com/jgunthorpe/linux/commit/ef90b0bf7d8552dc7dfaad82d964446f6a9b6a3b
> > PCI: mvebu - Support a bridge with no IO port window
> 
> I don't see this one in my stack, have you submitted it yet?  When you
> do, please add a note mentioning the dependency on this commit in
> mvebu/fixes.

Yes, I posted it along with the other PCI patches:

http://permalink.gmane.org/gmane.linux.kernel.pci/25498

Just so we are on the same page, these are the Kirkwood/mvebu patches
I was hoping to progress for 3.13:

https://github.com/jgunthorpe/linux/commit/9f20eec4696627afe87bf0f6a204909004062e8e
PCI: mvebu: Dynamically detect if the PEX link is up to enable hot plug
(Thomas soft ack'd this @ http://www.spinics.net/lists/linux-pci/msg25323.html)

https://github.com/jgunthorpe/linux/commit/ef90b0bf7d8552dc7dfaad82d964446f6a9b6a3b
PCI: mvebu - Support a bridge with no IO port window
(no comments)

And these which I think you have already taken:

ARM: kirkwood - Remove kirkwood_setup_wins and rely on the DT binding
ARM: kirkwood: Move the crypto node under the mbus node 
ARM: kirkwood: Move the nand node under the mbus node 
bus: mvebu-mbus: Fix optional pcie-mem/io-aperture properties

Thanks,
Jason

  reply	other threads:[~2013-10-01 17:22 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-09-17 20:11 [PATCH v2] bus: mvebu-mbus: Fix optional pcie-mem/io-aperture properties Jason Gunthorpe
2013-10-01 16:44 ` Jason Cooper
2013-10-01 16:50   ` Jason Gunthorpe
2013-10-01 17:09     ` Jason Cooper
2013-10-01 17:22       ` Jason Gunthorpe [this message]
2013-10-01 17:28         ` Jason Cooper

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=20131001172259.GA19668@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).