From: Manivannan Sadhasivam <manivannan.sadhasivam@linaro.org>
To: Niklas Cassel <cassel@kernel.org>
Cc: "Lorenzo Pieralisi" <lpieralisi@kernel.org>,
"Krzysztof Wilczyński" <kw@linux.com>,
"Rob Herring" <robh@kernel.org>,
"Bjorn Helgaas" <bhelgaas@google.com>,
"Heiko Stuebner" <heiko@sntech.de>,
"Damien Le Moal" <dlemoal@kernel.org>,
"Siddharth Vadapalli" <s-vadapalli@ti.com>,
"Udit Kumar" <u-kumar1@ti.com>,
"Vignesh Raghavendra" <vigneshr@ti.com>,
linux-pci@vger.kernel.org, linux-arm-kernel@lists.infradead.org,
linux-rockchip@lists.infradead.org
Subject: Re: [PATCH v3 6/6] PCI: dw-rockchip: Describe resizable BARs as resizable BARs
Date: Sun, 19 Jan 2025 11:03:34 +0530 [thread overview]
Message-ID: <20250119053334.tgp7yycky5s6ub2v@thinkpad> (raw)
In-Reply-To: <20250113102730.1700963-14-cassel@kernel.org>
On Mon, Jan 13, 2025 at 11:27:37AM +0100, Niklas Cassel wrote:
> Looking at "11.4.4.29 USP_PCIE_RESBAR Registers Summary" in the rk3588 TRM,
> we can see that none of the BARs are Fixed BARs, but actually Resizable
> BARs.
>
> I couldn't find any reference in the rk3568 TRM, but looking at the
> downstream PCIe endpoint driver, rk3568 and rk3588 are treated as the same,
> so the BARs on rk3568 must also be Resizable BARs.
>
> Now when we actually have support for Resizable BARs, let's configure
> these BARs as such.
>
> Signed-off-by: Niklas Cassel <cassel@kernel.org>
Reviewed-by: Manivannan Sadhasivam <manivannan.sadhasivam@linaro.org>
- Mani
> ---
> drivers/pci/controller/dwc/pcie-dw-rockchip.c | 22 +++++++++----------
> 1 file changed, 11 insertions(+), 11 deletions(-)
>
> diff --git a/drivers/pci/controller/dwc/pcie-dw-rockchip.c b/drivers/pci/controller/dwc/pcie-dw-rockchip.c
> index ce4b511bff9b..6a307a961756 100644
> --- a/drivers/pci/controller/dwc/pcie-dw-rockchip.c
> +++ b/drivers/pci/controller/dwc/pcie-dw-rockchip.c
> @@ -273,12 +273,12 @@ static const struct pci_epc_features rockchip_pcie_epc_features_rk3568 = {
> .msi_capable = true,
> .msix_capable = true,
> .align = SZ_64K,
> - .bar[BAR_0] = { .type = BAR_FIXED, .fixed_size = SZ_1M, },
> - .bar[BAR_1] = { .type = BAR_FIXED, .fixed_size = SZ_1M, },
> - .bar[BAR_2] = { .type = BAR_FIXED, .fixed_size = SZ_1M, },
> - .bar[BAR_3] = { .type = BAR_FIXED, .fixed_size = SZ_1M, },
> - .bar[BAR_4] = { .type = BAR_FIXED, .fixed_size = SZ_1M, },
> - .bar[BAR_5] = { .type = BAR_FIXED, .fixed_size = SZ_1M, },
> + .bar[BAR_0] = { .type = BAR_RESIZABLE, },
> + .bar[BAR_1] = { .type = BAR_RESIZABLE, },
> + .bar[BAR_2] = { .type = BAR_RESIZABLE, },
> + .bar[BAR_3] = { .type = BAR_RESIZABLE, },
> + .bar[BAR_4] = { .type = BAR_RESIZABLE, },
> + .bar[BAR_5] = { .type = BAR_RESIZABLE, },
> };
>
> /*
> @@ -293,12 +293,12 @@ static const struct pci_epc_features rockchip_pcie_epc_features_rk3588 = {
> .msi_capable = true,
> .msix_capable = true,
> .align = SZ_64K,
> - .bar[BAR_0] = { .type = BAR_FIXED, .fixed_size = SZ_1M, },
> - .bar[BAR_1] = { .type = BAR_FIXED, .fixed_size = SZ_1M, },
> - .bar[BAR_2] = { .type = BAR_FIXED, .fixed_size = SZ_1M, },
> - .bar[BAR_3] = { .type = BAR_FIXED, .fixed_size = SZ_1M, },
> + .bar[BAR_0] = { .type = BAR_RESIZABLE, },
> + .bar[BAR_1] = { .type = BAR_RESIZABLE, },
> + .bar[BAR_2] = { .type = BAR_RESIZABLE, },
> + .bar[BAR_3] = { .type = BAR_RESIZABLE, },
> .bar[BAR_4] = { .type = BAR_RESERVED, },
> - .bar[BAR_5] = { .type = BAR_FIXED, .fixed_size = SZ_1M, },
> + .bar[BAR_5] = { .type = BAR_RESIZABLE, },
> };
>
> static const struct pci_epc_features *
> --
> 2.47.1
>
--
மணிவண்ணன் சதாசிவம்
next prev parent reply other threads:[~2025-01-19 5:39 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-01-13 10:27 [PATCH v3 0/6] PCI: endpoint: Add support for resizable BARs Niklas Cassel
2025-01-13 10:27 ` [PATCH v3 6/6] PCI: dw-rockchip: Describe resizable BARs as " Niklas Cassel
2025-01-19 5:33 ` Manivannan Sadhasivam [this message]
2025-01-19 5:08 ` [PATCH v3 0/6] PCI: endpoint: Add support for " Manivannan Sadhasivam
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=20250119053334.tgp7yycky5s6ub2v@thinkpad \
--to=manivannan.sadhasivam@linaro.org \
--cc=bhelgaas@google.com \
--cc=cassel@kernel.org \
--cc=dlemoal@kernel.org \
--cc=heiko@sntech.de \
--cc=kw@linux.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-pci@vger.kernel.org \
--cc=linux-rockchip@lists.infradead.org \
--cc=lpieralisi@kernel.org \
--cc=robh@kernel.org \
--cc=s-vadapalli@ti.com \
--cc=u-kumar1@ti.com \
--cc=vigneshr@ti.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