From: Peter Ujfalusi <peter.ujfalusi@ti.com>
To: Govindraj <govindraj.ti@gmail.com>
Cc: Richard Watts <rrw@kynesim.co.uk>, Kevin Hilman <khilman@ti.com>,
linux-omap <linux-omap@vger.kernel.org>,
balbi@ti.com
Subject: Re: help: BeagleBoard xM RevC ethernet port
Date: Mon, 05 Mar 2012 11:52:45 +0200 [thread overview]
Message-ID: <4F548CED.4090406@ti.com> (raw)
In-Reply-To: <CAAL8m4x=6--5irPBPdW4n0dtYuMm_UThqWEuCSyTtsm+cEx4jQ@mail.gmail.com>
On 02/28/2012 04:04 PM, Govindraj wrote:
> The issue seems to a mux conflict issue, uart2_rx mux is been taken
> by uart init and gpio_147 needed for usb phy init is not in mux mode4
> as set by bootloader.
>
> On beagle I see no other uarts being used other than uart3 as console_uart.
> So I think it should be okay to init only uart3 from beagle board data.
> Here is the patch [1] to do the same. (Tested on Beagle Xm Rev.C)
>
> (Any other approach is welcome)
Thank you, I have working ethernet port finally!!!
> From f1b43f983a2926c637e6bc6ab5d1e5044339ffd3 Mon Sep 17 00:00:00 2001
> From: "Govindraj.R" <govindraj.raja@ti.com>
> Date: Tue, 28 Feb 2012 19:16:33 +0530
> Subject: [PATCH] omap3_beagle: Init only uart3 used for console
>
> On beagle some of uart mux lines are used for other
> purpose so init only uart3.
>
> Uart2 rx line clashes with gpio_147 used for usb ehci
> phy reset.
Tested-by: Peter Ujfalusi <peter.ujfalusi@ti.com>
next prev parent reply other threads:[~2012-03-05 9:52 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-02-17 8:24 help: BeagleBoard xM RevC ethernet port Peter Ujfalusi
2012-02-22 22:00 ` Kevin Hilman
2012-02-23 10:23 ` Richard Watts
2012-02-27 14:32 ` Peter Ujfalusi
2012-02-28 14:04 ` Govindraj
2012-02-28 15:37 ` Robert Nelson
2012-02-29 18:06 ` Brian Austin
2012-03-01 7:22 ` Govindraj
2012-03-07 20:48 ` Brian Austin
2012-03-07 20:56 ` Brian Austin
2012-03-08 6:13 ` Govindraj
2012-03-05 9:52 ` Peter Ujfalusi [this message]
2012-03-05 18:28 ` 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=4F548CED.4090406@ti.com \
--to=peter.ujfalusi@ti.com \
--cc=balbi@ti.com \
--cc=govindraj.ti@gmail.com \
--cc=khilman@ti.com \
--cc=linux-omap@vger.kernel.org \
--cc=rrw@kynesim.co.uk \
/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).