Hi,
On Thu, Mar 14, 2013 at 4:23 PM, Felipe Balbi ba...@ti.com wrote:
Hi,
On Thu, Mar 14, 2013 at 04:14:58PM +0530, Vivek Gautam wrote:
Convert clk_enable/clk_disable to clk_prepare_enable/clk_disable_unprepare
calls as required by common clock framework.
Signed-off-by: Vivek Gautam
On Thu, Mar 14, 2013 at 12:19:04PM +0200, Felipe Balbi wrote:
Hi,
On Thu, Mar 14, 2013 at 05:24:39PM +0800, Peter Chen wrote:
@@ -278,7 +278,10 @@ static int udc_bind_to_driver(struct usb_udc *udc,
struct usb_gadget_driver *dri
driver-unbind(gadget);
On Thu, Mar 14, 2013 at 12:12:47PM +0200, Felipe Balbi wrote:
Hi,
On Thu, Mar 14, 2013 at 05:38:03PM +0800, Peter Chen wrote:
@@ -160,6 +163,24 @@ usb_phy_shutdown(struct usb_phy *x)
x-shutdown(x);
}
+static inline int
+usb_phy_vbus_on(struct
On Thu, Mar 14, 2013 at 12:31:38PM +0200, Alexander Shishkin wrote:
Peter Chen peter.c...@freescale.com writes:
Hi Alex and all,
Currently, we have two problems to block chipidea driver coming
development.
As there are so many chipidea versions, we impossible to collect
all to
Ben Hutchings b...@decadent.org.uk writes:
On Thu, 2013-03-14 at 12:05 +0100, Bjørn Mork wrote:
commit bd329e1 (net: cdc_ncm: do not bind to NCM compatible MBIM devices)
introduced a new policy, preferring MBIM for dual NCM/MBIM functions if
the cdc_mbim driver was enabled. This caused a
On Thu, Mar 14, 2013 at 03:34:31PM -0400, Alan Stern wrote:
On Thu, 14 Mar 2013, Felipe Balbi wrote:
Here's the diff which needs testing:
Can't test the net2272 part.
diff --git a/drivers/usb/gadget/net2280.c b/drivers/usb/gadget/net2280.c
index 691cc65..d23c1b8 100644
---
On Thu, Mar 14, 2013 at 03:25:05PM -0700, Greg KH wrote:
FYI, I just applied this patch to my staging and USB trees, hopefully
this makes some people here happy.
From: Greg Kroah-Hartman gre...@linuxfoundation.org
Date: Thu, 14 Mar 2013 15:22:40 -0700
Hi,
On Fri, Mar 15, 2013 at 09:25:28AM +0900, UCHINO Satoshi wrote:
Without this memory barrier, the file-storage thread may fail to
escape from the following while loop, because it may observe new
common-thread_wakeup_needed and old bh-state which are updated by
the callback functions.
Hi,
On Fri, Mar 15, 2013 at 11:36:00AM +0530, Vivek Gautam wrote:
Convert clk_enable/clk_disable to clk_prepare_enable/clk_disable_unprepare
calls as required by common clock framework.
Signed-off-by: Vivek Gautam gautam.vi...@samsung.com
CC: Felipe Balbi ba...@ti.com
CC: Kukjin Kim
Hi,
On Fri, Mar 15, 2013 at 02:06:16PM +0800, Peter Chen wrote:
@@ -278,7 +278,10 @@ static int udc_bind_to_driver(struct usb_udc
*udc, struct usb_gadget_driver *dri
driver-unbind(gadget);
goto err1;
}
-
On Fri, Mar 15, 2013 at 02:15:16PM +0800, Peter Chen wrote:
On Thu, Mar 14, 2013 at 12:12:47PM +0200, Felipe Balbi wrote:
Hi,
On Thu, Mar 14, 2013 at 05:38:03PM +0800, Peter Chen wrote:
@@ -160,6 +163,24 @@ usb_phy_shutdown(struct usb_phy *x)
x-shutdown(x);
}
Based on 'for-next' of linux-samsung tree with following patches
from Doug on top:
usb: Document clocks in samsung, exynos4210-ehci/ohci bindings
ARM: dts: add usb 2.0 clock references to exynos5250 device tree
Also depending upon following patch-series for Samsung-usb-phy driver:
[PATCH v7 0/2]
Adding usbphy node for Exynos5250 along with the
necessary device data to be parsed.
Signed-off-by: Vivek Gautam gautam.vi...@samsung.com
---
arch/arm/boot/dts/exynos5250.dtsi | 15 +++
1 files changed, 15 insertions(+), 0 deletions(-)
diff --git
Adding usb3.0 phy node for Exynos5250 along with the
necessary device data to be parsed.
Signed-off-by: Vivek Gautam gautam.vi...@samsung.com
---
arch/arm/boot/dts/exynos5250.dtsi | 14 ++
1 files changed, 14 insertions(+), 0 deletions(-)
diff --git
On Thu, 14 Mar 2013, Rafael J. Wysocki wrote:
commit 181380b702eee1a9aca51354d7b87c7b08541fcf
Author: Yinghai Lu ying...@kernel.org
Date: Sat Feb 16 11:58:34 2013 -0700
PCI/ACPI: Don't cache _PRT, and don't associate them with bus numbers
This patch __fixed__ this
This patch enables support for XHCI on exynos5 series of SOCs,
to support host side USB 3.0 support.
Signed-off-by: Vivek Gautam gautam.vi...@samsung.com
---
arch/arm/mach-exynos/Kconfig |1 +
1 files changed, 1 insertions(+), 0 deletions(-)
diff --git a/arch/arm/mach-exynos/Kconfig
This patch-set is in continuation with patch-series:
[PATCH v4 0/4] Enable ehci, ohci and dwc3 devices on exynos5250
out of which follwowing patches have been picked up:
ARM: Exynos5250: Enabling ehci-s5p driver
ARM: Exynos5250: Enabling ohci-exynos driver
Based on following patch-set for
Adding DWC3 device tree node for Exynos5250 needed to
parse device tree data.
Signed-off-by: Vivek Gautam gautam.vi...@samsung.com
---
arch/arm/boot/dts/exynos5250.dtsi | 20 ++--
1 files changed, 18 insertions(+), 2 deletions(-)
diff --git a/arch/arm/boot/dts/exynos5250.dtsi
Document device tree binding information as required by the
Samsung' USB 3.0 controller.
Signed-off-by: Vivek Gautam gautam.vi...@samsung.com
---
.../devicetree/bindings/usb/exynos-usb.txt | 34
1 files changed, 34 insertions(+), 0 deletions(-)
diff --git
On Fri, Mar 15, 2013 at 09:53:27AM +0200, Felipe Balbi wrote:
On Fri, Mar 15, 2013 at 02:15:16PM +0800, Peter Chen wrote:
On Thu, Mar 14, 2013 at 12:12:47PM +0200, Felipe Balbi wrote:
Hi,
On Thu, Mar 14, 2013 at 05:38:03PM +0800, Peter Chen wrote:
@@ -160,6 +163,24 @@
Hi,
On Fri, 15 Mar 2013 07:39:02, Felipe Balbi ba...@ti.com wrote:
Hi,
On Fri, Mar 15, 2013 at 09:25:28AM +0900, UCHINO Satoshi wrote:
Without this memory barrier, the file-storage thread may fail to
escape from the following while loop, because it may observe new
Hi,
On Fri, Mar 15, 2013 at 04:05:52PM +0800, Peter Chen wrote:
@@ -160,6 +163,24 @@ usb_phy_shutdown(struct usb_phy *x)
x-shutdown(x);
}
+static inline int
+usb_phy_vbus_on(struct usb_phy *x)
+{
+ if
Hi,
On Fri, Mar 15, 2013 at 01:59:30PM +0800, victor yeo wrote:
For bulk transfer, the new UDC driver has one problem. When SCSI
Inquiry command is received, the UDC driver interrupt routine will
receive it first. However, the queue function is not yet called, and
queue buffer is not yet
On Fri, Mar 15, 2013 at 10:11:04AM +0200, Felipe Balbi wrote:
Hi,
if you look at your PCB, VBUS, D+ and D- are directly routed to the PHY,
not the USB controller itself.
If you read ULPI and UTMI specs, you'll see that there are methods for
the PHY to tell the USB controller about VBUS
On Fri, Mar 15, 2013 at 04:26:10PM +0800, victor yeo wrote:
Hi,
On Fri, Mar 15, 2013 at 01:59:30PM +0800, victor yeo wrote:
For bulk transfer, the new UDC driver has one problem. When SCSI
Inquiry command is received, the UDC driver interrupt routine will
receive it first. However, the
On Fri, Mar 15, 2013 at 12:08:54PM +0800, Ming Lei wrote:
If suspend callback fails in system sleep context, usb core will
ignore the failure and let system sleep go ahead further, so
this patch comments on the case and requires that serial-type-suspend()
MUST return 0 in system sleep context.
Hi Folks,
this patch set depends on [1] which makes PHY layer
*always* return an error as suggested by Alan Stern.
I have compiled what I could, please go over the
patches and give your Acked-by or NAK it if you think
there's something wrong with any of the patches.
cheers
[1]
PHY layer no longer returns NULL. It will
return -ENXIO when PHY layer isn't enabled
and we can use that to bail out instead of
request a probe deferral.
Signed-off-by: Felipe Balbi ba...@ti.com
---
drivers/usb/dwc3/core.c | 24 ++--
1 file changed, 22 insertions(+), 2
PHY layer no longer returns NULL. It will
return -ENXIO when PHY layer isn't enabled
and we can use that to bail out instead of
request a probe deferral.
Signed-off-by: Felipe Balbi ba...@ti.com
---
drivers/usb/gadget/mv_udc_core.c | 11 +++
1 file changed, 7 insertions(+), 4
PHY laye rno longer return NULL. We need to
switch over from IS_ERR_OR_NULL() to IS_ERR().
Signed-off-by: Felipe Balbi ba...@ti.com
---
drivers/usb/gadget/s3c-hsotg.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/drivers/usb/gadget/s3c-hsotg.c
PHY layer no longer returns NULL. It will
return -ENXIO when PHY layer isn't enabled
and we can use that to bail out instead of
request a probe deferral.
Signed-off-by: Felipe Balbi ba...@ti.com
---
drivers/usb/musb/omap2430.c | 7 ++-
1 file changed, 6 insertions(+), 1 deletion(-)
diff
PHY layer no longer returns NULL. We must
switch from IS_ERR_OR_NULL() to IS_ERR().
Signed-off-by: Felipe Balbi ba...@ti.com
---
drivers/usb/host/ehci-mv.c | 19 +--
1 file changed, 9 insertions(+), 10 deletions(-)
diff --git a/drivers/usb/host/ehci-mv.c
PHY layer no longer returns NULL, we must
switch from IS_ERR_OR_NULL() to IS_ERR().
Signed-off-by: Felipe Balbi ba...@ti.com
---
drivers/usb/host/ehci-tegra.c | 12 +++-
1 file changed, 3 insertions(+), 9 deletions(-)
diff --git a/drivers/usb/host/ehci-tegra.c
PHY layer no longer returns NULL. We must
switch from IS_ERR_OR_NULL() to IS_ERR().
Signed-off-by: Felipe Balbi ba...@ti.com
---
drivers/usb/host/ehci-s5p.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/drivers/usb/host/ehci-s5p.c b/drivers/usb/host/ehci-s5p.c
index
PHY layer no longer returns NULL. We must
switch from IS_ERR_OR_NULL() to IS_ERR().
Signed-off-by: Felipe Balbi ba...@ti.com
---
drivers/usb/host/ohci-exynos.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/drivers/usb/host/ohci-exynos.c b/drivers/usb/host/ohci-exynos.c
PHY layer no longer returns NULL. We must
switch from IS_ERR_OR_NULL() to IS_ERR().
Signed-off-by: Felipe Balbi ba...@ti.com
---
drivers/usb/host/ehci-msm.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/drivers/usb/host/ehci-msm.c b/drivers/usb/host/ehci-msm.c
index
I have the same problem on my Lenovo T500. I think the graphics card is
involved.
This laptop has hybrid graphics - one Intel GMA 4500MHD and one ATI
Mobility Radeon HD 3650. When I boot with the Intel card, I get irq 16:
nobody cared during boot, not when I boot with the ATI card.
And
On 03/14/2013 06:54 PM, Tony Lindgren wrote:
* Roger Quadros rog...@ti.com [130314 08:45]:
OK. Let me know how the below patch looks. After that, the board code
will look like.
static struct usbhs_phy_data phy_data[] = {
{
.reset_gpio = 147,
.vcc_gpio = 148
On Wed, Mar 13, 2013 at 03:43:43PM -0400, Peter Hurley wrote:
On Thu, 2013-03-07 at 15:55 +0100, Johan Hovold wrote:
Make sure to check ASYNC_INITIALISED before raising DTR when waking up
from blocked open in tty_port_block_til_ready.
Currently DTR could get raised at hang up as a
On Wed, Mar 13, 2013 at 03:50:32PM -0400, Peter Hurley wrote:
On Thu, 2013-03-07 at 15:55 +0100, Johan Hovold wrote:
These patches against 3.9-rc1 fix a few issues with tty-port hangup and
close.
The first and fifth patch are essentially clean ups.
The second and third patch fix the
On Fri, Mar 15, 2013 at 09:51:29AM +0200, Felipe Balbi wrote:
that's all wrong and needs to be fixed. UDC-core has to be the central
point for all these details. We start with the easiest way (call connect
unconditionally after gadget driver is loaded) and optimize it as we go
(making sure
Hi Kishon,
On 03/13/2013 10:11 AM, kishon wrote:
Benoit,
Will you be queuing this patch series?
I'm reviewing them right now.
Regards,
Benoit
Thanks
Kishon
On Thursday 07 March 2013 07:05 PM, Kishon Vijay Abraham I wrote:
Hi Benoit,
Here are the dt data patches to get usb device
Peter Chen peter.c...@freescale.com writes:
On Thu, Mar 14, 2013 at 12:31:38PM +0200, Alexander Shishkin wrote:
Peter Chen peter.c...@freescale.com writes:
Hi Alex and all,
Currently, we have two problems to block chipidea driver coming
development.
As there are so many chipidea
Hi,
On Fri, Mar 15, 2013 at 06:04:08PM +0800, Peter Chen wrote:
On Fri, Mar 15, 2013 at 09:51:29AM +0200, Felipe Balbi wrote:
that's all wrong and needs to be fixed. UDC-core has to be the central
point for all these details. We start with the easiest way (call connect
unconditionally
On Fri, 2013-03-15 at 10:24 +0100, Johan Hovold wrote:
On Wed, Mar 13, 2013 at 03:43:43PM -0400, Peter Hurley wrote:
On Thu, 2013-03-07 at 15:55 +0100, Johan Hovold wrote:
Make sure to check ASYNC_INITIALISED before raising DTR when waking up
from blocked open in tty_port_block_til_ready.
On Fri, Mar 15, 2013 at 07:03:08AM -0400, Peter Hurley wrote:
On Fri, 2013-03-15 at 10:24 +0100, Johan Hovold wrote:
On Wed, Mar 13, 2013 at 03:43:43PM -0400, Peter Hurley wrote:
On Thu, 2013-03-07 at 15:55 +0100, Johan Hovold wrote:
Make sure to check ASYNC_INITIALISED before raising
On Fri, 2013-03-15 at 12:30 +0100, Johan Hovold wrote:
On Fri, Mar 15, 2013 at 07:03:08AM -0400, Peter Hurley wrote:
On Fri, 2013-03-15 at 10:24 +0100, Johan Hovold wrote:
On Wed, Mar 13, 2013 at 03:43:43PM -0400, Peter Hurley wrote:
On Thu, 2013-03-07 at 15:55 +0100, Johan Hovold wrote:
On Thu, Mar 14, 2013 at 5:48 PM, Felipe Balbi ba...@ti.com wrote:
On Thu, Mar 14, 2013 at 11:53:57AM +0530, Kishon Vijay Abraham I wrote:
Used devres APIs devm_request_threaded_irq and devm_regulator_get for
requesting irq and for getting regulator respectively.
Signed-off-by: Kishon Vijay
On Thu, 2013-03-14 at 19:30 +0100, Johan Hovold wrote:
On Thu, Mar 14, 2013 at 01:39:39PM -0400, Peter Hurley wrote:
On Thu, 2013-03-14 at 16:23 +0100, Johan Hovold wrote:
Make sure to unregister the tty-device before calling subdriver
port_remove.
This way remove will reverse
On Fri, Mar 15, 2013 at 02:00:33PM +0200, Grazvydas Ignotas wrote:
On Thu, Mar 14, 2013 at 5:48 PM, Felipe Balbi ba...@ti.com wrote:
On Thu, Mar 14, 2013 at 11:53:57AM +0530, Kishon Vijay Abraham I wrote:
Used devres APIs devm_request_threaded_irq and devm_regulator_get for
requesting irq
On Fri, Mar 15, 2013 at 12:38:07PM +0200, Alexander Shishkin wrote:
I'd say, in the core driver:
1) get dr_mode from platform data
2) only if that's DR_MODE_UNKNOWN (iirc), read DCCPARAMS, since it's
not guaranteed to work across all chipideas;
3) if dr_mode == OTG or dr_mode
Hello.
On 15-03-2013 4:25, Kuninori Morimoto wrote:
0x ===
EHCI
--
0x0094 PHY
0x009C PHY
--
EHCI
0x0400 ==
...
0x0800 --
PHY
0x0900
On Fri, Mar 15, 2013 at 12:37:01PM +0200, Felipe Balbi wrote:
*/
static inline int usb_gadget_disconnect(struct usb_gadget *gadget)
{
+ int ret = 0;
+
if (!gadget-ops-pullup)
return -EOPNOTSUPP;
- return gadget-ops-pullup(gadget, 0);
+
+ if
Hello Alan again, we will clear things up. Sorry for the late reply,
dark forces delayed us.
Intel probably doesn't care, because they don't make the affected
chipsets any more. I don't know what AMD is currently making. Do you?
Yes we do. One of our ICH5 board uses ICH5 with SL7YC SL spec,
Hello ,here are the logs from the failing EHCI hosts(chipset-SL
Spec/revision@mainboard-system):
ICH4-SL66K@FIC VC37
00:1d.7 USB Controller [0c03]: Intel Corporation 82801DB/DBM
(ICH4/ICH4-M) USB2 EHCI Controller [8086:24cd] (rev 01) (prog-if 20
[EHCI])
Subsystem: FIRST INTERNATIONAL
+ Jon
Hi Kishon,
On 03/07/2013 02:35 PM, Kishon Vijay Abraham I wrote:
Hi Benoit,
Here are the dt data patches to get usb device functional in OMAP platforms.
All the patches deal with modifying arch/arm/boot except one which modifies
Documentation/../usb/omap-usb.txt
Changes from v2:
Peter Chen a écrit :
On Fri, Mar 15, 2013 at 12:38:07PM +0200, Alexander Shishkin wrote:
Do you see any problems with this?
How to know vbus status if dr_mode == gadget, we need to indicate connection
and disconnection?
We don't. Do we need to indicate vbus session valid for gadget only
Having twl4030_usb_phy_init() (detects if a cable is connected before
twl4030 is probed) in twl4030 probe makes cable connect events to be
missed by musb glue, since it gets loaded after twl4030. Having
twl4030_usb_phy_init as a usb_phy ops lets twl4030_usb_phy_init to be
called when glue is
Used devres APIs devm_request_threaded_irq and devm_regulator_get for
requesting irq and for getting regulator respectively.
Signed-off-by: Kishon Vijay Abraham I kis...@ti.com
Tested-by: Grazvydas Ignotas nota...@gmail.com
---
drivers/usb/phy/phy-twl4030-usb.c | 28
musb does not use DMA buffer for ep0 but it uses the same giveback
function *musb_g_giveback* for all endpoints (*musb_g_ep0_giveback* calls
*musb_g_giveback*). So for ep0 case request.dma will be '0'
and will result in kernel OOPS if tried to *unmap_dma_buffer* for requests in
ep0. Fixed it by
commit 63378a (usb: phy: remove CONFIG_USB_OTG_UTILS) removed
CONFIG_USB_OTG_UTILS from Kconfig but failed to removed from Makefile.
Fixed it here.
Signed-off-by: Kishon Vijay Abraham I kis...@ti.com
---
drivers/usb/Makefile |2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git
On Fri, 15 Mar 2013, Harald Arnesen wrote:
I have the same problem on my Lenovo T500. I think the graphics card is
involved.
This laptop has hybrid graphics - one Intel GMA 4500MHD and one ATI
Mobility Radeon HD 3650. When I boot with the Intel card, I get irq 16:
nobody cared during boot,
On Friday 15 March 2013 06:11 PM, Benoit Cousson wrote:
+ Jon
Hi Kishon,
On 03/07/2013 02:35 PM, Kishon Vijay Abraham I wrote:
Hi Benoit,
Here are the dt data patches to get usb device functional in OMAP platforms.
All the patches deal with modifying arch/arm/boot except one which modifies
On Fri, Mar 15 2013, UCHINO Satoshi satoshi.uch...@toshiba.co.jp wrote:
Without this memory barrier, the file-storage thread may fail to
escape from the following while loop, because it may observe new
common-thread_wakeup_needed and old bh-state which are updated by
the callback functions.
On Fri, Mar 15, 2013 at 06:58:49PM +0530, Kishon Vijay Abraham I wrote:
commit 63378a (usb: phy: remove CONFIG_USB_OTG_UTILS) removed
CONFIG_USB_OTG_UTILS from Kconfig but failed to removed from Makefile.
Fixed it here.
Signed-off-by: Kishon Vijay Abraham I kis...@ti.com
I can fold it in
On Fri, Mar 15, 2013 at 06:58:50PM +0530, Kishon Vijay Abraham I wrote:
musb does not use DMA buffer for ep0 but it uses the same giveback
function *musb_g_giveback* for all endpoints (*musb_g_ep0_giveback* calls
*musb_g_giveback*). So for ep0 case request.dma will be '0'
and will result in
On Fri, 15 Mar 2013, Soeren Moch wrote:
The log shows a 1-1 match between allocations and deallocations, except
for three excess allocations about 45 lines before the end. I have no
idea what's up with those. They may be an artifact arising from where
you stopped copying the log data.
From: Kishon Vijay Abraham I kis...@ti.com
musb does not use DMA buffer for ep0 but it uses the same giveback
function *musb_g_giveback* for all endpoints (*musb_g_ep0_giveback* calls
*musb_g_giveback*). So for ep0 case request.dma will be '0'
and will result in kernel OOPS if tried to
On Fri, 15 Mar 2013, Peter Chen wrote:
On Thu, Mar 14, 2013 at 10:59:45AM -0400, Alan Stern wrote:
On Thu, 14 Mar 2013, Peter Chen wrote:
/home/b29397/work/code/git/linus/linux-2.6/drivers/usb/host/xhci-ring.c:
In function ‘handle_port_status’:
On Fri, 15 Mar 2013, Felipe Balbi wrote:
Adding this back in revealed a bug in udc-core. It is fixed as
follows:
Index: usb-3.9/drivers/usb/gadget/udc-core.c
===
--- usb-3.9.orig/drivers/usb/gadget/udc-core.c
+++
On Fri, 15 Mar 2013, Felipe Balbi wrote:
On Fri, Mar 15, 2013 at 04:26:10PM +0800, victor yeo wrote:
Hi,
On Fri, Mar 15, 2013 at 01:59:30PM +0800, victor yeo wrote:
For bulk transfer, the new UDC driver has one problem. When SCSI
Inquiry command is received, the UDC driver
On Fri, 15 Mar 2013, Felipe Balbi wrote:
Hi Folks,
this patch set depends on [1] which makes PHY layer
*always* return an error as suggested by Alan Stern.
I have compiled what I could, please go over the
patches and give your Acked-by or NAK it if you think
there's something wrong with
On Fri, 15 Mar 2013, Noone Nowhere wrote:
Hello Alan again, we will clear things up. Sorry for the late reply,
dark forces delayed us.
Intel probably doesn't care, because they don't make the affected
chipsets any more. I don't know what AMD is currently making. Do you?
Yes we do.
On Fri, Mar 15, 2013 at 09:37:02AM +0200, Felipe Balbi wrote:
On Thu, Mar 14, 2013 at 03:25:05PM -0700, Greg KH wrote:
FYI, I just applied this patch to my staging and USB trees, hopefully
this makes some people here happy.
From: Greg Kroah-Hartman
On Fri, 15 Mar 2013, Jiri Kosina wrote:
I have the same problem on my Lenovo T500. I think the graphics card is
involved.
This laptop has hybrid graphics - one Intel GMA 4500MHD and one ATI
Mobility Radeon HD 3650. When I boot with the Intel card, I get irq 16:
nobody cared during
Peter Chen peter.c...@freescale.com writes:
On Fri, Mar 15, 2013 at 12:38:07PM +0200, Alexander Shishkin wrote:
I'd say, in the core driver:
1) get dr_mode from platform data
2) only if that's DR_MODE_UNKNOWN (iirc), read DCCPARAMS, since it's
not guaranteed to work across all
Adds device nodes for HS USB Host module, TLL module,
OHCI and EHCI controllers.
CC: Benoît Cousson b-cous...@ti.com
Signed-off-by: Roger Quadros rog...@ti.com
---
arch/arm/boot/dts/omap3.dtsi | 31 +++
1 files changed, 31 insertions(+), 0 deletions(-)
diff --git
Provide RESET and Power regulators for the USB PHY,
the USB Host port mode and the PHY device.
Also provide pin multiplexer information for USB host
pins.
CC: Benoît Cousson b-cous...@ti.com
Signed-off-by: Roger Quadros rog...@ti.com
---
arch/arm/boot/dts/omap3-beagle.dts | 71
Add platform device for 'nop-usb-xceiv'. This will be used as a
PHY for HS USB Port 2, so provide binding information for it.
Use usbhs_init_phys() to register the PHY's RESET regulator.
VAUX2 supplies the PHY's VCC.
Signed-off-by: Roger Quadros rog...@ti.com
---
Add 2 platform devices for 'nop-usb-xceiv'. These will be used as a
PHY for HS USB Ports 1 and 2, so provide binding information for them.
Use usbhs_init_phys() to register the PHY's RESET regulator.
Signed-off-by: Roger Quadros rog...@ti.com
---
arch/arm/mach-omap2/board-omap3touchbook.c |
Add platform device for 'nop-usb-xceiv'. This will be used as a
PHY for HS USB Port 2, so provide binding information for it.
Use usbhs_init_phys() to register the PHY's RESET regulator.
Signed-off-by: Roger Quadros rog...@ti.com
---
arch/arm/mach-omap2/board-omap3stalker.c | 29
Provide the RESET and Power regulators for the USB PHY,
the USB Host port mode and the PHY device.
Also provide pin multiplexer information for the USB host
pins.
CC: Benoît Cousson b-cous...@ti.com
Signed-off-by: Roger Quadros rog...@ti.com
---
arch/arm/boot/dts/omap4-panda.dts | 56
Add platform device for 'nop-usb-xceiv'. This will be used as a
PHY for HS USB Port 2, so provide binding information for it.
Use usbhs_init_phys() to register the PHY's RESET regulator.
Signed-off-by: Roger Quadros rog...@ti.com
---
arch/arm/mach-omap2/board-zoom.c | 32
Add platform device for 'nop-usb-xceiv'. This will be used as a
PHY for HS USB Port 2, so provide binding information for it.
Use usbhs_init_phys() to register the PHY's RESET regulator.
Signed-off-by: Roger Quadros rog...@ti.com
---
arch/arm/mach-omap2/board-overo.c | 32
Add 2 platform devices for 'nop-usb-xceiv'. These will be used
as PHYs for HS USB ports 1 and 2 so provide binding information
for them.
Use usbhs_init_phys() to register the PHY's RESET regulators.
Signed-off-by: Roger Quadros rog...@ti.com
---
arch/arm/mach-omap2/board-3430sdp.c | 47
Add platform device for 'nop-usb-xceiv'. This will be used as a
PHY for HS USB Port 1, so provide binding information for it.
Use usbhs_init_phys() to register the PHY's VCC and RESET
regulators.
Signed-off-by: Roger Quadros rog...@ti.com
---
arch/arm/mach-omap2/board-am3517crane.c | 38
Add 2 platform devices for 'nop-usb-xceiv'. These will be used
as PHYs for HS USB ports 1 and 2 so provide binding information
for them.
Use usbhs_init_phys() to register the PHY's RESET regulators.
Signed-off-by: Roger Quadros rog...@ti.com
---
arch/arm/mach-omap2/board-cm-t35.c | 45
Add 2 platform devices for 'nop-usb-xceiv'. These will be used
as PHYs for HS USB ports 1 and 2 so provide binding information
for them.
Use usbhs_init_phys() to register the PHY's RESET regulators.
Signed-off-by: Roger Quadros rog...@ti.com
---
arch/arm/mach-omap2/board-igep0020.c | 66
Add platform device for 'nop-usb-xceiv'. This will be used as a
PHY for HS USB Port 2, so provide binding information for it.
Use usbhs_init_phys() to register the PHY's RESET regulator.
VAUX2 supplies the PHY's VCC.
Signed-off-by: Roger Quadros rog...@ti.com
---
Add platform device for 'nop-usb-xceiv'. This will be used as a
PHY for HS USB Port 1, so provide binding information for it.
Signed-off-by: Roger Quadros rog...@ti.com
Acked-by: Felipe Balbi ba...@ti.com
---
arch/arm/mach-omap2/board-devkit8000.c | 20
1 files changed, 12
On Fri, Mar 15, 2013 at 08:02:45AM -0400, Peter Hurley wrote:
On Thu, 2013-03-14 at 19:30 +0100, Johan Hovold wrote:
On Thu, Mar 14, 2013 at 01:39:39PM -0400, Peter Hurley wrote:
On Thu, 2013-03-14 at 16:23 +0100, Johan Hovold wrote:
Make sure to unregister the tty-device before calling
On Fri, 15 Mar 2013, Noone Nowhere wrote:
USB stick on 12 different EHCI USB hosts. On VT8235M it took ages to
go to 1000. A human readable timestamp could be used.
Evidently the VT8235M is very slow for some of the operations used by
the test program.
To sum up printing a start up message
Add 2 platform devices for 'nop-usb-xceiv'. These will be used
as PHYs for HS USB ports 1 and 2 so provide binding information
for them.
Use usbhs_init_phys() to register the PHY's RESET regulators.
Signed-off-by: Roger Quadros rog...@ti.com
---
arch/arm/mach-omap2/board-cm-t3517.c | 45
Add 2 platform devices for 'nop-usb-xceiv'. These will be used as a
PHY for HS USB Port 1 and 2, so provide binding information for them.
Use usbhs_init_phys() to register the PHY's RESET regulators.
Signed-off-by: Roger Quadros rog...@ti.com
---
arch/arm/mach-omap2/board-am3517evm.c | 41
Add 2 platform devices for 'nop-usb-xceiv'. These will be used
as PHYs for HS USB ports 1 and 2 so provide binding information
for them.
Use usbhs_init_phys() to register the PHY's RESET regulators.
Signed-off-by: Roger Quadros rog...@ti.com
---
arch/arm/mach-omap2/board-3630sdp.c | 48
Add platform device for 'nop-usb-xceiv'. This will be used as a
PHY for HS USB Port 2, so provide binding information for it.
Use usbhs_init_phys() to register the PHY's VCC and RESET
regulators.
Signed-off-by: Roger Quadros rog...@ti.com
---
arch/arm/mach-omap2/board-omap3beagle.c | 44
Hi Tony,
These patches provide the SoC side code required to support
the changes in the OMAP USB Host drivers done in [1], [2] [3].
Device tree support is added for Beagleboard and Panda.
NOTE: The first patch needs to be shared between the
OMAP tree and Felipe's USB tree.
v2:
- Added helper
This helper allows board support code to add the PHY's
VCC and RESET regulators which are GPIO controlled.
It also links the vcc and reset supplies to the
PHY's device ID that is supplied in the struct usbhs_phy_data
argument.
Signed-off-by: Roger Quadros rog...@ti.com
---
Use usbhs_init_phys() to register the PHY's VCC and RESET
regulators.
The VCC and RESET will then be managed by the PHY driver.
Signed-off-by: Roger Quadros rog...@ti.com
---
arch/arm/mach-omap2/board-omap4panda.c | 37 +--
1 files changed, 11 insertions(+), 26
Add platform device and data for 'nop-usb-xceiv'. This will be used
as PHY for HS USB port 1, so provide binding information for it.
Get rid of managing the PHY clock as it will be done by the PHY driver.
For that to work we create a clock alias that links the PHY clock name
to the PHY device
1 - 100 of 150 matches
Mail list logo
