linux-arm-kernel.lists.infradead.org archive mirror
 help / color / mirror / Atom feed
From: t.figa@samsung.com (Tomasz Figa)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH 2/2] arm: add early_ioremap support
Date: Tue, 22 Jul 2014 19:27:08 +0200	[thread overview]
Message-ID: <53CE9EEC.4080709@samsung.com> (raw)
In-Reply-To: <CAL_Jsq+hRYySuT_40iGVwe-8GYuPBmHy+GbqQ6T5HSCDfCSMQw@mail.gmail.com>

On 22.07.2014 19:11, Rob Herring wrote:
> On Tue, Jul 22, 2014 at 11:48 AM, Tomasz Figa <t.figa@samsung.com> wrote:
>> Hi Leif,
>>
>> On 09.07.2014 11:39, Leif Lindholm wrote:
>>> From: Mark Salter <msalter@redhat.com>
>>>
>>> This patch uses the generic early_ioremap code to implement
>>> early_ioremap for ARM. The ARM-specific bits come mostly from
>>> an earlier patch from Leif Lindholm <leif.lindholm@linaro.org>
>>> here:
>>>
>>>   https://lkml.org/lkml/2013/10/3/279
>>
>> [snip]
>>
>>> diff --git a/arch/arm/mm/early_ioremap.c b/arch/arm/mm/early_ioremap.c
>>> new file mode 100644
>>> index 0000000..1013109
>>> --- /dev/null
>>> +++ b/arch/arm/mm/early_ioremap.c
>>> @@ -0,0 +1,86 @@
>>> +/*
>>> + * early_ioremap() support for ARM
>>> + *
>>> + * Based on existing support in arch/x86/mm/ioremap.c
>>> + *
>>> + * Restrictions: currently only functional before paging_init()
>>
>> Uhm, that's bad... This would explain why my earlycon code generates a
>> fault as soon as something prints after paging_init(). I'd say this
>> feature would be much more useful if mappings were carried over
>> paging_init(), so that mapped devices are available later as well.
>>
>> I'll see if I can code this on top of your patch, but unfortunately it
>> might end up with -ENOTIME.
> 
> I have fixmap support that's needed for earlycon. Here is the branch:
> 
> git://git.kernel.org/pub/scm/linux/kernel/git/robh/linux.git fixmap
> 
> It is based on an earlier version of patchset and not on the latest
> version from Leif. Unfortunately, I don't have more time to spend on
> it ATM.

Thanks Rob. I'll give it a try.

Best regards,
Tomasz

  reply	other threads:[~2014-07-22 17:27 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-07-09  9:39 [PATCH 0/2] arm: add early_ioremap support Leif Lindholm
2014-07-09  9:39 ` [PATCH 1/2] arm: use generic fixmap.h Leif Lindholm
2014-07-09 20:49   ` Mark Salter
2014-07-18 14:33     ` Leif Lindholm
2014-07-25 19:56       ` Kees Cook
2014-07-22 16:39   ` Tomasz Figa
2014-07-09  9:39 ` [PATCH 2/2] arm: add early_ioremap support Leif Lindholm
2014-07-09  9:49   ` Russell King - ARM Linux
2014-07-09 11:48     ` Leif Lindholm
2014-07-22 16:48   ` Tomasz Figa
2014-07-22 17:11     ` Rob Herring
2014-07-22 17:27       ` Tomasz Figa [this message]
2014-07-09  9:42 ` [PATCH 0/2] " Russell King - ARM Linux
2014-07-09  9:58   ` Leif Lindholm
2014-07-09  9:47 ` Will Deacon
2014-07-09 10:02   ` Leif Lindholm
  -- strict thread matches above, loose matches on Subject: below --
2013-06-25 17:46 [PATCH 0/2] arm: add early_ioremap() support Leif Lindholm
2013-06-25 17:46 ` [PATCH 2/2] arm: add early_ioremap support Leif Lindholm

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=53CE9EEC.4080709@samsung.com \
    --to=t.figa@samsung.com \
    --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).