From: Lorenzo Pieralisi <lorenzo.pieralisi@arm.com>
To: Nicolas Saenz Julienne <nsaenzjulienne@suse.de>
Cc: andrew.murray@arm.com, maz@kernel.org,
linux-kernel@vger.kernel.org, james.quinlan@broadcom.com,
mbrugger@suse.com, f.fainelli@gmail.com, phil@raspberrypi.org,
wahrenst@gmx.net, jeremy.linton@arm.com,
linux-pci@vger.kernel.org, linux-rpi-kernel@lists.infradead.org,
bcm-kernel-feedback-list@broadcom.com,
linux-arm-kernel@lists.infradead.org, devicetree@vger.kernel.org
Subject: Re: [PATCH v5 0/6] Raspberry Pi 4 PCIe support
Date: Wed, 15 Jan 2020 12:02:38 +0000 [thread overview]
Message-ID: <20200115120238.GA7233@e121166-lin.cambridge.arm.com> (raw)
In-Reply-To: <20191216110113.30436-1-nsaenzjulienne@suse.de>
On Mon, Dec 16, 2019 at 12:01:06PM +0100, Nicolas Saenz Julienne wrote:
> This series aims at providing support for Raspberry Pi 4's PCIe
> controller, which is also shared with the Broadcom STB family of
> devices.
>
> There was a previous attempt to upstream this some years ago[1] but was
> blocked as most STB PCIe integrations have a sparse DMA mapping[2] which
> is something currently not supported by the kernel. Luckily this is not
> the case for the Raspberry Pi 4.
>
> Note the series is based on top of linux next, as the DTS patch depends
> on it.
>
> [1] https://patchwork.kernel.org/cover/10605933/
> [2] https://patchwork.kernel.org/patch/10605957/
>
> ---
>
> Changes since v4:
> - Rebase DTS patch
> - Respin log2.h code into it's own series as it's still contentious
> yet mostly unrelated to the PCIe part
>
> Changes since v3:
> - Moved all the log2.h related changes at the end of the series, as I
> presume they will be contentious and I don't want the PCIe patches
> to depend on them. Ultimately I think I'll respin them on their own
> series but wanted to keep them in for this submission just for the
> sake of continuity.
> - Addressed small nits here and there.
>
> Changes since v2:
> - Redo register access in driver avoiding indirection while keeping
> the naming intact
> - Add patch editing ARM64's config
> - Last MSI cleanups, notably removing MSIX flag
> - Got rid of all _RB writes
> - Got rid of all of_data
> - Overall churn removal
> - Address the rest of Andrew's comments
>
> Changes since v1:
> - add generic rounddown/roundup_pow_two64() patch
> - Add MAINTAINERS patch
> - Fix Kconfig
> - Cleanup probe, use up to date APIs, exit on MSI failure
> - Get rid of linux,pci-domain and other unused constructs
> - Use edge triggered setup for MSI
> - Cleanup MSI implementation
> - Fix multiple cosmetic issues
> - Remove supend/resume code
>
> Jim Quinlan (3):
> dt-bindings: PCI: Add bindings for brcmstb's PCIe device
> PCI: brcmstb: Add Broadcom STB PCIe host controller driver
> PCI: brcmstb: Add MSI support
>
> Nicolas Saenz Julienne (3):
> ARM: dts: bcm2711: Enable PCIe controller
> MAINTAINERS: Add brcmstb PCIe controller
> arm64: defconfig: Enable Broadcom's STB PCIe controller
>
> .../bindings/pci/brcm,stb-pcie.yaml | 97 ++
> MAINTAINERS | 4 +
> arch/arm/boot/dts/bcm2711.dtsi | 31 +-
> arch/arm64/configs/defconfig | 1 +
> drivers/pci/controller/Kconfig | 9 +
> drivers/pci/controller/Makefile | 1 +
> drivers/pci/controller/pcie-brcmstb.c | 1007 +++++++++++++++++
> 7 files changed, 1149 insertions(+), 1 deletion(-)
> create mode 100644 Documentation/devicetree/bindings/pci/brcm,stb-pcie.yaml
> create mode 100644 drivers/pci/controller/pcie-brcmstb.c
Applied patches [1,3,4] to pci/brcmstb, please have a look to check
everything is in order after the minor update I included.
Thanks !
Lorenzo
next prev parent reply other threads:[~2020-01-15 12:02 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-12-16 11:01 [PATCH v5 0/6] Raspberry Pi 4 PCIe support Nicolas Saenz Julienne
2019-12-16 11:01 ` [PATCH v5 1/6] dt-bindings: PCI: Add bindings for brcmstb's PCIe device Nicolas Saenz Julienne
2019-12-16 11:14 ` Matthias Brugger
2019-12-16 11:18 ` Nicolas Saenz Julienne
2019-12-16 11:01 ` [PATCH v5 2/6] ARM: dts: bcm2711: Enable PCIe controller Nicolas Saenz Julienne
2020-01-14 18:11 ` Lorenzo Pieralisi
2020-01-14 18:15 ` Florian Fainelli
2020-01-15 23:41 ` Florian Fainelli
2019-12-16 11:01 ` [PATCH v5 3/6] PCI: brcmstb: Add Broadcom STB PCIe host controller driver Nicolas Saenz Julienne
2020-01-14 17:11 ` Lorenzo Pieralisi
2020-01-14 18:18 ` Nicolas Saenz Julienne
2020-01-15 10:00 ` Lorenzo Pieralisi
2020-01-15 11:29 ` Nicolas Saenz Julienne
2019-12-16 11:01 ` [PATCH v5 4/6] PCI: brcmstb: Add MSI support Nicolas Saenz Julienne
2019-12-16 11:01 ` [PATCH v5 5/6] MAINTAINERS: Add brcmstb PCIe controller Nicolas Saenz Julienne
2020-01-15 23:41 ` Florian Fainelli
2019-12-16 11:01 ` [PATCH v5 6/6] arm64: defconfig: Enable Broadcom's STB " Nicolas Saenz Julienne
2020-01-16 17:21 ` Florian Fainelli
2019-12-16 11:36 ` [PATCH v5 0/6] Raspberry Pi 4 PCIe support Andrew Murray
2019-12-16 11:45 ` Nicolas Saenz Julienne
2020-01-15 12:02 ` Lorenzo Pieralisi [this message]
2020-01-15 12:45 ` Nicolas Saenz Julienne
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=20200115120238.GA7233@e121166-lin.cambridge.arm.com \
--to=lorenzo.pieralisi@arm.com \
--cc=andrew.murray@arm.com \
--cc=bcm-kernel-feedback-list@broadcom.com \
--cc=devicetree@vger.kernel.org \
--cc=f.fainelli@gmail.com \
--cc=james.quinlan@broadcom.com \
--cc=jeremy.linton@arm.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pci@vger.kernel.org \
--cc=linux-rpi-kernel@lists.infradead.org \
--cc=maz@kernel.org \
--cc=mbrugger@suse.com \
--cc=nsaenzjulienne@suse.de \
--cc=phil@raspberrypi.org \
--cc=wahrenst@gmx.net \
/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).