From: f.fainelli@gmail.com (Florian Fainelli)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH] ARM: brcmstb: Add earlyprintk support using run-time checks
Date: Fri, 1 Jul 2016 10:32:11 -0700 [thread overview]
Message-ID: <5776A91B.1000401@gmail.com> (raw)
In-Reply-To: <1467333764-2900-1-git-send-email-f.fainelli@gmail.com>
On 06/30/2016 05:42 PM, Florian Fainelli wrote:
> SUN_TOP_CTRL_FAMILY_ID is at a fixed absolute address for all of our supported
> chips, so utilize its value to determine what the UARTA base address should be.
>
> Since the code is called both during decompressor when the MMU is off, and
> after the MMU has been turned on, and we want to do the lookup only
> once, we use the same technique as tegra.S and have a shared storage
> location between the decompressor and the kernel.
>
> Signed-off-by: Florian Fainelli <f.fainelli@gmail.com>
Looks like I missed an update to DEBUG_UNCOMPRESS to make it disbaled if
DEBUG_BRCMSTB_UART is enabled.
Should patches to Kconfig.debug be submitted to RMK's patch system, or
pulled via arm-soc changes?
Thanks
--
Florian
prev parent reply other threads:[~2016-07-01 17:32 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-07-01 0:42 [PATCH] ARM: brcmstb: Add earlyprintk support using run-time checks Florian Fainelli
2016-07-01 17:32 ` Florian Fainelli [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=5776A91B.1000401@gmail.com \
--to=f.fainelli@gmail.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).