From: Stanimir Varbanov <svarbanov@suse.de>
To: James Quinlan <james.quinlan@broadcom.com>,
Stanimir Varbanov <svarbanov@suse.de>,
linux-kernel@vger.kernel.org, devicetree@vger.kernel.org,
linux-arm-kernel@lists.infradead.org,
linux-rpi-kernel@lists.infradead.org, linux-pci@vger.kernel.org,
Broadcom internal kernel review list
<bcm-kernel-feedback-list@broadcom.com>
Cc: Thomas Gleixner <tglx@linutronix.de>,
Rob Herring <robh@kernel.org>,
Krzysztof Kozlowski <krzk+dt@kernel.org>,
Conor Dooley <conor+dt@kernel.org>,
Florian Fainelli <florian.fainelli@broadcom.com>,
Jim Quinlan <jim2101024@gmail.com>,
Nicolas Saenz Julienne <nsaenz@kernel.org>,
Bjorn Helgaas <bhelgaas@google.com>,
Lorenzo Pieralisi <lpieralisi@kernel.org>,
kw@linux.com, Philipp Zabel <p.zabel@pengutronix.de>,
Andrea della Porta <andrea.porta@suse.com>,
Phil Elwell <phil@raspberrypi.com>,
Jonathan Bell <jonathan@raspberrypi.com>
Subject: Re: [PATCH v4 06/10] PCI: brcmstb: Enable external MSI-X if available
Date: Wed, 18 Dec 2024 16:54:57 +0200 [thread overview]
Message-ID: <ab136131-a306-4344-adaf-904e3b32326e@suse.de> (raw)
In-Reply-To: <f0a734d9-6bf6-4d28-b30b-99b6be9f62dc@broadcom.com>
Hi Jim,
Thanks for comments!
On 12/11/24 10:01 PM, James Quinlan wrote:
> On 10/25/24 08:45, Stanimir Varbanov wrote:
>> On RPi5 there is an external MIP MSI-X interrupt controller
>> which can handle up to 64 interrupts.
>>
>> Signed-off-by: Stanimir Varbanov <svarbanov@suse.de>
>> ---
>> v3 -> v4:
>> - no changes.
>>
>> drivers/pci/controller/pcie-brcmstb.c | 63 +++++++++++++++++++++++++--
>> 1 file changed, 59 insertions(+), 4 deletions(-)
>>
>> diff --git a/drivers/pci/controller/pcie-brcmstb.c b/drivers/pci/
>> controller/pcie-brcmstb.c
>> index c01462b07eea..af01a7915c94 100644
>> --- a/drivers/pci/controller/pcie-brcmstb.c
>> +++ b/drivers/pci/controller/pcie-brcmstb.c
>> @@ -1318,6 +1318,52 @@ static int brcm_pcie_start_link(struct
>> brcm_pcie *pcie)
>> return 0;
>> }
>> +static int brcm_pcie_enable_external_msix(struct brcm_pcie *pcie,
>> + struct device_node *msi_np)
>> +{
>> + struct inbound_win inbound_wins[PCIE_BRCM_MAX_INBOUND_WINS];
>> + u64 msi_pci_addr, msi_phys_addr;
>> + struct resource r;
>> + int mip_bar, ret;
>> + u32 val, reg;
>> +
>> + ret = of_property_read_reg(msi_np, 1, &msi_pci_addr, NULL);
>> + if (ret)
>> + return ret;
>> +
>> + ret = of_address_to_resource(msi_np, 0, &r);
>> + if (ret)
>> + return ret;
>> +
>> + msi_phys_addr = r.start;
>> +
>> + /* Find free inbound window for MIP access */
>> + mip_bar = brcm_pcie_get_inbound_wins(pcie, inbound_wins);
>> + if (mip_bar < 0)
>> + return mip_bar;
>> +
>> + mip_bar += 1;
>> + reg = brcm_bar_reg_offset(mip_bar);
>> +
>> + val = lower_32_bits(msi_pci_addr);
>> + val |= brcm_pcie_encode_ibar_size(SZ_4K);
>> + writel(val, pcie->base + reg);
>> +
>> + val = upper_32_bits(msi_pci_addr);
>> + writel(val, pcie->base + reg + 4);
>> +
>> + reg = brcm_ubus_reg_offset(mip_bar);
>> +
>> + val = lower_32_bits(msi_phys_addr);
>> + val |= PCIE_MISC_UBUS_BAR1_CONFIG_REMAP_ACCESS_EN_MASK;
>> + writel(val, pcie->base + reg);
>> +
>> + val = upper_32_bits(msi_phys_addr);
>> + writel(val, pcie->base + reg + 4);
>
> Hi Stan,
>
> It looks like all this is doing is setting up an identity-mapped inbound
> window, is that correct? If so, couldn't you get the same effect by
> adding an identity-mapped dma-range in the PCIe DT node?
Yes, that approach could work, I verified it.
Do you want me to drop this patch from the series and make the relevant
changes in PCIe dma-ranges properties?
~Stan
next prev parent reply other threads:[~2024-12-18 14:55 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-10-25 12:45 [PATCH v4 00/10] Add PCIe support for bcm2712 Stanimir Varbanov
2024-10-25 12:45 ` [PATCH v4 01/10] dt-bindings: interrupt-controller: Add bcm2712 MSI-X DT bindings Stanimir Varbanov
2024-10-25 12:45 ` [PATCH v4 02/10] dt-bindings: PCI: brcmstb: Update bindings for PCIe on bcm2712 Stanimir Varbanov
2024-10-25 21:55 ` Rob Herring
2024-10-25 12:45 ` [PATCH v4 03/10] irqchip: Add Broadcom bcm2712 MSI-X interrupt controller Stanimir Varbanov
2024-10-28 20:06 ` Thomas Gleixner
2024-11-01 13:15 ` Stanimir Varbanov
2024-10-25 12:45 ` [PATCH v4 04/10] PCI: brcmstb: Reuse config structure Stanimir Varbanov
2024-10-25 12:45 ` [PATCH v4 05/10] PCI: brcmstb: Expand inbound window size up to 64GB Stanimir Varbanov
2024-10-25 12:45 ` [PATCH v4 06/10] PCI: brcmstb: Enable external MSI-X if available Stanimir Varbanov
2024-11-10 9:41 ` Stanimir Varbanov
2024-12-11 20:01 ` James Quinlan
2024-12-18 14:54 ` Stanimir Varbanov [this message]
2024-12-18 16:20 ` Jim Quinlan
2024-10-25 12:45 ` [PATCH v4 07/10] PCI: brcmstb: Add bcm2712 support Stanimir Varbanov
2024-10-25 12:45 ` [PATCH v4 08/10] PCI: brcmstb: Adjust PHY PLL setup to use a 54MHz input refclk Stanimir Varbanov
2024-10-25 22:08 ` Florian Fainelli
2024-12-09 22:52 ` James Quinlan
2024-12-10 13:42 ` Stanimir Varbanov
2024-12-11 19:39 ` James Quinlan
2024-12-11 20:54 ` Jonathan Bell
2024-12-12 13:48 ` Stanimir Varbanov
2024-10-25 12:45 ` [PATCH v4 09/10] arm64: dts: broadcom: bcm2712: Add PCIe DT nodes Stanimir Varbanov
2024-10-25 12:45 ` [PATCH v4 10/10] arm64: dts: broadcom: bcm2712-rpi-5-b: Enable " Stanimir Varbanov
2024-12-23 16:35 ` [PATCH v4 00/10] Add PCIe support for bcm2712 Olivier Benjamin
2025-01-21 15:01 ` Stanimir Varbanov
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=ab136131-a306-4344-adaf-904e3b32326e@suse.de \
--to=svarbanov@suse.de \
--cc=andrea.porta@suse.com \
--cc=bcm-kernel-feedback-list@broadcom.com \
--cc=bhelgaas@google.com \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=florian.fainelli@broadcom.com \
--cc=james.quinlan@broadcom.com \
--cc=jim2101024@gmail.com \
--cc=jonathan@raspberrypi.com \
--cc=krzk+dt@kernel.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-rpi-kernel@lists.infradead.org \
--cc=lpieralisi@kernel.org \
--cc=nsaenz@kernel.org \
--cc=p.zabel@pengutronix.de \
--cc=phil@raspberrypi.com \
--cc=robh@kernel.org \
--cc=tglx@linutronix.de \
/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
all inboxes | Powered by JetHome®