From: Olof Johansson <olof@lixom.net>
To: "Pandita, Vikram" <vikram.pandita@ti.com>
Cc: "tony@atomide.com" <tony@atomide.com>,
"linux-omap@vger.kernel.org" <linux-omap@vger.kernel.org>,
"Gadiyar, Anand" <gadiyar@ti.com>
Subject: Re: [PATCH v2] arm: omap: Add omap3_defconfig
Date: Mon, 30 Nov 2009 22:13:27 -0600 [thread overview]
Message-ID: <20091201041327.GA20316@lixom.net> (raw)
In-Reply-To: <FCCFB4CDC6E5564B9182F639FC35608702FA902176@dbde02.ent.ti.com>
On Tue, Dec 01, 2009 at 09:29:42AM +0530, Pandita, Vikram wrote:
>
>
> >-----Original Message-----
> >From: linux-omap-owner@vger.kernel.org [mailto:linux-omap-owner@vger.kernel.org] On Behalf Of Olof
> <snip>
> >+# CONFIG_OMAP_LL_DEBUG_UART1 is not set
> >+# CONFIG_OMAP_LL_DEBUG_UART2 is not set
> >+CONFIG_OMAP_LL_DEBUG_UART3=y
> >+# CONFIG_OMAP_LL_DEBUG_NONE is not set
>
> I will suggest to keep LL_DEBUG_NONE as the default option and also disable the DEBUG_LL by default.
Yeah, good point.
However:
> a) Not all omap boards have UART3 as the debug low level interface
Correct.
> b) Boards like zoom2/zoom3 have external uarts and should not define internal omap uart as Low level debug function.
Actually, the only way to get DEBUG_LL output out of a zoom2/3 right
now is to use S2-1=ON and OMAP_LL_DEBUG_UART3 output on J13...
Anyway, changing it makes sense, will repost tomorrow.
-Olof
next prev parent reply other threads:[~2009-12-01 4:11 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-11-30 3:34 [PATCH] Add omap3_defconfig Olof Johansson
2009-11-30 5:47 ` Gadiyar, Anand
2009-11-30 15:52 ` Olof Johansson
2009-12-01 3:19 ` [PATCH v2] arm: omap: " Olof Johansson
2009-12-01 3:59 ` Pandita, Vikram
2009-12-01 4:13 ` Olof Johansson [this message]
2009-12-01 20:09 ` [PATCH v3] " Olof Johansson
2009-12-02 0:08 ` Tony Lindgren
2009-12-02 2:14 ` Olof Johansson
2009-12-03 0:52 ` [APPLIED] " Tony Lindgren
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=20091201041327.GA20316@lixom.net \
--to=olof@lixom.net \
--cc=gadiyar@ti.com \
--cc=linux-omap@vger.kernel.org \
--cc=tony@atomide.com \
--cc=vikram.pandita@ti.com \
/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.