From: Stephen Warren <swarren@wwwdotorg.org>
To: u-boot@lists.denx.de
Subject: [U-Boot] [PATCH] fdt: fix fdtdec_get_pci_addr() for CONFIG_PHYS_64BIT
Date: Wed, 21 Oct 2015 10:31:26 -0600 [thread overview]
Message-ID: <5627BDDE.3080505@wwwdotorg.org> (raw)
In-Reply-To: <CAPnjgZ35iUPdjfkchgJ+Qz_ZA4Haey=-quQ4HH5TY76DiB1BbQ@mail.gmail.com>
On 10/03/2015 08:30 AM, Simon Glass wrote:
> On 3 October 2015 at 00:44, Stephen Warren <swarren@wwwdotorg.org> wrote:
>> From: Stephen Warren <swarren@nvidia.com>
>>
>> PCI addresses are always represented as 3 cells in DT. (one cell for bus
>> and device, and two cells for a 64-bit addres). This does not vary based
>> on either the physical address size of the CPU, nor any #address-cells
>> property in DT (or more precisely, #address-cells must be set to 3 in any
>> PCIe controller's node).
>>
>> Fix fdtdec_get_pci_addr() to use conversion functions that operate on
>> (fixed) cell-sized data rather than (varying) physical-address-sized
>> data, so that the function works on 64-bit systems.
>>
>> Signed-off-by: Stephen Warren <swarren@nvidia.com>
>> ---
>> lib/fdtdec.c | 14 +++++++-------
>> 1 file changed, 7 insertions(+), 7 deletions(-)
>
> Acked-by: Simon Glass <sjg@chromium.org>
Simon, this patch appears to be assigned to you in patchwork. Will you
apply it now the merge window is open, or are you assuming it will go
through the Tegra tree with all the PCIe patches?
next prev parent reply other threads:[~2015-10-21 16:31 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-10-02 23:44 [U-Boot] [PATCH] fdt: fix fdtdec_get_pci_addr() for CONFIG_PHYS_64BIT Stephen Warren
2015-10-03 14:30 ` Simon Glass
2015-10-21 16:31 ` Stephen Warren [this message]
2015-10-21 20:42 ` Simon Glass
2015-10-26 13:26 ` Simon Glass
2015-10-06 9:56 ` Thierry Reding
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=5627BDDE.3080505@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