linux-arm-kernel.lists.infradead.org archive mirror
 help / color / mirror / Atom feed
From: jgunthorpe@obsidianresearch.com (Jason Gunthorpe)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH] ARM: pci: add call to pcie_bus_configure_settings()
Date: Wed, 28 May 2014 10:58:56 -0600	[thread overview]
Message-ID: <20140528165856.GA20193@obsidianresearch.com> (raw)
In-Reply-To: <1401287176-4986-1-git-send-email-m-karicheri2@ti.com>

On Wed, May 28, 2014 at 10:26:16AM -0400, Murali Karicheri wrote:
> PCI core supports PCIE_BUS_SAFE and PCIE_BUS_PERFORMANCE modes.
> PCI controllers may not be able to handle pay load size higher
> than MPS and also read data size higher than MRSS. So limit the
> max to the least common supported payload size by calling
> pcie_bus_configure_settings(). Using pci=pcie_bus_safe do a walk
> and set the MPS to least common value used by devices on the bus.
> pci=pcie_bus_perf does do a walk and set MRSS to MPS.

This text doesn't make much sense.. Calling
pcie_bus_configure_settings is just a good thing to do, the fact it
helps avoid a HW defect in a specific PCI-E implementation is not the
main reason to add this to the core ARM code.

 Call pcie_bus_configure_settings on ARM, like for other
 platforms. pcie_bus_configure_settings makes sure the MPS across the
 bus is uniform and provides the ability to tune the MRSS and MPS to
 higher performance values.

 This is particularly important for embedded where there is no
 firmware to program these PCI-E settings for the OS.

> +
> +			list_for_each_entry(child, &bus->children, node)
> +			pcie_bus_configure_settings(child);
                  ^^^^^^^^^^^^^^^

Missing indent.

Regards,
Jason

  reply	other threads:[~2014-05-28 16:58 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-05-28 14:26 [PATCH] ARM: pci: add call to pcie_bus_configure_settings() Murali Karicheri
2014-05-28 16:58 ` Jason Gunthorpe [this message]
2014-05-28 17:14   ` 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=20140528165856.GA20193@obsidianresearch.com \
    --to=jgunthorpe@obsidianresearch.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;
as well as URLs for NNTP newsgroup(s).