From: Stefan Roese <sr@denx.de>
To: u-boot@lists.denx.de
Subject: [U-Boot] [PATCH] dm: core: Add platform specific bus translation function
Date: Wed, 2 Dec 2015 18:43:29 +0100 [thread overview]
Message-ID: <565F2DC1.7040608@denx.de> (raw)
In-Reply-To: <CAPnjgZ1PQQG9=HeheZdU_PYizuPKxFezmNbq51ZnF51-oZ8oOg@mail.gmail.com>
Hi Simon,
( Last mail for tonight - a glass of quite nice red wine is
waiting for me ... ;) )
On 02.12.2015 17:53, Simon Glass wrote:
> Hi Stefan,
>
> On 2 December 2015 at 09:00, Stefan Roese <sr@denx.de> wrote:
>>
>> Hi Simon,
>>
>> On 02.12.2015 16:50, Simon Glass wrote:
>>
>> <snip>
>>
>>>>> I think it would be better to make it depend on whether the bit is
>>>>> flipped, rather than whether you are in SPL or not.
>>>>
>>>>
>>>> You simply can't detect if this "bit is flipped". You just have
>>>> to know. This is a long lasting ugly thing on some Marvell
>>>> patforms. Here the comment from armada-xp-gp.dts:
>>>
>>>
>>> Can you point me to the place in U-Boot where this bit is flipped?
>>> Something, somewhere has to make the change. So something has to know.
>>> Before it makes the change, the range works one way. Afterwards it
>>> works another way.
>>
>>
>> Sure. I've mentioned this before. Its here:
>>
>> arch/arm/mach-mvebu/cpu.c:
>>
>> int arch_cpu_init(void)
>> {
>> ...
>>
>> /* Linux expects the internal registers to be at 0xf1000000 */
>> writel(SOC_REGS_PHY_BASE, INTREG_BASE_ADDR_REG);
>>
>> This is the line that changes the register base address. And
>> to change it back you need to write to the new address, as the
>> address holding this base address is also moved. Quite ugly!
>>
>> So its really right at the start of U-Boot proper.
>
> OK I see. So really we can determine which way the address 'switch'
> it. It's just a case of making the change when we are ready, and
> keeping a record of that.
Yes. But how is the "common code" in dev_get_addr() supposed to know
which version of U-Boot we are running on? This boils down to some
callback again, or not? Or even worse the ugly #ifdef.
Thanks,
Stefan
next prev parent reply other threads:[~2015-12-02 17:43 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-11-27 10:22 [U-Boot] [PATCH] dm: core: Add platform specific bus translation function Stefan Roese
2015-11-27 18:36 ` Simon Glass
2015-11-30 6:52 ` Stefan Roese
2015-11-30 23:17 ` Simon Glass
2015-12-01 6:05 ` Stefan Roese
2015-12-01 20:02 ` Simon Glass
2015-12-02 14:11 ` Stefan Roese
2015-12-02 14:49 ` Simon Glass
2015-12-02 15:24 ` Stefan Roese
2015-12-02 15:50 ` Simon Glass
2015-12-02 16:00 ` Stefan Roese
2015-12-02 16:53 ` Simon Glass
2015-12-02 17:43 ` Stefan Roese [this message]
2015-12-02 17:45 ` Simon Glass
2015-12-03 11:31 ` Stefan Roese
2015-12-03 17:21 ` Simon Glass
2015-12-04 7:45 ` Stefan Roese
2015-12-08 2:46 ` Simon Glass
2015-12-10 6:58 ` Stefan Roese
2015-12-10 15:36 ` Simon Glass
2015-12-11 4:45 ` Stefan Roese
2015-12-11 5:54 ` Stefan Roese
2015-12-11 13:30 ` Simon Glass
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=565F2DC1.7040608@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