From: Stefan Roese <sr@denx.de>
To: u-boot@lists.denx.de
Subject: [U-Boot] [PATCH] dm: core: Enable optional use of fdt_translate_address()
Date: Thu, 10 Sep 2015 07:54:32 +0200 [thread overview]
Message-ID: <55F11B18.2010002@denx.de> (raw)
In-Reply-To: <CAPnjgZ0=xpxrE6znHLki6Y3otwMjz+HAcb6uTGZ+NqKT_UyLPQ@mail.gmail.com>
Hi Simon,
On 09.09.2015 20:07, Simon Glass wrote:
> On Thursday, 3 September 2015, Stefan Roese <sr@denx.de> wrote:
>>
>> The current "simple" address translation simple_bus_translate() is not
>> working on some platforms (e.g. MVEBU). As here more complex "ranges"
>> properties are used in many nodes (multiple tuples etc). This patch
>> enables the optional use of the common fdt_translate_address() function
>> which handles this translation correctly.
>>
>> Signed-off-by: Stefan Roese <sr@denx.de>
>> Cc: Simon Glass <sjg@chromium.org>
>> Cc: Bin Meng <bmeng.cn@gmail.com>
>> Cc: Marek Vasut <marex@denx.de>
>> Cc: Masahiro Yamada <yamada.masahiro@socionext.com>
>> ---
>> v2:
>> - Rework code a bit as suggested by Simon. Also added some comments
>> to make the use of the code paths more clear.
>
>
> While this works I'm reluctant to commit it as is. The call to
> fdt_parent_offset() is very slow.
You've mentioned this before. But how slow could this function really
be? And it should not be called that often via dev_get_addr(). Usually
only once for each driver in the probe function. Or am I missing something?
> I wonder if this code should be copied into a new file in
> drivers/core/, tidied up and updated to use dev->parent?
You mean fdt_translate_address()? It references many functions from
fdt_support.c though which we would need to duplicate here as well.
> Other options:
> - Add a library to unflatten the tree - but this would not be very
> useful in SPL or before relocation due to memory/speed constraints
> - Add a helper to find a node parent which uses a cached tree scan to
> build a table of previous nodes (or some other means to go backwards
> in the tree)
> - Worry about it later and go ahead with this patch
I see no problems to defer this patch (or a "better" version of it) to
after this release. The Marvell mvebu DM patches are also not targeted
for this release.
Thanks,
Stefan
next prev parent reply other threads:[~2015-09-10 5:54 UTC|newest]
Thread overview: 30+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-09-02 6:22 [U-Boot] [PATCH] dm: core: Enable optional use of fdt_translate_address() Stefan Roese
2015-09-04 3:56 ` Simon Glass
2015-09-04 5:11 ` [U-Boot] [PATCH v2] " Stefan Roese
2015-09-09 18:07 ` [U-Boot] [PATCH] " Simon Glass
2015-09-10 5:54 ` Stefan Roese [this message]
2015-09-11 0:42 ` Simon Glass
2015-09-11 5:41 ` Stefan Roese
2015-09-11 17:07 ` Stephen Warren
2015-09-14 5:25 ` Stefan Roese
2015-09-21 18:06 ` Stephen Warren
2015-10-03 12:50 ` Simon Glass
2015-10-03 19:17 ` Stephen Warren
2015-10-04 1:02 ` Simon Glass
2015-10-04 7:35 ` Stefan Roese
2015-10-04 11:38 ` Thomas Chou
2015-10-05 1:22 ` Stephen Warren
2015-10-06 14:17 ` Simon Glass
2015-09-15 7:31 ` [U-Boot] [PATCH v2] " Thomas Chou
2015-09-30 5:00 ` [U-Boot] [PATCH v3] " Stefan Roese
2015-09-30 16:13 ` Stephen Warren
2015-10-01 6:59 ` Stefan Roese
2015-10-03 12:53 ` Simon Glass
2015-10-18 23:16 ` Simon Glass
2015-12-03 13:34 ` Bin Meng
2015-12-03 14:12 ` Stefan Roese
2015-12-03 16:59 ` Stephen Warren
2015-12-04 5:31 ` Bin Meng
2015-12-04 6:17 ` Bin Meng
2015-12-04 7:52 ` Stefan Roese
2015-12-04 15:01 ` Bin Meng
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=55F11B18.2010002@denx.de \
--to=sr@denx.de \
--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