From: Ayman El-Khashab <ayman@elkhashab.com>
To: Benjamin Herrenschmidt <benh@kernel.crashing.org>,
Paul Mackerras <paulus@samba.org>,
Tony Breeds <tony@bakeyournoodle.com>,
linuxppc-dev@lists.ozlabs.org, linux-kernel@vger.kernel.org
Cc: Ayman El-Khashab <ayman@elkhashab.com>
Subject: [PATCH 0/1] powerpc/4xx: enable and fix pcie gen1/gen2 on the 460sx
Date: Wed, 13 Jul 2011 19:33:30 -0500 [thread overview]
Message-ID: <1310603611-8960-1-git-send-email-ayman@elkhashab.com> (raw)
In-Reply-To: <y>
Old code didn't check the proper registers for the 460sx and so the link check
would always fail. This changes the link check to use the config space reg and
adds the definition for the register. Also changes the vc0 to a pll check.
Sets up the port for gen2 speeds.
This uses the check_link function to specialize the link detect for the 460sx.
Tested on an eiger and custom board. Note that is swaps the order of the link
check and dcr initialization since the config space needs the DCRs setup before
it can be mapped and used to check the link.
Ayman El-Khashab (1):
powerpc/4xx: enable and fix pcie gen1/gen2 on the 460sx
arch/powerpc/sysdev/ppc4xx_pci.c | 83 +++++++++++++++++++++++++++++--------
arch/powerpc/sysdev/ppc4xx_pci.h | 3 +
2 files changed, 68 insertions(+), 18 deletions(-)
--
1.7.4.3
next reply other threads:[~2011-07-14 0:39 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-07-14 0:33 Ayman El-Khashab [this message]
2011-07-14 0:33 ` [PATCH 1/1] " Ayman El-Khashab
2011-07-14 1:16 ` Tony Breeds
2011-07-14 16:04 ` Ayman El-Khashab
2011-07-14 22:36 ` Benjamin Herrenschmidt
2011-07-15 16:40 ` [v2 PATCH " Ayman Elkhashab
2011-07-18 4:01 ` Tony Breeds
2011-07-18 13:31 ` Ayman El-Khashab
2011-07-19 1:23 ` Tony Breeds
2011-07-20 13:02 ` [v3 PATCH 0/1] " Ayman Elkhashab
2011-07-20 13:02 ` [v3 PATCH 1/1] " Ayman Elkhashab
2011-07-21 0:59 ` Tony Breeds
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=1310603611-8960-1-git-send-email-ayman@elkhashab.com \
--to=ayman@elkhashab.com \
--cc=benh@kernel.crashing.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linuxppc-dev@lists.ozlabs.org \
--cc=paulus@samba.org \
--cc=tony@bakeyournoodle.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
all inboxes | Powered by JetHome®