On Fri, May 24, 2013 at 04:38:29PM -0300, Fabio Estevam wrote:
> From: Fabio Estevam
>
> Fix the following sparse warnings:
>
> drivers/usb/chipidea/usbmisc_imx.c:246:5: warning: symbol
> 'usbmisc_imx_drv_init' was not declared. Should it be static?
> drivers/usb/chipidea/usbmisc_imx.c:252:6: w
This patch Initializes the register offset values depending
on the X_MAJOR of USBOTGSS_REVISION register. Also adds register
offset defines and new debug register defines.
X_MAJOR is 1 for OMAP5 and 2 for AM437x.
Register offsets are cached in dwc3_omap struct for reg reads and writes.
Signed-off
This patch modifies dwc3_omap_readl/writel calls to accomodate
both OMAP5 and AM437x reg maps (It uses the cached register offsets).
Also renames OMAP5 IRQ1 as IRQMISC, IRQ1 bits as IRQMISC bits.
Signed-off-by: George Cherian
---
drivers/usb/dwc3/dwc3-omap.c | 136 +--
AM437x and OMAP5 dwc3 subsytem have different register map.
Major differences are as follows.
OMAP5 has one main interrupt and one misc interrupt
Aegis has four main interrupts and one misc interrupt.
Miscellanous Interrupt offsets are changed.
UTMI OTG Control and Status Registers offsets are ch
Initial patch set to add support for dwc3 in am437x platform.
This patch series addresses the regiter map differences between
OMAP5 and AM437x, to re-use the same driver.
AM437x and OMAP5 dwc3 subsytem have different register map.
Major differences are as follows.
OMAP5 has one main interrupt and
On 04/24/2013 05:23 PM, Felipe Balbi wrote:
commit 145cadfc79a41633364940df6279e2c131f633b2
Author: Felipe Balbi
Date: Wed Apr 24 17:21:42 2013 +0300
usb: musb: fix incorrect usage of resource pointer
We can't simply pass the resource pointer from our
device down to our
> Hi list,
>
> I'm experiencing problems while booting on a Freescale P1013 based board. It
> hangs on USB initialization:
> [3.763584] ehci_hcd: USB 2.0 'Enhanced' Host Controller (EHCI) Driver
> [3.770519] ehci-pci: EHCI PCI platform driver
> [3.775116] ohci_hcd: USB 1.1 'Open' Hos
we never allocate a TRB pool for physical endpoints
0 and 1 so trying to free it (a invalid TRB pool pointer)
will lead us in a warning while removing dwc3.ko module.
In order to fix the situation, all we have to do is skip
dwc3_free_trb_pool() for physical endpoints 0 and 1 just
as we while delet
Hi,
On Monday 27 May 2013 12:26 PM, Laxman Dewangan wrote:
On Monday 27 May 2013 12:11 PM, Kishon Vijay Abraham I wrote:
Hi,
On Monday 27 May 2013 12:06 PM, Laxman Dewangan wrote:
On Monday 27 May 2013 12:01 PM, Kishon Vijay Abraham I wrote:
Hi,
On Monday 27 May 2013 11:52 AM, Laxman Dewang
> -Original Message-
> From: Cherian, George
> Sent: Monday, May 27, 2013 2:36 PM
> To: linux-usb@vger.kernel.org; linux-o...@vger.kernel.org; linux-
> ker...@vger.kernel.org
> Cc: Balbi, Felipe; gre...@linuxfoundation.org; Cherian, George
> Subject: [PATCH 1/4] usb: dwc3: gadget: free tr
Raise the maximum number of usb-serial devices to 256, which is the
actual limit supported by the codebase.
Signed-off-by: Jakob-Tobias Winter
Tested-by: Jakob-Tobias Winter
---
include/linux/usb/serial.h |2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/include/linux/usb/
From: Thomas Abraham
Exynos5440 does not require any explict USB phy configuration. So skip
the USB phy configuration for Exynos5440 based platforms.
Signed-off-by: Thomas Abraham
Cc: Alan Stern
Signed-off-by: Jingoo Han
---
Changes since v3:
- added empty_platdata as Alan Stern guided.
Chan
Hi,
>> I am able to solve the SCSI command timeout problem by adding a code
>> to check the hardware register busy bit continuously, in
>> kagen2_ep_queue():
>>
>> do {
>> read_hardware_register_busy_bit
>> } while (hardware_is_busy)
>
> This is silly. Drivers shouldn't poll in this way. That'
Hi,
I did a bit more fiddling with the usb-serial stack and got it to
support more than 256 devices. I tested it with up to 281 FTDI
singleport adapters. (After that i ran out of usb cables.. )
Signed-off-by: Jakob-Tobias Winter
---
include/linux/usb/serial.h |6 +++---
1 file changed, 3 in
Hi Alexander,
On Thu, May 16, 2013 at 04:05:24PM +0800, Peter Chen wrote:
> On Thu, May 16, 2013 at 09:53:57AM +0200, Michael Grzeschik wrote:
> > This patch adds iso endpoint support to the device controller.
> > It makes use of the multiplication bits in the maxpacket field
> > of the endpoint a
This series of patches begins the process of splitting ohci-hcd up into
a core library module and independent pci driver modules.
Patch 1/3 prepares the way by exporting a few functions from ohci-hcd
and adding a new mechanism for platform-specific drivers to initialize
their hc_driver structures.
This patch prepares ohci-hcd for being split up into a core
library and separate platform driver modules. A generic
ohci_hc_driver structure is created, containing all the "standard"
values, and a new mechanism is added whereby a driver module can
specify a set of overrides to those values. In ad
Note that this changes is part of separating the ohci pci host controller
driver from ohci-hcd host code.
This contains :
-Moved sb800_prefetch() function from ohci-pci.c to pci-quirks.c file
and EXPORTed, this is part of the effort to move the ohci pci related
code to generic pci
This patch splits the PCI portion of ohci-hcd out into its
own separate driver module, called ohci-pci.
The major point of difficulty lies in ohci-pci's many vendor- and
device-specific workarounds. Some of them have to be applied before
calling ohci_start() some after, which necessitates a fair
Tobias Winter writes:
> Hi,
>
> I did a bit more fiddling with the usb-serial stack and got it to
> support more than 256 devices. I tested it with up to 281 FTDI
> singleport adapters. (After that i ran out of usb cables.. )
>
> Signed-off-by: Jakob-Tobias Winter
> ---
> include/linux/usb/seri
Michael Grzeschik writes:
> Hi Alexander,
Hi,
>
> On Thu, May 16, 2013 at 04:05:24PM +0800, Peter Chen wrote:
>> On Thu, May 16, 2013 at 09:53:57AM +0200, Michael Grzeschik wrote:
>> > This patch adds iso endpoint support to the device controller.
>> > It makes use of the multiplication bits in
Fix regression introduced by commit 0eafe4de1a ("USB: serial: mos7840:
add support for MCS7810 devices") which used stack-allocated buffers for
control messages.
Cc: sta...@vger.kernel.org
Signed-off-by: Johan Hovold
---
drivers/usb/serial/mos7840.c | 35 +++
1 fi
The control-message timeout is specified in milliseconds and should not
depend on HZ.
Cc: sta...@vger.kernel.org
Signed-off-by: Johan Hovold
---
drivers/usb/serial/ark3116.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/drivers/usb/serial/ark3116.c b/drivers/usb/serial/ark3
The control and bulk-message timeouts are specified in milliseconds and
should not depend on HZ.
Cc: sta...@vger.kernel.org
Signed-off-by: Johan Hovold
---
drivers/usb/serial/mos7720.c | 6 +++---
1 file changed, 3 insertions(+), 3 deletions(-)
diff --git a/drivers/usb/serial/mos7720.c b/driver
Here's a few more usb-serial fixes for v3.10.
Johan
Johan Hovold (8):
USB: serial: fix Treo/Kyocera interrrupt-in urb context
USB: visor: fix initialisation of Treo/Kyocera devices
USB: mos7720: fix DMA to stack
USB: mos7840: fix DMA to stack
USB: ark3116: fix control-message timeout
The read_mos_reg function is called with stack-allocated buffers, which
must not be used for control messages.
Cc: sta...@vger.kernel.org
Signed-off-by: Johan Hovold
---
drivers/usb/serial/mos7720.c | 17 ++---
1 file changed, 14 insertions(+), 3 deletions(-)
diff --git a/drivers/us
The bulk-message timeout is specified in milliseconds and should not
depend on HZ.
Cc: sta...@vger.kernel.org
Signed-off-by: Johan Hovold
---
drivers/usb/serial/iuu_phoenix.c | 4 ++--
1 file changed, 2 insertions(+), 2 deletions(-)
diff --git a/drivers/usb/serial/iuu_phoenix.c b/drivers/usb/se
The first and second interrupt-in urbs are swapped for some Treo/Kyocera
devices, but the urb context was never updated with the new port.
Cc: sta...@vger.kernel.org
Signed-off-by: Johan Hovold
---
drivers/usb/serial/visor.c | 1 +
1 file changed, 1 insertion(+)
diff --git a/drivers/usb/serial/
The control-message timeout is specified in milliseconds and should not
depend on HZ.
Cc: sta...@vger.kernel.org
Signed-off-by: Johan Hovold
---
drivers/usb/serial/zte_ev.c | 28 ++--
1 file changed, 14 insertions(+), 14 deletions(-)
diff --git a/drivers/usb/serial/zte_e
Fix regression introduced by commit 214916f2e ("USB: visor: reimplement
using generic framework") which broke initialisation of Treo/Kyocera
devices that re-mapped bulk-in endpoints.
Cc: sta...@vger.kernel.org
Signed-off-by: Johan Hovold
---
drivers/usb/serial/visor.c | 8
1 file change
If usbmisc_ops->post() fails it should point the error path to release all
previously acquired resources, so adjust it to call ci13xxx_remove_device().
While at it, remove the unnecessary 'plat_ci' indirection, as we can directly
use the private structure.
Signed-off-by: Fabio Estevam
---
driv
There is no need to keep a 'reg_vbus' indirection, so get rid of it.
The motivation for doing this change is that in the case of error, the current
code only sets the local reg_vbus to NULL instead of updating the private
structure 'data->reg_vbus'.
Updating only the local reg_vbus is wrong, sin
Similarly as it is done in ci13xxx_imx_remove(), only calls of_node_put if
data->phy_np is not NULL.
Signed-off-by: Fabio Estevam
---
drivers/usb/chipidea/ci13xxx_imx.c | 3 ++-
1 file changed, 2 insertions(+), 1 deletion(-)
diff --git a/drivers/usb/chipidea/ci13xxx_imx.c
b/drivers/usb/chipide
There is no need to keep a local 'phy_np' as we can directly use the private
structure in data->phy_np.
Signed-off-by: Fabio Estevam
---
drivers/usb/chipidea/ci13xxx_imx.c | 12 +---
1 file changed, 5 insertions(+), 7 deletions(-)
diff --git a/drivers/usb/chipidea/ci13xxx_imx.c
b/drive
On 27 May 2013 17:55, Manjunath Goudar wrote:
> This series of patches begins the process of splitting ohci-hcd up into
> a core library module and independent pci driver modules.
>
> Patch 1/3 prepares the way by exporting a few functions from ohci-hcd
> and adding a new mechanism for platform-sp
From: Graeme Gregory
This is the driver for the USB comparator 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 Vi
Modified dwc3-omap to receive connect and disconnect notification using
extcon framework. Also did the necessary cleanups required after
adapting to extcon framework.
Signed-off-by: Kishon Vijay Abraham I
Acked-by: Chanwoo Choi
---
Changes from v1:
* regulator enable/disable is now done here ins
On Sun, May 26, 2013 at 07:19:03PM +0200, Andrew Lunn wrote:
> On Sun, May 26, 2013 at 06:04:24PM +0200, Johan Hovold wrote:
> > On Sun, May 26, 2013 at 01:00:51PM +0200, Andrew Lunn wrote:
[...]
> > > +/*
> > > + * mxuport_prepare_write_buffer - fill in the buffer, ready for
> > > + * sending
>
On Mon, 27 May 2013, Jingoo Han wrote:
> From: Thomas Abraham
>
> Exynos5440 does not require any explict USB phy configuration. So skip
> the USB phy configuration for Exynos5440 based platforms.
>
> Signed-off-by: Thomas Abraham
> Cc: Alan Stern
> Signed-off-by: Jingoo Han
> ---
> Changes
On Mon, 27 May 2013, Manjunath Goudar wrote:
> This patch prepares ohci-hcd for being split up into a core
> library and separate platform driver modules. A generic
> ohci_hc_driver structure is created, containing all the "standard"
> values, and a new mechanism is added whereby a driver module
On Mon, 27 May 2013, Manjunath Goudar wrote:
> Note that this changes is part of separating the ohci pci host controller
> driver from ohci-hcd host code.
> This contains :
> -Moved sb800_prefetch() function from ohci-pci.c to pci-quirks.c file
> and EXPORTed, this is part of the effort
On Mon, 27 May 2013, Manjunath Goudar wrote:
> This patch splits the PCI portion of ohci-hcd out into its
> own separate driver module, called ohci-pci.
>
> The major point of difficulty lies in ohci-pci's many vendor- and
> device-specific workarounds. Some of them have to be applied before
> c
Hi Felipe,
We've gone through remaining work items for getting the ARM kernel
to full multiplatform support again, and MUSB came up. I'm sure you
have your own thoughts on this, but I'd like to know if there is
already a plan in place.
>From what I can see, the driver in PIO mode should almost wo
On Mon, 27 May 2013, victor yeo wrote:
> > I can't say much more without seeing the code. However, you should not
> > need to wait for the hardware to do something -- instead the interrupt
> > handler routine should be called when the hardware is finished.
>
> Yes, it is silly. The hardware inte
On Sat, 25 May 2013, Tobias Diedrich wrote:
> I've recently upgraded my kernel from 3.8.5 to 3.9.2 and ran into an
> issue with usb-audio:
> With two different usb-headsets, pulseaudio is now regularily losing the
> microphone audio stream (which just gets 'stuck', i.e. the level
> indicator bar i
On Mon, 27 May 2013, Oleksij Rempel wrote:
> Am 27.05.2013 17:24, schrieb Alan Stern:
> > On Mon, 27 May 2013, Oleksij Rempel wrote:
> >
> >> Hello Alan,
> >>
> >> i have regression with this patch:
> >>
> >> commit c1fdb68e3d73741630ca16695cf9176c233be7ed
> >> Author: Alan Stern
> >> Date: Fri
This patchset tries to loose the check on DMA buffer size in check_unmap()
of dma-debug first, then only unmap the actual completed DMA buffer in USB
unmap path.
Considered that DMA unmapping often runs in hard irq context, the patch set
may save irq handling time. And the improvement can be obser
This patch looses the check on DMA buffer size for streaming
DMA unmap, based on the below fact:
- it is common to see only part of DMA transfer is completed,
especially in case of DMA_FROM_DEVICE
So it isn't necessary to unmap the whole DMA buffer inside DMA
unmapping, and unmapping the actual c
This patch only unmap the actual completed DMA buffer instead of
the whole transfer buffer.
It is common to see only part of DMA transfer is completed, especially
in case of DMA_FROM_DEVICE because the length of incoming traffic often
is unknown before submitting URB, so this patch may improve USB
Am 27.05.2013 17:59, schrieb Alan Stern:
On Mon, 27 May 2013, Oleksij Rempel wrote:
Am 27.05.2013 17:24, schrieb Alan Stern:
On Mon, 27 May 2013, Oleksij Rempel wrote:
Hello Alan,
i have regression with this patch:
commit c1fdb68e3d73741630ca16695cf9176c233be7ed
Author: Alan Stern
Date:
Hello.
On 27-05-2013 20:13, Ming Lei wrote:
This patch only unmap the actual completed DMA buffer instead of
the whole transfer buffer.
Who will unmap the rest of the buffer?
It is common to see only part of DMA transfer is completed, especially
in case of DMA_FROM_DEVICE because the le
On Saturday 25 May 2013, Adrien Vergé wrote:
> On OMAP4 platforms, EHCI HCD needs the physical layer signalling
> activated, along with the NOP USB Transceiver driver. Otherwise, the
> kernel boots without registering any USB device.
This does not actually sound like a critical error: If a user fo
On Tue, 28 May 2013, Ming Lei wrote:
> This patchset tries to loose the check on DMA buffer size in check_unmap()
> of dma-debug first, then only unmap the actual completed DMA buffer in USB
> unmap path.
>
> Considered that DMA unmapping often runs in hard irq context, the patch set
> may save i
On 05/27/2013 09:13 AM, Ming Lei wrote:
> This patch looses the check on DMA buffer size for streaming
> DMA unmap, based on the below fact:
>
> - it is common to see only part of DMA transfer is completed,
> especially in case of DMA_FROM_DEVICE
>
> So it isn't necessary to unmap the whole DMA b
On Monday 27 May 2013, Manjunath Goudar wrote:
> This patch splits the PCI portion of ohci-hcd out into its
> own separate driver module, called ohci-pci.
>
> The major point of difficulty lies in ohci-pci's many vendor- and
> device-specific workarounds. Some of them have to be applied before
>
On 05/27/2013 10:35 PM, Kishon Vijay Abraham I wrote:
> Modified dwc3-omap to receive connect and disconnect notification using
> extcon framework. Also did the necessary cleanups required after
> adapting to extcon framework.
>
> Signed-off-by: Kishon Vijay Abraham I
> Acked-by: Chanwoo Choi
> -
On 05/27/2013 10:33 PM, Kishon Vijay Abraham I wrote:
> From: Graeme Gregory
>
> This is the driver for the USB comparator 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: Moi
Hi Tony,
On Friday 17 May 2013 06:52 PM, Kishon Vijay Abraham I wrote:
In order for controllers to get PHY in case of non dt boot, the phy
binding information (phy label) should be added in the platform
data of the controller.
This series would be needed to get MUSB working in OMAP3 boards for
On Tuesday 28 May 2013 07:54 AM, Chanwoo Choi wrote:
On 05/27/2013 10:35 PM, Kishon Vijay Abraham I wrote:
Modified dwc3-omap to receive connect and disconnect notification using
extcon framework. Also did the necessary cleanups required after
adapting to extcon framework.
Signed-off-by: Kishon
On 05/27/2013 04:30:12 AM, Tobias Winter wrote:
Raise the maximum number of usb-serial devices to 256, which is the
actual limit supported by the codebase.
Signed-off-by: Jakob-Tobias Winter
Tested-by: Jakob-Tobias Winter
---
include/linux/usb/serial.h |2 +-
1 file changed, 1 insertion(
Hi,
On Tuesday 21 May 2013 10:31 AM, Kishon Vijay Abraham I wrote:
Hi,
On Monday 29 April 2013 03:33 PM, Kishon Vijay Abraham I wrote:
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 P
61 matches
Mail list logo
