On Mon, Aug 26, 2013 at 7:37 PM, Alan Stern st...@rowland.harvard.edu wrote:
Clemens and everyone else:
Not having heard any responses to the patch posted last Wednesday, I
have updated and completed it. The version below is ready for testing.
Please let me know what you find.
It is not
Hi guys!! :)
First of all - I would like to thank both of you for your interest and time in
my patches.
I agree with Joe's point of view, completely. The Coding style document tries
to leverage on the developer's good sense, even when defining some rules.
Apart from that - checkpatch.po
Dear Peter,
On 08/27/2013 04:51 AM, Peter Chen wrote:
On Mon, Aug 26, 2013 at 06:24:48PM +0200, Hector Palacios wrote:
Dear Peter,
On 08/12/2013 03:22 AM, Peter Chen wrote:
This patchset adds tested otg id switch function and vbus connect
and disconnect detection for chipidea driver. And fix
Alan Stern wrote:
All the difficulty arises from the fact that we don't know beforehand
how many URBs will constitute an ALSA period since for playback
endpoints, the URB sizes can vary. [...]
the number of URBs per period is fixed, and the number of packets in
each URB is adjusted during
On 27.8.2013 09:19, Clemens Ladisch wrote:
The driver cannot control how many samples actually end up in a capture
packet,...
Does this reasoning apply to asynchronous playback too? I understand the
driver has some control, but has to satisfy the endpoint feedback requests.
Sorry if this is
Hector Palacios hector.palac...@digi.com writes:
Dear Peter,
On 08/27/2013 04:51 AM, Peter Chen wrote:
On Mon, Aug 26, 2013 at 06:24:48PM +0200, Hector Palacios wrote:
Dear Peter,
On 08/12/2013 03:22 AM, Peter Chen wrote:
This patchset adds tested otg id switch function and vbus connect
Use the wrapper functions for getting and setting the driver data using
platform_device instead of using dev_{get,set}_drvdata() with pdev-dev,
so we can directly pass a struct platform_device.
Signed-off-by: Libo Chen libo.c...@huawei.com
---
drivers/usb/host/r8a66597-hcd.c |4 ++--
1
Pavel Hofman wrote:
On 27.8.2013 09:19, Clemens Ladisch wrote:
The driver cannot control how many samples actually end up in a capture
packet,...
Does this reasoning apply to asynchronous playback too?
No.
I understand the driver has some control, but has to satisfy the endpoint
feedback
Use the wrapper functions for getting and setting the driver data using
platform_device instead of using dev_{get,set}_drvdata() with pdev-dev,
so we can directly pass a struct platform_device.
Signed-off-by: Libo Chen libo.c...@huawei.com
---
drivers/usb/phy/phy-tegra-usb.c |2 +-
1 files
On 08/27/2013 10:09 AM, Alexander Shishkin wrote:
Hector Palacios hector.palac...@digi.com writes:
Dear Peter,
On 08/27/2013 04:51 AM, Peter Chen wrote:
On Mon, Aug 26, 2013 at 06:24:48PM +0200, Hector Palacios wrote:
Dear Peter,
On 08/12/2013 03:22 AM, Peter Chen wrote:
This patchset
Use the wrapper functions for getting and setting the driver data using
platform_device instead of using dev_{get,set}_drvdata() with pdev-dev,
so we can directly pass a struct platform_device.
Libo Chen (4):
usb: fotg210-udc: use platform_{get,set}_drvdata()
usb: r8a66597-hcd: use
Use the wrapper functions for getting and setting the driver data using
platform_device instead of using dev_{get,set}_drvdata() with pdev-dev,
so we can directly pass a struct platform_device.
Signed-off-by: Libo Chen libo.c...@huawei.com
---
drivers/usb/renesas_usbhs/common.c |2 +-
1
Use the wrapper functions for getting and setting the driver data using
platform_device instead of using dev_{get,set}_drvdata() with pdev-dev,
so we can directly pass a struct platform_device.
Signed-off-by: Libo Chen libo.c...@huawei.com
---
drivers/usb/gadget/fotg210-udc.c |4 ++--
1
It needs to free ci-hw_bank.regmap explicitly since it is not managed
resource.
Signed-off-by: Peter Chen peter.c...@freescale.com
---
drivers/usb/chipidea/core.c |1 +
1 files changed, 1 insertions(+), 0 deletions(-)
diff --git a/drivers/usb/chipidea/core.c b/drivers/usb/chipidea/core.c
Changed for v2:
- Fixed the build error for patch 5/5
Below are un-queued chipidea patches, some of them were reviewed.
Peter Chen (5):
usb: host: delete chipidea dependency
usb: chipidea: udc: Consolidate the calling of ci-driver-disconnect
usb: chipidea: udc: fix the oops when plugs in
Like vbus, the dr_mode and phy_mode are also got from glue layer's
platform data or device node.
Signed-off-by: Peter Chen peter.c...@freescale.com
---
drivers/usb/chipidea/core.c | 19 +--
1 files changed, 9 insertions(+), 10 deletions(-)
diff --git
When we rmmod gadget, the ci-driver needs to be cleared.
Otherwise, when we plug in usb cable again, the driver will
consider gadget is there, and go to enumeration procedure,
but in fact, it was removed.
ci_hdrc ci_hdrc.0: Connected to host
Unable to handle kernel paging request at virtual
Subject: Re: [PATCH 0/2] fs: supply inode uid/gid setting interface
On 2013/8/23 12:10, Greg KH wrote:
On Fri, Aug 23, 2013 at 10:48:36AM +0800, Rui Xiang wrote:
This patchset implements an accessor functions to set uid/gid
in inode struct. Just finish code clean up.
Why?
It can
On 08/27/2013 10:12 AM, Hector Palacios wrote:
On 08/27/2013 10:09 AM, Alexander Shishkin wrote:
Hector Palacios hector.palac...@digi.com writes:
Dear Peter,
On 08/27/2013 04:51 AM, Peter Chen wrote:
On Mon, Aug 26, 2013 at 06:24:48PM +0200, Hector Palacios wrote:
Dear Peter,
On
Hi Dinh,
Any chance anyone has a similar experience with this DWC2 driver, any
help will greatly appreciated. Of course, I will go back and verify the
initialization between the DWC2 and the old driver to see if I can spot
anything.
At first glance, the symptoms (getting transaction errors on
On Tue, Aug 27, 2013 at 4:05 AM, Alan Stern st...@rowland.harvard.edu wrote:
On Mon, 26 Aug 2013, Ming Lei wrote:
The problem is that once an interrupt QH has been unlinked, relinking
it might not make it visible to the hardware until the next frame
starts. Therefore interrupt endpoints
On Tue 2013-08-27 12:22:59, Matthijs Kooijman wrote:
Hi Dinh,
Any chance anyone has a similar experience with this DWC2 driver, any
help will greatly appreciated. Of course, I will go back and verify the
initialization between the DWC2 and the old driver to see if I can spot
anything.
Hello Alan,
On 2013-08-23 21:33, Alan Stern wrote:
Well, I replaced the motherboard by one of the same type and same BIOS
version.
And the problem is still here.
kernel:[ 3013.199945] Disabling IRQ #18
So what can we conclude?
Kernel bug?
Hardware bug?
Something else?
Any of the
Hi!
I was wondering if anyone has come across the problem I am experiencing
with the staging DWC2 driver. The problem is that the driver is failing
to detect a device when connected.
I know that HW works because I have an older version of the driver for
this IP and it seems to work OK,
On Tue, 27 Aug 2013, Ming Lei wrote:
Yes. A new spinlock would be needed to synchronize the top half and
the bottom half. The same spinlock would also be used to avoid
scheduling the tasklet when it is already running, like in your
implementation.
Then every HCD need to copy these
On Tue, 27 Aug 2013, Ming Lei wrote:
I don't understand your argument. The uhci-hcd _does_ support
interrupt URBs being submitted from tasklets, workqueues, kernel
threads, or whatever. The guarantee is that the interrupt URB will be
scheduled right away if the endpoint queue has not
Reset PORT_ENABLE bit of port status on loosing PD.
Signed-off-by: Rupesh Gujare rupesh.guj...@atmel.com
---
drivers/staging/ozwpan/ozhcd.c |2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/drivers/staging/ozwpan/ozhcd.c b/drivers/staging/ozwpan/ozhcd.c
index
Fixes following error caused during unloading driver.
[ 1127.542888] usb 5-1: USB disconnect, device number 2
[ 1127.542909] ozwpan ozwpan: remove, state 1
[ 1127.542933] usb usb5: USB disconnect, device number 1
[ 1127.618634] hub 5-0:1.0: hub_port_status failed (err = -19)
[ 1127.618647]
Return error if we receive write(), while PD is not connected.
Signed-off-by: Rupesh Gujare rupesh.guj...@atmel.com
---
drivers/staging/ozwpan/ozcdev.c |2 ++
1 file changed, 2 insertions(+)
diff --git a/drivers/staging/ozwpan/ozcdev.c b/drivers/staging/ozwpan/ozcdev.c
index
Increase ISOC IN buffer depth to 100 units.
Signed-off-by: Rupesh Gujare rupesh.guj...@atmel.com
---
drivers/staging/ozwpan/ozhcd.c |2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/drivers/staging/ozwpan/ozhcd.c b/drivers/staging/ozwpan/ozhcd.c
index 3548860..b0398c5 100644
On Tue, 27 Aug 2013, Clemens Ladisch wrote:
There is no reasoning about capture endpoints.
The driver cannot control how many samples actually end up in a capture
packet, so it is possible that URBs end up being one USB frame longer
than a period, in which case the ALSA period interrupts
On 08/27/13 10:14, Mike Turquette wrote:
Quoting Tomasz Figa (2013-08-20 17:33:21)
This patch modifies PLL6552 and PLL6553 clock drivers to use recently
added common Samsung PLL registration method.
Signed-off-by: Tomasz Figatomasz.f...@gmail.com
Sigh. This change won't apply on top of
On Mon, 26 Aug 2013, Kevin Archer wrote:
I think the link in my first email was wrong
here is the correct link
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1210858
I did run 2.6.33 and 2.6.39 in which the 2 usb ports did appear to
work, but the Xserver did not work correctly so I
Hello.
On 08/27/2013 07:53 PM, Rupesh Gujare wrote:
Return error if we receive write(), while PD is not connected.
Signed-off-by: Rupesh Gujare rupesh.guj...@atmel.com
---
drivers/staging/ozwpan/ozcdev.c |2 ++
1 file changed, 2 insertions(+)
diff --git
On Tue, 27 Aug 2013, Udo van den Heuvel wrote:
Hello Alan,
On 2013-08-23 21:33, Alan Stern wrote:
Well, I replaced the motherboard by one of the same type and same BIOS
version.
And the problem is still here.
kernel:[ 3013.199945] Disabling IRQ #18
So what can we conclude?
On Tue, 27 Aug 2013, Jürgen Liebmann wrote:
Alan, sorry your mail was redirect in the recycle folder of my email account
and I read this at first today.
Please can you help me, how I can get this both kernels without doing a new
bisect?
The results of bisect I'd already delete. I'm
On Tue, 27 Aug 2013, Adam Borowski wrote:
What happens if go back to a kernel without that commit and enable
CONFIG_USB_SUSPEND? The behavior should be identical -- basically the
commit is supposed to have the effect of always assuming that
CONFIG_USB_SUSPEND has the same value as
From: Mathias Nyman mathias.ny...@linux.intel.com
Wrong capability bit was checked for best effort service latency.
bit 20 indicate port is BESL LPM capable (BLC),
bit 19 is hardware LPM capable (HLC)
This patch should be backported to kernels as old as 3.11, that
contain the commit
From: Shawn Nematbakhsh sha...@chromium.org
If a USB controller with XHCI_RESET_ON_RESUME goes to runtime suspend,
a reset will be performed upon runtime resume. Any previously suspended
devices attached to the controller will be re-enumerated at this time.
This will cause problems, for example,
From: Dmitry Kasatkin d.kasat...@samsung.com
When debug is not enabled and dev_dbg() will expand to nothing,
log might be flooded with callbacks suppressed. If it was not
done on purpose, better to use dev_dbg_ratelimited() instead.
Signed-off-by: Dmitry Kasatkin d.kasat...@samsung.com
On Fri, Aug 23, 2013 at 04:34:43PM -0700, Greg Kroah-Hartman wrote:
From: Greg Kroah-Hartman gre...@linuxfoundation.org
Convert all USB gadget sysfs attributes to use the _RO or _RW variants,
to make them easier to audit and ensure that the permissions are
correct.
Note, two are left
On Tue, Aug 13, 2013 at 02:11:27PM +0530, Tushar Behera wrote:
On 12 July 2013 12:27, Felipe Balbi ba...@ti.com wrote:
Hi,
On Wed, Jul 10, 2013 at 10:42:27AM -0700, Julius Werner wrote:
Hi Felipe,
This is intended to pull down a reset signal line, not to switch power
to the device.
On Wed, Aug 14, 2013 at 12:28:17PM +0300, Ivan T. Ivanov wrote:
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
Hi,
On Tue, Aug 13, 2013 at 02:34:10PM +0100, Mark Rutland wrote:
On Mon, Aug 12, 2013 at 07:05:53PM +0100, Felipe Balbi wrote:
On Fri, Aug 09, 2013 at 01:42:15PM -0500, Kumar Gala wrote:
On Aug 9, 2013, at 11:28 AM, Mark Rutland wrote:
On Fri, Aug 09, 2013 at 04:40:32PM +0100,
On Thu, Aug 15, 2013 at 01:40:01AM +0300, Philippe De Swert wrote:
Hi,
On 12/08/13 21:08, Felipe Balbi wrote:
On Fri, Aug 09, 2013 at 09:23:08PM +0300, Philippe De Swert wrote:
Some bad gadget drivers do not check the return status of usb_add_config.
fix the gadget driver
As stated in
On Tue, Aug 27, 2013 at 04:53:40PM +0100, Rupesh Gujare wrote:
Increase ISOC IN buffer depth to 100 units.
This change log is not useful. What are the user visible effects of
this bug?
regards,
dan carpenter
--
To unsubscribe from this list: send the line unsubscribe linux-usb in
the body
Hi,
On Fri, Aug 16, 2013 at 03:21:07PM +0800, Huang Rui wrote:
Hi Felipe,
USB transceivers should be selected when platform glues are enabled.
Because it need initialize usb phy platform device for binding related
phy driver when gules are probing.
Patch 1 and patch 2 add NOP USB
Hi,
On Mon, Aug 26, 2013 at 01:44:49PM +0530, Kishon Vijay Abraham I wrote:
On Wednesday 21 August 2013 11:16 AM, 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
On Mon, Aug 19, 2013 at 09:24:01AM +0800, Peter Chen wrote:
On Sun, Aug 18, 2013 at 10:20:44PM +0200, Geert Uytterhoeven wrote:
If NO_DMA=y:
drivers/built-in.o: In function `dma_set_coherent_mask':
include/linux/dma-mapping.h:93: undefined reference to `dma_supported'
Signed-off-by:
Hello.
On 08/12/2013 12:20 AM, Sergei Shtylyov wrote:
After commit 09fc7d22b024692b2fe8a943b246de1af307132b (usb: musb: fix incorrect
usage of resource pointer), CPPI DMA driver on DaVinci DM6467 can't detect its
dedicated IRQ and so the MUSB IRQ is erroneously used instead. This is because
On Tue, Aug 27, 2013 at 9:16 PM, Felipe Balbi ba...@ti.com wrote:
On Mon, Aug 19, 2013 at 09:24:01AM +0800, Peter Chen wrote:
On Sun, Aug 18, 2013 at 10:20:44PM +0200, Geert Uytterhoeven wrote:
If NO_DMA=y:
drivers/built-in.o: In function `dma_set_coherent_mask':
Hi,
On Thu, Aug 22, 2013 at 09:24:49PM +, Paul Zimmerman wrote:
From: Ivan T. Ivanov [mailto:iiva...@mm-sol.com]
Sent: Tuesday, August 20, 2013 8:26 AM
On Tue, 2013-08-20 at 10:01 -0500, Kumar Gala wrote:
On Aug 20, 2013, at 9:54 AM, Ivan T. Ivanov wrote:
Hi,
On
On Tue, Aug 27, 2013 at 01:28:41PM -0500, Felipe Balbi wrote:
On Fri, Aug 23, 2013 at 04:34:43PM -0700, Greg Kroah-Hartman wrote:
From: Greg Kroah-Hartman gre...@linuxfoundation.org
Convert all USB gadget sysfs attributes to use the _RO or _RW variants,
to make them easier to audit and
On Tue, Aug 27, 2013 at 11:26:55AM -0700, Sarah Sharp wrote:
The following changes since commit 154547c4fe0fbe92185e69a6cdc2b0502b361995:
USB: serial: clean up attribute permissions (2013-08-25 15:12:03 -0700)
are available in the git repository at:
On Tue, Aug 27, 2013 at 11:23:43PM +0400, Sergei Shtylyov wrote:
Hello.
On 08/12/2013 12:20 AM, Sergei Shtylyov wrote:
After commit 09fc7d22b024692b2fe8a943b246de1af307132b (usb: musb: fix
incorrect
usage of resource pointer), CPPI DMA driver on DaVinci DM6467 can't detect
its
On Tue, 27 Aug 2013, Clemens Ladisch wrote:
Alan Stern wrote:
On Tue, 27 Aug 2013, Clemens Ladisch wrote:
The current algorithm uses very short capture URBs to ensure that _some_
URB is completed as soon as possible after a period ends.
[...]
I'd suggest to keep the old calculation for
Alan Stern wrote:
On Tue, 27 Aug 2013, Clemens Ladisch wrote:
The current algorithm uses very short capture URBs to ensure that _some_
URB is completed as soon as possible after a period ends.
[...]
I'd suggest to keep the old calculation for capture URBs. It would
make sense to use longer
On Wed, Aug 21, 2013 at 11:38:21AM +0300, Dan Carpenter wrote:
We need to unlock and enable IRQs before returning on error.
Signed-off-by: Dan Carpenter dan.carpen...@oracle.com
doesn't apply
--
balbi
signature.asc
Description: Digital signature
Hi Greg,
As promissed, here's a set of important fixes for
the first v3.12-rc release. If you want me to change
anything, just let me know.
The following changes since commit 154547c4fe0fbe92185e69a6cdc2b0502b361995:
USB: serial: clean up attribute permissions (2013-08-25 15:12:03 -0700)
are
*Ping!*
Are there still unanswered concerns left with this patch? I hope my
prior mails could clear up why I think that the PMU register
description in the device tree for a specific PHY is represents the
hardware more accurately after my patch, and my analysis of the
Exynos4 situation currently
On 08/28/2013 12:06 AM, Felipe Balbi wrote:
After commit 09fc7d22b024692b2fe8a943b246de1af307132b (usb: musb: fix incorrect
usage of resource pointer), CPPI DMA driver on DaVinci DM6467 can't detect its
dedicated IRQ and so the MUSB IRQ is erroneously used instead. This is because
only 2
On Tue, Aug 27, 2013 at 03:16:05PM -0500, Felipe Balbi wrote:
Hi Greg,
As promissed, here's a set of important fixes for
the first v3.12-rc release. If you want me to change
anything, just let me know.
The following changes since commit 154547c4fe0fbe92185e69a6cdc2b0502b361995:
USB:
On Tue, 2013-08-27 at 14:13 +0200, ZY - pavel wrote:
On Tue 2013-08-27 12:22:59, Matthijs Kooijman wrote:
Hi Dinh,
Any chance anyone has a similar experience with this DWC2 driver, any
help will greatly appreciated. Of course, I will go back and verify the
initialization between the
These two patches fix some minor issues in the dummy_hcd driver. Both
errors were detected with the help of coverity analysis.
Philippe De Swert (2):
usb:gadget:dummy_hcd : Avoid infinite loop
usb:gadget:dummy_hcd : Detect port and link state correctly to avoid
unreachable code
When an error occurs adding a platform device there is a risk of an infinite
loop.
If more than one platform device was added i will remain = than 0. The
intention seems
to clean up all the different already added platform devices before the failure
occurs,
so fixed the code to actually do so.
Since USB_SS_PORT_LS_U0 is 0x the operation with the port state would
always be 0. Thus the if would never be true. The code tries to check if the
port is enabled and link is active (U0 state). This means the port_status
should be 0x0001, so the right check is an | with USB_SS_PORT_LS_U0.
From: Dinh Nguyen [mailto:dingu...@altera.com]
Sent: Tuesday, August 27, 2013 2:09 PM
On Tue, 2013-08-27 at 14:13 +0200, ZY - pavel wrote:
On Tue 2013-08-27 12:22:59, Matthijs Kooijman wrote:
What hardware are you working with?
Very probably Altera Socfpga Cyclone V board.
Yes,
On Mon, Aug 26, 2013 at 11:49:15AM -0400, Alan Stern wrote:
David and Paul:
Here's a question that doesn't seem to be answered in
Documentation/memory-barriers.txt. Are memory accesses within an
interrupt handler synchronized with respect to interrupts?
In more detail, suppose we have
On Mon, Aug 26, 2013 at 03:01:40PM -0400, Alan Stern wrote:
Since ohci-hcd supports runtime PM, the .pm field in its pci_driver
structure should be protected by CONFIG_PM rather than
CONFIG_PM_SLEEP.
Without this change, OHCI controllers won't do runtime suspend if
system suspend or
69 matches
Mail list logo
