All of lore.kernel.org
 help / color / mirror / Atom feed
From: Kevin Hilman <khilman@ti.com>
To: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
Cc: linux-omap@vger.kernel.org,
	Enric Balletbo i Serra <eballetbo@iseebcn.com>
Subject: Re: ttyO2 broken on IGEPv2 on 3.3, 3.4-rc5 or arm-soc/for-next, working on 3.2
Date: Fri, 04 May 2012 09:27:35 -0700	[thread overview]
Message-ID: <87397fewso.fsf@ti.com> (raw)
In-Reply-To: <20120504155255.140b4e3f@skate> (Thomas Petazzoni's message of "Fri, 4 May 2012 15:52:55 +0200")

Hi Thomas,

Thomas Petazzoni <thomas.petazzoni@free-electrons.com> writes:

> I have an IGEPv2 revision 6 board, which uses the DM3730 OMAP3. With
> 3.2 omap2plus_defconfig, the system boots fine and have a working shell
> on ttyO2. On either 3.3, 3.4-rc5 or arm-soc/for-next from Arnd, the
> system boots all the way up to showing the shell prompt, but I can't
> type any character, as if UART RX was broken.

On v3.4-rc, can you see if reverting bce492c04ba8fc66a4ea0a52b181ba255daaaf54
has any effect?

That patch had some unfortunate side effects, but I haven't seen the
problem you see, so I'm not sure if it's related.

Kevin

  reply	other threads:[~2012-05-04 16:27 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-05-04 13:52 ttyO2 broken on IGEPv2 on 3.3, 3.4-rc5 or arm-soc/for-next, working on 3.2 Thomas Petazzoni
2012-05-04 16:27 ` Kevin Hilman [this message]
2012-05-04 17:51   ` Tony Lindgren
2012-05-04 23:46     ` Kevin Hilman
2012-10-04 16:07       ` Thomas Petazzoni
2012-10-04 17:18         ` Kevin Hilman
2012-10-04 20:11           ` Thomas Petazzoni
     [not found]             ` <CAKQ2WVp71=ULs_yK7Tkuo=8F4hATq0YCQ6RtV0ziJQQmnrib_g@mail.gmail.com>
2012-10-04 20:57               ` Thomas Petazzoni
2012-10-04 23:08                 ` Kevin Hilman
2012-10-05  7:32                   ` Javier Martinez Canillas
2012-10-05  8:10                     ` Thomas Petazzoni
2012-10-05 10:01                       ` Javier Martinez Canillas
2012-10-06  9:04                         ` Enric Balletbò i Serra
2012-10-07 23:37                           ` Javier Martinez Canillas
2012-10-04 23:06             ` Kevin Hilman
2012-10-05  8:06               ` Thomas Petazzoni

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=87397fewso.fsf@ti.com \
    --to=khilman@ti.com \
    --cc=eballetbo@iseebcn.com \
    --cc=linux-omap@vger.kernel.org \
    --cc=thomas.petazzoni@free-electrons.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.