linuxppc-dev.lists.ozlabs.org archive mirror
 help / color / mirror / Atom feed
From: Kleber Sacilotto de Souza <klebers@linux.vnet.ibm.com>
To: linuxppc-dev@lists.ozlabs.org, dri-devel@lists.freedesktop.org,
	Benjamin Herrenschmidt <benh@kernel.crashing.org>,
	Bjorn Helgaas <bhelgaas@google.com>,
	David Airlie <airlied@linux.ie>,
	Michael Ellerman <michael@ellerman.id.au>
Cc: Brian King <brking@linux.vnet.ibm.com>,
	Alex Deucher <alexander.deucher@amd.com>,
	Jerome Glisse <jglisse@redhat.com>,
	Thadeu Lima de Souza Cascardo <cascardo@linux.vnet.ibm.com>,
	Kleber Sacilotto de Souza <klebers@linux.vnet.ibm.com>
Subject: [PATCHv5 0/2] Speed Cap fixes for ppc64
Date: Fri,  3 May 2013 19:43:11 -0300	[thread overview]
Message-ID: <1367620993-27037-1-git-send-email-klebers@linux.vnet.ibm.com> (raw)

This v5 of the patch series is based on v4 sent by Lucas Kannebley Tavares
with a few changes:

  1. Fix a compilation warning on the code from the first patch, where it was
missing a declaration of struct pci_host_bridge, used on the definition of
the function pointer pcibios_root_bridge_prepare() in
arch/powerpc/include/asm/machdep.h.
  2. Incorporate some changes proposed by Tony Breeds in
pseries_root_bridge_prepare().

The following description of the changes was extrated from v4:

This patch series does:
  1. max_bus_speed is used to set the device to gen2 speeds
  2. on power there's no longer a conflict between the pseries call and other
architectures, because the overwrite is done via a ppc_md hook
  3. radeon is using bus->max_bus_speed instead of drm_pcie_get_speed_cap_mask
for gen2 capability detection

The first patch consists of some architecture changes, such as adding a hook on
powerpc for pci_root_bridge_prepare, so that pseries will initialize it to a
function, while all other architectures get a NULL pointer. So that whenever
pci_create_root_bus is called, we'll get max_bus_speed properly setup from
OpenFirmware.

The second patch consists of simple radeon changes not to call
drm_get_pcie_speed_cap_mask anymore. I assume that on x86 machines,
the max_bus_speed property will be properly set already.

Kleber Sacilotto de Souza (2):
  ppc64: perform proper max_bus_speed detection
  radeon: use max_bus_speed to activate gen2 speeds

 arch/powerpc/include/asm/machdep.h       |    3 ++
 arch/powerpc/kernel/pci-common.c         |    8 ++++
 arch/powerpc/platforms/pseries/pci.c     |   53 ++++++++++++++++++++++++++++++
 arch/powerpc/platforms/pseries/pseries.h |    4 ++
 arch/powerpc/platforms/pseries/setup.c   |    2 +
 drivers/gpu/drm/radeon/evergreen.c       |   10 ++----
 drivers/gpu/drm/radeon/r600.c            |    9 +----
 drivers/gpu/drm/radeon/rv770.c           |    9 +----
 8 files changed, 77 insertions(+), 21 deletions(-)

             reply	other threads:[~2013-05-03 22:43 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-05-03 22:43 Kleber Sacilotto de Souza [this message]
2013-05-03 22:43 ` [PATCHv5 1/2] ppc64: perform proper max_bus_speed detection Kleber Sacilotto de Souza
2013-05-03 22:43 ` [PATCHv5 2/2] radeon: use max_bus_speed to activate gen2 speeds Kleber Sacilotto de Souza
2013-05-03 23:01 ` [PATCHv5 0/2] Speed Cap fixes for ppc64 Benjamin Herrenschmidt
2013-05-06 14:32   ` Alex Deucher
2013-05-06 14:33     ` Jerome Glisse
2013-05-15 12:35     ` Kleber Sacilotto de Souza
2013-05-15 12:58       ` Alex Deucher
2013-05-15 13:12         ` Kleber Sacilotto de Souza

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=1367620993-27037-1-git-send-email-klebers@linux.vnet.ibm.com \
    --to=klebers@linux.vnet.ibm.com \
    --cc=airlied@linux.ie \
    --cc=alexander.deucher@amd.com \
    --cc=benh@kernel.crashing.org \
    --cc=bhelgaas@google.com \
    --cc=brking@linux.vnet.ibm.com \
    --cc=cascardo@linux.vnet.ibm.com \
    --cc=dri-devel@lists.freedesktop.org \
    --cc=jglisse@redhat.com \
    --cc=linuxppc-dev@lists.ozlabs.org \
    --cc=michael@ellerman.id.au \
    /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).