From: Lorenzo Pieralisi <lorenzo.pieralisi@arm.com>
To: Zhiqiang Hou <Zhiqiang.Hou@nxp.com>,
linux-pci@vger.kernel.org, linux-kernel@vger.kernel.org
Cc: gustavo.pimentel@synopsys.com, robh@kernel.org,
bhelgaas@google.com, jingoohan1@gmail.com
Subject: Re: [PATCH] PCI: dwc: Move forward the iATU detection process
Date: Mon, 22 Mar 2021 18:09:17 +0000 [thread overview]
Message-ID: <20210322180917.GA15539@e121166-lin.cambridge.arm.com> (raw)
In-Reply-To: <161643622212.21337.14859040633786233709.b4-ty@arm.com>
On Mon, Mar 22, 2021 at 06:03:57PM +0000, Lorenzo Pieralisi wrote:
> On Mon, 25 Jan 2021 12:48:03 +0800, Zhiqiang Hou wrote:
> > In the dw_pcie_ep_init(), it depends on the detected iATU region
> > numbers to allocate the in/outbound window management bit map.
> > It fails after the commit 281f1f99cf3a ("PCI: dwc: Detect number
> > of iATU windows").
> >
> > So this patch move the iATU region detection into a new function,
> > move forward the detection to the very beginning of functions
> > dw_pcie_host_init() and dw_pcie_ep_init(). And also remove it
> > from the dw_pcie_setup(), since it's more like a software
> > perspective initialization step than hardware setup.
>
> Applied to pci/dwc, thanks!
>
> [1/1] PCI: dwc: Move forward the iATU detection process
> https://git.kernel.org/lpieralisi/pci/c/5ff8ca16f8
Bjorn will queue it for v5.12, so I have dropped it, ignore
this notification.
Thanks,
Lorenzo
next prev parent reply other threads:[~2021-03-22 18:10 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <CGME20210325092429eucas1p25e95dd1920f2a1c9f808c72d10d1952d@eucas1p2.samsung.com>
2021-01-25 4:48 ` [PATCH] PCI: dwc: Move forward the iATU detection process Zhiqiang Hou
2021-01-26 5:25 ` Kunihiko Hayashi
2021-01-27 6:27 ` Z.q. Hou
2021-01-28 0:19 ` Kunihiko Hayashi
2021-03-05 16:18 ` Rob Herring
2021-03-22 18:03 ` Lorenzo Pieralisi
2021-03-22 18:09 ` Lorenzo Pieralisi [this message]
2021-03-22 18:10 ` Bjorn Helgaas
2021-03-25 9:24 ` Marek Szyprowski
2021-03-25 20:19 ` Bjorn Helgaas
2021-03-26 17:05 ` Marek Szyprowski
2021-03-30 7:51 ` Marek Szyprowski
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=20210322180917.GA15539@e121166-lin.cambridge.arm.com \
--to=lorenzo.pieralisi@arm.com \
--cc=Zhiqiang.Hou@nxp.com \
--cc=bhelgaas@google.com \
--cc=gustavo.pimentel@synopsys.com \
--cc=jingoohan1@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pci@vger.kernel.org \
--cc=robh@kernel.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