[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-Id: <175068040623.12516.4425064763865712731.b4-ty@kernel.org>
Date: Mon, 23 Jun 2025 06:06:46 -0600
From: Manivannan Sadhasivam <mani@...nel.org>
To: Jon Mason <jdmason@...zu.us>, Dave Jiang <dave.jiang@...el.com>,
Allen Hubbe <allenbh@...il.com>, Kishon Vijay Abraham I <kishon@...nel.org>,
Bjorn Helgaas <bhelgaas@...gle.com>, Frank Li <Frank.Li@....com>,
Krzysztof Wilczyński <kwilczynski@...nel.org>,
Krzysztof Wilczyński <kwilczynski@...nel.org>,
Manivannan Sadhasivam <mani@...nel.org>,
Jerome Brunet <jbrunet@...libre.com>
Cc: ntb@...ts.linux.dev, linux-pci@...r.kernel.org,
linux-kernel@...r.kernel.org
Subject: Re: [PATCH v2 0/3] PCI: endpoint: pci-epf-vntb: allow arbitrary
BAR mapping
On Tue, 03 Jun 2025 19:03:37 +0200, Jerome Brunet wrote:
> The patchset allows arbitrary BAR mapping for vNTB PCI endpoint function.
>
> This was developed for the Renesas platform with requires a mapping that
> was not possible before:
> * BAR0 (1MB): CTRL+SPAD
> * BAR2 (1MB): MW0
> * BAR4 (256B): Doorbell
>
> [...]
Applied, thanks!
[1/3] PCI: endpoint: pci-epf-vntb: Return an error code on bar init
commit: 7ea488cce73263231662e426639dd3e836537068
[2/3] PCI: endpoint: pci-epf-vntb: Align mw naming with config names
commit: a079d83c4afd4896f7f29bd9e807cb382043b360
[3/3] PCI: endpoint: pci-epf-vntb: Allow BAR assignment via configfs
commit: a0cc6e6fd072616315147ac68a12672d5a2fa223
Best regards,
--
Manivannan Sadhasivam <mani@...nel.org>
Powered by blists - more mailing lists