From: robert.richter@cavium.com (Robert Richter)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH 2/2] PCI: Add legacy firmware support for Cavium ThunderX host controller
Date: Mon, 20 Mar 2017 12:02:41 +0100 [thread overview]
Message-ID: <20170320110241.GG16822@rric.localdomain> (raw)
In-Reply-To: <1489564155-3881-3-git-send-email-tn@semihalf.com>
On 15.03.17 08:49:15, Tomasz Nowicki wrote:
> During early days of PCI quirks support ThunderX firmware did not provide
> PNP0c02 node with PCI configuration space and PEM-specific register ranges.
> This means that for legacy FW we are not reserving these resources and
> cannot gather PEM-specific resources for further PEM initialization.
>
> In order to support already deployed legacy FW calculate PEM-specific ranges
> and provide resources reservation as fallback scenario into PEM driver when
> we could not gather PEM reg base from ACPI tables.
>
> Signed-off-by: Tomasz Nowicki <tn@semihalf.com>
> Signed-off-by: Vadim Lomovtsev <Vadim.Lomovtsev@caviumnetworks.com>
Works with old and new firmware.
Tested-by: Robert Richter <rrichter@cavium.com>
Acked-by: Robert Richter <rrichter@cavium.com>
-Robert
next prev parent reply other threads:[~2017-03-20 11:02 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-03-15 7:49 [PATCH 0/2] ThunderX external PCI fixes for legacy&new ACPI firmware Tomasz Nowicki
2017-03-15 7:49 ` [PATCH 1/2] PCI: Use Cavium assigned hardware ID for ThunderX host controller Tomasz Nowicki
2017-03-20 10:49 ` Robert Richter
2017-03-15 7:49 ` [PATCH 2/2] PCI: Add legacy firmware support for Cavium " Tomasz Nowicki
2017-03-20 11:02 ` Robert Richter [this message]
2017-03-24 15:55 ` Tomasz Nowicki
2017-03-28 19:21 ` Tomasz Nowicki
2017-03-28 19:28 ` Tomasz Nowicki
2017-03-21 17:43 ` [PATCH 0/2] ThunderX external PCI fixes for legacy&new ACPI firmware Bjorn Helgaas
2017-03-22 14:19 ` Tomasz Nowicki
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=20170320110241.GG16822@rric.localdomain \
--to=robert.richter@cavium.com \
--cc=linux-arm-kernel@lists.infradead.org \
/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