Re: help: BeagleBoard xM RevC ethernet port
On Thu, 1 Mar 2012, Govindraj wrote: On Wed, Feb 29, 2012 at 11:36 PM, Brian Austin brian.aus...@cirrus.com wrote: Applying this patch gives this on my beagleboard xM revC Linux debian 3.3.0-rc4 Unable to set up timer: unexpected error Failed to bring up eth0. Works for me on 3.3-rc4 + sent patch on beagle xm revc here this the log [1] Ensure you have selected following for ehci and usb Ethernet adapter support. CONFIG_USB_EHCI_HCD CONFIG_USB_EHCI_HCD_OMAP CONFIG_USB_NET_SMSC95XX Thanks for the config. Unfortunately this does nothing for Debian Unstable on the beagleboard Xm RevC DHCPREQUEST on eth0 to 255.255.255.255 port 67 Unable to set up timer: unexpected error Failed to bring up eth0. root@debian:~# [ 310.470581] smsc95xx 1-2.1:1.0: eth0: link up, 100Mbps, full-duplex, lpa 0x45E1 Kernel log shows the device getting registered. [4.768096] smsc95xx 1-2.1:1.0: eth0: register 'smsc95xx' at usb-ehci-omap.0-2.1, smsc95xx USB 2.0 Ethernet, 76:22:51:1f:d9:b6 I'm guessing this is a Debian problem. The Debian kernel binary 3.2.7-x5 works fine. I'm building from git://git.kernel.org/pub/scm/linux/kernel/git/tmlind/linux-omap.git with tag v3.3-rc4. Thanks, Brian -- To unsubscribe from this list: send the line unsubscribe linux-omap in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html
Re: help: BeagleBoard xM RevC ethernet port
On Wed, 7 Mar 2012, Brian Austin wrote: On Thu, 1 Mar 2012, Govindraj wrote: On Wed, Feb 29, 2012 at 11:36 PM, Brian Austin brian.aus...@cirrus.com wrote: Applying this patch gives this on my beagleboard xM revC Linux debian 3.3.0-rc4 Unable to set up timer: unexpected error Failed to bring up eth0. Works for me on 3.3-rc4 + sent patch on beagle xm revc here this the log [1] Ensure you have selected following for ehci and usb Ethernet adapter support. CONFIG_USB_EHCI_HCD CONFIG_USB_EHCI_HCD_OMAP CONFIG_USB_NET_SMSC95XX Thanks for the config. Unfortunately this does nothing for Debian Unstable on the beagleboard Xm RevC I should rephrase this. It does actually show up in the kernel log so the kernel sees the device. My bad. It just wont grab an IP from Debian. DHCPREQUEST on eth0 to 255.255.255.255 port 67 Unable to set up timer: unexpected error Failed to bring up eth0. root@debian:~# [ 310.470581] smsc95xx 1-2.1:1.0: eth0: link up, 100Mbps, full-duplex, lpa 0x45E1 Kernel log shows the device getting registered. [4.768096] smsc95xx 1-2.1:1.0: eth0: register 'smsc95xx' at usb-ehci-omap.0-2.1, smsc95xx USB 2.0 Ethernet, 76:22:51:1f:d9:b6 I'm guessing this is a Debian problem. The Debian kernel binary 3.2.7-x5 works fine. I'm building from git://git.kernel.org/pub/scm/linux/kernel/git/tmlind/linux-omap.git with tag v3.3-rc4. Thanks, Brian -- To unsubscribe from this list: send the line unsubscribe linux-omap in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html
Re: help: BeagleBoard xM RevC ethernet port
On Thu, Mar 8, 2012 at 2:26 AM, Brian Austin brian.aus...@cirrus.com wrote: On Wed, 7 Mar 2012, Brian Austin wrote: On Thu, 1 Mar 2012, Govindraj wrote: On Wed, Feb 29, 2012 at 11:36 PM, Brian Austin brian.aus...@cirrus.com wrote: Applying this patch gives this on my beagleboard xM revC Linux debian 3.3.0-rc4 Unable to set up timer: unexpected error Failed to bring up eth0. Works for me on 3.3-rc4 + sent patch on beagle xm revc here this the log [1] Ensure you have selected following for ehci and usb Ethernet adapter support. CONFIG_USB_EHCI_HCD CONFIG_USB_EHCI_HCD_OMAP CONFIG_USB_NET_SMSC95XX Thanks for the config. Unfortunately this does nothing for Debian Unstable on the beagleboard Xm RevC I should rephrase this. It does actually show up in the kernel log so the kernel sees the device. My bad. It just wont grab an IP from Debian. Thanks for the clarification. -- Thanks, Govindraj.R -- To unsubscribe from this list: send the line unsubscribe linux-omap in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html
Re: help: BeagleBoard xM RevC ethernet port
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.r...@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.ujfal...@ti.com -- To unsubscribe from this list: send the line unsubscribe linux-omap in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html
Re: help: BeagleBoard xM RevC ethernet port
* Peter Ujfalusi peter.ujfal...@ti.com [120305 01:21]: 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.r...@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.ujfal...@ti.com Thanks applying into board branch. Regards, Tony -- To unsubscribe from this list: send the line unsubscribe linux-omap in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html
Re: help: BeagleBoard xM RevC ethernet port
Applying this patch gives this on my beagleboard xM revC
Linux debian 3.3.0-rc4
Unable to set up timer: unexpected error
Failed to bring up eth0.
On Tue, 28 Feb 2012, Robert Nelson wrote:
On Tue, Feb 28, 2012 at 8:04 AM, Govindraj govindraj...@gmail.com wrote:
Hi Peter,
On Mon, Feb 27, 2012 at 8:02 PM, Peter Ujfalusi peter.ujfal...@ti.com wrote:
Hi,
On 02/23/2012 12:23 PM, Richard Watts wrote:
On 22/02/12 22:00, Kevin Hilman wrote:
The first thing I try when I see these regulator failures is to add
CONFIG_REGULATOR_DUMMY=y to the .config to see if that helps. If so,
then the board file needs some help configuring the right regulators.
Thanks for the hint Kevin
Apologies for the malformed patch, but I don't have time to clean it up
this morning (or test it in its cleaned state); however, the following
fixes the problem for me.
It used to be masked because u-boot turns the regulator on to activate
ethernet on Beagle xM and no-one ever turns it off again, but some versions
of u-boot don't identify xM rev C correctly, so never turn it on ..
Anyway, it's neater for the kernel to know what it's doing. And removes
a whole two lines of kernel startup output :-)
I have did similar thing as well, but it did not helped. The two line
complaining about the regulator was gone, but still neither the ethernet
nor the USB ports were working.
The LED between the USB ports are lit, shich indicates that the LAN9514
should have the needed power.
With the REGULATOR_DUMMY enabled I have this in the kernel log:
beagle-gentoo ~ # dmesg | grep ehci-omap
[ 1.443420] _regulator_get: ehci-omap.0 supply hsusb0 not found,
using dummy regulator
[ 1.452026] _regulator_get: ehci-omap.0 supply hsusb1 not found,
using dummy regulator
[ 2.465637] ehci-omap ehci-omap.0: phy reset operation timed out
[ 3.473449] ehci-omap ehci-omap.0: phy reset operation timed out
[ 3.479766] ehci-omap ehci-omap.0: reset hcs_params 0x1313 dbg=0 cc=1
pcc=3 ordered ports=3
[ 3.488586] ehci-omap ehci-omap.0: reset hcc_params 0016 thresh 1
uframes 256/512/1024 park
[ 3.497436] ehci-omap ehci-omap.0: reset command 0080b02 park=3
ithresh=8 period=1024 Reset HALT
[ 3.506774] ehci-omap ehci-omap.0: OMAP-EHCI Host Controller
[ 3.524871] ehci-omap ehci-omap.0: new USB bus registered, assigned
bus number 1
[ 3.532806] ehci-omap ehci-omap.0: park 0
[ 3.537139] ehci-omap ehci-omap.0: irq 77, io mem 0x48064800
[ 3.543121] ehci-omap ehci-omap.0: init command 0010005 (park)=0
ithresh=1 period=512 RUN
[ 3.567260] ehci-omap ehci-omap.0: USB 2.0 started, EHCI 1.00
[ 3.609771] usb usb1: SerialNumber: ehci-omap.0
[ 3.690460] ehci-omap ehci-omap.0: ...powerup ports...
I have a faint recollection that the ethernet port along with the USB
ports were working in some ancient kernel (2.6.3x) - I think it was the
distro which come with board...
It might be that I have everything built into the kernel?
Will debug this further when time allows...
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)
Thanks, this patch fixed it on my xM B on v3.3-rc5
Tested-by: Robert Nelson robertcnel...@gmail.com
Regards,
[1]:
From f1b43f983a2926c637e6bc6ab5d1e5044339ffd3 Mon Sep 17 00:00:00 2001
From: Govindraj.R govindraj.r...@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.
Signed-off-by: Govindraj.R govindraj.r...@ti.com
---
arch/arm/mach-omap2/board-omap3beagle.c | 50 ++-
1 files changed, 49 insertions(+), 1 deletions(-)
diff --git a/arch/arm/mach-omap2/board-omap3beagle.c
b/arch/arm/mach-omap2/board-omap3beagle.c
index 817be06..a2e0052 100644
--- a/arch/arm/mach-omap2/board-omap3beagle.c
+++ b/arch/arm/mach-omap2/board-omap3beagle.c
@@ -493,6 +493,54 @@ static const struct usbhs_omap_board_data
usbhs_bdata __initconst = {
static struct omap_board_mux board_mux[] __initdata = {
{ .reg_offset = OMAP_MUX_TERMINATOR },
};
+
+static struct omap_device_pad uart3_pads[] __initdata = {
+ {
+ .name = uart3_cts_rctx.uart3_cts_rctx,
+ .enable = OMAP_PIN_INPUT_PULLUP | OMAP_MUX_MODE0,
+ },
+ {
+ .name = uart3_rts_sd.uart3_rts_sd,
+ .enable = OMAP_PIN_OUTPUT | OMAP_MUX_MODE0,
+ },
+ {
+ .name = uart3_tx_irtx.uart3_tx_irtx,
+ .enable = OMAP_PIN_OUTPUT | OMAP_MUX_MODE0,
+ },
+ {
+ .name =
Re: help: BeagleBoard xM RevC ethernet port
Hi Peter,
On Mon, Feb 27, 2012 at 8:02 PM, Peter Ujfalusi peter.ujfal...@ti.com wrote:
Hi,
On 02/23/2012 12:23 PM, Richard Watts wrote:
On 22/02/12 22:00, Kevin Hilman wrote:
The first thing I try when I see these regulator failures is to add
CONFIG_REGULATOR_DUMMY=y to the .config to see if that helps. If so,
then the board file needs some help configuring the right regulators.
Thanks for the hint Kevin
Apologies for the malformed patch, but I don't have time to clean it up
this morning (or test it in its cleaned state); however, the following
fixes the problem for me.
It used to be masked because u-boot turns the regulator on to activate
ethernet on Beagle xM and no-one ever turns it off again, but some versions
of u-boot don't identify xM rev C correctly, so never turn it on ..
Anyway, it's neater for the kernel to know what it's doing. And removes
a whole two lines of kernel startup output :-)
I have did similar thing as well, but it did not helped. The two line
complaining about the regulator was gone, but still neither the ethernet
nor the USB ports were working.
The LED between the USB ports are lit, shich indicates that the LAN9514
should have the needed power.
With the REGULATOR_DUMMY enabled I have this in the kernel log:
beagle-gentoo ~ # dmesg | grep ehci-omap
[ 1.443420] _regulator_get: ehci-omap.0 supply hsusb0 not found,
using dummy regulator
[ 1.452026] _regulator_get: ehci-omap.0 supply hsusb1 not found,
using dummy regulator
[ 2.465637] ehci-omap ehci-omap.0: phy reset operation timed out
[ 3.473449] ehci-omap ehci-omap.0: phy reset operation timed out
[ 3.479766] ehci-omap ehci-omap.0: reset hcs_params 0x1313 dbg=0 cc=1
pcc=3 ordered ports=3
[ 3.488586] ehci-omap ehci-omap.0: reset hcc_params 0016 thresh 1
uframes 256/512/1024 park
[ 3.497436] ehci-omap ehci-omap.0: reset command 0080b02 park=3
ithresh=8 period=1024 Reset HALT
[ 3.506774] ehci-omap ehci-omap.0: OMAP-EHCI Host Controller
[ 3.524871] ehci-omap ehci-omap.0: new USB bus registered, assigned
bus number 1
[ 3.532806] ehci-omap ehci-omap.0: park 0
[ 3.537139] ehci-omap ehci-omap.0: irq 77, io mem 0x48064800
[ 3.543121] ehci-omap ehci-omap.0: init command 0010005 (park)=0
ithresh=1 period=512 RUN
[ 3.567260] ehci-omap ehci-omap.0: USB 2.0 started, EHCI 1.00
[ 3.609771] usb usb1: SerialNumber: ehci-omap.0
[ 3.690460] ehci-omap ehci-omap.0: ...powerup ports...
I have a faint recollection that the ethernet port along with the USB
ports were working in some ancient kernel (2.6.3x) - I think it was the
distro which come with board...
It might be that I have everything built into the kernel?
Will debug this further when time allows...
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)
[1]:
From f1b43f983a2926c637e6bc6ab5d1e5044339ffd3 Mon Sep 17 00:00:00 2001
From: Govindraj.R govindraj.r...@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.
Signed-off-by: Govindraj.R govindraj.r...@ti.com
---
arch/arm/mach-omap2/board-omap3beagle.c | 50 ++-
1 files changed, 49 insertions(+), 1 deletions(-)
diff --git a/arch/arm/mach-omap2/board-omap3beagle.c
b/arch/arm/mach-omap2/board-omap3beagle.c
index 817be06..a2e0052 100644
--- a/arch/arm/mach-omap2/board-omap3beagle.c
+++ b/arch/arm/mach-omap2/board-omap3beagle.c
@@ -493,6 +493,54 @@ static const struct usbhs_omap_board_data
usbhs_bdata __initconst = {
static struct omap_board_mux board_mux[] __initdata = {
{ .reg_offset = OMAP_MUX_TERMINATOR },
};
+
+static struct omap_device_pad uart3_pads[] __initdata = {
+ {
+ .name = uart3_cts_rctx.uart3_cts_rctx,
+ .enable = OMAP_PIN_INPUT_PULLUP | OMAP_MUX_MODE0,
+ },
+ {
+ .name = uart3_rts_sd.uart3_rts_sd,
+ .enable = OMAP_PIN_OUTPUT | OMAP_MUX_MODE0,
+ },
+ {
+ .name = uart3_tx_irtx.uart3_tx_irtx,
+ .enable = OMAP_PIN_OUTPUT | OMAP_MUX_MODE0,
+ },
+ {
+ .name = uart3_rx_irrx.uart3_rx_irrx,
+ .flags = OMAP_DEVICE_PAD_REMUX | OMAP_DEVICE_PAD_WAKEUP,
+ .enable = OMAP_PIN_INPUT | OMAP_MUX_MODE0,
+ .idle = OMAP_PIN_INPUT | OMAP_MUX_MODE0,
+ },
+};
+
+static inline void board_serial_init(void)
+{
+ struct omap_board_data uart3_bdata;
+
Re: help: BeagleBoard xM RevC ethernet port
On Tue, Feb 28, 2012 at 8:04 AM, Govindraj govindraj...@gmail.com wrote:
Hi Peter,
On Mon, Feb 27, 2012 at 8:02 PM, Peter Ujfalusi peter.ujfal...@ti.com wrote:
Hi,
On 02/23/2012 12:23 PM, Richard Watts wrote:
On 22/02/12 22:00, Kevin Hilman wrote:
The first thing I try when I see these regulator failures is to add
CONFIG_REGULATOR_DUMMY=y to the .config to see if that helps. If so,
then the board file needs some help configuring the right regulators.
Thanks for the hint Kevin
Apologies for the malformed patch, but I don't have time to clean it up
this morning (or test it in its cleaned state); however, the following
fixes the problem for me.
It used to be masked because u-boot turns the regulator on to activate
ethernet on Beagle xM and no-one ever turns it off again, but some versions
of u-boot don't identify xM rev C correctly, so never turn it on ..
Anyway, it's neater for the kernel to know what it's doing. And removes
a whole two lines of kernel startup output :-)
I have did similar thing as well, but it did not helped. The two line
complaining about the regulator was gone, but still neither the ethernet
nor the USB ports were working.
The LED between the USB ports are lit, shich indicates that the LAN9514
should have the needed power.
With the REGULATOR_DUMMY enabled I have this in the kernel log:
beagle-gentoo ~ # dmesg | grep ehci-omap
[ 1.443420] _regulator_get: ehci-omap.0 supply hsusb0 not found,
using dummy regulator
[ 1.452026] _regulator_get: ehci-omap.0 supply hsusb1 not found,
using dummy regulator
[ 2.465637] ehci-omap ehci-omap.0: phy reset operation timed out
[ 3.473449] ehci-omap ehci-omap.0: phy reset operation timed out
[ 3.479766] ehci-omap ehci-omap.0: reset hcs_params 0x1313 dbg=0 cc=1
pcc=3 ordered ports=3
[ 3.488586] ehci-omap ehci-omap.0: reset hcc_params 0016 thresh 1
uframes 256/512/1024 park
[ 3.497436] ehci-omap ehci-omap.0: reset command 0080b02 park=3
ithresh=8 period=1024 Reset HALT
[ 3.506774] ehci-omap ehci-omap.0: OMAP-EHCI Host Controller
[ 3.524871] ehci-omap ehci-omap.0: new USB bus registered, assigned
bus number 1
[ 3.532806] ehci-omap ehci-omap.0: park 0
[ 3.537139] ehci-omap ehci-omap.0: irq 77, io mem 0x48064800
[ 3.543121] ehci-omap ehci-omap.0: init command 0010005 (park)=0
ithresh=1 period=512 RUN
[ 3.567260] ehci-omap ehci-omap.0: USB 2.0 started, EHCI 1.00
[ 3.609771] usb usb1: SerialNumber: ehci-omap.0
[ 3.690460] ehci-omap ehci-omap.0: ...powerup ports...
I have a faint recollection that the ethernet port along with the USB
ports were working in some ancient kernel (2.6.3x) - I think it was the
distro which come with board...
It might be that I have everything built into the kernel?
Will debug this further when time allows...
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)
Thanks, this patch fixed it on my xM B on v3.3-rc5
Tested-by: Robert Nelson robertcnel...@gmail.com
Regards,
[1]:
From f1b43f983a2926c637e6bc6ab5d1e5044339ffd3 Mon Sep 17 00:00:00 2001
From: Govindraj.R govindraj.r...@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.
Signed-off-by: Govindraj.R govindraj.r...@ti.com
---
arch/arm/mach-omap2/board-omap3beagle.c | 50
++-
1 files changed, 49 insertions(+), 1 deletions(-)
diff --git a/arch/arm/mach-omap2/board-omap3beagle.c
b/arch/arm/mach-omap2/board-omap3beagle.c
index 817be06..a2e0052 100644
--- a/arch/arm/mach-omap2/board-omap3beagle.c
+++ b/arch/arm/mach-omap2/board-omap3beagle.c
@@ -493,6 +493,54 @@ static const struct usbhs_omap_board_data
usbhs_bdata __initconst = {
static struct omap_board_mux board_mux[] __initdata = {
{ .reg_offset = OMAP_MUX_TERMINATOR },
};
+
+static struct omap_device_pad uart3_pads[] __initdata = {
+ {
+ .name = uart3_cts_rctx.uart3_cts_rctx,
+ .enable = OMAP_PIN_INPUT_PULLUP | OMAP_MUX_MODE0,
+ },
+ {
+ .name = uart3_rts_sd.uart3_rts_sd,
+ .enable = OMAP_PIN_OUTPUT | OMAP_MUX_MODE0,
+ },
+ {
+ .name = uart3_tx_irtx.uart3_tx_irtx,
+ .enable = OMAP_PIN_OUTPUT | OMAP_MUX_MODE0,
+ },
+ {
+ .name = uart3_rx_irrx.uart3_rx_irrx,
+ .flags = OMAP_DEVICE_PAD_REMUX | OMAP_DEVICE_PAD_WAKEUP,
+
Re: help: BeagleBoard xM RevC ethernet port
On 22/02/12 22:00, Kevin Hilman wrote:
Peter Ujfalusi peter.ujfal...@ti.com writes:
Hi,
I hoped that time will solve this, but so far no luck. I just can not
get the ethernet port (along with the USB host ports) working on my xM RevC.
What is the trick to get it working on 3.3-rc3?
There seams to be some configuration issue:
[1.437530] ehci_hcd: USB 2.0 'Enhanced' Host Controller (EHCI) Driver
[1.444671] ehci_hcd: block sizes: qh 64 qtd 96 itd 160 sitd 96
[1.451354] ehci-omap ehci-omap.0: failed to get ehci port0 regulator
[1.458282] ehci-omap ehci-omap.0: failed to get ehci port1 regulator
The first thing I try when I see these regulator failures is to add
CONFIG_REGULATOR_DUMMY=y to the .config to see if that helps. If so,
then the board file needs some help configuring the right regulators.
Kevin
--
Apologies for the malformed patch, but I don't have time to clean it up
this morning (or test it in its cleaned state); however, the following
fixes the problem for me.
It used to be masked because u-boot turns the regulator on to activate
ethernet on Beagle xM and no-one ever turns it off again, but some versions
of u-boot don't identify xM rev C correctly, so never turn it on ..
Anyway, it's neater for the kernel to know what it's doing. And removes
a whole two lines of kernel startup output :-)
Richard.
---
commit 39d26ad563023ac06e8aaaf154378c373187
Author: Richard Watts r...@kynesim.co.uk
Date: Fri Jan 20 12:27:59 2012 +
Turn on the USB regulator on Beagle xM explicitly, when the USB
subsystem asks for it, rather than relying on u-boot to do it.
diff --git a/arch/arm/mach-omap2/board-omap3beagle.c
b/arch/arm/mach-omap2/board-omap3beagle.c
index 4a71cb7..69ed6a0 100644
--- a/arch/arm/mach-omap2/board-omap3beagle.c
+++ b/arch/arm/mach-omap2/board-omap3beagle.c
@@ -362,11 +362,32 @@ static struct regulator_init_data beagle_vsim = {
.consumer_supplies = beagle_vsim_supply,
};
+static struct regulator_consumer_supply beagle_usb_supply[] = {
+REGULATOR_SUPPLY(hsusb0, ehci-omap.0),
+REGULATOR_SUPPLY(hsusb1, ehci-omap.0)
+};
+
+static struct regulator_init_data usb_power = {
+.constraints = {
+.min_uV = 180,
+.max_uV = 180,
+.valid_modes_mask = REGULATOR_MODE_NORMAL,
+.valid_ops_mask = REGULATOR_CHANGE_VOLTAGE
+| REGULATOR_CHANGE_MODE
+| REGULATOR_CHANGE_STATUS,
+},
+.num_consumer_supplies = ARRAY_SIZE(beagle_usb_supply),
+.consumer_supplies = beagle_usb_supply
+};
+
+
+
static struct twl4030_platform_data beagle_twldata = {
/* platform_data for children goes here */
.gpio = beagle_gpio_data,
.vmmc1 = beagle_vmmc1,
.vsim = beagle_vsim,
+.vaux2 = usb_power,
};
static struct i2c_board_info __initdata beagle_i2c_eeprom[] =
--
To unsubscribe from this list: send the line unsubscribe linux-omap in
the body of a message to majord...@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Re: help: BeagleBoard xM RevC ethernet port
Peter Ujfalusi peter.ujfal...@ti.com writes: Hi, I hoped that time will solve this, but so far no luck. I just can not get the ethernet port (along with the USB host ports) working on my xM RevC. What is the trick to get it working on 3.3-rc3? There seams to be some configuration issue: [1.437530] ehci_hcd: USB 2.0 'Enhanced' Host Controller (EHCI) Driver [1.444671] ehci_hcd: block sizes: qh 64 qtd 96 itd 160 sitd 96 [1.451354] ehci-omap ehci-omap.0: failed to get ehci port0 regulator [1.458282] ehci-omap ehci-omap.0: failed to get ehci port1 regulator The first thing I try when I see these regulator failures is to add CONFIG_REGULATOR_DUMMY=y to the .config to see if that helps. If so, then the board file needs some help configuring the right regulators. Kevin -- To unsubscribe from this list: send the line unsubscribe linux-omap in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html
help: BeagleBoard xM RevC ethernet port
Hi, I hoped that time will solve this, but so far no luck. I just can not get the ethernet port (along with the USB host ports) working on my xM RevC. What is the trick to get it working on 3.3-rc3? There seams to be some configuration issue: [1.437530] ehci_hcd: USB 2.0 'Enhanced' Host Controller (EHCI) Driver [1.444671] ehci_hcd: block sizes: qh 64 qtd 96 itd 160 sitd 96 [1.451354] ehci-omap ehci-omap.0: failed to get ehci port0 regulator [1.458282] ehci-omap ehci-omap.0: failed to get ehci port1 regulator [2.465850] ehci-omap ehci-omap.0: phy reset operation timed out [3.473663] ehci-omap ehci-omap.0: phy reset operation timed out [3.479980] ehci-omap ehci-omap.0: reset hcs_params 0x1313 dbg=0 cc=1 pcc=3 ordered ports=3 [3.488769] ehci-omap ehci-omap.0: reset hcc_params 0016 thresh 1 uframes 256/512/1024 park [3.497589] ehci-omap ehci-omap.0: reset command 0080b02 park=3 ithresh=8 period=1024 Reset HALT [3.506927] ehci-omap ehci-omap.0: OMAP-EHCI Host Controller gentoo ~ # lsusb Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub So only the root hub is working, the LAN9514 does not. Yes, I have enabled the needed configs in my kernel. Can someone send me a config file for 3.3-rc3 with working ethernet port? Thanks, Péter -- To unsubscribe from this list: send the line unsubscribe linux-omap in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html
