From: Rick Wertenbroek <rick.wertenbroek@gmail.com>
To: Damien Le Moal <dlemoal@kernel.org>
Cc: alberto.dassatti@heig-vd.ch, xxm@rock-chips.com,
"Shawn Lin" <shawn.lin@rock-chips.com>,
"Bjorn Helgaas" <bhelgaas@google.com>,
"Lorenzo Pieralisi" <lpieralisi@kernel.org>,
"Krzysztof Wilczyński" <kw@linux.com>,
"Rob Herring" <robh@kernel.org>,
"Krzysztof Kozlowski" <krzysztof.kozlowski+dt@linaro.org>,
"Heiko Stuebner" <heiko@sntech.de>,
"Brian Norris" <briannorris@chromium.org>,
"Johan Jonker" <jbx6244@gmail.com>,
"Caleb Connolly" <kc@postmarketos.org>,
"Corentin Labbe" <clabbe@baylibre.com>,
"Judy Hsiao" <judyhsiao@chromium.org>,
"Arnaud Ferraris" <arnaud.ferraris@collabora.com>,
"Hugh Cole-Baker" <sigmaris@gmail.com>,
linux-pci@vger.kernel.org, linux-rockchip@lists.infradead.org,
devicetree@vger.kernel.org, linux-arm-kernel@lists.infradead.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH v4 00/11] PCI: rockchip: Fix RK3399 PCIe endpoint controller driver
Date: Tue, 18 Apr 2023 09:51:21 +0200 [thread overview]
Message-ID: <CAAEEuhpj4TZNrPEPn7LuGOHHoYt1FbCEGH1d9g+8iKMeoBA+=Q@mail.gmail.com> (raw)
In-Reply-To: <ea29e339-6f61-5bbb-7290-03df629d5b11@kernel.org>
On Tue, Apr 18, 2023 at 2:09 AM Damien Le Moal <dlemoal@kernel.org> wrote:
>
> On 4/17/23 18:26, Rick Wertenbroek wrote:
> > This is a series of patches that fixes the PCIe endpoint controller driver
> > for the Rockchip RK3399 SoC. The driver was introduced in commit
> > cf590b078391 ("PCI: rockchip: Add EP driver for Rockchip PCIe controller")
> > The original driver had issues and would not allow for the RK3399 to
> > operate in PCIe endpoint mode correctly. This patch series fixes that so
> > that the PCIe core controller of the RK3399 SoC can now act as a PCIe
> > endpoint. This is v4 of the patch series and addresses the comments received
> > during the review of the v3 [1]. The changes to the v3 are minor and none of
> > them change the logic of the driver.
> >
> > Thank you in advance for reviewing this patch series and hopefully
> > getting this merged. Having a functional PCIe endpoint controller
> > driver for the RK3399 would allow to develop further PCIe endpoint
> > functions through the Linux PCIe endpoint framework using this SoC.
> >
> > [1] https://lore.kernel.org/linux-pci/20230404082426.3880812-1-rick.wertenbroek@gmail.com/
> >
> > Summary of changes to V3 :
> >
> > * Set the fields in the standard order in the dtsi and removed unnecessary
> > change in associated documentation, thanks to Krzysztof for pointing this out.
> > * Added comment to explain how MSI-X capabilities advertisement was removed.
> > * Changed Damien Le Moal <damien.lemoal@opensource.wdc.com> address to his
> > kernel.org address Damien Le Moal <dlemoal@kernel.org> in tags.
> > * [minor] Simplified code where a power of 2 was applied followed by a ilog2
> > operation.
> > * [minor] Small code changes, replaced constant variable by macro, split
> > remaining long lines.
>
> I retested this series, all good. So my Tested-by tag stands.
>
> Lorenzo, Krzysztof, Bjorn,
>
> Let's please get this series queued for 6.4 ASAP as otherwise the rockchip EP
> controller is unusable.
>
> Also please note that working with Rick off-list, we found out that more fixes
> are in fact needed for the PCI address mapping (ATU programming) on top of this
> series. But the problems detected are subtle and harder to trigger. The fixes
> needed involve changes to the EPC core API so we are still working on the best
> way to do that. We'll work on another series on top of this one for addressing
> these issues.
>
>
Thank you Damien for taking the time testing and reviewing this, it is
highly appreciated.
I just sent a v5 [1] addressing your comments and added the tags.
Best regards,
Rick
[1] https://lore.kernel.org/linux-pci/20230418074700.1083505-1-rick.wertenbroek@gmail.com/
next prev parent reply other threads:[~2023-04-18 7:52 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-04-17 9:26 [PATCH v4 00/11] PCI: rockchip: Fix RK3399 PCIe endpoint controller driver Rick Wertenbroek
2023-04-17 9:26 ` [PATCH v4 01/11] PCI: rockchip: Remove writes to unused registers Rick Wertenbroek
2023-04-17 23:58 ` Damien Le Moal
2023-04-17 9:26 ` [PATCH v4 02/11] PCI: rockchip: Write PCI Device ID to correct register Rick Wertenbroek
2023-04-17 9:26 ` [PATCH v4 03/11] PCI: rockchip: Assert PCI Configuration Enable bit after probe Rick Wertenbroek
2023-04-17 9:26 ` [PATCH v4 04/11] PCI: rockchip: Add poll and timeout to wait for PHY PLLs to be locked Rick Wertenbroek
2023-04-17 9:26 ` [PATCH v4 05/11] arm64: dts: rockchip: Add dtsi entry for RK3399 PCIe endpoint core Rick Wertenbroek
2023-04-17 9:26 ` [PATCH v4 06/11] dt-bindings: PCI: Update the RK3399 example to a valid one Rick Wertenbroek
2023-04-17 9:26 ` [PATCH v4 07/11] PCI: rockchip: Fix legacy IRQ generation for RK3399 PCIe endpoint core Rick Wertenbroek
2023-04-17 23:57 ` Damien Le Moal
2023-04-17 9:26 ` [PATCH v4 08/11] PCI: rockchip: Fix window mapping and address translation for endpoint Rick Wertenbroek
2023-04-17 23:55 ` Damien Le Moal
2023-04-17 9:26 ` [PATCH v4 09/11] PCI: rockchip: Use u32 variable to access 32-bit registers Rick Wertenbroek
2023-04-17 23:56 ` Damien Le Moal
2023-04-17 9:26 ` [PATCH v4 10/11] PCI: rockchip: Don't advertise MSI-X in PCIe capabilities Rick Wertenbroek
2023-04-17 23:50 ` Damien Le Moal
2023-04-17 9:26 ` [PATCH v4 11/11] PCI: rockchip: Set address alignment for endpoint mode Rick Wertenbroek
2023-04-17 23:51 ` Damien Le Moal
2023-04-18 7:11 ` Rick Wertenbroek
2023-04-18 0:09 ` [PATCH v4 00/11] PCI: rockchip: Fix RK3399 PCIe endpoint controller driver Damien Le Moal
2023-04-18 7:51 ` Rick Wertenbroek [this message]
2023-04-18 8:00 ` Damien Le Moal
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='CAAEEuhpj4TZNrPEPn7LuGOHHoYt1FbCEGH1d9g+8iKMeoBA+=Q@mail.gmail.com' \
--to=rick.wertenbroek@gmail.com \
--cc=alberto.dassatti@heig-vd.ch \
--cc=arnaud.ferraris@collabora.com \
--cc=bhelgaas@google.com \
--cc=briannorris@chromium.org \
--cc=clabbe@baylibre.com \
--cc=devicetree@vger.kernel.org \
--cc=dlemoal@kernel.org \
--cc=heiko@sntech.de \
--cc=jbx6244@gmail.com \
--cc=judyhsiao@chromium.org \
--cc=kc@postmarketos.org \
--cc=krzysztof.kozlowski+dt@linaro.org \
--cc=kw@linux.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pci@vger.kernel.org \
--cc=linux-rockchip@lists.infradead.org \
--cc=lpieralisi@kernel.org \
--cc=robh@kernel.org \
--cc=shawn.lin@rock-chips.com \
--cc=sigmaris@gmail.com \
--cc=xxm@rock-chips.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).