Hi,
Here is the fresh usbmon trace. Four SCSI commands are shown. The
first SCSI_READ_10 command has LBA of 0. The second SCSI_READ_10
command has LBA of 0x00ed2900, which is wrong. Somehow, the first
SCSI_READ_10 command got the wrong data, i think. Isn't it?
It looks like the data is
-Original Message-
From: gre...@linuxfoundation.org [mailto:gre...@linuxfoundation.org]
Sent: Tuesday, March 05, 2013 6:04 AM
To: Stephen Warren
Cc: Venu Byravarasu; st...@rowland.harvard.edu; linux-
u...@vger.kernel.org; linux-ker...@vger.kernel.org
Subject: Re: [PATCH] usb: host:
I'm making a burn-in test (see serialtest.py
http://pastebin.com/pz47gaar) for our devices, that have built-in FTDI
chips. If FT2232C is attached directly to the USB host controller
port, the tests run properly. If I connect the chip to a USB-hub some
of the tests show timeout errors (read()
avoid reading fifo rxcount is zero of fifo is empty, hence
read fifo only if rxcount is non-zero
Signed-off-by: Ravi Babu ravib...@ti.com
---
drivers/usb/musb/musb_gadget_ep0.c |6 --
1 files changed, 4 insertions(+), 2 deletions(-)
diff --git a/drivers/usb/musb/musb_gadget_ep0.c
Hi,
On Thu, Mar 28, 2013 at 03:18:14PM +0200, Alexander Shishkin wrote:
+ dr_mode = ci-platdata-dr_mode;
+ if (dr_mode == USB_DR_MODE_UNKNOWN || dr_mode ==
USB_DR_MODE_DUAL_ROLE)
+ dr_mode = USB_DR_MODE_OTG;
+
/* initialize role(s) before the
On Sun, Mar 24, 2013 at 10:06:04PM +0800, Shawn Guo wrote:
Commit edc7cb2 (usb: phy: make it a menuconfig) makes USB_MXS_PHY
be a sub-item of menuconfig symbol USB_PHY. This change gets the
selection of CONFIG_USB_MXS_PHY in imx_v6_v7_defconfig lost. Hence the
boot stops at the point below.
On Monday 01 April 2013 22:05:47 Mike Verstegen wrote:
Hi,
Such a simple question you asked -- but it lead to a useful discovery.
My logs show that acm_tty_write is called multiple times
- The application opens the device and then calls write() to send the 4 byte
message to the fd. This
Hi,
On Mon, Mar 25, 2013 at 03:06:57AM -0400, Chao Xie wrote:
Using pdata to pass clock name is not correct.
Directly get clock from usb drivers.
Signed-off-by: Chao Xie chao@marvell.com
---
include/linux/platform_data/mv_usb.h |2 --
1 files changed, 0 insertions(+), 2
On Sun, Mar 31, 2013 at 06:34:43PM -0700, Kuninori Morimoto wrote:
This patch fixup below sparse errors
${RENESAS_USB} = ${LINUX}/drivers/usb/renesas_usbhs
CHECK ${RENESAS_USB}/common.c
${RENESAS_USB}/common.c:313:17: error: incompatible types in conditional
expression (different base
On Mon, Apr 01, 2013 at 07:24:01PM +0530, Vivek Gautam wrote:
The current code in the dwc3 probe effectively disables runtime pm
from ever working because it calls a get() that was never put() until
device removal. Change the runtime pm code to match the standard
formula and allow runtime pm
Hi,
On Mon, Apr 01, 2013 at 07:24:03PM +0530, Vivek Gautam wrote:
+#else
+#define dwc3_runtime_suspend NULL
+#define dwc3_runtime_resume NULL
this #else branch is unnecessary. Look at the definition for
SET_RUNTIME_PM_OPS()
--
balbi
signature.asc
Description: Digital
On Mon, Apr 01, 2013 at 07:24:04PM +0530, Vivek Gautam wrote:
Enabling runtime power management on dwc3-exynos
letting dwc3 controller to be autosuspended on exynos
platform when not in use.
Signed-off-by: Vivek Gautam gautam.vi...@samsung.com
---
drivers/usb/dwc3/dwc3-exynos.c | 12
Hi again,
On Thu, Mar 21, 2013 at 11:19:51AM -0600, Stephen Warren wrote:
On 03/21/2013 06:23 AM, Felipe Balbi wrote:
PHY layer no longer returns NULL, we must
switch from IS_ERR_OR_NULL() to IS_ERR().
The patches that I'll put into my topic branch are not yet complete;
Venu first posted
Hi,
On Thursday 28 March 2013 09:15 PM, Stephen Warren wrote:
On 03/27/2013 11:43 PM, Kishon Vijay Abraham I wrote:
The PHY framework provides a set of APIs for the PHY drivers to
create/destroy a PHY and APIs for the PHY users to obtain a reference to the
diff --git
Hi,
On Tuesday 02 April 2013 01:04 AM, Sylwester Nawrocki wrote:
Just couple minor comments...
On 03/28/2013 06:43 AM, Kishon Vijay Abraham I wrote:
The PHY framework provides a set of APIs for the PHY drivers to
create/destroy a PHY and APIs for the PHY users to obtain a reference
to the
PHY
Hi,
-Original Message-
From: Felipe Balbi [mailto:ba...@ti.com]
Sent: 2013年4月2日 16:15
To: Chao Xie
Cc: linux-usb@vger.kernel.org; linux-arm-ker...@lists.infradead.org;
haojian.zhu...@gmail.com; ba...@ti.com; xiechao.m...@gmail.com; Yu Xu
Subject: Re: [PATCH V2 6/6] usb: mv_usb:
On Mon, Apr 01, 2013 at 10:49:26AM +0800, Peter Chen wrote:
On Fri, Mar 29, 2013 at 12:32:00AM +0100, Michael Grzeschik wrote:
[snip]
What's the value of sizeof(struct ci13xxx_qh) after you pack it
as 64 bytes aligned?
With the struct attribute aligned(64) the result
of sizeof(struct
On Tue, Apr 02, 2013 at 11:31:47AM +0200, Michael Grzeschik wrote:
dma_pool_destroy(ci-td_pool);
free_qh_pool:
- dma_pool_destroy(ci-qh_pool);
You may need dma_free_coherent.
Will add that here.
The same for de-init procedure.
-} __attribute__ ((packed, aligned(4)));
Hi,
On Tue, Apr 2, 2013 at 1:53 PM, Felipe Balbi ba...@ti.com wrote:
On Mon, Apr 01, 2013 at 07:24:00PM +0530, Vivek Gautam wrote:
Adding APIs to handle runtime power management on PHY
devices. PHY consumers may need to wake-up/suspend PHYs
when they work across autosuspend.
On Tue, Apr 02, 2013 at 11:07:06AM +0300, Felipe Balbi wrote:
On Sun, Mar 24, 2013 at 10:06:04PM +0800, Shawn Guo wrote:
Commit edc7cb2 (usb: phy: make it a menuconfig) makes USB_MXS_PHY
be a sub-item of menuconfig symbol USB_PHY. This change gets the
selection of CONFIG_USB_MXS_PHY in
The final version of fusb300 controller adds EPSET0_STL_CLR
for clearing EP0 stall and also removes EPSET0_EPn_TX0BYTE.
fusb300_udc driver is tested on FARADAY platform a369 with
FUSB300 FPGA v1.8
Signed-off-by: Yuan-Hsin Chen yhc...@faraday-tech.com
---
v2:
split patch
Enter IDMA_RESET only when the controller has been reset or
the device has been plugged in to or out from a host. In
IDMA_RESET, we should disable the corresponding PRD interrupt.
Also there is a redundant space eliminated.
fusb300_udc driver is tested on FARADAY platform a369 with
FUSB300 FPGA
Hi,
On Tue, Apr 2, 2013 at 5:40 PM, Felipe Balbi ba...@ti.com wrote:
Hi,
On Tue, Apr 02, 2013 at 04:04:01PM +0530, Vivek Gautam wrote:
On Mon, Apr 01, 2013 at 07:24:00PM +0530, Vivek Gautam wrote:
Adding APIs to handle runtime power management on PHY
devices. PHY consumers may need to
Hi,
On Tue, Apr 02, 2013 at 07:12:47PM +0800, Shawn Guo wrote:
On Tue, Apr 02, 2013 at 11:07:06AM +0300, Felipe Balbi wrote:
On Sun, Mar 24, 2013 at 10:06:04PM +0800, Shawn Guo wrote:
Commit edc7cb2 (usb: phy: make it a menuconfig) makes USB_MXS_PHY
be a sub-item of menuconfig symbol
Hi Andrejz,
On Wed, Jan 23, 2013 at 12:45:31PM +0100, Andrzej Pietrasiewicz wrote:
The prerequisite for providing the configfs interface for mass storage and all
its users is converting them to the new function interface from Sebastian.
This patch series serves the purpose stated above.
On Tue, 2 Apr 2013, victor yeo wrote:
Hi,
Here is the fresh usbmon trace. Four SCSI commands are shown. The
first SCSI_READ_10 command has LBA of 0. The second SCSI_READ_10
command has LBA of 0x00ed2900, which is wrong. Somehow, the first
SCSI_READ_10 command got the wrong data, i
On Tue, 2 Apr 2013, Oliver Neukum wrote:
On Monday 01 April 2013 22:05:47 Mike Verstegen wrote:
Hi,
Such a simple question you asked -- but it lead to a useful discovery.
My logs show that acm_tty_write is called multiple times
- The application opens the device and then calls
On Tue, 2 Apr 2013, Yegor Yefremov wrote:
I'm making a burn-in test (see serialtest.py
http://pastebin.com/pz47gaar) for our devices, that have built-in FTDI
chips. If FT2232C is attached directly to the USB host controller
port, the tests run properly. If I connect the chip to a USB-hub some
Remove all section annotations to fix the
following section mismatches:
WARNING: drivers/usb/gadget/pxa27x_udc.o(.text+0x597c): Section mismatch in
reference from the function .pxa_udc_probe() to the function
.init.text:.udc_init_data.constprop.11()
The function .pxa_udc_probe() references
Remove all section annotations to fix the
following section mismatches:
WARNING: drivers/usb/gadget/pxa27x_udc.o(.text+0x597c): Section mismatch in
reference from the function .pxa_udc_probe() to the function
.init.text:.udc_init_data.constprop.11()
The function .pxa_udc_probe() references
On Tue, Apr 02, 2013 at 03:44:07PM +0300, Felipe Balbi wrote:
alright, in that case can you rebase on next branch ? patch 2 didn't
apply.
Have you tried git am -3?
Shawn
--
To unsubscribe from this list: send the line unsubscribe linux-usb in
the body of a message to majord...@vger.kernel.org
On Tue, Apr 2, 2013 at 4:14 PM, Alan Stern st...@rowland.harvard.edu wrote:
On Tue, 2 Apr 2013, Yegor Yefremov wrote:
I'm making a burn-in test (see serialtest.py
http://pastebin.com/pz47gaar) for our devices, that have built-in FTDI
chips. If FT2232C is attached directly to the USB host
On Tue, 2 Apr 2013, Yegor Yefremov wrote:
On Tue, Apr 2, 2013 at 4:14 PM, Alan Stern st...@rowland.harvard.edu wrote:
On Tue, 2 Apr 2013, Yegor Yefremov wrote:
I'm making a burn-in test (see serialtest.py
http://pastebin.com/pz47gaar) for our devices, that have built-in FTDI
chips. If
Commit 756aa6b3d536afe85e151138cb03a293998887b3 added port power cycling on
overcurrent indications as needed by the MPC8349 USB controller after
resolving of the overcurrent situation in order to have the host state machine
assert the correct port status again.
Commit
On Tue, 2 Apr 2013, Christian Engelmayer wrote:
Commit 756aa6b3d536afe85e151138cb03a293998887b3 added port power cycling on
overcurrent indications as needed by the MPC8349 USB controller after
resolving of the overcurrent situation in order to have the host state machine
assert the correct
On 04/02/2013 01:12 AM, Venu Byravarasu wrote:
gre...@linuxfoundation.org wrote at Tuesday, March 05, 2013 6:04 AM:
On Mon, Mar 04, 2013 at 09:55:44AM -0700, Stephen Warren wrote:
On 03/04/2013 12:55 AM, Venu Byravarasu wrote:
Stephen Warren wrote at Thursday, February 28, 2013 11:47 PM:
On
On Mon, 1 Apr 2013, Yuan-Hsin Chen wrote:
FUSBH200 is an ehci-like controller with some differences.
First, register layout of FUSBH200 is incompatible with EHCI.
We use a quirk flag and modify struct ehci_regs with anonymous
union and struct to make sure driver of FUSBH200 and EHCI could
On 04/02/2013 02:36 AM, Felipe Balbi wrote:
Hi again,
On Thu, Mar 21, 2013 at 11:19:51AM -0600, Stephen Warren wrote:
On 03/21/2013 06:23 AM, Felipe Balbi wrote:
PHY layer no longer returns NULL, we must switch from
IS_ERR_OR_NULL() to IS_ERR().
The patches that I'll put into my topic
On 04/02/2013 02:37 AM, Kishon Vijay Abraham I wrote:
Hi,
On Thursday 28 March 2013 09:15 PM, Stephen Warren wrote:
On 03/27/2013 11:43 PM, Kishon Vijay Abraham I wrote:
The PHY framework provides a set of APIs for the PHY drivers to
create/destroy a PHY and APIs for the PHY users to obtain
Hi,
On Tue, Apr 02, 2013 at 09:33:56AM -0600, Stephen Warren wrote:
On 04/02/2013 02:36 AM, Felipe Balbi wrote:
Hi again,
On Thu, Mar 21, 2013 at 11:19:51AM -0600, Stephen Warren wrote:
On 03/21/2013 06:23 AM, Felipe Balbi wrote:
PHY layer no longer returns NULL, we must switch from
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 m.grzesc...@pengutronix.de
Signed-off-by: Marc Kleine-Budde m...@pengutronix.de
Reviewed-by: Felipe Balbi ba...@ti.com
---
drivers/usb/chipidea/core.c
From: Manjunath Goudar manjunath.gou...@linaro.org
Separate the Qualcomm QSD/MSM on-chip host controller driver from
ehci-hcd host code so that it can be built as a separate driver module.
This work is part of enabling multi-platform kernels on ARM;
however, note that other changes are still
Hi Greg,
Here are the EHCI patches that I think are good for inclusion in 3.10,
I hope you are willing to include them after the debacle over these
patches in 3.9.
The patches are all logically independent but sorted by priority,
so decide for yourself how many you want to take, starting at the
From: Manjunath Goudar manjunath.gou...@linaro.org
Separate the Samsung S5P/EXYNOS host controller driver from ehci-hcd
host code so that it can be built as a separate driver module.
This work is part of enabling multi-platform kernels on ARM;
however, note that other changes are still needed
Like the EHCI driver, OHCI supports a large number of different platform
glue drivers by directly including them, which causes problems with
conflicting macro definitions in some cases. As more ARM architecture
specific back-ends are required to coexist in a single build, we should
split those out
From: Manjunath Goudar manjunath.gou...@linaro.org
Separate the SPEAr host controller driver from ehci-hcd host code
so that it can be built as a separate driver module.
This work is part of enabling multi-platform kernels on ARM;
however, note that other changes are still needed before SPEAr can
From: Manjunath Goudar manjunath.gou...@linaro.org
Separate the Orion host controller driver from ehci-hcd host
code into its own driver module because of following reason.
With the multiplatform changes in arm-soc tree, it becomes
possible to enable the mvebu platform (which uses
ehci-orion) at
From: Manjunath Goudar manjunath.gou...@linaro.org
Separate the Atmel host controller driver from ehci-hcd host code
so that it can be built as a separate driver module.
This work is part of enabling multi-platform kernels on ARM;
however, note that other changes are still needed before Atmel can
This patch removes the depends on USB from all config symbols in
drivers/usb/host/Kconfig and replace that with an if USB / endif block
as suggested by Alan Stern. Some source ... Kconfig lines have been
shuffled around to permit a better regroupment of the Kconfig files
depending on config USB
Hello Alan, Greg,
These 5 patches contain my Kconfig cleanup on which I based the removal
of the USB_ARCH_HAS_* patches. They have been suggested by Alan Stern
as part of an earlier conversations.
Let me know what you think about it so I can post subsequent work based
on it. This time I dropped
Just like the OHCI counter part we just can remove the architecture
specific symbols which prevent these configuration symbols from being
selected by platforms/architectures requiring it. The original
implementation did not scale at all since it required each and every
single architecture to be
This patch encloses all symbols depending on USB_XHCI_HCD within an if
USB_XHCI_HCD / endif block.
Signed-off-by: Florian Fainelli flor...@openwrt.org
---
drivers/usb/host/Kconfig |6 --
1 file changed, 4 insertions(+), 2 deletions(-)
diff --git a/drivers/usb/host/Kconfig
Thist patch removes the depends on USB_EHCI_HCD that the various USB
EHCI HCD drivers use and encloses every driver within an if USB_EHCI_HCD
/ endif block. The EHCI HCD platform and Octeon drivers have been moved
around to remain enclosed within this block.
Signed-off-by: Florian Fainelli
This patch removes the various depends on USB_OHCI_HCD from the OHCI HCD
drivers and enclose them within an if USB_OHCI_HCD / endif block. The
Octeon OHCI HCD driver has been moved around to remain in this block.
Signed-off-by: Florian Fainelli flor...@openwrt.org
---
drivers/usb/host/Kconfig |
Just like the OHCI counter part we just can remove the architecture
specific symbols which prevent these configuration symbols from being
selected by platforms/architectures requiring it. The original
implementation did not scale at all since it required each and every
single architecture to be
Le 04/02/13 19:05, Florian Fainelli a écrit :
Hello Alan, Greg,
These 5 patches contain my Kconfig cleanup on which I based the removal
of the USB_ARCH_HAS_* patches. They have been suggested by Alan Stern
as part of an earlier conversations.
Let me know what you think about it so I can post
This patch removes the depends on USB from all config symbols in
drivers/usb/host/Kconfig and replace that with an if USB / endif block
as suggested by Alan Stern. Some source ... Kconfig lines have been
shuffled around to permit a better regroupment of the Kconfig files
depending on config USB
Hello Alan, Greg,
These 5 patches contain my Kconfig cleanup on which I based the removal
of the USB_ARCH_HAS_* patches. They have been suggested by Alan Stern
as part of an earlier conversations.
Let me know what you think about it so I can post subsequent work based
on it. This time I dropped
Thist patch removes the depends on USB_EHCI_HCD that the various USB
EHCI HCD drivers use and encloses every driver within an if USB_EHCI_HCD
/ endif block. The EHCI HCD platform and Octeon drivers have been moved
around to remain enclosed within this block.
Signed-off-by: Florian Fainelli
This patch removes the various depends on USB_OHCI_HCD from the OHCI HCD
drivers and enclose them within an if USB_OHCI_HCD / endif block. The
Octeon OHCI HCD driver has been moved around to remain in this block.
Signed-off-by: Florian Fainelli flor...@openwrt.org
---
drivers/usb/host/Kconfig |
This patch encloses all symbols depending on USB_XHCI_HCD within an if
USB_XHCI_HCD / endif block.
Signed-off-by: Florian Fainelli flor...@openwrt.org
---
drivers/usb/host/Kconfig |6 --
1 file changed, 4 insertions(+), 2 deletions(-)
diff --git a/drivers/usb/host/Kconfig
based on commit 6ff1f3d3bd7c69c62ca5773b1b684bce42eff06a.
On TI81xx, tx and rx interrupt are detected together with
the disconnect event. This generates a kernel panic in musb_interrupt,
because rx / tx are handled after disconnect.
Signed-off-by: Shane Whalen swha...@dekaresearch.com
---
* Felipe Balbi ba...@ti.com [130320 09:24]:
On Wed, Mar 20, 2013 at 09:13:24AM -0700, Tony Lindgren wrote:
* Felipe Balbi ba...@ti.com [130320 09:00]:
On Wed, Mar 20, 2013 at 05:44:40PM +0200, Roger Quadros wrote:
Add clk_rate parameter to platform data. If supplied, the
NOP phy
Hello.
On 04/02/2013 06:54 PM, Christian Engelmayer wrote:
Commit 756aa6b3d536afe85e151138cb03a293998887b3 added port power cycling on
overcurrent indications as needed by the MPC8349 USB controller after
resolving of the overcurrent situation in order to have the host state machine
assert the
Hello.
On 04/02/2013 07:44 PM, Felipe Balbi wrote:
Hi again,
On Thu, Mar 21, 2013 at 11:19:51AM -0600, Stephen Warren wrote:
On 03/21/2013 06:23 AM, Felipe Balbi wrote:
PHY layer no longer returns NULL, we must switch from
IS_ERR_OR_NULL() to IS_ERR().
The patches that I'll put into my
Hi,
On Tue, Apr 02, 2013 at 09:39:57PM +0400, Sergei Shtylyov wrote:
On 03/21/2013 06:23 AM, Felipe Balbi wrote:
PHY layer no longer returns NULL, we must switch from
IS_ERR_OR_NULL() to IS_ERR().
The patches that I'll put into my topic branch are not yet
complete; Venu first posted them a
On Tue, 2 Apr 2013, Florian Fainelli wrote:
This patch removes the depends on USB from all config symbols in
drivers/usb/host/Kconfig and replace that with an if USB / endif block
as suggested by Alan Stern. Some source ... Kconfig lines have been
shuffled around to permit a better
Sarah Sharp sarah.a.sh...@linux.intel.com wrote:
I guess my question is a deeper one: do we need to rename all the xHCI
macros to have the XHCI_ prefix, in order to avoid future collision?
For example, one of the macros is MAX_HC_PORTS, which could possibly be
used by other host drivers in
Hi,
On Tue, Apr 02, 2013 at 07:10:22PM +0200, Florian Fainelli wrote:
diff --git a/drivers/usb/musb/Kconfig b/drivers/usb/musb/Kconfig
index 05e5143..ab5a3b9 100644
--- a/drivers/usb/musb/Kconfig
+++ b/drivers/usb/musb/Kconfig
@@ -6,7 +6,6 @@
# (M)HDRC = (Multipoint) Highspeed Dual-Role
On Tue, 2 Apr 2013, Florian Fainelli wrote:
Just like the OHCI counter part we just can remove the architecture
specific symbols which prevent these configuration symbols from being
selected by platforms/architectures requiring it. The original
implementation did not scale at all since it
On Tue, 2 Apr 2013, Florian Fainelli wrote:
Thist patch removes the depends on USB_EHCI_HCD that the various USB
EHCI HCD drivers use and encloses every driver within an if USB_EHCI_HCD
/ endif block. The EHCI HCD platform and Octeon drivers have been moved
around to remain enclosed within
On Tue, 2 Apr 2013, Florian Fainelli wrote:
This patch removes the various depends on USB_OHCI_HCD from the OHCI HCD
drivers and enclose them within an if USB_OHCI_HCD / endif block. The
Octeon OHCI HCD driver has been moved around to remain in this block.
Signed-off-by: Florian Fainelli
On Tue, 2 Apr 2013, Florian Fainelli wrote:
This patch encloses all symbols depending on USB_XHCI_HCD within an if
USB_XHCI_HCD / endif block.
Signed-off-by: Florian Fainelli flor...@openwrt.org
Acked-by: Alan Stern st...@rowland.harvard.edu
--
To unsubscribe from this list: send the line
On Tue, Apr 02, 2013 at 07:07:36PM +0100, David Howells wrote:
Sarah Sharp sarah.a.sh...@linux.intel.com wrote:
I guess my question is a deeper one: do we need to rename all the xHCI
macros to have the XHCI_ prefix, in order to avoid future collision?
For example, one of the macros is
On 04/02/2013 02:40 PM, Thierry Reding wrote:
The cleanup path checks whether the transceiver was properly initialized
using IS_ERR(). However it can also happen that the cleanup path is run
before the transceiver was initialized (or the operating mode isn't set
to TEGRA_USB_OTG) and is
On 04/02/2013 12:38 AM, Stephen Warren wrote:
On 04/01/2013 04:27 PM, Sylwester Nawrocki wrote:
On 03/28/2013 06:43 AM, Kishon Vijay Abraham I wrote:
diff --git a/Documentation/devicetree/bindings/phy/phy-bindings.txt
+example2:
+phys: phy {
+compatible = xxx;
+reg =...;
+.
+
Hi,
It looks like the data is wrong, but I have no way of knowing what the
data actually should be. Only you know that.
f31a9740 4037054141 S Bo:2:071:1 -115 31 = 55534243 0c00 0010
8a28 0008 00
f31a9740 4037054176 C Bo:2:071:1 0 31
f4a555c0
On Tue, Apr 02, 2013 at 06:10:54PM +0200, Michael Grzeschik wrote:
/* first nuke then test link, e.g. previous status has not sent */
if (!list_empty(mReq-queue)) {
dev_err(mEp-ci-dev, request already in queue\n);
@@ -1071,6 +1077,9 @@ static int ep_enable(struct
Hi Balbi,
On Tue, Apr 2, 2013 at 2:02 PM, Felipe Balbi ba...@ti.com wrote:
Hi,
On Mon, Apr 01, 2013 at 07:24:03PM +0530, Vivek Gautam wrote:
+#else
+#define dwc3_runtime_suspend NULL
+#define dwc3_runtime_resume NULL
this #else branch is unnecessary. Look at the
Hi,
On Monday 01 April 2013 07:24 PM, Vivek Gautam wrote:
Adding APIs to handle runtime power management on PHY
devices. PHY consumers may need to wake-up/suspend PHYs
when they work across autosuspend.
Signed-off-by: Vivek Gautam gautam.vi...@samsung.com
---
include/linux/usb/phy.h | 141
On Tuesday 02 April 2013 09:10 PM, Stephen Warren wrote:
On 04/02/2013 02:37 AM, Kishon Vijay Abraham I wrote:
Hi,
On Thursday 28 March 2013 09:15 PM, Stephen Warren wrote:
On 03/27/2013 11:43 PM, Kishon Vijay Abraham I wrote:
The PHY framework provides a set of APIs for the PHY drivers to
81 matches
Mail list logo
