From: linus.walleij@linaro.org (Linus Walleij)
To: linux-arm-kernel@lists.infradead.org
Subject: [GIT PULL] ux500 patches for v3.4
Date: Sun, 26 Feb 2012 10:41:16 +0100 [thread overview]
Message-ID: <CACRpkdbqsMOeA1BPo+0iWyZCTiaOJQ3Pr40-DGjO81Vkryhg0g@mail.gmail.com> (raw)
In-Reply-To: <201202241625.13080.arnd@arndb.de>
On Fri, Feb 24, 2012 at 5:25 PM, Arnd Bergmann <arnd@arndb.de> wrote:
> On Friday 24 February 2012, Linus Walleij wrote:
>> > Then you just need to find a convenient value for UX500_ASICID_VIRT
>> > that does not conflict with the other static mappings.
>>
>> But the problem is that the ASIC address is not
>> at all constant across ASIC variants. They are on different
>> places in the ROM for U8500, U5500. U9540... So as described
>> above we already know the main type of ASIC, but we need to
>> read this value to get the subvariant, process etc.
>>
>> So there is no such thing as UX500_ASICID_ADDR.
>>
>> Unless we defines it with #ifdefs and compile a kernel for just
>> U8500, U5500 or U9540 and that's mainly what we want to
>> get away from you know...
>
> My point was that you use the same virtual address here independent
> of which physical address is used. The physical address already gets
> passed into the function as its argument, we only need to map it
> to a convenient place in order to read it!
Oh sorry I'm slow in the head :-/
Yes that should work of course, I will attempt to make an additional
patch on top of these that consolidates the whole thing into one
function that does that.
Thanks Arnd!
Linus Walleij
prev parent reply other threads:[~2012-02-26 9:41 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-02-21 7:36 [GIT PULL] ux500 patches for v3.4 Linus Walleij
2012-02-21 17:00 ` Arnd Bergmann
2012-02-24 6:51 ` Linus Walleij
2012-02-24 15:23 ` Arnd Bergmann
2012-02-24 15:39 ` Linus Walleij
2012-02-24 16:25 ` Arnd Bergmann
2012-02-26 9:41 ` Linus Walleij [this message]
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=CACRpkdbqsMOeA1BPo+0iWyZCTiaOJQ3Pr40-DGjO81Vkryhg0g@mail.gmail.com \
--to=linus.walleij@linaro.org \
--cc=linux-arm-kernel@lists.infradead.org \
/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;
as well as URLs for NNTP newsgroup(s).