On Mon, Mar 04, 2013 at 11:26:07AM +0800, Peter Chen wrote:
> On Fri, Mar 01, 2013 at 03:42:24PM +0100, Michael Grzeschik wrote:
> > The implementation is derived from the fsl_udc_core code in
> > fsl_ep_enable and makes basic iso handling possible.
> >
> > Signed-off-by: Michael Grzeschik
> > Si
On Wed, Mar 06, 2013 at 11:33:02AM +0100, Maxime Ripard wrote:
> Hi,
>
> Just noticed this in 3.9-rc1 on an iMX28 (ARM) board with a config
> based on mxs_defconfig. I'm using the patchset "Add tested id switch
> and vbus connect detect support for Chipidea" from Peter Chen in its
> 10th version [
On Tue, Mar 05, 2013 at 04:40:12PM +0800, Peter Chen wrote:
> On Fri, Mar 01, 2013 at 03:42:26PM +0100, Michael Grzeschik wrote:
> > Instead of having a limited number of usable tds in the udc we use a
> > linked list to support dynamic amount of needed tds for all special
> > gadget types. This im
>
> I will add defines und use them.
>
> > > + max &= 0x7ff; /* bit 0~10 */
> >
> > Useless line?
>
> Not intended. I will have to change the capability
> setting of the qh to use max instead of mEp->ep.maxpacket.
mult = (unsigned char)(1 + ((max >> 11) & 0x03));
On Tue, Mar 05, 2013 at 05:13:54PM +0800, Peter Chen wrote:
> On Fri, Mar 01, 2013 at 03:42:27PM +0100, Michael Grzeschik wrote:
> > This patch removes the limitation of having a limited amount of only
> > four active tds on one endpoint. We use the linked list implementation
> > to manage all tds
Add transceiver notifier event handling to the ux500 driver to set vbus
on specific transceiver events.
Acked-by: Linus Walleij
Signed-off-by: Fabio Baltieri
---
drivers/usb/musb/ux500.c | 42 ++
1 file changed, 42 insertions(+)
diff --git a/drivers/usb/
Hi,
We try to get our device (based on p2020rdb) usb 2.0 compliant. We ran the
usb30cv test suite (version 1.0.1.2, chapter 9 tests for usb 2.0 devices) on
win7 with g_zero and g_serial. We access the device via an usb 3.0 hcd from
intel. Our device runs the 3.2.35-rt52 kernel. I spotted the fo
On Thu, Mar 07, 2013 at 09:16:12AM +0100, Michael Grzeschik wrote:
> On Tue, Mar 05, 2013 at 04:40:12PM +0800, Peter Chen wrote:
> > On Fri, Mar 01, 2013 at 03:42:26PM +0100, Michael Grzeschik wrote:
> > > Instead of having a limited number of usable tds in the udc we use a
> > > linked list to sup
On Thu, Mar 07, 2013 at 04:57:40PM +0800, Fabio Baltieri wrote:
> Add transceiver notifier event handling to the ux500 driver to set vbus
> on specific transceiver events.
>
> Acked-by: Linus Walleij
> Signed-off-by: Fabio Baltieri
> ---
Sorry, I forgot about:
v2:
- turn off vbus on USB_EVENT_
On Fri, Mar 01, 2013 at 03:42:26PM +0100, Michael Grzeschik wrote:
> Instead of having a limited number of usable tds in the udc we use a
> linked list to support dynamic amount of needed tds for all special
> gadget types. This improves throughput.
>
Is it better just allocate td at ep_queue? F
>
> > > - mReq->req.actual = node_first->ptr->token & TD_TOTAL_BYTES;
> > > - mReq->req.actual >>= ffs_nr(TD_TOTAL_BYTES);
> > > - mReq->req.actual = mReq->req.length - mReq->req.actual;
> > > + mReq->req.actual = actual;
> >
> > If the mReq->req.actual will be changed at below line, any reas
CONFIG_USB_OTG_UTILS will be removed very
soon, so we should check CONFIG_USB_PHY
instead.
Signed-off-by: Felipe Balbi
---
drivers/power/pda_power.c | 14 +++---
1 file changed, 7 insertions(+), 7 deletions(-)
diff --git a/drivers/power/pda_power.c b/drivers/power/pda_power.c
index 7df7
We already have a considerable amount of USB
PHY drivers, making it a menuconfig just
prevents us from adding too much churn to
USB's menuconfig.
While at that, also select USB_OTG_UTILS from
this new menuconfig just to keep backwards
compatibility until we manage to remove
that symbol.
Signed-of
otg.c only had a single function definition
which might make more sense to be placed in
usb-common.c. While doing that, we also delete
otg.c since it's now empty.
Signed-off-by: Felipe Balbi
---
drivers/usb/otg/Makefile | 3 ---
drivers/usb/otg/otg.c| 47
CONFIG_USB_OTG_UTILS will be removed very
soon, so we should check CONFIG_USB_PHY
instead.
Signed-off-by: Felipe Balbi
---
drivers/usb/host/ehci-tegra.c | 6 +++---
1 file changed, 3 insertions(+), 3 deletions(-)
diff --git a/drivers/usb/host/ehci-tegra.c b/drivers/usb/host/ehci-tegra.c
index 5
there are no more users of CONFIG_USB_OTG_UTILS
left in tree, we can remove it just fine.
Signed-off-by: Felipe Balbi
---
drivers/usb/phy/Kconfig | 23 ---
1 file changed, 23 deletions(-)
diff --git a/drivers/usb/phy/Kconfig b/drivers/usb/phy/Kconfig
index 832cd69..97de6de 1
that's a much more reasonable location for
those drivers. It helps us saving drivers/usb/otg/
for when we actually start adding generic OTG
code.
Also completely delete drivers/usb/otg/ as there's
nothing left there.
Signed-off-by: Felipe Balbi
---
drivers/usb/Kconfig | 2
CONFIG_USB_OTG_UTILS will be removed very
soon, so we should check CONFIG_USB_PHY
instead.
Signed-off-by: Felipe Balbi
---
drivers/usb/gadget/mv_udc_core.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/drivers/usb/gadget/mv_udc_core.c b/drivers/usb/gadget/mv_udc_core.c
inde
Hi folks,
inspired by Paul's DWC2 patchset which added usb_otg_state_string()
(a copy of otg_state_string()) I have now renamed otg_state_string()
to usb_otg_state_string(), moved it to usb-common, then moved all
phy drivers to drivers/usb/phy/ and completely deleted the otg directory.
We're also
we only want GPL users for our generic functions,
so let's switch over to EXPORT_SYMBOL_GPL.
Signed-off-by: Felipe Balbi
---
drivers/usb/phy/phy.c | 20 ++--
1 file changed, 10 insertions(+), 10 deletions(-)
diff --git a/drivers/usb/phy/phy.c b/drivers/usb/phy/phy.c
index bc1970
all other functions under drivers/usb/ start
with usb_, let's do the same thing.
This patch is in preparation for moving otg_state_string
to usb-common.c and deleting otg.c completely.
Signed-off-by: Felipe Balbi
---
drivers/usb/musb/am35x.c| 8
drivers/usb/musb/blackfin.c
CONFIG_USB_OTG_UTILS will be removed very
soon, so we should check CONFIG_USB_PHY
instead.
Signed-off-by: Felipe Balbi
---
drivers/usb/host/ehci-mv.c | 4 ++--
1 file changed, 2 insertions(+), 2 deletions(-)
diff --git a/drivers/usb/host/ehci-mv.c b/drivers/usb/host/ehci-mv.c
index 3065809..975
On Wed, Mar 06, 2013 at 02:14:56PM -0500, Peter Hurley wrote:
> On Wed, 2013-03-06 at 17:52 +0100, Johan Hovold wrote:
>
> > > > @@ -225,15 +232,13 @@ void tty_port_hangup(struct tty_port *port)
> > > spin_lock_irqsave(&port->lock, flags);
> > > port->count = 0;
> > > port-
On Thu, Mar 07, 2013 at 09:42:58AM +0200, Felipe Balbi wrote:
> Hi,
>
> On Thu, Mar 07, 2013 at 12:58:04AM +, Paul Zimmerman wrote:
> > > From: Felipe Balbi [mailto:ba...@ti.com]
> > > Sent: Tuesday, March 05, 2013 11:42 PM
> > > On Mon, Mar 04, 2013 at 12:21:44PM -0800, Paul Zimmerman wrote:
On Thu, Mar 07, 2013 at 09:58:52AM +0100, Peter Bestler wrote:
> Hi,
>
> We try to get our device (based on p2020rdb) usb 2.0 compliant. We ran the
> usb30cv test suite (version 1.0.1.2, chapter 9 tests for usb 2.0 devices) on
> win7 with g_zero and g_serial. We access the device via an usb 3.0
Hi,
On Thu, Mar 07, 2013 at 10:36:13AM +0800, Peter Chen wrote:
> > > diff --git a/drivers/usb/chipidea/udc.c b/drivers/usb/chipidea/udc.c
> > > index e82dae4..70f9f2d 100644
> > > --- a/drivers/usb/chipidea/udc.c
> > > +++ b/drivers/usb/chipidea/udc.c
> > > @@ -91,8 +91,10 @@ static int hw_device
On Thu, Mar 07, 2013 at 10:41:03AM +0800, Peter Chen wrote:
> On Wed, Mar 06, 2013 at 01:29:16PM +0200, Felipe Balbi wrote:
> > Hi,
> >
> > On Wed, Mar 06, 2013 at 05:56:37PM +0800, Peter Chen wrote:
> > > For boards which have board level vbus control (eg, gpio), we
> > > need to operation vbus a
Hi Peter,
Le 07/03/2013 09:08, Peter Chen a écrit :
> On Wed, Mar 06, 2013 at 11:33:02AM +0100, Maxime Ripard wrote:
>> [2.149645] other info that might help us debug this:
>> [2.149645]
>> [2.157667] Possible unsafe locking scenario:
>> [2.157667]
>> [2.163598]CPU0
On Thu, Mar 07, 2013 at 05:10:57PM +0800, Fabio Baltieri wrote:
> On Thu, Mar 07, 2013 at 04:57:40PM +0800, Fabio Baltieri wrote:
> > Add transceiver notifier event handling to the ux500 driver to set vbus
> > on specific transceiver events.
> >
> > Acked-by: Linus Walleij
> > Signed-off-by: Fabi
Modern speed handling has been introduced by commit
9b80fee149a875a6292b2556ab2c64dc7ab7d6f5 in 2009 and the
acm_tty_speed array has been unused since.
Signed-off-by: Samuel Tardieu
---
drivers/usb/class/cdc-acm.c | 8
1 file changed, 8 deletions(-)
diff --git a/drivers/usb/class/cdc-a
On Thursday 07 March 2013 11:39:28 Samuel Tardieu wrote:
> Modern speed handling has been introduced by commit
> 9b80fee149a875a6292b2556ab2c64dc7ab7d6f5 in 2009 and the
> acm_tty_speed array has been unused since.
>
> Signed-off-by: Samuel Tardieu
Acked-by: Oliver Neukum
--
To unsubscribe from
Modern speed handling has been introduced in 2009 by commit
9b80fee149a875a6292b2556ab2c64dc7ab7d6f5 (cdc_acm: Fix to use modern
speed interfaces) and the acm_tty_speed array has been unused since.
Signed-off-by: Samuel Tardieu
Acked-by: Oliver Neukum
---
drivers/usb/class/cdc-acm.c | 8 ---
"Fangxiaozhi (Franko)" writes:
> As far as I know, except switching in kernel, there isn't any
> mode switch solution on Android now. Do you have any good ideas
> for the mode switch on Android system?
Josh, the usb_modeswitch maintainer, is also maintaining this Android app:
On 04.03.2013 00:53, Daniel Mack wrote:
> Hi Peter,
>
> On 03.03.2013 23:24, Peter Korsgaard wrote:
>>> "Daniel" == Daniel Mack writes:
>>
>> Hi,
>>
>> Daniel> On my board, the USB is purely used as host interface, with a
>> Daniel> type B plug soldered. In the DT, I'm using the following
>
*dma_mask* is not set for devices created from dt data. So filled dma_mask
for dwc3_omap device here. And dwc3 core will copy the dma_mask from its
parent.
Signed-off-by: Kishon Vijay Abraham I
---
drivers/usb/dwc3/core.c |4
drivers/usb/dwc3/dwc3-omap.c |3 +++
2 files changed
return -EPROBE_DEFER from dwc3_omap_mailbox in dwc3-omap.c, if the probe of
dwc3-omap has not yet been executed or failed.
Signed-off-by: Kishon Vijay Abraham I
---
drivers/usb/dwc3/dwc3-omap.c |7 +--
include/linux/usb/dwc3-omap.h |6 +++---
2 files changed, 8 insertions(+), 5 dele
Added palmas-usb driver which is mainly used as comparator driver to
detect vbus/id events when a USB cable is connected and passes on the
event information to omap glue (dwc3-omap.c)
The other fixes include setting dma_mask for dwc3 device since device
tree doesn't fill dma_mask, returning EPROBE
No functional change. Replace *_* with *-* in property names of otg to
follow the general convention.
Signed-off-by: Kishon Vijay Abraham I
---
Documentation/devicetree/bindings/usb/omap-usb.txt | 12 ++--
drivers/usb/musb/omap2430.c|6 +++---
2 files change
From: Graeme Gregory
This is the driver for the OTG transceiver built into the Palmas chip. It
handles the various USB OTG events that can be generated by cable
insertion/removal.
Signed-off-by: Graeme Gregory
Signed-off-by: Moiz Sonasath
Signed-off-by: Ruchika Kharwar
Signed-off-by: Kishon V
Add ocp2scp data node in omap5 device tree file. The information for
the node added here can be found @
Documentation/devicetree/bindings/bus/omap-ocp2scp.txt
Signed-off-by: Kishon Vijay Abraham I
---
arch/arm/boot/dts/omap5.dtsi |8
1 file changed, 8 insertions(+)
diff --git a/arc
Add dwc3 omap glue data to the omap5 dt data file. The information about
the dt node added here is available @
Documentation/devicetree/bindings/usb/omap-usb.txt.
Also added dwc3 core dt data as a subnode to dwc3 omap glue data in omap5 dt
data file. The information for the entered data node is av
Add usb otg data node in omap4/omap3 device tree file. Also update
the node with board specific setting in omapx-.dts file.
The dt data specifies among others the interface type (ULPI or UTMI), mode
which is mostly OTG, power that specifies the amount of power this can supply
when in host mode.
The
Add omap-usb2 data node in omap4 device tree file. Since omap-usb2 is
connected to ocp2scp, omap-usb2 dt data is added as a child node
of ocp2scp. The information about this data node is availabe @
Documentation/devicetree/bindings/usb/usb-phy.txt
Acked-by: Felipe Balbi
Signed-off-by: Kishon Vija
Add omap control usb data in omap4 device tree file. This will have the
register address of registers to power on the PHY and to write to
mailbox. The information about this data node is available @
Documentation/devicetree/bindings/usb/omap-usb.txt
Signed-off-by: Kishon Vijay Abraham I
---
arch
Add omap-usb3 and omap-usb2 data node in omap5 device tree file.
The information for the node added here is available @
Documentation/devicetree/bindings/usb/usb-phy.txt
Signed-off-by: Kishon Vijay Abraham I
---
arch/arm/boot/dts/omap5.dtsi | 14 ++
1 file changed, 14 insertions(+)
Add omap control usb data in omap5 device tree file. This will have the
register address of registers to power on the USB2 PHY and USB3 PHY. The
information for the node added here is available in
Documentation/devicetree/bindings/usb/omap-usb.txt
Signed-off-by: Kishon Vijay Abraham I
---
arch/a
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:
* squashed the dt data for dwc3-omap with dwc3 core into a single patch.
Changes
On Thu, Mar 07, 2013 at 09:25:34AM +0100, Michael Grzeschik wrote:
> On Tue, Mar 05, 2013 at 05:13:54PM +0800, Peter Chen wrote:
> > On Fri, Mar 01, 2013 at 03:42:27PM +0100, Michael Grzeschik wrote:
> > > This patch removes the limitation of having a limited amount of only
> > > four active tds on
Am 07.03.2013 13:19, schrieb Bjørn Mork:
it looks like your app will need to be a member of the "usb" group to do
this. I assume there is a way for an app to request such permissions in
Android. Josh has obviously managed to get it.
Actually, the PPP Widget app requires access to a root shell
Add platform data for Tahvo.
Signed-off-by: Aaro Koskinen
---
arch/arm/mach-omap1/board-nokia770.c | 10 ++
1 file changed, 10 insertions(+)
diff --git a/arch/arm/mach-omap1/board-nokia770.c
b/arch/arm/mach-omap1/board-nokia770.c
index 62a15e2..91449c5 100644
--- a/arch/arm/mach-omap
Add Tahvo USB transceiver driver.
Based on old code from linux-omap tree. The original driver was written
by Juha Yrjölä, Tony Lindgren, and Timo Teräs.
Signed-off-by: Aaro Koskinen
---
drivers/usb/otg/Kconfig | 16 ++
drivers/usb/otg/Makefile|1 +
drivers/usb/otg/tahvo-usb.c | 6
omap-otg platform device will be needed also by other transceivers.
It's not possible to have multiple instances of the driver, so it needs
to be moved into a separate file so that other drivers can hook into it.
Start this change with a very simplest implementation, much of the
OMAP OTG code in i
Hi,
These patches add support for Tahvo USB transceiver and allow use both
host and peripheral modes on Nokia 770.
Patches work with 3.9-rc1, but the following fixes must be also applied:
ARM: OMAP1: fix USB host on 1710
http://marc.info/?l=linux-omap&m=135906630828618&w=2
Tahvo is a multi-function device on Nokia 770, implementing USB
transceiver and charge/battery control.
It's so close to Retu that a single driver can support both.
Signed-off-by: Aaro Koskinen
Cc: Samuel Ortiz
---
drivers/mfd/Kconfig |6 +--
drivers/mfd/retu-mfd.c | 95 ++
there are no more users of CONFIG_USB_OTG_UTILS
left in tree, we can remove it just fine.
Signed-off-by: Felipe Balbi
---
v1 -> v2:
. removed a few extra instances which my original (and stupid)
grep didn't find
drivers/power/Kconfig | 2 +-
drivers/usb/dwc3/Kconf
Hi,
On Thu, Mar 07, 2013 at 04:40:18PM +0200, Aaro Koskinen wrote:
> Tahvo is a multi-function device on Nokia 770, implementing USB
> transceiver and charge/battery control.
>
> It's so close to Retu that a single driver can support both.
>
> Signed-off-by: Aaro Koskinen
> Cc: Samuel Ortiz
>
On Thu, Mar 07, 2013 at 04:40:20PM +0200, Aaro Koskinen wrote:
> omap-otg platform device will be needed also by other transceivers.
> It's not possible to have multiple instances of the driver, so it needs
> to be moved into a separate file so that other drivers can hook into it.
>
> Start this c
On Thu, Mar 07, 2013 at 04:40:21PM +0200, Aaro Koskinen wrote:
> Add Tahvo USB transceiver driver.
>
> Based on old code from linux-omap tree. The original driver was written
> by Juha Yrjölä, Tony Lindgren, and Timo Teräs.
>
> Signed-off-by: Aaro Koskinen
> ---
> drivers/usb/otg/Kconfig |
Move wake up of processes on blocked-open and modem-status wait queues
to after port shutdown at hangup.
This way the woken up processes can use the ASYNC_INITIALIZED flag to
detect port shutdown.
Note that this is the order currently used by serial-core.
Signed-off-by: Johan Hovold
---
driver
Make sure we do not make tty-driver callbacks or wait for port to drain
on uninitialised ports (e.g. when open failed) in
tty_port_close_start().
No callback, such as flush_buffer or wait_until_sent, needs to be made
on a port that has never been opened. Neither does it make much sense to
add drai
Move HUPCL handling to port shutdown so that DTR is dropped also on hang
up (tty_port_close is a noop for hung-up ports).
Also do not try to drop DTR for uninitialised ports where it has never
been raised (e.g. after a failed open).
Note that this is also the current behaviour of serial-core.
Ni
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 fact that DTR could get raised
(rather than dropped) at hangup if there are blocked opens. [ Note that
the second patch has been s
Untangle port-shutdown logic and make sure the initialised flag is
always cleared for non-console ports.
Signed-off-by: Johan Hovold
---
drivers/tty/tty_port.c | 9 +++--
1 file changed, 7 insertions(+), 2 deletions(-)
diff --git a/drivers/tty/tty_port.c b/drivers/tty/tty_port.c
index b7ff5
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 blocked process would
raise DTR unconditionally before checking for hang up and returning.
Signed-off-by: Johan Hovold
---
drivers
Move port drain-delay handling to a separate function.
Signed-off-by: Johan Hovold
---
drivers/tty/tty_port.c | 27 ---
1 file changed, 16 insertions(+), 11 deletions(-)
diff --git a/drivers/tty/tty_port.c b/drivers/tty/tty_port.c
index cd65f7e..048cc85 100644
--- a/driv
On Wed, 6 Mar 2013, Paul Zimmerman wrote:
> > BTW, you _do_ have a race because you don't check ep->hcpriv when
> > ->urb_enqueue() is called. This means that you could queue to an
> > endpoint which is in the process of getting disabled. The urb would
> > either be lost or completed before being
this will make sure that we have sensible names
for all phy drivers. Current situation was already
quite bad with too generic names being used.
Signed-off-by: Felipe Balbi
---
drivers/usb/phy/Makefile | 42 +++---
drivers/usb/phy/{ab8500-usb.c => phy-ab8
On Thu, Mar 07, 2013 at 05:45:26PM +0200, Felipe Balbi wrote:
> this will make sure that we have sensible names
> for all phy drivers. Current situation was already
> quite bad with too generic names being used.
>
> Signed-off-by: Felipe Balbi
Hi, I compiled what I could with allmodconfig and al
On Thu, 7 Mar 2013, Felipe Balbi wrote:
> Hi folks,
>
> inspired by Paul's DWC2 patchset which added usb_otg_state_string()
> (a copy of otg_state_string()) I have now renamed otg_state_string()
> to usb_otg_state_string(), moved it to usb-common, then moved all
> phy drivers to drivers/usb/phy/
On Thu, 7 Mar 2013, Jenya Y wrote:
>
> UPDATE correction to the name of the device Apple Cinema HD Display (
> A1082)
>
> Since kernel 3.8 Apple Cinema Display's usb hub spits errors randomly at
> boot. (their count seems to be random, but the type of the error is
> always the same)
>
> As so
This patch adds comments on interface driver suspend callback
to emphasize that the failure return value is ignored by
USB core in system sleep context, so do not try to recover
device for this case and let resume/reset_resume callback
handle the suspend failure if needed.
Also kerneldoc for usb_s
Hi,
This patch adds comments on interface driver suspend callback
to emphasize that the failure return value is ignored by
USB core in system sleep context, so do not try to recover
device for this case, otherwise the recovery things may confuse
resume().
Also fixes the USB serial, HID and severa
This patch kills traffic even though type->suspend returns
failure inside usb_serial_suspend from system sleep context
because USB core ignores the failiure and lets system sleep
go ahread, so the serial URB traffic need to be killed
in this case.
Cc: Johan Hovold
Signed-off-by: Ming Lei
---
dr
Hi,
Sorry for my broken email client just now.
This patch adds comments on interface driver suspend callback
to emphasize that the failure return value is ignored by
USB core in system sleep context, so do not try to recover
device for this case, otherwise the recovery things may confuse
resume()
This patch adds comments on interface driver suspend callback
to emphasize that the failure return value is ignored by
USB core in system sleep context, so do not try to recover
device for this case and let resume/reset_resume callback
handle the suspend failure if needed.
Also kerneldoc for usb_s
This patch kills traffic even though type->suspend returns
failure inside usb_serial_suspend from system sleep context
because USB core ignores the failiure and lets system sleep
go ahread, so the serial URB traffic need to be killed
in this case.
Cc: Johan Hovold
Signed-off-by: Ming Lei
---
dr
If suspend callback fails in system sleep context, usb core will
ignore the failure and let the system sleep go ahead further, so this
patch doesn't recover device under this situation, otherwise
may cause resume() confused.
Cc: Jiri Kosina
Signed-off-by: Ming Lei
---
drivers/hid/usbhid/hid-cor
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 both
usbnet_suspend() and subdriver->suspend() MUST return 0 in
system sleep context.
Cc: Bjørn Mork
Signed-off-by: Ming
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 both
usbnet_suspend() and subdriver->suspend() MUST return 0 in
system sleep context.
Cc: Bjørn Mork
Signed-off-by: Ming
If suspend callback fails in system sleep context, usb core will
ignore the failure and let system sleep go ahead further, so
this patch doesn't recover device under this situation.
Also add comments on the case.
Cc: Steve Glendinning
Signed-off-by: Ming Lei
---
drivers/net/usb/smsc95xx.c |
If suspend callback fails in system sleep context, usb core will
ignore the failure and let system sleep go ahead further, so
this patch doesn't recover device under this situation.
Also add comments on this case.
Cc: Steve Glendinning
Signed-off-by: Ming Lei
---
drivers/net/usb/smsc75xx.c |
On Thu, Mar 07, 2013 at 11:01:47AM -0500, Alan Stern wrote:
> On Thu, 7 Mar 2013, Felipe Balbi wrote:
>
> > Hi folks,
> >
> > inspired by Paul's DWC2 patchset which added usb_otg_state_string()
> > (a copy of otg_state_string()) I have now renamed otg_state_string()
> > to usb_otg_state_string(),
Hi,
On Fri, Feb 22, 2013 at 10:24:41AM +0200, Felipe Balbi wrote:
> chipidea's ffs_nr() is pretty much what __ffs() does.
>
> Use that one instead.
>
> Signed-off-by: Felipe Balbi
it has been almost 2 weeks, just a gentle ping here.
cheers
--
balbi
signature.asc
Description: Digital signa
On 7 March 2013 18:47, Felipe Balbi wrote:
> Hi,
>
> On Fri, Feb 22, 2013 at 10:24:41AM +0200, Felipe Balbi wrote:
>> chipidea's ffs_nr() is pretty much what __ffs() does.
>>
>> Use that one instead.
>>
>> Signed-off-by: Felipe Balbi
>
> it has been almost 2 weeks, just a gentle ping here.
It's
* Aaro Koskinen [130307 06:44]:
> +#include
We should be getting rid of the plat and mach includes for
drivers for omap1 also, so let's not make it harder by adding
more of it. We should have just the following:
include/linux/platform_data/usb-omap.h this contains just minimal pdata
include/li
On Thu, Mar 07, 2013 at 07:03:38PM +0200, Alexander Shishkin wrote:
> On 7 March 2013 18:47, Felipe Balbi wrote:
> > Hi,
> >
> > On Fri, Feb 22, 2013 at 10:24:41AM +0200, Felipe Balbi wrote:
> >> chipidea's ffs_nr() is pretty much what __ffs() does.
> >>
> >> Use that one instead.
> >>
> >> Signed
On Tue, Feb 26, 2013 at 10:50:21AM -0600, Seth Forshee wrote:
> On Tue, Feb 26, 2013 at 12:30:58AM +0100, Christian Lamparter wrote:
> > On Monday, February 25, 2013 09:19:03 PM Alan Stern wrote:
> > > On Mon, 25 Feb 2013, Seth Forshee wrote:
> > > > > > >88012fe19500 1519981417 S Bo:3:003:1 -1
Hi,
On Thu, Mar 07, 2013 at 04:51:59PM +0200, Felipe Balbi wrote:
> why is this otg_dev even needed ? Can you refresh my memory ?
If you want to handle OTG controller interrupt you need it... Though looks
like tahvo does not really need it, and it can be disabled.
A.
--
To unsubscribe from this
Please use Reply-To-All, so that your message gets sent to the mailing
list as well as to me.
On Thu, 7 Mar 2013, Jenya Y wrote:
> Thank you Alan for the reply.
> I'd be bold enough to categorize this as a problem, since the usb hub
> doesn't work.
> It could be 'expected' if it were a RC ve
Ming Lei writes:
> 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 both
> usbnet_suspend() and subdriver->suspend() MUST return 0 in
> system sleep context.
>
> Cc:
Ming Lei writes:
> 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 both
> usbnet_suspend() and subdriver->suspend() MUST return 0 in
> system sleep context.
>
> Cc:
// sorry for double-post I was advised to use 'reply to all' and wasn't
sure if the prev. message was forwarded to linux-usb
Thank you for the reply.
I'd be bold enough to categorize this as a problem, since the usb hub
doesn't work.
It could be 'expected' if it were a RC version of the ke
> From: Felipe Balbi [mailto:ba...@ti.com]
> Sent: Wednesday, March 06, 2013 11:39 PM
>
> On Wed, Mar 06, 2013 at 08:14:34PM +, Paul Zimmerman wrote:
> > > From: Felipe Balbi [mailto:ba...@ti.com]
> > > Sent: Wednesday, March 06, 2013 12:11 PM
> > > On Wed, Mar 06, 2013 at 07:22:33PM +, Pa
> From: Alan Stern [mailto:st...@rowland.harvard.edu]
> Sent: Thursday, March 07, 2013 7:35 AM
>
> On Wed, 6 Mar 2013, Paul Zimmerman wrote:
>
> > > BTW, you _do_ have a race because you don't check ep->hcpriv when
> > > ->urb_enqueue() is called. This means that you could queue to an
> > > endpo
On Thu, 7 Mar 2013, Jenya Y wrote:
> // sorry for double-post I was advised to use 'reply to all' and wasn't
> sure if the prev. message was forwarded to linux-usb
>
> Thank you for the reply.
> I'd be bold enough to categorize this as a problem, since the usb hub
> doesn't work.
> It could b
On Thu, 7 Mar 2013, Paul Zimmerman wrote:
> Hi Alan,
>
> I was talking about uhci_hcd_endpoint_disable(). It drops the spinlock,
> reacquires it, but doesn't reload qh from hep->hcpriv before continuing.
> Maybe that's not required for uhci, I didn't look any deeper.
No, it's not required. hep-
On Fri, 8 Mar 2013, Ming Lei wrote:
> This patch adds comments on interface driver suspend callback
> to emphasize that the failure return value is ignored by
> USB core in system sleep context, so do not try to recover
> device for this case and let resume/reset_resume callback
> handle the suspe
From: Ming Lei
Date: Fri, 8 Mar 2013 00:15:17 +0800
> This patch adds comments on interface driver suspend callback
> to emphasize that the failure return value is ignored by
> USB core in system sleep context, so do not try to recover
> device for this case, otherwise the recovery things may co
On 03/07/2013 08:45 AM, Felipe Balbi wrote:
> this will make sure that we have sensible names
> for all phy drivers. Current situation was already
> quite bad with too generic names being used.
Is phy-$name specific enough? There are other types of PHY such as
Ethernet, etc. What about phy-usb-$na
On 03/07/2013 02:36 AM, Felipe Balbi wrote:
> CONFIG_USB_OTG_UTILS will be removed very
> soon, so we should check CONFIG_USB_PHY
> instead.
The Tegra EHCI driver isn't very useful without the Tegra PHY driver.
Perhaps its Kconfig should simply "select USB_PHY", and the ifdefs be
removed rather th
1 - 100 of 141 matches
Mail list logo
