From: Stefan Roese <sr@denx.de>
To: u-boot@lists.denx.de
Subject: [U-Boot] [PATCH v3] dm: core: Enable optional use of fdt_translate_address()
Date: Thu, 3 Dec 2015 15:12:19 +0100 [thread overview]
Message-ID: <56604DC3.1030006@denx.de> (raw)
In-Reply-To: <CAEUhbmWAm9-5Fg_QA3LeKWK7-gGkxfHTJeZxogA28vME_rzdCg@mail.gmail.com>
Hi Bin,
On 03.12.2015 14:34, Bin Meng wrote:
> Hi Stefan, Simon,
>
> On Mon, Oct 19, 2015 at 7:16 AM, Simon Glass <sjg@chromium.org> wrote:
>> On 29 September 2015 at 23:00, 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>
>>> Cc: Stephen Warren <swarren@nvidia.com>
>>> Cc: Lukasz Majewski <l.majewski@samsung.com>
>>> ---
>>> v3:
>>> - Rebased on current U-Boot version
>>> - Added Stephen and Lukasz to Cc
>>>
>>> v2:
>>> - Rework code a bit as suggested by Simon. Also added some comments
>>> to make the use of the code paths more clear.
>>>
>>> drivers/core/Kconfig | 30 ++++++++++++++++++++++++++++++
>>> drivers/core/device.c | 20 ++++++++++++++++++++
>>> 2 files changed, 50 insertions(+)
>>
>> Applied to u-boot-dm, thanks!
>
> When testing Simon's patch [1], I found PCI UART on Intel Crown Bay no
> longer works. git bisect leads to this commit. Somehow I missed this
> patch before although I see the commit message get me cc'ed but the
> email did not bring to my attention.
>
> I see this patch introduced OF_TRANSLATE and by default set it to y.
> This makes the code logic in dev_get_addr() go through
> fdt_translate_address(), which breaks the things.
I'm a bit surprised that using the common fdt_translate_address()
function instead of the DM internal simple_bus_translate() causes
problems on your platform. Are you sure that the ranges are
described correctly in your dts? Is the dts a copy from the Linux
original one? Ah, probably not, since we're talking about x86
which has no DT support in Linux, right?
> Should we set
> OF_TRANSLATE to n by default? If set to y, this requires dts to have
> complete ranges property everywhere.
My understanding here is that x86 is a special case. As it doesn't
use the full-blown dts sources from Linux. But most likely some
"simple" ones, written exactly for U-Boot / DM.
I would still prefer to have this OF_TRANSLATE set to y as default.
As its needed for at least some platforms. But if we decide to
set it to n, I can live with it as well.
Thanks,
Stefan
next prev parent reply other threads:[~2015-12-03 14:12 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
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 [this message]
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=56604DC3.1030006@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