From: robert.jarzmik@free.fr (Robert Jarzmik)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH] Revert "ARM: pxa: call debug_ll_io_init for earlyprintk"
Date: Mon, 06 Oct 2014 21:29:36 +0200 [thread overview]
Message-ID: <87a959aten.fsf@free.fr> (raw)
In-Reply-To: <87egulausv.fsf@free.fr> (Robert Jarzmik's message of "Mon, 06 Oct 2014 20:59:28 +0200")
Robert Jarzmik <robert.jarzmik@free.fr> writes:
> Dmitry Eremin-Solenikov <dbaryshkov@gmail.com> writes:
>
>> This reverts commit 2111667b4677 ("ARM: pxa: call debug_ll_io_init for
>> earlyprintk")
>>
>> This commit gives the following backtrace on PXA/tosa early in the boot
>> time when DEBUG_LL is enabled. It is due to overlap between uart memory
>> and PERIPH_ memory block mapped by pxa_map_io.
>
> Indeed, all available UARTs IO mappings are already covered by pxa_map_io(), so
> the revert will remove the bug and keep the DEBUG_LL functionality. I suppose
> you did the test with the revert and the lowlevel debugging works, right ?
Actually, I have a question for Andrew : was your commit aimed at the 3 or 4
available UARTs (ie. in peripheral address space), or is it a case where an
external UART is mapped on the system bus (if that is possible) ?
--
Robert
next prev parent reply other threads:[~2014-10-06 19:29 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-10-06 13:32 [PATCH] Revert "ARM: pxa: call debug_ll_io_init for earlyprintk" Dmitry Eremin-Solenikov
2014-10-06 18:59 ` Robert Jarzmik
2014-10-06 19:29 ` Robert Jarzmik [this message]
2014-10-06 21:02 ` Andrew Ruder
2014-10-06 21:18 ` Arnd Bergmann
2014-10-06 21:44 ` Robert Jarzmik
2014-10-06 21:59 ` Andrew Ruder
2014-10-07 9:18 ` Arnd Bergmann
2014-10-07 19:33 ` Robert Jarzmik
2014-10-07 21:36 ` Arnd Bergmann
2014-10-12 13:37 ` Robert Jarzmik
2014-10-13 22:17 ` Andrew Ruder
2014-10-19 19:19 ` Robert Jarzmik
2014-10-06 21:55 ` Andrew Ruder
2014-10-06 19:30 ` Arnd Bergmann
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=87a959aten.fsf@free.fr \
--to=robert.jarzmik@free.fr \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.