All of lore.kernel.org
 help / color / mirror / Atom feed
From: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
To: Kevin Hilman <khilman@deeprootsystems.com>
Cc: "Tony Lindgren" <tony@atomide.com>,
	linux-omap@vger.kernel.org,
	"Enric Balletbo i Serra" <eballetbo@iseebcn.com>,
	"Gregory Clément" <gregory.clement@free-electrons.com>,
	"Michael Opdenacker" <michael.opdenacker@free-electrons.com>,
	"Maxime Ripard" <maxime.ripard@free-electrons.com>
Subject: Re: ttyO2 broken on IGEPv2 on 3.3, 3.4-rc5 or arm-soc/for-next, working on 3.2
Date: Fri, 5 Oct 2012 10:06:19 +0200	[thread overview]
Message-ID: <20121005100619.13345be0@skate> (raw)
In-Reply-To: <877gr5vnv0.fsf@deeprootsystems.com>

Kevin,

On Thu, 04 Oct 2012 16:06:27 -0700, Kevin Hilman wrote:

> > It seems they are exactly the same, unless my eyes missed
> > something, of course.
> 
> The example I gave was only for the UART3 RX, you should dump the
> UART3 TX pins as.  Using the omap_mux debugfs, you can see all of the
> potential pins where uart3_tx can be routed:

Well, UART3 TX seems to be working fine. Do RX and TX have mutual
influence in terms of pin muxing?

> Yes, that tells me where UART3 is expected to be mux'd on the board.
> So you can ignore the dss_data* and husb_data* files above and focus
> on uart3*
> 
> So to summarize, in /sys/kernel/debug/omap_mux, just do a 'cat uart3*'
> on a working and non-working board and see if there are any
> differences.

3.2 (working)

name: uart3_cts_rctx.uart3_cts_rctx (0x4800219a/0x16a = 0x0108), b h18, t NA
mode: OMAP_PIN_INPUT_PULLDOWN | OMAP_MUX_MODE0
signals: uart3_cts_rctx | NA | NA | NA | gpio_163 | NA | NA | safe_mode
name: uart3_rts_sd.uart3_rts_sd (0x4800219c/0x16c = 0x0000), b h19, t NA
mode: OMAP_PIN_OUTPUT | OMAP_MUX_MODE0
signals: uart3_rts_sd | NA | NA | NA | gpio_164 | NA | NA | safe_mode
name: uart3_rx_irrx.uart3_rx_irrx (0x4800219e/0x16e = 0x0100), b h20, t NA
mode: OMAP_PIN_INPUT | OMAP_MUX_MODE0
signals: uart3_rx_irrx | NA | NA | NA | gpio_165 | NA | NA | safe_mode
name: uart3_tx_irtx.uart3_tx_irtx (0x480021a0/0x170 = 0x0000), b h21, t NA
mode: OMAP_PIN_OUTPUT | OMAP_MUX_MODE0
signals: uart3_tx_irtx | NA | NA | NA | gpio_166 | NA | NA | safe_mode

3.6 (not working)

name: uart3_cts_rctx.uart3_cts_rctx (0x4800219a/0x16a = 0x0108), b h18, t NA
mode: OMAP_PIN_INPUT_PULLDOWN | OMAP_MUX_MODE0
signals: uart3_cts_rctx | NA | NA | NA | gpio_163 | NA | NA | safe_mode
name: uart3_rts_sd.uart3_rts_sd (0x4800219c/0x16c = 0x0000), b h19, t NA
mode: OMAP_PIN_OUTPUT | OMAP_MUX_MODE0
signals: uart3_rts_sd | NA | NA | NA | gpio_164 | NA | NA | safe_mode
name: uart3_rx_irrx.uart3_rx_irrx (0x4800219e/0x16e = 0x0100), b h20, t NA
mode: OMAP_PIN_INPUT | OMAP_MUX_MODE0
signals: uart3_rx_irrx | NA | NA | NA | gpio_165 | NA | NA | safe_mode
name: uart3_tx_irtx.uart3_tx_irtx (0x480021a0/0x170 = 0x0000), b h21, t NA
mode: OMAP_PIN_OUTPUT | OMAP_MUX_MODE0
signals: uart3_tx_irtx | NA | NA | NA | gpio_166 | NA | NA | safe_mode

Best regards,

Thomas
-- 
Thomas Petazzoni, Free Electrons
Kernel, drivers, real-time and embedded Linux
development, consulting, training and support.
http://free-electrons.com

      reply	other threads:[~2012-10-05  8:06 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
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 [this message]

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=20121005100619.13345be0@skate \
    --to=thomas.petazzoni@free-electrons.com \
    --cc=eballetbo@iseebcn.com \
    --cc=gregory.clement@free-electrons.com \
    --cc=khilman@deeprootsystems.com \
    --cc=linux-omap@vger.kernel.org \
    --cc=maxime.ripard@free-electrons.com \
    --cc=michael.opdenacker@free-electrons.com \
    --cc=tony@atomide.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.