From: Leigh Brown <leigh@solinno.co.uk>
To: Bjorn Helgaas <helgaas@kernel.org>
Cc: "Thomas Petazzoni" <thomas.petazzoni@bootlin.com>,
"Lorenzo Pieralisi" <lorenzo.pieralisi@arm.com>,
linux-pci@vger.kernel.org, "Andrew Lunn" <andrew@lunn.ch>,
"Russell King" <linux@arm.linux.org.uk>,
"Jason Cooper" <jason@lakedaemon.net>,
"Gregory Clement" <gregory.clement@bootlin.com>,
"Luís Mendes" <luis.p.mendes@gmail.com>,
linux-arm-kernel@lists.infradead.org,
"Sebastian Hesselbarth" <sebastian.hesselbarth@gmail.com>
Subject: Re: [PATCH 0/2] PCI: fix pci-mvebu after conversion to common bridge emul code
Date: Fri, 22 Feb 2019 08:11:01 +0000 [thread overview]
Message-ID: <3ead4de3a0a5a0fe4aa5a76c92f01629@solinno.co.uk> (raw)
In-Reply-To: <20190221232317.GB219879@google.com>
On 2019-02-21 23:23, Bjorn Helgaas wrote:
> On Wed, Feb 20, 2019 at 10:48:39AM +0100, Thomas Petazzoni wrote:
>> Hello,
>>
>> This set of two patches aim at fixing some regression reported by two
>> users (Luis and Leigh), that were introduced by the conversion of the
>> pci-mvebu driver to the common PCI bridge emulation code shared
>> between pci-aardvark and pci-mvebu.
>>
>> Due to this conversion, some registers of the PCI configuration that
>> used to be read-only are now read-write, making the Linux PCI core
>> believe that some features are implemented by the PCI bridge. Namely
>> in the case of pci-mvebu, the prefetchable memory base/limit registers
>> were read-only, while they are now read-write. Due to this, the Linux
>> PCI core now believes it can configure a prefetchable memory area, but
>> this is not supported by pci-mvebu, which does not have the logic to
>> create the appropriate MBUs windows.
>>
>> This set of two commits allow PCI controller code to tell the PCI
>> bridge emulation logic about their capabilities. Because we envision
>> that other capabilities than prefetchable memory support might need to
>> be communicated from the PCI controller code to the PCI bridge
>> emulation code in the future, we introduce a "flags" argument, even if
>> for now only one flag is supported.
>>
>> Lorenzo, let me know what you think about this approach. I am open to
>> suggestions if the proposed approach is not satisfying.
>>
>> Both patches have been confirmed by Luis and Leigh to fix the
>> regression, but I'll let them give a formal Tested-by.
>>
>> Best regards,
>>
>> Thomas Petazzoni
>>
>> Thomas Petazzoni (2):
>> PCI: pci-bridge-emul: Create per-bridge copy of register behavior
>> PCI: pci-bridge-emul: Extend pci_bridge_emul_init() with flags
>>
>> drivers/pci/controller/pci-aardvark.c | 2 +-
>> drivers/pci/controller/pci-mvebu.c | 2 +-
>> drivers/pci/pci-bridge-emul.c | 86
>> ++++++++++++++++++---------
>> drivers/pci/pci-bridge-emul.h | 13 +++-
>> 4 files changed, 73 insertions(+), 30 deletions(-)
>
> Lorenzo, I assume you'll take both of these, so for both patches,
>
> Acked-by: Bjorn Helgaas <bhelgaas@google.com>
>
> Maybe we should add a stable tag (v4.20+)?
That would be great, as it would get that kernel version working again.
Regards,
Leigh.
next prev parent reply other threads:[~2019-02-22 8:11 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-02-20 9:48 [PATCH 0/2] PCI: fix pci-mvebu after conversion to common bridge emul code Thomas Petazzoni
2019-02-20 9:48 ` [PATCH 1/2] PCI: pci-bridge-emul: Create per-bridge copy of register behavior Thomas Petazzoni
2019-02-21 23:01 ` Luís Mendes
2019-02-20 9:48 ` [PATCH 2/2] PCI: pci-bridge-emul: Extend pci_bridge_emul_init() with flags Thomas Petazzoni
2019-02-21 23:03 ` Luís Mendes
2019-02-21 23:23 ` [PATCH 0/2] PCI: fix pci-mvebu after conversion to common bridge emul code Bjorn Helgaas
2019-02-22 8:11 ` Leigh Brown [this message]
2019-02-22 8:35 ` Thomas Petazzoni
2019-02-22 11:05 ` Lorenzo Pieralisi
2019-02-22 12:45 ` Thomas Petazzoni
2019-02-22 8:06 ` Leigh Brown
2019-02-22 11:22 ` Lorenzo Pieralisi
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=3ead4de3a0a5a0fe4aa5a76c92f01629@solinno.co.uk \
--to=leigh@solinno.co.uk \
--cc=andrew@lunn.ch \
--cc=gregory.clement@bootlin.com \
--cc=helgaas@kernel.org \
--cc=jason@lakedaemon.net \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-pci@vger.kernel.org \
--cc=linux@arm.linux.org.uk \
--cc=lorenzo.pieralisi@arm.com \
--cc=luis.p.mendes@gmail.com \
--cc=sebastian.hesselbarth@gmail.com \
--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).