From: nico@fluxnic.net (Nicolas Pitre)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCHv3 2/2] msm: Support DEBUG_LL on MSM8660 and MSM8960
Date: Tue, 08 Nov 2011 14:08:58 -0500 (EST) [thread overview]
Message-ID: <alpine.LFD.2.02.1111081406220.3307@xanadu.home> (raw)
In-Reply-To: <1320777184-22446-3-git-send-email-sboyd@codeaurora.org>
On Tue, 8 Nov 2011, Stephen Boyd wrote:
> Add support for DEBUG_LL on the 8660 and 8960 development boards.
> While we're here cleanup the uncompress.h code a bit. Avoid
> the use of readl/writel as those are Linux specific APIs that
> aren't guaranteed to work in the decompressor.
>
> Cc: Nicolas Pitre <nico@fluxnic.net>
> Signed-off-by: Stephen Boyd <sboyd@codeaurora.org>
Acked-by: Nicolas Pitre <nico@linaro.org>
Independently from this patch, I was wondering about this code:
> + .macro senduart, rd, rx
> +#ifdef CONFIG_MSM_HAS_DEBUG_UART_HS
> + @ Write the 1 character to UARTDM_TF
> + str \rd, [\rx, #0x70]
> +#else
> teq \rx, #0
> strne \rd, [\rx, #0x0C]
> +#endif
> .endm
Why testing for zero in the #else part? The upper level code should
never call this macro with a null byte.
Nicolas
next prev parent reply other threads:[~2011-11-08 19:08 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-11-08 18:33 [PATCHv3 0/2] MSM8660/8960 DEBUG_LL support and cleanups Stephen Boyd
2011-11-08 18:33 ` [PATCHv3 1/2] ARM: msm: Consolidate and move DEBUG_LL to DEBUG_LL choice Stephen Boyd
2011-11-08 18:33 ` [PATCHv3 2/2] msm: Support DEBUG_LL on MSM8660 and MSM8960 Stephen Boyd
2011-11-08 19:08 ` Nicolas Pitre [this message]
2011-11-08 19:14 ` Stephen Boyd
2011-11-08 19:59 ` David Brown
2011-11-08 20:22 ` Nicolas Pitre
2011-11-09 4:11 ` Stephen Boyd
2011-12-05 18:27 ` [PATCHv3 3/2] ARM: msm: Drop useless teq from DEBUG_LL support Stephen Boyd
2011-12-05 18:40 ` Nicolas Pitre
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=alpine.LFD.2.02.1111081406220.3307@xanadu.home \
--to=nico@fluxnic.net \
--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).