From: Lorenzo Pieralisi <lorenzo.pieralisi@arm.com>
To: "Krzysztof Wilczyński" <kw@linux.com>,
"Andrew Murray" <amurray@thegoodpenguin.co.uk>,
"Rob Herring" <robh@kernel.org>,
"Toan Le" <toan@os.amperecomputing.com>,
"Bjorn Helgaas" <bhelgaas@google.com>
Cc: "Lorenzo Pieralisi" <lorenzo.pieralisi@arm.com>,
linux-kernel@vger.kernel.org,
linux-arm-kernel@lists.infradead.org,
"Stéphane Graber" <stgraber@ubuntu.com>,
stable@vger.kernel.org, linux-pci@vger.kernel.org
Subject: Re: [PATCH] PCI: xgene: Fix IB window setup
Date: Tue, 30 Nov 2021 14:30:46 +0000 [thread overview]
Message-ID: <163828263383.20216.14338890370157557636.b4-ty@arm.com> (raw)
In-Reply-To: <20211129173637.303201-1-robh@kernel.org>
On Mon, 29 Nov 2021 11:36:37 -0600, Rob Herring wrote:
> Commit 6dce5aa59e0b ("PCI: xgene: Use inbound resources for setup")
> broke PCI support on XGene. The cause is the IB resources are now sorted
> in address order instead of being in DT dma-ranges order. The result is
> which inbound registers are used for each region are swapped. I don't
> know the details about this h/w, but it appears that IB region 0
> registers can't handle a size greater than 4GB. In any case, limiting
> the size for region 0 is enough to get back to the original assignment
> of dma-ranges to regions.
>
> [...]
Applied to pci/xgene, thanks!
[1/1] PCI: xgene: Fix IB window setup
https://git.kernel.org/lpieralisi/pci/c/c7a75d0782
Thanks,
Lorenzo
next prev parent reply other threads:[~2021-11-30 14:30 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-11-29 17:36 [PATCH] PCI: xgene: Fix IB window setup Rob Herring
2021-11-29 19:14 ` Stéphane Graber
2021-11-30 7:55 ` Krzysztof Wilczyński
2021-11-30 14:30 ` Lorenzo Pieralisi [this message]
2022-02-04 23:01 ` dann frazier
2022-02-05 16:05 ` Rob Herring
2022-02-05 21:12 ` dann frazier
2022-02-07 16:09 ` Rob Herring
2022-02-08 1:19 ` dann frazier
2022-02-08 14:34 ` Rob Herring
2022-02-11 2:16 ` dann frazier
2022-02-21 11:50 ` Thorsten Leemhuis
2022-02-06 9:52 ` Thorsten Leemhuis
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=163828263383.20216.14338890370157557636.b4-ty@arm.com \
--to=lorenzo.pieralisi@arm.com \
--cc=amurray@thegoodpenguin.co.uk \
--cc=bhelgaas@google.com \
--cc=kw@linux.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pci@vger.kernel.org \
--cc=robh@kernel.org \
--cc=stable@vger.kernel.org \
--cc=stgraber@ubuntu.com \
--cc=toan@os.amperecomputing.com \
/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).