From: Stephen Warren <swarren@wwwdotorg.org>
To: u-boot@lists.denx.de
Subject: [U-Boot] [PATCH] Revert "fdt: Fix fdtdec_get_addr_size() for 64-bit"
Date: Mon, 03 Aug 2015 09:12:35 -0600 [thread overview]
Message-ID: <55BF84E3.7010108@wwwdotorg.org> (raw)
In-Reply-To: <1438560830-31221-1-git-send-email-sjg@chromium.org>
On 08/02/2015 06:13 PM, Simon Glass wrote:
> This reverts commit 5b34436035fc862b5e8d0d2c3eab74ba36f1a7f4.
>
> This function has a few problems. It calls fdt_parent_offset() which as
> mentioned in code review is very slow.
>
> https://patchwork.ozlabs.org/patch/499482/
> https://patchwork.ozlabs.org/patch/452604/
>
> It also happens to break SPI flash on Minnowboard max which is how I noticed
> that this was applied. I can send a patch to tidy that up, but in any case
> I think we should consider a revert until the function is better implemented.
The fact that the function needs to perform a slow operation is not a
good reason for a revert. The slowness of the operation is just a matter
of fact with DT not having uplinks in its data structure, and U-Boot
using those data structures directly.
You'd requested during review that I additionally implement a faster
version of the function in the case where the parent node is already
known, and said it was fine if that happened in a later patch. I have
this on my TODO list, but it's only been a couple of days.
Why not just fix the bug since you said you could? That seems far better
than breaking the newly added Tegra210 support.
P.S. What is the issue with SPI flash? The commit description doesn't
mention this at all.
next prev parent reply other threads:[~2015-08-03 15:12 UTC|newest]
Thread overview: 34+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-08-03 0:13 [U-Boot] [PATCH] Revert "fdt: Fix fdtdec_get_addr_size() for 64-bit" Simon Glass
2015-08-03 15:12 ` Stephen Warren [this message]
2015-08-03 15:52 ` Simon Glass
2015-08-03 17:25 ` Tom Rini
2015-08-03 17:27 ` Simon Glass
2015-08-03 18:20 ` Stephen Warren
2015-08-05 4:08 ` Simon Glass
2015-08-05 18:22 ` Stephen Warren
2015-08-05 23:45 ` Simon Glass
2015-08-06 7:09 ` Michal Suchanek
2015-08-06 18:43 ` Stephen Warren
2015-08-06 19:03 ` Stephen Warren
2015-08-09 15:08 ` Simon Glass
2015-08-14 8:10 ` Bin Meng
2015-08-14 8:32 ` Thierry Reding
2015-08-14 8:44 ` Bin Meng
2015-08-14 14:06 ` Thierry Reding
2015-08-14 14:29 ` Bin Meng
2015-08-14 9:01 ` Michal Suchanek
2015-08-14 9:08 ` Bin Meng
2015-08-14 10:04 ` Simon Glass
2015-09-02 16:52 ` Tom Warren
2015-09-02 16:58 ` Simon Glass
2015-09-02 20:04 ` Stephen Warren
2015-09-02 20:39 ` Tom Warren
2015-09-02 20:54 ` Stephen Warren
2015-09-02 23:43 ` Stephen Warren
2015-09-03 2:02 ` Tom Warren
2015-09-16 21:46 ` Tom Warren
2015-09-17 1:10 ` Simon Glass
2015-09-17 1:58 ` Tom Warren
2015-08-14 16:50 ` Simon Glass
2015-08-03 15:40 ` Bin Meng
2015-08-04 15:27 ` 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=55BF84E3.7010108@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