public inbox for u-boot@lists.denx.de
 help / color / mirror / Atom feed
From: Stephen Warren <swarren@wwwdotorg.org>
To: u-boot@lists.denx.de
Subject: [U-Boot] [PATCH 1/2] ARM: tegra: add PCI to Tegra210 SoC DT
Date: Wed, 21 Oct 2015 10:42:01 -0600	[thread overview]
Message-ID: <5627C059.7080702@wwwdotorg.org> (raw)
In-Reply-To: <1444086160-30298-1-git-send-email-swarren@wwwdotorg.org>

On 10/05/2015 05:02 PM, Stephen Warren wrote:
> From: Stephen Warren <swarren@nvidia.com>
>
> Tegra210's PCI controller is largely identical to Tegra124, and hence
> shares the same binding. However, it has a unique compatible value due
> to the existence of at least one new HW bug that would prevent any driver
> for a previous HW version from operating correctly.
>
> Signed-off-by: Stephen Warren <swarren@nvidia.com>
> ---
> For this series to operate correctly, it relies on my previous patches for:
> - fdt: fix fdtdec_get_pci_addr() for CONFIG_PHYS_64BIT
> - net: rtl8169: Build warning fixes for 64-bit
>    (Compile warning only)
> - Enabling CONFIG_SYS_NONCACHED_MEMORY
> - ARM: tegra210: implement PLLE init procedure from TRM
> - Tegra210 XUSB padctl support
> - Tegra210 PCI controller support

Tom,

Is this series OK? I assume it's only waiting for all the dependencies 
to go in first.

      parent reply	other threads:[~2015-10-21 16:42 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-10-05 23:02 [U-Boot] [PATCH 1/2] ARM: tegra: add PCI to Tegra210 SoC DT Stephen Warren
2015-10-05 23:02 ` [U-Boot] [PATCH 2/2] ARM: tegra: enable PCI support of p2371-2180 Stephen Warren
2015-10-21 23:03   ` Tom Warren
2015-10-21 23:10     ` Stephen Warren
2015-10-21 23:24       ` Tom Warren
2015-10-22  1:51         ` Stephen Warren
2015-10-21 16:42 ` Stephen Warren [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=5627C059.7080702@wwwdotorg.org \
    --to=swarren@wwwdotorg.org \
    --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