From: Brian Swetland <swetland@google.com>
To: Russell King - ARM Linux <linux@arm.linux.org.uk>
Cc: Pavel Machek <pavel@ucw.cz>, "Arve Hj?nnev?g" <arve@android.com>,
kernel list <linux-kernel@vger.kernel.org>,
linux-arm-kernel <linux-arm-kernel@lists.infradead.org>
Subject: Re: [PATCH 2/3] msm: add minimal board file for HTC Dream device
Date: Mon, 16 Nov 2009 08:43:20 -0800 [thread overview]
Message-ID: <a55d774e0911160843h22938604s8966a58ee71992a@mail.gmail.com> (raw)
In-Reply-To: <20091116163659.GB3568@n2100.arm.linux.org.uk>
On Mon, Nov 16, 2009 at 8:36 AM, Russell King - ARM Linux
<linux@arm.linux.org.uk> wrote:
> On Mon, Nov 02, 2009 at 11:49:49AM +0100, Pavel Machek wrote:
>> +MACHINE_START(TROUT, "HTC Dream")
>> +#ifdef CONFIG_MSM_DEBUG_UART
>> + .phys_io = MSM_DEBUG_UART_PHYS,
>> + .io_pg_offst = ((MSM_DEBUG_UART_BASE) >> 18) & 0xfffc,
>> +#endif
>
> Why is this ifdef'd? Two reasons why not to do this:
>
> 1. MSM_DEBUG_UART is always defined, so the conditional is pointless
For a default dream build, definitely, but not always on every msm7k
target (some devices may not have a serial port that can safely be
chattered at by the debug code). For this board file, no harm to
require it.
> 2. the low level page table building code does not expect these to be
> unset (or even set to an invalid value). Leaving them unset and
> having DEBUG_LL enabled is a recipe to prevent booting.
What's the best way to handle a situation where there is no valid
debug uart? Could the arch/platform require DEBUG_LL be unset via
Kconfig directives if it is configured in a way where there is no
valid debug uart?
> To put it another way, these two fields aren't optional.
>
Thanks,
Brian
next prev parent reply other threads:[~2009-11-16 16:43 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-11-02 10:49 Pavel Machek
2009-11-16 16:36 ` Russell King - ARM Linux
2009-11-16 16:43 ` Brian Swetland [this message]
2009-11-16 16:57 ` Russell King - ARM Linux
2009-11-16 17:07 ` Brian Swetland
2009-11-16 18:56 ` Robert Jarzmik
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=a55d774e0911160843h22938604s8966a58ee71992a@mail.gmail.com \
--to=swetland@google.com \
--cc=arve@android.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux@arm.linux.org.uk \
--cc=pavel@ucw.cz \
/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
all inboxes | Powered by JetHome®