Hi,
On Fri, 2013-07-26 at 02:06 +, Paul Zimmerman wrote:
From: Felipe Balbi [mailto:ba...@ti.com]
Sent: Thursday, July 25, 2013 1:52 PM
On Thu, Jul 25, 2013 at 07:46:58PM +, Paul Zimmerman wrote:
diff --git a/drivers/usb/dwc3/core.c b/drivers/usb/dwc3/core.c
index
Alan Stern wrote:
On Thu, 25 Jul 2013, James Stone wrote:
The only slight difference I can see is that maybe the 3.10 uses
slightly higher CPU load than 3.5 at the ridiculously low latency of
64 frames/period duplex.
With the new patch, what you actually get is 44.1 frames/period (on
From: caizhiyong caizhiy...@huawei.com
When ohci-hcd is shutting down, call ohci_usb_reset reset ohci-hcd, the root
hub generate an interrupt, but ohci-rh_state is OHCI_RH_HALTED, and ohci_irq
ignore the interrupt, the kernel trigger warning irq nobody cared. ehci-hcd
is first disable
From: caizhiyong caizhiy...@huawei.com
When ohci-hcd is shutting down, call ohci_usb_reset reset ohci-hcd, the root
hub generate an interrupt, but ohci-rh_state is OHCI_RH_HALTED, and ohci_irq
ignore the interrupt, the kernel trigger warning irq nobody cared. ehci-hcd
is first disable
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 that
to
2013/7/26 Greg Kroah-Hartman:
+ Say Y here if you want to usb the Suunto ANT+ USB device.
I think there might be a thinko: s/to usb/to use/
--
Daniele Forsi
--
To unsubscribe from this list: send the line unsubscribe linux-usb in
the body of a message to majord...@vger.kernel.org
More
After the platform devices are created using PLATFORM_DEVID_AUTO, the
device names given in usb_bind_phy (in board file) does not match with
the actual device name causing the USB PHY library not to return the
PHY reference when the MUSB controller request for the PHY in the non-dt boot
case.
So
Previously MUSB wrapper (OMAP) device used PLATFORM_DEVID_AUTO while creating
MUSB core device. So in usb_bind_phy (binds the controller with the PHY), the
device name of the controller had *.auto* in it. Since with using
PLATFORM_DEVID_AUTO, there is no way to know the exact device name in
After the platform devices are created using PLATFORM_DEVID_AUTO, the
device names given in usb_bind_phy (in board file) does not match with
the actual device name causing the USB PHY library not to return the
PHY reference when the MUSB controller request for the PHY in the non-dt boot
case.
So
The EOI register is not present in the AM335x memory space according to
the TRM and thus removed.
Should any platform using the EOI register get merged then it may be
used again if the register address is not zero.
Signed-off-by: Sebastian Andrzej Siewior bige...@linutronix.de
---
Since we have added vbus reguatlor operation at common
host file (chipidea/host.c), the glue layer vbus operation
isn't needed any more.
Tested-by: Marek Vasut ma...@denx.de
Signed-off-by: Peter Chen peter.c...@freescale.com
---
drivers/usb/chipidea/ci_hdrc_imx.c | 30
When the flag CI_HDRC_PULLUP_ON_VBUS is set, .pullup should only be
called when the vbus is active. When the CI_HDRC_PULLUP_ON_VBUS
is set, the controller only begins to run when the vbus is on,
So, it is only meaningful software set pullup/pulldown after
the controller begins to run.
Tested-by:
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 set.
CI_HDRC_PULLUP_ON_VBUS stands for pullup dp when the vbus is on. This
flag doesn't need to set if the vbus is always on for gadget
since dp has
On Thu, 2013-07-11 at 15:29 -0400, Steven Rostedt wrote:
Note that there's no easy way to dynamically allocate the right amount
of space in the ringbuffer, or at least I haven't found one. We
therefore have a static size, which is somewhat inefficient.
Can you add a helper function? If
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 switches.
When the host roles begins, it opens
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 CI_HDRC_DUAL_ROLE_NOT_OTG to indicate if the
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
---
drivers/usb/chipidea/core.c | 11 ++-
1 files
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 Vasut ma...@denx.de
Signed-off-by: Peter
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 detection.
This patch are fully tested at imx6 sabresd and imx28evk platform by me.
Besides, marek tested it
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
---
drivers/usb/chipidea/udc.c |7 ++-
1 files changed, 6 insertions(+), 1
Move otg relate things to otg file.
Tested-by: Marek Vasut ma...@denx.de
Signed-off-by: Peter Chen peter.c...@freescale.com
---
drivers/usb/chipidea/core.c | 63 +--
drivers/usb/chipidea/otg.c | 57 +-
When we rmmod gadget, the ci-driver needs to be cleared.
Otherwise, we plug in usb cable again, the driver will
consider gadget is there, in fact, it was removed.
Besides, consolidate the calling of ci-driver-disconnect, when
we do rmmod gadget, the gadget's disconnect should be called from
udc
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
---
drivers/usb/chipidea/Makefile |2 +-
drivers/usb/chipidea/bits.h | 10
- The role's init will be called at probe procedure.
- The role's destory 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
Signed-off-by: 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 wait vbus to lower
than OTGSC_BSV, but it can
On Thu, 2013-07-25 at 22:19 +0800, Ming Lei wrote:
Hi,
On Thu, Jul 25, 2013 at 3:38 PM, Oliver Neukum oneu...@suse.de wrote:
On Thu, 2013-07-25 at 13:47 +0800, Ming Lei wrote:
Hi,
There are two patches on computing max rx/tx qlen, and fix one
performance problem on USB3 NIC.
I am
On Thu, Jul 25, 2013 at 05:32:35PM +0200, Lars-Peter Clausen wrote:
I see. But it can't be reused before calling the callback if it is
going to call the callback, right?
So if this is a no-no, I'm left with an additional argument to the
complete callback?
Hm, maybe using
Hi,
On Fri, Jul 26, 2013 at 09:48:26AM +0300, Ivan T. Ivanov wrote:
Also, this is not *modifying* what was passed, just skipping the xHCI
address space so we don't request_mem_region() an area we won't really
handle and prevent xhci-hcd.ko from probing.
Hmm? platform_get_resource()
On Thu, Jul 25, 2013 at 01:59:51PM -0700, Olof Johansson wrote:
On Thu, Jul 25, 2013 at 10:19 AM, Felipe Balbi ba...@ti.com wrote:
On Thu, Jul 25, 2013 at 09:18:39AM -0700, Olof Johansson wrote:
That's what the code does today, and I wasn't trying to second-guess
their decisions on that.
Here's a resend of the three remaining mos7840-fixes for v3.11 rebased
on usb-linus of today.
Tested using a mcs7820-device (and by faking the mcs7810 LED).
Johan
Johan Hovold (3):
USB: mos7840: fix race in register handling
USB: mos7840: fix device-type detection
USB: mos7840: fix race
Fix race in LED handling introduced by commit 0eafe4de (USB: serial:
mos7840: add support for MCS7810 devices) which reused the port control
urb for manipulating the LED without making sure that the urb is not
already in use. This could lead to the control urb being manipulated
while in flight.
Fix race in mos7840_get_reg which unconditionally manipulated the
control urb (which may already be in use) by adding a control-urb busy
flag.
Cc: sta...@vger.kernel.org
Signed-off-by: Johan Hovold jhov...@gmail.com
---
drivers/usb/serial/mos7840.c | 18 --
1 file changed, 16
Fix race in device-type detection introduced by commit 0eafe4de (USB:
serial: mos7840: add support for MCS7810 devices) which used a static
variable to hold the device type.
Move type detection to probe and use serial data to store the device
type.
Cc: sta...@vger.kernel.org
Signed-off-by: Johan
Hi Balbi,
On Thu, Jul 18, 2013 at 07:04:14PM -0400, Scott Jiang wrote:
Reset endpoint data toggle would lead to failure for musb
RTL version 1.9 on blackfin.
is this specific to musb 1.9 or to blackfin ?
I'm not sure about this. It failed in musb 1.9 on bf527.
But this bug didn't affect
Hi,
On Fri, Jul 26, 2013 at 05:59:22PM +0800, Scott Jiang wrote:
Hi Balbi,
On Thu, Jul 18, 2013 at 07:04:14PM -0400, Scott Jiang wrote:
Reset endpoint data toggle would lead to failure for musb
RTL version 1.9 on blackfin.
is this specific to musb 1.9 or to blackfin ?
I'm not sure
On Thu, Jul 25, 2013 at 09:52:29PM -0700, Greg Kroah-Hartman wrote:
Steinar, I've tested the driver below with my device and it seems to
work. If you have any problems with it, please let me know, otherwise
I'll queue it up to get into the 3.11 kernel release soon.
Backported to 3.10.3 and
On Fri, 2013-07-26 at 11:19 +0200, Johannes Berg wrote:
My original though here was that we should be able to reserve (maximum)
space on the per-CPU buffer, and then relinquish some of it after the
tracepoint was written to the data, but I never had the time to check if
that was possible to
The compatibility layer which the USBF_PHONET_INCLUDED was a part of
is no longer present - the USBF_PHONET_INCLUDED is not #defined by anyone
anymore, so the ifndef is always true. Removing it.
Signed-off-by: Andrzej Pietrasiewicz andrze...@samsung.com
Signed-off-by: Kyungmin Park
A randconfig build hit the following build errors because xhci.c and
xhci-mem.c use dma mapping functions but don't include
linux/dma-mapping.h. Add the missing includes to fix the build errors.
drivers/usb/host/xhci.c In function 'xhci_gen_setup':
drivers/usb/host/xhci.c +4872 : error: implicit
Fix to return a negative error code from the error handling
case instead of 0, as returned elsewhere in this function.
Introduced by commit 59835a (usb: gadget: multi: use
function framework for ACM.)
Make rndis_do_config() consistent with cdc_do_config() in the way it
handles returning the
Updated the usb_otg_hs dt data to include the *phy* and *phy-names*
binding in order for the driver to use the new generic PHY framework.
Also updated the Documentation to include the binding information.
The PHY binding information can be found at
Use the generic PHY framework API to get the PHY. The usb_phy_set_resume
and usb_phy_set_suspend is replaced with power_on and
power_off to align with the new PHY framework.
musb-xceiv can't be removed as of now because musb core uses xceiv.state and
xceiv.otg. Once there is a separate state
Now that twl4030-usb is adapted to the new generic PHY framework,
*set_suspend* and *phy_init* ops can be removed from twl4030-usb driver.
Signed-off-by: Kishon Vijay Abraham I kis...@ti.com
Acked-by: Felipe Balbi ba...@ti.com
Reviewed-by: Sylwester Nawrocki s.nawro...@samsung.com
---
The PHY framework uses the phy consumer data populated in platform data in the
case of non-dt boot to return the reference to the PHY when the controller
(PHY consumer) requests for it. So populated the phy consumer data in the
platform
data of twl usb.
Signed-off-by: Kishon Vijay Abraham I
Now that omap-usb2 is adapted to the new generic PHY framework,
*set_suspend* ops can be removed from omap-usb2 driver.
Signed-off-by: Kishon Vijay Abraham I kis...@ti.com
Acked-by: Felipe Balbi ba...@ti.com
Reviewed-by: Sylwester Nawrocki s.nawro...@samsung.com
---
drivers/phy/phy-omap-usb2.c |
Used the generic PHY framework API to create the PHY. Now the power off and
power on are done in omap_usb_power_off and omap_usb_power_on respectively.
The omap-usb2 driver is also moved to driver/phy.
However using the old USB PHY library cannot be completely removed
because OTG is intertwined
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 with or without using phandle. For dt-boot, the PHY drivers should
also register *PHY provider* with the framework.
PHY drivers should create the PHY by
On Thursday, July 25, 2013 7:33 PM Felipe Balbi wrote:
On Fri, Jul 19, 2013 at 12:28:13PM +0200, Andrzej Pietrasiewicz wrote:
Fix to return a negative error code from the error handling case
instead of 0, as returned elsewhere in this function.
Introduced by commit 59835a (usb: gadget:
The PHY framework uses the phy consumer data populated in platform data in the
case of non-dt boot to return the reference to the PHY when the controller
(PHY consumer) requests for it. So populated the phy consumer data in the
platform
data of twl usb.
Signed-off-by: Kishon Vijay Abraham I
Use the generic PHY framework API to get the PHY. The usb_phy_set_resume
and usb_phy_set_suspend is replaced with power_on and
power_off to align with the new PHY framework.
musb-xceiv can't be removed as of now because musb core uses xceiv.state and
xceiv.otg. Once there is a separate state
Used the generic PHY framework API to create the PHY. For powering on
and powering off the PHY, power_on and power_off ops are used. Once the
MUSB OMAP glue is adapted to the new framework, the suspend and resume
ops of usb phy library will be removed. Also twl4030-usb driver is moved
to
Now that twl4030-usb is adapted to the new generic PHY framework,
*set_suspend* and *phy_init* ops can be removed from twl4030-usb driver.
Signed-off-by: Kishon Vijay Abraham I kis...@ti.com
Acked-by: Felipe Balbi ba...@ti.com
Reviewed-by: Sylwester Nawrocki s.nawro...@samsung.com
---
Updated the usb_otg_hs dt data to include the *phy* and *phy-names*
binding in order for the driver to use the new generic PHY framework.
Also updated the Documentation to include the binding information.
The PHY binding information can be found at
Resending with fixed device tree mailing address!
Added a generic PHY framework that 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 with or without using phandle.
This framework will be of use only to devices that
Used the generic PHY framework API to create the PHY. Now the power off and
power on are done in omap_usb_power_off and omap_usb_power_on respectively.
The omap-usb2 driver is also moved to driver/phy.
However using the old USB PHY library cannot be completely removed
because OTG is intertwined
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 with or without using phandle. For dt-boot, the PHY drivers should
also register *PHY provider* with the framework.
PHY drivers should create the PHY by
On Fri, 2013-07-26 at 08:28 -0400, Steven Rostedt wrote:
My original though here was that we should be able to reserve (maximum)
space on the per-CPU buffer, and then relinquish some of it after the
tracepoint was written to the data, but I never had the time to check if
that was possible
On Fri, 2013-07-26 at 15:06 +0200, Johannes Berg wrote:
On Fri, 2013-07-26 at 08:28 -0400, Steven Rostedt wrote:
Ah, yes, that'd work. I was considering putting it into the trace event
handling itself so I don't have to allocate those buffers and put the
handling into every tracepoint, but I
On Fri, 2013-07-26 at 09:17 -0400, Steven Rostedt wrote:
On Fri, 2013-07-26 at 15:06 +0200, Johannes Berg wrote:
On Fri, 2013-07-26 at 08:28 -0400, Steven Rostedt wrote:
Ah, yes, that'd work. I was considering putting it into the trace event
handling itself so I don't have to allocate
On Fri, 2013-07-26 at 15:45 +0200, Johannes Berg wrote:
Well, right now I can live with allocation 110 bytes for each
tracepoint, this would just optimise it down. If I was in the middle of
writing one such event while an interrupt came in, I'd not be able to
reduce the ring-buffer allocation
On Thu, 25 Jul 2013, Greg Kroah-Hartman wrote:
From: Greg Kroah-Hartman gre...@linuxfoundation.org
This adds a driver for the Suunto ANT+ USB device, exposing it as a usb
serial device. This lets the userspace gant program to talk to the
device to communicate over the ANT+ protocol to any
On 07/11/2013 11:05 AM, Ming Lei wrote:
Complete() will be run with interrupt enabled, so change to
spin_lock_irqsave().
Cc: Mauro Carvalho Chehab mche...@redhat.com
Cc: Hans Verkuil hans.verk...@cisco.com
Cc: linux-me...@vger.kernel.org
Signed-off-by: Ming Lei ming@canonical.com
On Fri, 26 Jul 2013, Caizhiyong wrote:
From: caizhiyong caizhiy...@huawei.com
When ohci-hcd is shutting down, call ohci_usb_reset reset ohci-hcd,
the root hub generate an interrupt, but ohci-rh_state is
OHCI_RH_HALTED, and ohci_irq ignore the interrupt, the kernel trigger
warning irq
On Thu, Jul 25, 2013 at 10:30 PM, Oleksii Shevchuk alx...@gmail.com wrote:
https://bugzilla.kernel.org/show_bug.cgi?id=60621
Randomly after returning from S3 or enabling powersaving this trace goes to
dmesg:
[13108.297051] ehci-pci :00:1a.0: power state changed by ACPI to D3cold
Separate the OHCI EP93XX host controller driver from ohci-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.
Signed-off-by: Manjunath Goudar manjunath.gou...@linaro.org
Acked-by: Alan Stern st...@rowland.harvard.edu
Cc:
Separate the OHCI pxa27x/pxa3xx host controller driver from
ohci-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.
Signed-off-by: Manjunath Goudar manjunath.gou...@linaro.org
Cc: Arnd Bergmann a...@arndb.de
Cc: Greg KH
These patches are for separating the SOC On-Chip ohci host controller
from ohci-hcd host code into its own driver module.
This work is part of enabling multi-platform kernels on ARM.
In V2:
patch 1/2:
-ohci_hcd_init() statements are removed,
because by default it is called in
On Fri, Jul 26, 2013 at 10:27:51AM -0400, Alan Stern wrote:
On Thu, 25 Jul 2013, Greg Kroah-Hartman wrote:
From: Greg Kroah-Hartman gre...@linuxfoundation.org
This adds a driver for the Suunto ANT+ USB device, exposing it as a usb
serial device. This lets the userspace gant program to
On Fri, Jul 26, 2013 at 01:56:19PM +0800, Barry Song wrote:
2013/7/18 Felipe Balbi ba...@ti.com:
On Thu, Jul 18, 2013 at 05:28:19PM +0800, Rong Wang wrote:
Hi Felipe,
Thanks, I'll test the patch.
But sysfs_notify(gadget-dev.kobj, NULL, status), status or state ?
I notice that
Hi Felipe,
On 07/25/2013 09:30 PM, Felipe Balbi wrote:
On Wed, Jul 24, 2013 at 12:20:17AM +0400, Alexey Khoroshilov wrote:
mv_u3d_nuke() expects to be calles with ep-u3d-lock held,
because mv_u3d_done() does. But mv_u3d_ep_disable() calls it
without lock that can lead to unpleasant
* Bin Liu | 2013-07-23 13:55:27 [-0500]:
Hi Sebastian,
Hi Bin,
either by SRP or HNP, or something else. In TI 3.2 kernel, there is
workaround in otg_timer() to _toggle_ the SESSION bit to detect if ID
pin is grounded, which means a USB device is connected.
I've been looking at
This is kernel 3.9.9-302.fc19.x86_64.
I plugged in a BN Nook (a usb mass storage device), used it, and
ejected it. This makes suspend fail:
[50135.265514] PM: Entering freeze sleep
[50135.265517] Suspending console(s) (use no_console_suspend to debug)
[50135.287724] sd 7:0:0:0: [sdb]
On Fri, 26 Jul 2013, Andy Lutomirski wrote:
This is kernel 3.9.9-302.fc19.x86_64.
I plugged in a BN Nook (a usb mass storage device), used it, and
ejected it. This makes suspend fail:
[50135.265514] PM: Entering freeze sleep
[50135.265517] Suspending console(s) (use no_console_suspend
Sebastian,
On Fri, Jul 26, 2013 at 11:31 AM, Sebastian Andrzej Siewior
bige...@linutronix.de wrote:
* Bin Liu | 2013-07-23 13:55:27 [-0500]:
Hi Sebastian,
Hi Bin,
either by SRP or HNP, or something else. In TI 3.2 kernel, there is
workaround in otg_timer() to _toggle_ the SESSION bit to
On Fri, Jul 26, 2013 at 12:53 PM, Bin Liu binml...@gmail.com wrote:
Sebastian,
On Fri, Jul 26, 2013 at 11:31 AM, Sebastian Andrzej Siewior
bige...@linutronix.de wrote:
* Bin Liu | 2013-07-23 13:55:27 [-0500]:
Hi Sebastian,
Hi Bin,
either by SRP or HNP, or something else. In TI 3.2 kernel,
On 07/26/2013 08:17 PM, Bin Liu wrote:
Hi Bin.
In TI 3.2 kernel, the otg_timer() toggles the SESSION bit in
OTG_STATE_B_IDLE state. So whenever the ID pin is grounded by
connecting a device, the controller will try go into host mode.
But I have no idea why your board is in a_idle not b_idle.
Sebastian,
On Fri, Jul 26, 2013 at 1:22 PM, Sebastian Andrzej Siewior
bige...@linutronix.de wrote:
On 07/26/2013 08:17 PM, Bin Liu wrote:
Hi Bin.
In TI 3.2 kernel, the otg_timer() toggles the SESSION bit in
OTG_STATE_B_IDLE state. So whenever the ID pin is grounded by
connecting a device,
From: Felipe Balbi [mailto:ba...@ti.com]
Sent: Friday, July 26, 2013 2:54 AM
Also, this is not *modifying* what was passed, just skipping the xHCI
address space so we don't request_mem_region() an area we won't really
handle and prevent xhci-hcd.ko from probing.
Hmm?
On Fri, 26 Jul 2013, Clemens Ladisch wrote:
Alan Stern wrote:
On Thu, 25 Jul 2013, James Stone wrote:
The only slight difference I can see is that maybe the 3.10 uses
slightly higher CPU load than 3.5 at the ridiculously low latency of
64 frames/period duplex.
With the new patch,
On Fri, 26 Jul 2013, Manjunath Goudar wrote:
Separate the OHCI pxa27x/pxa3xx host controller driver from
ohci-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.
Signed-off-by: Manjunath Goudar
Fabio Estevam fabio.este...@freescale.com writes:
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
On 07/26/2013 08:29 PM, Bin Liu wrote:
Hi Bin,
[ 97.570852] musb-hdrc musb-hdrc.1.auto: Poll devctl 19 (a_wait_bcon)
I don't think you are testing with the 3.2 kernel you referred from
the ti.com link you mentioned above.
3.2 kernel should have no '.auto' at the end of the device name.
Sebastian,
On Fri, Jul 26, 2013 at 2:55 PM, Sebastian Andrzej Siewior
bige...@linutronix.de wrote:
The bit is removed in otg_timer() because the phy gets into
OTG_STATE_A_WAIT_BCON.
Now, this is current HEAD + my stuff to get second port working. I
downloaded v3.2 and browsed as I was
The nop driver isn't a do-nothing-stub but supports a couple functions
like clock on/off or is able to use a voltage regulator. This patch
simply renames the driver to generic since it is easy possible to
extend it by a simple function istead of writing a complete driver.
Signed-off-by: Sebastian
dsps uses a nop driver which is added in dsps itself and does the PHY
on/off calls within dsps. Since those calls are now moved the nop driver
itself, we can now request the phy proper phy and remove those calls.
Currently only the first musb interface is used so we only add one phy
node for now.
This moves the two instances from the big node into two child nodes. The
glue layer ontop does almost nothing.
There is one devices containing the (2) phy, (2) usb and later the dma
engine. The usb device is the glue device which contains the musb
device as a child. This is what we do ever since.
Hi,
The last series has been rebased ontop Felipe's testing branch. It contains
only the support for multiple devices. I decided to keep the temporary change
in the nop (now generic) phy driver which should ease the transition.
I still have the problem that the second USB port does not work
This patch copies the phy support bits from dsps into the generic phy
driver. Most code can be re-used except for the on/off.
The additional am335x can be removed once we have a phy driver that does
more than this.
Signed-off-by: Sebastian Andrzej Siewior bige...@linutronix.de
---
On Fri, Jul 26, 2013 at 03:31:34PM +0300, Ivan T. Ivanov wrote:
Hi Felipe,
On Thu, 2013-07-25 at 16:43 +0300, Ivan T. Ivanov wrote:
On Wed, 2013-07-24 at 15:39 +0300, Felipe Balbi wrote:
On Tue, Jul 09, 2013 at 06:47:09PM +0300, Ivan T. Ivanov wrote:
From: Ivan T. Ivanov
On Fri, Jul 26, 2013 at 09:23:35AM -0700, Olof Johansson wrote:
On Fri, Jul 26, 2013 at 2:54 AM, Felipe Balbi ba...@ti.com wrote:
On Thu, Jul 25, 2013 at 01:59:51PM -0700, Olof Johansson wrote:
On Thu, Jul 25, 2013 at 10:19 AM, Felipe Balbi ba...@ti.com wrote:
On Thu, Jul 25, 2013 at
On Fri, 26 Jul 2013, Andy Lutomirski wrote:
This is kernel 3.9.9-302.fc19.x86_64.
I plugged in a BN Nook (a usb mass storage device), used it, and
ejected it. This makes suspend fail:
[50135.265514] PM: Entering freeze sleep
[50135.265517] Suspending console(s) (use no_console_suspend
Hi,
On Fri, Jul 26, 2013 at 06:44:23PM +, Paul Zimmerman wrote:
From: Felipe Balbi [mailto:ba...@ti.com]
Sent: Friday, July 26, 2013 2:54 AM
Also, this is not *modifying* what was passed, just skipping the xHCI
address space so we don't request_mem_region() an area we won't
On 07/26/2013 10:15 PM, Bin Liu wrote:
Sebastian,
Hi Bin,
I started thinking when I tried this git.ti.com 3.8 kernel, I might
have done 'devmem2 0x47401c60 b 0x81' to manually set the SESSION bit
after plugged a device. It was months ago, I don't quite remember what
I tested.
Ah. You
On Fri, Jul 26, 2013 at 1:30 PM, Felipe Balbi ba...@ti.com wrote:
On Fri, Jul 26, 2013 at 09:23:35AM -0700, Olof Johansson wrote:
On Fri, Jul 26, 2013 at 2:54 AM, Felipe Balbi ba...@ti.com wrote:
On Thu, Jul 25, 2013 at 01:59:51PM -0700, Olof Johansson wrote:
On Thu, Jul 25, 2013 at 10:19
On Fri, Jul 26, 2013 at 09:52:56AM +, Feng-Hsin Chiang wrote:
FOTG210 is an OTG controller which can be configured as an
USB2.0 host. FOTG210 host is an ehci-like controller with
some differences. First, register layout of FOTG210 is
incompatible with EHCI. Furthermore, FOTG210 is lack of
On Fri, Jul 26, 2013 at 02:00:42PM +0200, Steinar H. Gunderson wrote:
On Thu, Jul 25, 2013 at 09:52:29PM -0700, Greg Kroah-Hartman wrote:
Steinar, I've tested the driver below with my device and it seems to
work. If you have any problems with it, please let me know, otherwise
I'll queue it
On Fri, Jul 26, 2013 at 10:55:19AM +0200, Daniele Forsi wrote:
2013/7/26 Greg Kroah-Hartman:
+ Say Y here if you want to usb the Suunto ANT+ USB device.
I think there might be a thinko: s/to usb/to use/
Thanks, now fixed, too much USB on the brain...
greg k-h
--
To unsubscribe
Hi all,
I've now caught up on all pending USB patches that were sent to me, with
the exception of Ming's EHCI patches, which I need to test further next
week.
If you've sent me something, that I haven't applied, please resend it,
as it's probably lost somewhere.
thanks,
greg k-h
--
To
On Fri, Jul 26, 2013 at 11:55:18AM +0200, Johan Hovold wrote:
Fix race in device-type detection introduced by commit 0eafe4de (USB:
serial: mos7840: add support for MCS7810 devices) which used a static
variable to hold the device type.
Move type detection to probe and use serial data to
On Fri, Jul 26, 2013 at 02:12:46PM -0700, Greg Kroah-Hartman wrote:
Backported to 3.10.3 and tested (with my own, old fork of gant), works fine.
Wonderful, thanks for testing.
Where is the official place for gant these days anyway?
I wish I knew. I think there are like four forks, some of
1 - 100 of 103 matches
Mail list logo
