From: Lorenzo Pieralisi <lpieralisi@kernel.org>
To: "Rob Herring" <robh@kernel.org>, "Pali Rohár" <pali@kernel.org>,
"Bjorn Helgaas" <bhelgaas@google.com>,
"Krzysztof Wilczyński" <kw@linux.com>
Cc: "Lorenzo Pieralisi" <lpieralisi@kernel.org>,
"Thomas Petazzoni" <thomas.petazzoni@bootlin.com>,
linux-kernel@vger.kernel.org, linux-pci@vger.kernel.org,
"Marek Behún" <kabel@kernel.org>
Subject: Re: [PATCH v3] PCI: pci-bridge-emul: Set position of PCI capabilities to real HW value
Date: Thu, 25 Aug 2022 12:09:54 +0200 [thread overview]
Message-ID: <166142217602.128276.10729379597803060542.b4-ty@kernel.org> (raw)
In-Reply-To: <20220824112124.21675-1-pali@kernel.org>
On Wed, 24 Aug 2022 13:21:24 +0200, Pali Rohár wrote:
> mvebu and aardvark HW have PCIe capabilities on different offset in PCI
> config space. Extend pci-bridge-emul.c code to allow setting custom driver
> custom value where PCIe capabilities starts.
>
> With this change PCIe capabilities of both drivers are reported at the same
> location as where they are reported by U-Boot - in their real HW offset.
>
> [...]
Applied to pci/bridge-emul, thanks!
[1/1] PCI: pci-bridge-emul: Set position of PCI capabilities to real HW value
https://git.kernel.org/lpieralisi/pci/c/658aea35ab88
Thanks,
Lorenzo
prev parent reply other threads:[~2022-08-25 10:10 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-07-03 10:46 [PATCH] PCI: pci-bridge-emul: Set position of PCI capabilities to real HW value Pali Rohár
2022-08-18 13:50 ` Pali Rohár
2022-08-18 22:31 ` Bjorn Helgaas
2022-08-18 22:36 ` Pali Rohár
2022-08-18 23:02 ` Bjorn Helgaas
2022-08-23 9:06 ` Lorenzo Pieralisi
2022-08-23 9:25 ` Pali Rohár
2022-08-23 10:14 ` [PATCH v2] " Pali Rohár
2022-08-23 15:55 ` Lorenzo Pieralisi
2022-08-23 16:31 ` Pali Rohár
2022-08-24 7:25 ` Lorenzo Pieralisi
2022-08-24 10:33 ` Pali Rohár
2022-08-24 11:21 ` [PATCH v3] " Pali Rohár
2022-08-25 10:09 ` Lorenzo Pieralisi [this message]
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=166142217602.128276.10729379597803060542.b4-ty@kernel.org \
--to=lpieralisi@kernel.org \
--cc=bhelgaas@google.com \
--cc=kabel@kernel.org \
--cc=kw@linux.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pci@vger.kernel.org \
--cc=pali@kernel.org \
--cc=robh@kernel.org \
--cc=thomas.petazzoni@bootlin.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).