From: linux@arm.linux.org.uk (Russell King - ARM Linux)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH 2/2] amba pl011: platform data for reg lockup and glitch
Date: Thu, 9 Jun 2011 22:02:18 +0100 [thread overview]
Message-ID: <20110609210218.GH24424@n2100.arm.linux.org.uk> (raw)
In-Reply-To: <1307653008-3398-1-git-send-email-linus.walleij@stericsson.com>
On Thu, Jun 09, 2011 at 10:56:48PM +0200, Linus Walleij wrote:
> + /* uart-0 pins gpio configuration should be
> + * kept intact to prevent glitch in tx line
> + * when tty dev is opened. Later these pins
> + * are configured to uart mop500_pins_uart0
> + *
> + * It will be replaced with uart configuration
> + * once the issue is solved.
> + */
> + GPIO0_GPIO | PIN_INPUT_PULLUP,
> + GPIO1_GPIO | PIN_OUTPUT_HIGH,
> + GPIO2_GPIO | PIN_INPUT_PULLUP,
> + GPIO3_GPIO | PIN_OUTPUT_LOW,
Why do you want the TXD line (GPIO3) to be indicating a break condition?
next prev parent reply other threads:[~2011-06-09 21:02 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-06-09 20:56 [PATCH 2/2] amba pl011: platform data for reg lockup and glitch Linus Walleij
2011-06-09 21:02 ` Russell King - ARM Linux [this message]
2011-06-10 9:07 ` Shreshtha Kumar SAHU
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=20110609210218.GH24424@n2100.arm.linux.org.uk \
--to=linux@arm.linux.org.uk \
--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).