public inbox for u-boot@lists.denx.de
 help / color / mirror / Atom feed
From: Tom Rini <trini@konsulko.com>
To: u-boot@lists.denx.de
Subject: [U-Boot] [U-Boot, v3, 2/2] vexpress64: Juno: Add initialisation code for Juno R1 PCIe host bridge.
Date: Mon, 19 Oct 2015 20:07:48 -0400	[thread overview]
Message-ID: <20151020000748.GD23893@bill-the-cat> (raw)
In-Reply-To: <1445249312-23292-3-git-send-email-Liviu.Dudau@foss.arm.com>

On Mon, Oct 19, 2015 at 11:08:32AM +0100, Liviu Dudau wrote:

> Juno R1 has an XpressRICH3 PCIe host bridge that needs to be initialised
> in order for the Linux kernel to be able to enumerate the bus. Add
> support code here that enables the host bridge, trains the links and
> sets up the Address Translation Tables.
> 
> Signed-off-by: Liviu Dudau <Liviu.Dudau@foss.arm.com>
> Tested-by: Ryan Harkin <ryan.harkin@linaro.org>

After tweaking so we always have the same prototype for
vexpress64_pcie_init,
Applied to u-boot/master, thanks!

-- 
Tom
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 836 bytes
Desc: Digital signature
URL: <http://lists.denx.de/pipermail/u-boot/attachments/20151019/e476ac42/attachment.sig>

      parent reply	other threads:[~2015-10-20  0:07 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-10-19 10:08 [U-Boot] [PATCH v3 0/2] vexpress64: Juno: Add support for PCIe on Juno Liviu Dudau
2015-10-19 10:08 ` [U-Boot] [PATCH v3 1/2] vexpress64: Juno: Declare all 8GB of RAM and make them visible to the kernel Liviu Dudau
2015-10-20  0:07   ` [U-Boot] [U-Boot, v3, " Tom Rini
2015-10-19 10:08 ` [U-Boot] [PATCH v3 2/2] vexpress64: Juno: Add initialisation code for Juno R1 PCIe host bridge Liviu Dudau
2015-10-19 10:27   ` Ryan Harkin
2015-10-20  0:07   ` Tom Rini [this message]

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=20151020000748.GD23893@bill-the-cat \
    --to=trini@konsulko.com \
    --cc=u-boot@lists.denx.de \
    /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