On 08/13/2013 08:11 PM, Bin Liu wrote:
Sebastian,
Hi Bin,
On Tue, Aug 13, 2013 at 12:38 PM, Sebastian Andrzej Siewior
bige...@linutronix.de wrote:
Since the musb-gadget code now calls the dma engine properly it is
possible to enable it for the TX path in device mode.
AM335x Advisory 1.0.13
Hi,
On Tue, 2013-08-13 at 13:57 -0600, Stephen Warren wrote:
On 08/09/2013 03:53 AM, Ivan T. Ivanov wrote:
From: Ivan T. Ivanov iiva...@mm-sol.com
MSM USB3.0 core wrapper consist of USB3.0 IP (SNPS)
and HS, SS PHY's controll and configuration registers.
s/controll/control/
On 08/13/2013 09:21 PM, Felipe Balbi wrote:
1.0.13 only presents in PG1.0. It has been fixed in PG2.x. Maybe
we should check for silicon rev here?
it would be quite difficult to check PG revision from this driver.
It would have to be passed as a flag through DT or something
similar.
If DT
+Benoit
Hi Felipe,
Any comments on this series?
cheers,
-roger
On 08/01/2013 05:05 PM, Roger Quadros wrote:
Hi,
This patchset does the following:
* Restructure and add support for new PHY types. We now support the follwing
four types
TYPE1 - if it has otghs_control mailbox register
+Benoit
On 08/01/2013 05:05 PM, Roger Quadros wrote:
Split otghs_ctrl and USB2 PHY power down into separate
omap-control-usb nodes. Update ti,mode property.
CC: Benoit Cousson benoit.cous...@linaro.org
Signed-off-by: Roger Quadros rog...@ti.com
---
arch/arm/boot/dts/omap4.dtsi | 17
+Benoit
On 08/01/2013 05:05 PM, Roger Quadros wrote:
Split USB2 PHY and USB3 PHY into separate omap-control-usb
nodes. Update ti,mode property.
CC: Benoit Cousson benoit.cous...@linaro.org
Signed-off-by: Roger Quadros rog...@ti.com
---
arch/arm/boot/dts/omap5.dtsi | 18
Hi all,
Going through the power suspend/resume sequence of USB, got hit by a doubt.
I am not able to figure out how the USB core driver takes care of
devices and root-hubs across suspend/resume. Are the device contexts
saved somewhere and then restored back on resume ?
How does the
CCing myself
On Wed, Aug 14, 2013 at 1:24 PM, Vivek Gautam gautamvivek1...@gmail.com wrote:
Hi all,
Going through the power suspend/resume sequence of USB, got hit by a doubt.
I am not able to figure out how the USB core driver takes care of
devices and root-hubs across suspend/resume. Are
On 08/13/2013 11:19 PM, Felipe Balbi wrote:
true, I'm sure Sebastian has plans on adding RX support, but only
after he knows it's working fine ;-)
I actually have none. I am not sure how likely it is that this bug will
trigger in device I just have the errata. Usually there is at least one
On Tue, 2013-08-13 at 11:40 -0500, Thomas Pugliese wrote:
static void wa_xfer_result_chew(struct wahc *wa, struct wa_xfer
*xfer)
{
@@ -1488,17 +1532,38 @@ error_submit_buf_in:
seg-result = result;
kfree(wa-buf_in_urb-sg);
error_sg_alloc:
+ __wa_xfer_abort(xfer);
The halted state of a endpoint cannot be cleared over CLEAR_HALT from a
user process, because the stopped_td variable was overwritten in the
handle_stopped_endpoint() function. So the xhci_endpoint_reset() function will
refuse the reset and communication with device can not run over this
* Felipe Balbi ba...@ti.com [130809 07:35]:
Hi Tony,
here's a pull request of one patch to avoid conflicts during the merge
window.
Please consider applying to your tree and I'll take this same patch
upstream.
Thanks, pulling into omap-for-v3.12/usb.
Regards,
Tony
The following
Hi Roger,
On 01/08/2013 16:05, Roger Quadros wrote:
Split otghs_ctrl and USB2 PHY power down into separate
omap-control-usb nodes. Update ti,mode property.
Nit: I guess you mean ti,type?
CC: Benoit Cousson benoit.cous...@linaro.org
Signed-off-by: Roger Quadros rog...@ti.com
---
On Wed, 2013-08-14 at 13:24 +0530, Vivek Gautam wrote:
Hi all,
Going through the power suspend/resume sequence of USB, got hit by a doubt.
I am not able to figure out how the USB core driver takes care of
It doesn't.
devices and root-hubs across suspend/resume. Are the device contexts
From: Oliver Neukum oneu...@suse.de
These devices tend to become unresponsive after S3
Signed-off-by: Oliver Neukum oneu...@suse.de
CC: sta...@vger.kernel.org
---
drivers/usb/core/quirks.c | 6 ++
1 file changed, 6 insertions(+)
diff --git a/drivers/usb/core/quirks.c
On 08/14/2013 11:41 AM, Benoit Cousson wrote:
Hi Roger,
On 01/08/2013 16:05, Roger Quadros wrote:
Split otghs_ctrl and USB2 PHY power down into separate
omap-control-usb nodes. Update ti,mode property.
Nit: I guess you mean ti,type?
Right :).
CC: Benoit Cousson
From: Julia Lawall julia.law...@lip6.fr
Remove unneeded error handling on the result of a call to
platform_get_resource when the value is passed to devm_ioremap_resource.
A simplified version of the semantic patch that makes this change is as
follows: (http://coccinelle.lip6.fr/)
// smpl
@@
Hi Oliver,
On Wed, Aug 14, 2013 at 2:19 PM, Oliver Neukum oneu...@suse.de wrote:
Thanks for you response.
On Wed, 2013-08-14 at 13:24 +0530, Vivek Gautam wrote:
Hi all,
Going through the power suspend/resume sequence of USB, got hit by a doubt.
I am not able to figure out how the USB
Hi All,
This patch adds documentation for all sysfs files used by libusb.
Changes in v2:
-Spelling fixes
-Add text about writing to bConfigurationValue, suggested by Alan Stern
Changes in v3:
-Rebase on latest usb-next
Regards,
Hans
--
To unsubscribe from this list: send the line unsubscribe
Signed-off-by: Hans de Goede hdego...@redhat.com
---
Documentation/ABI/testing/sysfs-bus-usb | 38 +
1 file changed, 38 insertions(+)
diff --git a/Documentation/ABI/testing/sysfs-bus-usb
b/Documentation/ABI/testing/sysfs-bus-usb
index 9c8926c..b0b9bb4 100644
---
devm_ioremap_resource often uses the result of a call to
platform_get_resource as its last argument. devm_ioremap_resource does
appropriate error handling on this argument, so error handling can be
removed from the call site. To make the connection between the call to
platform_get_resource and
Hi,
On Mon, 2013-08-12 at 13:24 -0500, Felipe Balbi wrote:
On Fri, Aug 09, 2013 at 07:09:18PM +0300, Ivan T. Ivanov wrote:
Hi,
On Fri, 2013-08-09 at 16:23 +0300, Felipe Balbi wrote:
Hi,
On Tue, Aug 06, 2013 at 02:53:11PM +0300, Ivan T. Ivanov wrote:
diff --git
Hi Felipe,
On 07/25/2013 08:28 PM, Felipe Balbi wrote:
On Thu, Jul 18, 2013 at 11:53:05AM +0300, Roger Quadros wrote:
Till now we were modelling the RESET line as a voltage regulator and
using the regulator framework to manage it.
[1] introduces a GPIO based reset controller driver. We use
Hi,
On Fri, 2013-08-09 at 16:23 +0300, Felipe Balbi wrote:
snip
+ /*
+* DWC3 Core requires its CORE CLK (aka master / bus clk) to
+* run at 125Mhz in SSUSB mode and 60MHZ for HSUSB mode.
+*/
+ clk_set_rate(mdwc-core_clk, 12500);
if this is dwc3's core clock,
Hi,
These are chipidea patches for v3.12. The highlight of the series is
vbus detection support. Other than that, a few cleanups and fixes,
mostly concerning imx platforms. Everything is sparse, smatch and
coccinelle clean and bisectable.
Fabio Estevam (3):
usb: chipidea: ci_hdrc_imx: remove
From: Fabio Estevam fabio.este...@freescale.com
Currently hw_phymode_configure() is located inside hw_device_reset(), which is
only called by chipidea udc driver.
When operating in host mode, we also need to call hw_phymode_configure() in
order to properly configure the PHY mode, so move this
From: Fabio Estevam fabio.este...@freescale.com
'res' is not used anywhere, so let's get rid of it.
Signed-off-by: Fabio Estevam fabio.este...@freescale.com
Acked-by: Peter Chen peter.c...@freescale.com
Signed-off-by: Alexander Shishkin alexander.shish...@linux.intel.com
---
From: Lothar Waßmann l...@karo-electronics.de
This prevents the USB PHY refcount to be decremented below zero upon
unloading the ci-hdrc-imx module.
Signed-off-by: Lothar Waßmann l...@karo-electronics.de
Acked-by: Peter Chen peter.c...@freescale.com
Signed-off-by: Alexander Shishkin
From: Peter Chen peter.c...@freescale.com
The vbus regulator is a common element for USB vbus operation,
So, move it from glue layer to core.
Tested-by: Marek Vasut ma...@denx.de
Signed-off-by: Michael Grzeschik m.grzesc...@pengutronix.de
Signed-off-by: Peter Chen peter.c...@freescale.com
From: Peter Chen peter.c...@freescale.com
Currently, the controller only runs when the ci-vbus_active is true.
So the flag CI_HDRC_PULLUP_ON_VBUS is useless no longer.
If the user doesn't have otgsc, he/she needs to change ci_handle_vbus_change
to update ci-vbus_active.
Signed-off-by: Peter Chen
From: Fabio Estevam fabio.este...@freescale.com
After the rename to ci_hdrc we ended up with two MODULE_ALIAS entries, so
remove the old one.
Signed-off-by: Fabio Estevam fabio.este...@freescale.com
Reviewed-by: Peter Chen peter.c...@freescale.com
Signed-off-by: Alexander Shishkin
From: Peter Chen peter.c...@freescale.com
During the initialization, it needs to disable all interrupts
enable bit as well as clear all interrupts status bits to avoid
exceptional interrupt.
Tested-by: Marek Vasut ma...@denx.de
Signed-off-by: Peter Chen peter.c...@freescale.com
Signed-off-by:
From: Peter Chen peter.c...@freescale.com
It is useless at below cases:
- If we implement both usb host and device at chipidea driver.
- If we don't need phy-otg.
Tested-by: Marek Vasut ma...@denx.de
Signed-off-by: Peter Chen peter.c...@freescale.com
Signed-off-by: Alexander Shishkin
From: Peter Chen peter.c...@freescale.com
For chipidea, the IP must know vbus before the controller
begins to run. So the .pullup should only be called when
the vbus is there.
Tested-by: Marek Vasut ma...@denx.de
Signed-off-by: Peter Chen peter.c...@freescale.com
Signed-off-by: Alexander
From: Peter Chen peter.c...@freescale.com
This file is mainly used to access otgsc currently, it may
add otg related things in the future.
Tested-by: Marek Vasut ma...@denx.de
Signed-off-by: Peter Chen peter.c...@freescale.com
Signed-off-by: Alexander Shishkin alexander.shish...@linux.intel.com
From: Peter Chen peter.c...@freescale.com
We add vbus interrupt handler at ci_otg_work, it uses OTGSC_BSV(at otgsc)
to know it is connect or disconnet event.
Meanwhile, we introduce two flags id_event and b_sess_valid_event to
indicate it is an id interrupt or a vbus interrupt.
Tested-by: Marek
From: Peter Chen peter.c...@freescale.com
- The role's init will be called at probe procedure.
- The role's destroy will be called at fail patch
at probe and driver's removal.
- The role's start/stop will be called when specific
role has started.
Tested-by: Marek Vasut ma...@denx.de
From: Peter Chen peter.c...@freescale.com
Remove an unused macro leftover from the old initialization code.
Signed-off-by: Peter Chen peter.c...@freescale.com
Signed-off-by: Alexander Shishkin alexander.shish...@linux.intel.com
---
drivers/usb/chipidea/ci_hdrc_imx.c | 3 ---
1 file changed, 3
From: Peter Chen peter.c...@freescale.com
Move otg related things to otg file.
Tested-by: Marek Vasut ma...@denx.de
Signed-off-by: Peter Chen peter.c...@freescale.com
Signed-off-by: Alexander Shishkin alexander.shish...@linux.intel.com
---
drivers/usb/chipidea/core.c | 63
From: Peter Chen peter.c...@freescale.com
CI_HDRC_REGS_SHARED stands for the controller registers is shared
with other USB drivers, if all USB drivers are at chipidea/, it doesn't
needed to be set.
CI_HDRC_PULLUP_ON_VBUS stands for pullup dp when the vbus is on. This
flag doesn't need to be set
From: Lothar Waßmann l...@karo-electronics.de
If a role fails to start, propagate the error code up the call stack
from probe.
Signed-off-by: Lothar Waßmann l...@karo-electronics.de
Signed-off-by: Alexander Shishkin alexander.shish...@linux.intel.com
---
drivers/usb/chipidea/core.c | 1 -
1
From: Peter Chen peter.c...@freescale.com
For boards which have board level vbus control (eg, through gpio), we
need to vbus operation according to below rules:
- For host, we need open vbus before start hcd, and close it
after remove hcd.
- For otg, the vbus needs to be on/off when usb role
From: Peter Chen peter.c...@freescale.com
Since we need otgsc to know vbus's status at some chipidea
controllers even it is peripheral-only mode. Besides, some
SoCs (eg, AR9331 SoC) don't have otgsc register even
the DCCPARAMS_DC and DCCPARAMS_HC are both 1 at CAP_DCCPARAMS.
We inroduce flag
From: Peter Chen peter.c...@freescale.com
When the gadget role starts, we need to make sure the vbus is lower
than OTGSC_BSV, or there will be an vbus interrupt since we use
B_SESSION_VALID as vbus interrupt to indicate connect and disconnect.
When the host role starts, it may not be useful to
From: Sascha Hauer s.ha...@pengutronix.de
The chipidea i.MX driver is split into two drivers. The ci_hdrc_imx driver
handles the chipidea cores and the usbmisc_imx driver handles the noncore
registers common to all chipidea cores (but SoC specific). Current flow is:
- usbmisc sets an ops pointer
From: Lothar Waßmann l...@karo-electronics.de
This patch provides a cleaner solution to the problem described in
commit 20a677fd (usb: chipidea: improve kconfig).
The goal to be achieved is to force USB_CHIPIDEA=m if either
USB_EHCI_HCD=m or USB_GADGET=m.
If both are 'y' USB_CHIPIDEA may be
Peter Chen peter.c...@freescale.com writes:
On Mon, Aug 12, 2013 at 09:22:46AM +0800, Peter Chen wrote:
This patchset adds tested otg id switch function and vbus connect
and disconnect detection for chipidea driver. And fix kinds of
bugs found at chipidea drivers after enabling id and vbus
Sascha Hauer s.ha...@pengutronix.de writes:
The chipidea i.MX driver is split into two drivers. The ci_hdrc_imx driver
handles the chipidea cores and the usbmisc_imx driver handles the noncore
registers common to all chipidea cores (but SoC specific). Current flow is:
- usbmisc sets an ops
On Wed, Aug 14, 2013 at 09:19:44AM +0800, Peter Chen wrote:
If CONFIG_PM_SLEEP is not defined, the current value is .pm = NULL,
but your version .pm != NULL (its content is NULL).
I am not sure if it will cause any problems.
It would cause a small amount of additional memory usage if the
On Wed, Aug 14, 2013 at 11:17:57AM +0200, Hans de Goede wrote:
+What:/sys/bus/usb/devices/.../busnum
+KernelVersion: 2.6.22
+Description:
+ Bus-number of the USB-bus the device is connected to.
+
+What:/sys/bus/usb/devices/.../descriptors
Dear people,
I have recently bought a transcend USB3.0/ SATA III PCIe card combo. The
sataIII works fine but, the USB does not work with either kernel 3.9 or
3.10 (I have only tried these two).
For the kernel 3.9 I get outputs of:
dmesg | grep xhci
[1.243092] xhci_hcd :05:00.0:
On 08/10/2013 01:59 PM, Ezequiel Garcia wrote:
Is there any reason why there's no DT binding patch to this
series? (aka Documentation/devicetree/... + sent to devicetree list)
(sorry if this has been already explained somewhere...)
Completely forgot. There are existent documents which need
On Wed, 2013-08-14 at 14:46 +0530, Vivek Gautam wrote:
Hi,
devices and root-hubs across suspend/resume. Are the device contexts
saved somewhere and then restored back on resume ?
Usually not. The state of interfaces are the responsibility of interface
drivers (colloquially called
USB3503 chip needs to be reset after the USB PHY controller has been
intiliazed, otherwise it is not detected as plugged in.
Currently there is no other way to ensure that USB3503 chip is probed
after the USB PHY has been initialized, hence the last resort.
Signed-off-by: Tushar Behera
ATTENTION.
Let me use the liberty of this medium to inform you that my principal is
interested in investing his bond as a silent business partner in your company.
He would like to invest in private sector projects with an established company
in any project(s) which are already in the
On Mon, Aug 12, 2013 at 09:04:00PM -0400, Alan Stern wrote:
The bus code would need hooks installed wherever the platform wants to
do something extra. This could end up growing to a lot of hooks. How
can the whole thing be done in a reasonable fashion?
I'd expect that we're just looking
Signed-off-by: Hans de Goede hdego...@redhat.com
---
drivers/usb/core/devio.c | 103 ++
include/uapi/linux/usbdevice_fs.h | 7 +++
2 files changed, 110 insertions(+)
diff --git a/drivers/usb/core/devio.c b/drivers/usb/core/devio.c
index
This is a preparation patch for adding support for bulk streams.
Signed-off-by: Hans de Goede hdego...@redhat.com
---
drivers/usb/core/devio.c | 18 --
1 file changed, 8 insertions(+), 10 deletions(-)
diff --git a/drivers/usb/core/devio.c b/drivers/usb/core/devio.c
index
This patch makes it possible to specify a bulk stream id when submitting
an urb using the async usbfs API. It overloads the number_of_packets
usbdevfs_urb field for this. This is not pretty, but given other
constraints it is the best we can do. The reasoning leading to this goes
as follows:
1) We
Hi All,
As discussed a long while back, usbfs is currently missing bulk streams
support, and we ought to fix this. So this patch extends the usbfs API with
bulk stream support. Please review.
Note this patch-set is compile-tested only, since I don't have access to
any USB-3 devices using bulk
This is a preparation patch for adding support for bulk streams to usbfs.
Signed-off-by: Hans de Goede hdego...@redhat.com
---
drivers/usb/core/hcd.c | 28 ++--
include/linux/usb.h| 1 +
2 files changed, 23 insertions(+), 6 deletions(-)
diff --git
Signed-off-by: Hans de Goede hdego...@redhat.com
---
drivers/usb/core/devio.c | 18 +++---
1 file changed, 11 insertions(+), 7 deletions(-)
diff --git a/drivers/usb/core/devio.c b/drivers/usb/core/devio.c
index c7e946f..94e7839 100644
--- a/drivers/usb/core/devio.c
+++
Sebastian,
On Wed, Aug 14, 2013 at 2:16 AM, Sebastian Andrzej Siewior
bige...@linutronix.de wrote:
On 08/13/2013 08:11 PM, Bin Liu wrote:
Sebastian,
Hi Bin,
On Tue, Aug 13, 2013 at 12:38 PM, Sebastian Andrzej Siewior
bige...@linutronix.de wrote:
Since the musb-gadget code now calls the
Enable tx checksum.
Signed-off-by: Hayes Wang hayesw...@realtek.com
---
drivers/net/usb/r8152.c | 64 +
1 file changed, 59 insertions(+), 5 deletions(-)
diff --git a/drivers/net/usb/r8152.c b/drivers/net/usb/r8152.c
index abb0b9f..4d938a7 100644
Use the interrupt transfer to replace polling link status.
Signed-off-by: Hayes Wang hayesw...@realtek.com
---
drivers/net/usb/r8152.c | 140 ++--
1 file changed, 113 insertions(+), 27 deletions(-)
diff --git a/drivers/net/usb/r8152.c
Enable the tx/rx aggregation which could contain one or more packets
for each bulk in/out. This could reduce the loading of the host
controller by sending less bulk transfer.
The rx packets in the bulk in buffer should be 8-byte aligned, and
the tx packets in the bulk out buffer should be 4-byte
From: Ivan T. Ivanov iiva...@mm-sol.com
DWC3 glue layer is hardware layer around Synopsys DesignWare
USB3 core. Its purpose is to supply Synopsys IP with required
clocks, voltages and interface it with the rest of the SoC.
Signed-off-by: Ivan T. Ivanov iiva...@mm-sol.com
---
From: Ivan T. Ivanov iiva...@mm-sol.com
MSM USB3.0 core wrapper consist of USB3.0 IP from Synopsys
(SNPS) and HS, SS PHY's control and configuration registers.
It could operate in device mode (SS, HS, FS) and host
mode (SS, HS, FS, LS).
Signed-off-by: Ivan T. Ivanov iiva...@mm-sol.com
---
From: Ivan T. Ivanov iiva...@mm-sol.com
Hi,
These patches add basic support for USB3.0 controllers found
on MSM platforms. USB3.0 core is based on Synopsys DesignWare
SuperSpeed IP.
Changes since v2:
* Several improvements in devicetree bindings description
* Disable regulators in glue layer
From: Ivan T. Ivanov iiva...@mm-sol.com
These drivers handles control and configuration of the HS
and SS USB PHY transceivers. They are part of the driver
which manage Synopsys DesignWare USB3 controller stack
inside Qualcomm SoC's.
Signed-off-by: Ivan T. Ivanov iiva...@mm-sol.com
---
Hi,
On Tuesday, August 13, 2013 at 8:40 PM, Greg KH wrote:
When communicating with AT90USB1287, at random intervals (1/25 boots)
the linux hid_output_field Oopses and kills the communicating thread.
The AT90USB1287 microcontroller uses LUFA library for usb/hid
communication. It is trigged
Hi,
On 08/14/2013 12:18 PM, Johan Hovold wrote:
On Wed, Aug 14, 2013 at 11:17:57AM +0200, Hans de Goede wrote:
+What: /sys/bus/usb/devices/.../busnum
+KernelVersion: 2.6.22
+Description:
+ Bus-number of the USB-bus the device is connected to.
+
+What:
Hi All,
This patch adds documentation for all sysfs files used by libusb.
Changes in v2:
-Spelling fixes
-Add text about writing to bConfigurationValue, suggested by Alan Stern
Changes in v3:
-Rebase on latest usb-next
Changes in v4:
-Improve the wording for the descriptors text, suggested by
Signed-off-by: Hans de Goede hdego...@redhat.com
---
Documentation/ABI/testing/sysfs-bus-usb | 38 +
1 file changed, 38 insertions(+)
diff --git a/Documentation/ABI/testing/sysfs-bus-usb
b/Documentation/ABI/testing/sysfs-bus-usb
index 9c8926c..0053ae2 100644
---
We no longer need to model the RESET line as a regulator since
the USB phy-nop driver accepts reset-gpios property.
Signed-off-by: Roger Quadros rog...@ti.com
---
arch/arm/boot/dts/omap5-uevm.dts | 13 +
1 files changed, 1 insertions(+), 12 deletions(-)
diff --git
We no longer need to model the RESET line as a regulator since
the USB phy-nop driver accepts reset-gpios property.
Signed-off-by: Roger Quadros rog...@ti.com
---
arch/arm/boot/dts/omap3-beagle.dts | 13 +
1 files changed, 1 insertions(+), 12 deletions(-)
diff --git
The platform data bits can be inferred from the other members of
struct usbhs_phy_data. So get rid of the platform_data member.
Build the platform data for the PHY device in usbhs_init_phys() instead.
Signed-off-by: Roger Quadros rog...@ti.com
---
arch/arm/mach-omap2/board-omap3beagle.c |6
Hi,
Modelling the RESET line as a regulator supply wasn't a good idea
as it abuses the regulator framework and makes adaptation
code/data more complex.
Instead, manage the RESET gpio line directly in the driver.
This also makes us easy to migrate to a dedicated GPIO RESET controller
whenever it
We no longer need to model the RESET line as a regulator since
the USB phy-nop driver accepts reset-gpios property.
Signed-off-by: Roger Quadros rog...@ti.com
---
arch/arm/boot/dts/omap4-panda-common.dtsi | 18 +-
1 files changed, 1 insertions(+), 17 deletions(-)
diff --git
The GPIO number of the RESET line can be passed to the
driver using the gpio_reset member.
Signed-off-by: Roger Quadros rog...@ti.com
---
include/linux/usb/nop-usb-xceiv.h |4 +++-
1 files changed, 3 insertions(+), 1 deletions(-)
diff --git a/include/linux/usb/nop-usb-xceiv.h
Use a common naming scheme mode0name.modename flags for the
USB host pins to be consistent.
Signed-off-by: Roger Quadros rog...@ti.com
---
arch/arm/boot/dts/omap3-beagle.dts | 24
1 files changed, 12 insertions(+), 12 deletions(-)
diff --git
Modelling the RESET line as a regulator supply wasn't a good idea
as it kind of abuses the regulator framework and also makes adaptation
code more complex.
Instead, manage the RESET gpio line directly in the driver. Update
the device tree binding information.
This also makes us easy to migrate
The USB phy-nop nop driver expects the RESET line information
to be sent as a GPIO number via platform data. Adapt to that.
Signed-off-by: Roger Quadros rog...@ti.com
---
arch/arm/mach-omap2/usb-host.c | 11 +--
1 files changed, 1 insertions(+), 10 deletions(-)
diff --git
Provide RESET GPIO and Power regulator for the USB PHY,
the USB Host port mode and the PHY device for the controller.
Also provide pin multiplexer information for USB host pins.
We also relocate omap3_pmx_core pin definations so that they
are close to omap3_pmx_wkup pin definations.
On Tue, 13 Aug 2013, Sarah Sharp wrote:
Martin is right; the BOS descriptors are leaked in
usb_reset_and_verify_device(). We need to store the old descriptor,
compare it with the new one following the reset, and delete one of them
afterward. I haven't had time to fix this.
I'll put
Hi,
On Tue, Aug 13, 2013 at 03:29:45PM -0700, Greg KH wrote:
On Tue, Aug 13, 2013 at 03:01:23PM -0500, Felipe Balbi wrote:
Hi,
On Tue, Aug 13, 2013 at 02:48:42PM -0500, Felipe Balbi wrote:
On Tue, Aug 13, 2013 at 02:41:25PM -0500, Felipe Balbi wrote:
Hi Greg,
Here's my
On Wed, 14 Aug 2013, Oliver Neukum wrote:
On Wed, 2013-08-14 at 13:24 +0530, Vivek Gautam wrote:
Hi all,
Going through the power suspend/resume sequence of USB, got hit by a doubt.
I am not able to figure out how the USB core driver takes care of
It doesn't.
All it does is
On Wed, Aug 14, 2013 at 03:59:42PM +0300, Ivan T. Ivanov wrote:
From: Ivan T. Ivanov iiva...@mm-sol.com
These drivers handles control and configuration of the HS
and SS USB PHY transceivers. They are part of the driver
which manage Synopsys DesignWare USB3 controller stack
inside Qualcomm
On Wed, 14 Aug 2013, Oliver Neukum wrote:
On Wed, 2013-08-14 at 14:46 +0530, Vivek Gautam wrote:
Hi,
devices and root-hubs across suspend/resume. Are the device contexts
saved somewhere and then restored back on resume ?
Usually not. The state of interfaces are the
On Wed, 14 Aug 2013, Mark Brown wrote:
On Mon, Aug 12, 2013 at 09:04:00PM -0400, Alan Stern wrote:
The bus code would need hooks installed wherever the platform wants to
do something extra. This could end up growing to a lot of hooks. How
can the whole thing be done in a reasonable
Hi,
On Wed, 2013-08-14 at 09:20 -0500, Josh Cartwright wrote:
On Wed, Aug 14, 2013 at 03:59:42PM +0300, Ivan T. Ivanov wrote:
From: Ivan T. Ivanov iiva...@mm-sol.com
These drivers handles control and configuration of the HS
and SS USB PHY transceivers. They are part of the driver
Well... finally it doesn't work.
When added to sw.c, the key is powered on, it's MAC address and few networks
can be seen.
But I can't connect to any network.
--
To unsubscribe from this list: send the line unsubscribe linux-usb in
the body of a message to majord...@vger.kernel.org
More
Hi,
On Wednesday 14 August 2013 04:34 AM, Tomasz Figa wrote:
On Wednesday 14 of August 2013 00:19:28 Sylwester Nawrocki wrote:
W dniu 2013-08-13 14:05, Kishon Vijay Abraham I pisze:
On Tuesday 13 August 2013 05:07 PM, Tomasz Figa wrote:
On Tuesday 13 of August 2013 16:14:44 Kishon Vijay
Hi Roger,
Am Mittwoch, den 14.08.2013, 16:58 +0300 schrieb Roger Quadros:
Modelling the RESET line as a regulator supply wasn't a good idea
as it kind of abuses the regulator framework and also makes adaptation
code more complex.
Instead, manage the RESET gpio line directly in the driver.
On Wed, Aug 14, 2013 at 10:27:26AM -0400, Alan Stern wrote:
On Wed, 14 Aug 2013, Mark Brown wrote:
I'd expect that we're just looking at hooks around connection and
disconnection here here - if we're looking at much more it seems like we
must be doing something wrong.
Connection and
On Wed, Aug 14, 2013 at 12:07 PM, srenau...@free.fr wrote:
Well... finally it doesn't work.
When added to sw.c, the key is powered on, it's MAC address and few networks
can be seen.
But I can't connect to any network.
Have you tried it on 3.11-rc5?
--
To unsubscribe from this list: send
On 08/14/13 05:59, Ivan T. Ivanov wrote:
+}
+
+static const struct of_device_id of_dwc3_matach[] = {
match? Maybe you can make it all one line too { .compatible = qcom,dwc3 }
+ {
+ .compatible = qcom,dwc3,
+ },
+ { },
+};
+MODULE_DEVICE_TABLE(of, of_dwc3_matach);
On Wed, 14 Aug 2013, Mark Brown wrote:
On Wed, Aug 14, 2013 at 10:27:26AM -0400, Alan Stern wrote:
On Wed, 14 Aug 2013, Mark Brown wrote:
I'd expect that we're just looking at hooks around connection and
disconnection here here - if we're looking at much more it seems like we
must
On Wed, 2013-08-14 at 09:40 -0700, Sarah Sharp wrote:
Hi Xenia,
I'm a bit confused. I thought that debugging messages would be turned
off by default for a module if CONFIG_DYNAMIC_DEBUG was turned on. When
I tested your patch to remove the CONFIG_USB_XHCI_HCD_DEBUGGING and just
use
On Wed, Aug 14, 2013 at 09:51:54AM -0700, Joe Perches wrote:
On Wed, 2013-08-14 at 09:40 -0700, Sarah Sharp wrote:
Hi Xenia,
I'm a bit confused. I thought that debugging messages would be turned
off by default for a module if CONFIG_DYNAMIC_DEBUG was turned on. When
I tested your
1 - 100 of 156 matches
Mail list logo
