From: Murali Karicheri <m-karicheri2@ti.com>
To: Bjorn Helgaas <bhelgaas@google.com>
Cc: <linux-pci@vger.kernel.org>,
<linux-arm-kernel@lists.infradead.org>,
<linux-kernel@vger.kernel.org>, <jgunthorpe@obsidianresearch.com>
Subject: Re: [PATCH - v4] PCI: keystone: add a pci quirk to limit mrrs
Date: Wed, 17 Sep 2014 10:11:53 -0400 [thread overview]
Message-ID: <541996A9.306@ti.com> (raw)
In-Reply-To: <20140916215448.GB5050@google.com>
On 09/16/2014 05:54 PM, Bjorn Helgaas wrote:
> On Mon, Sep 08, 2014 at 01:03:34PM -0400, Murali Karicheri wrote:
>> Keystone PCI controller has a limitation that memory read request
>> size must not exceed 256 bytes. This is a hardware limitation and
>> add a quirk to force this limit on all downstream devices by
>> updating mrrs.
>>
>> Signed-off-by: Murali Karicheri<m-karicheri2@ti.com>
>
> Applied to pci/host-keystone for v3.18, thanks.
>
> I moved the pci-keystone.txt update regarding pci=pcie_bus_perf into this
> patch. This is where it belongs, isn't it? I'm pretty sure it wasn't
> related to setting the PCI device ID dynamically.
Yes. Thanks for taking care of the documentation part.
Thanks
Murali
>
>> ---
>> -v4: re-send removing extra lines
>> -v3: added check for vendor id and use pci_matc_id() to do matching
>> -v2: made the quirk happens after tuning
>> -v1: changed printk to indicate PCI bdf
>>
>> drivers/pci/host/pci-keystone.c | 45 +++++++++++++++++++++++++++++++++++++++
>> 1 file changed, 45 insertions(+)
>>
>> diff --git a/drivers/pci/host/pci-keystone.c b/drivers/pci/host/pci-keystone.c
>> index c1cfaef..ff8ed25 100644
>> --- a/drivers/pci/host/pci-keystone.c
>> +++ b/drivers/pci/host/pci-keystone.c
>> @@ -42,8 +42,53 @@
>> /* DEV_STAT_CTRL */
>> #define PCIE_CAP_BASE 0x70
>>
>> +/* PCIE controller device IDs */
>> +#define PCIE_RC_K2HK 0xb008
>> +#define PCIE_RC_K2E 0xb009
>> +#define PCIE_RC_K2L 0xb00a
>> +
>> #define to_keystone_pcie(x) container_of(x, struct keystone_pcie, pp)
>>
>> +static void quirk_limit_mrrs(struct pci_dev *dev)
>> +{
>> + struct pci_bus *bus = dev->bus;
>> + struct pci_dev *bridge = bus->self;
>> + static const struct pci_device_id rc_pci_devids[] = {
>> + { PCI_DEVICE(PCI_VENDOR_ID_TI, PCIE_RC_K2HK),
>> + .class = PCI_CLASS_BRIDGE_PCI<< 8, .class_mask = ~0, },
>> + { PCI_DEVICE(PCI_VENDOR_ID_TI, PCIE_RC_K2E),
>> + .class = PCI_CLASS_BRIDGE_PCI<< 8, .class_mask = ~0, },
>> + { PCI_DEVICE(PCI_VENDOR_ID_TI, PCIE_RC_K2L),
>> + .class = PCI_CLASS_BRIDGE_PCI<< 8, .class_mask = ~0, },
>> + { 0, },
>> + };
>> +
>> + if (pci_is_root_bus(bus))
>> + return;
>> +
>> + /* look for the host bridge */
>> + while (!pci_is_root_bus(bus)) {
>> + bridge = bus->self;
>> + bus = bus->parent;
>> + }
>> +
>> + if (bridge) {
>> + /*
>> + * Keystone PCI controller has a h/w limitation of
>> + * 256 bytes maximum read request size. It can't handle
>> + * anything higher than this. So force this limit on
>> + * all downstream devices
>> + */
>> + if (pci_match_id(rc_pci_devids, bridge)) {
>> + if (pcie_get_readrq(dev)> 256) {
>> + dev_info(&dev->dev, "limiting mrrs to 256\n");
>> + pcie_set_readrq(dev, 256);
>> + }
>> + }
>> + }
>> +}
>> +DECLARE_PCI_FIXUP_ENABLE(PCI_ANY_ID, PCI_ANY_ID, quirk_limit_mrrs);
>> +
>> static int ks_pcie_establish_link(struct keystone_pcie *ks_pcie)
>> {
>> struct pcie_port *pp =&ks_pcie->pp;
>> --
>> 1.7.9.5
>>
--
Murali Karicheri
Linux Kernel, Texas Instruments
WARNING: multiple messages have this Message-ID (diff)
From: m-karicheri2@ti.com (Murali Karicheri)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH - v4] PCI: keystone: add a pci quirk to limit mrrs
Date: Wed, 17 Sep 2014 10:11:53 -0400 [thread overview]
Message-ID: <541996A9.306@ti.com> (raw)
In-Reply-To: <20140916215448.GB5050@google.com>
On 09/16/2014 05:54 PM, Bjorn Helgaas wrote:
> On Mon, Sep 08, 2014 at 01:03:34PM -0400, Murali Karicheri wrote:
>> Keystone PCI controller has a limitation that memory read request
>> size must not exceed 256 bytes. This is a hardware limitation and
>> add a quirk to force this limit on all downstream devices by
>> updating mrrs.
>>
>> Signed-off-by: Murali Karicheri<m-karicheri2@ti.com>
>
> Applied to pci/host-keystone for v3.18, thanks.
>
> I moved the pci-keystone.txt update regarding pci=pcie_bus_perf into this
> patch. This is where it belongs, isn't it? I'm pretty sure it wasn't
> related to setting the PCI device ID dynamically.
Yes. Thanks for taking care of the documentation part.
Thanks
Murali
>
>> ---
>> -v4: re-send removing extra lines
>> -v3: added check for vendor id and use pci_matc_id() to do matching
>> -v2: made the quirk happens after tuning
>> -v1: changed printk to indicate PCI bdf
>>
>> drivers/pci/host/pci-keystone.c | 45 +++++++++++++++++++++++++++++++++++++++
>> 1 file changed, 45 insertions(+)
>>
>> diff --git a/drivers/pci/host/pci-keystone.c b/drivers/pci/host/pci-keystone.c
>> index c1cfaef..ff8ed25 100644
>> --- a/drivers/pci/host/pci-keystone.c
>> +++ b/drivers/pci/host/pci-keystone.c
>> @@ -42,8 +42,53 @@
>> /* DEV_STAT_CTRL */
>> #define PCIE_CAP_BASE 0x70
>>
>> +/* PCIE controller device IDs */
>> +#define PCIE_RC_K2HK 0xb008
>> +#define PCIE_RC_K2E 0xb009
>> +#define PCIE_RC_K2L 0xb00a
>> +
>> #define to_keystone_pcie(x) container_of(x, struct keystone_pcie, pp)
>>
>> +static void quirk_limit_mrrs(struct pci_dev *dev)
>> +{
>> + struct pci_bus *bus = dev->bus;
>> + struct pci_dev *bridge = bus->self;
>> + static const struct pci_device_id rc_pci_devids[] = {
>> + { PCI_DEVICE(PCI_VENDOR_ID_TI, PCIE_RC_K2HK),
>> + .class = PCI_CLASS_BRIDGE_PCI<< 8, .class_mask = ~0, },
>> + { PCI_DEVICE(PCI_VENDOR_ID_TI, PCIE_RC_K2E),
>> + .class = PCI_CLASS_BRIDGE_PCI<< 8, .class_mask = ~0, },
>> + { PCI_DEVICE(PCI_VENDOR_ID_TI, PCIE_RC_K2L),
>> + .class = PCI_CLASS_BRIDGE_PCI<< 8, .class_mask = ~0, },
>> + { 0, },
>> + };
>> +
>> + if (pci_is_root_bus(bus))
>> + return;
>> +
>> + /* look for the host bridge */
>> + while (!pci_is_root_bus(bus)) {
>> + bridge = bus->self;
>> + bus = bus->parent;
>> + }
>> +
>> + if (bridge) {
>> + /*
>> + * Keystone PCI controller has a h/w limitation of
>> + * 256 bytes maximum read request size. It can't handle
>> + * anything higher than this. So force this limit on
>> + * all downstream devices
>> + */
>> + if (pci_match_id(rc_pci_devids, bridge)) {
>> + if (pcie_get_readrq(dev)> 256) {
>> + dev_info(&dev->dev, "limiting mrrs to 256\n");
>> + pcie_set_readrq(dev, 256);
>> + }
>> + }
>> + }
>> +}
>> +DECLARE_PCI_FIXUP_ENABLE(PCI_ANY_ID, PCI_ANY_ID, quirk_limit_mrrs);
>> +
>> static int ks_pcie_establish_link(struct keystone_pcie *ks_pcie)
>> {
>> struct pcie_port *pp =&ks_pcie->pp;
>> --
>> 1.7.9.5
>>
--
Murali Karicheri
Linux Kernel, Texas Instruments
next prev parent reply other threads:[~2014-09-17 14:11 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-09-08 17:03 [PATCH - v4] PCI: keystone: add a pci quirk to limit mrrs Murali Karicheri
2014-09-08 17:03 ` Murali Karicheri
2014-09-11 19:07 ` Murali Karicheri
2014-09-11 19:07 ` Murali Karicheri
2014-09-16 21:54 ` Bjorn Helgaas
2014-09-16 21:54 ` Bjorn Helgaas
2014-09-17 14:11 ` Murali Karicheri [this message]
2014-09-17 14:11 ` Murali Karicheri
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=541996A9.306@ti.com \
--to=m-karicheri2@ti.com \
--cc=bhelgaas@google.com \
--cc=jgunthorpe@obsidianresearch.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pci@vger.kernel.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.