[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <20110929180428.GA8125@huya.qualcomm.com>
Date: Thu, 29 Sep 2011 11:04:28 -0700
From: David Brown <davidb@...eaurora.org>
To: Stephen Boyd <sboyd@...eaurora.org>
Cc: Will Deacon <will.deacon@....com>,
Russell King - ARM Linux <linux@....linux.org.uk>,
"linux-arm-kernel@...ts.infradead.org"
<linux-arm-kernel@...ts.infradead.org>,
"linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>,
David Brown <davidb@...eaurora.org>
Subject: Re: [PATCHv2 2/2] ARM: debug: Move DEBUG_ICEDCC into the DEBUG_LL
choice
On Thu, Sep 29, 2011 at 10:22:42AM -0700, Stephen Boyd wrote:
> >> One of the problems you'll encounter is that there's places where we
> >> don't have any timer infrastructure (eg, decompressor) and software
> >> timing loops won't work (they'll be too slow for the lower-end CPUs
> >> and too fast for the upper-end CPUs.)
> > Agreed, software timing loops are the only option and it's impossible to get
> > them right everywhere. I think the Kconfig help text should be updated so
> > that the timeout paragraph is removed.
>
> Yes if you wait a long time the timeout for each character will expire
> and the execution will continue.
Wouldn't it be better to detect the first timeout and then stop trying
to write to the DCC?
But, do we really want fancy auto-detection stuff in DEBUG_LL? A
timeout might make sense for a DCC console, but not here.
David
--
Sent by an employee of the Qualcomm Innovation Center, Inc.
The Qualcomm Innovation Center, Inc. is a member of the Code Aurora Forum.
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists