Since we introduce -EPROBE_DEFER for udc driver, it will be
probed at late_initcall if it is defered. When the gadget
is built in, it will return couldn't find an available UDC
at such case. That's the problem we met at below link:
http://marc.info/?l=linux-usbm=137706435611447w=2
We have no
From: Wei Yongjun yongjun_...@trendmicro.com.cn
Using list_move_tail() instead of list_del() + list_add_tail().
Signed-off-by: Wei Yongjun yongjun_...@trendmicro.com.cn
---
drivers/usb/wusbcore/wa-xfer.c | 6 ++
1 file changed, 2 insertions(+), 4 deletions(-)
diff --git
On Monday, September 23, 2013 12:38 PM, Vivek Gautam wrote:
This delay got introduced in:
7415f17 usb: dwc3: core: add power management support
which reflected similar code in dwc3_core_soft_reset() function.
However, originally the delay of 100ms in dwc3_core_soft_reset() was
meant to
This patch adds isochronous transfer support. It adds few modifications:
- Modify s3c_hsotg_write_fifo() function. It actually calculates transfer
size, taking into account Multi Count value, which indicates number of
transactions per microframe.
- Fix s3c_hsotg_start_req() function by setting
Hello,
There is my initial proposal for isochronous transfers support in s3c-hsotg
driver.
This patch does few modifications:
- Fix few functions to make them usable in isochronous transfers handling.
- Add few fields to s3c_hsotg_ep structure, used for isochronous ep handling.
- Add isochronous
Am 22.09.2013 22:36, schrieb Marc MERLIN:
On Sun, Sep 22, 2013 at 04:32:08PM -0400, Alan Stern wrote:
I'm somehow thinking there is a driver or hardware problem when the device
does get stuck in a mode where it won't sleep properly again until the next
reboot (just unloading/loading the driver
Hi,
On 09/23/2013 07:26 AM, Kumar Gaurav wrote:
Hi Alan,
I have one question just for knowledge. I was looking for the reason of this
bug but wasn't even able to identify which driver (ehci,xhci etc) these
devices are using. I tried inspecting with my USB mouse and found out it was
ehci
On Thu, Sep 19, 2013 at 04:11:57PM +0200, Dominik Paulus wrote:
+int usbip_init_crypto(struct usbip_device *ud, unsigned char *sendkey,
unsigned
+ char *recvkey)
+{
+ int ret;
+
+ ud-use_crypto = 1;
+
+ ud-tfm_recv = crypto_alloc_aead(gcm(aes), 0, 0);
+ if
On Thu, Sep 19, 2013 at 04:11:57PM +0200, Dominik Paulus wrote:
+int usbip_init_crypto(struct usbip_device *ud, unsigned char *sendkey,
unsigned
+ char *recvkey)
+{
+ int ret;
+
+ ud-use_crypto = 1;
+
+ ud-tfm_recv = crypto_alloc_aead(gcm(aes), 0, 0);
+ if
On Mon, Sep 23, 2013 at 07:53:11AM +0200, Daniel Mack wrote:
On 23.09.2013 06:09, Vinod Koul wrote:
On Sun, Sep 22, 2013 at 04:50:04PM +0200, Daniel Mack wrote:
+#ifdef CONFIG_PM_SLEEP
a
+static int cppi41_suspend(struct device *dev)
+{
+ struct cppi41_dd *cdd =
On Sun, Sep 22, 2013 at 04:50:04PM +0200, Daniel Mack wrote:
This patch adds support for suspend/resume functionality to the cppi41
DMA driver. The steps necessary to make the system resume properly were
figured out by trial-and-error. The code as it stands now is the
minimum that has to be
On Thu, Sep 19, 2013 at 04:11:57PM +0200, Dominik Paulus wrote:
+/*
+ * Perform encryption/decryption on one chunk of data.
+ * Uses global crypto state stored in usbip_device.
+ * Parameters:
+ * encrypt: 1 to perform encryption, 0 to perform decryption operation
Make this a define:
#define
On Thu, Sep 19, 2013 at 10:48:01PM +0100, Russell King wrote:
The DMA API requires drivers to call the appropriate dma_set_mask()
functions before doing any DMA mapping. Add this required call to
the AMBA PL08x driver.
Signed-off-by: Russell King rmk+ker...@arm.linux.org.uk
Acked-by: Vinod
On Fri, Sep 20, 2013 at 12:15:39AM +0100, Russell King wrote:
register_platform_device_full() can setup the DMA mask provided the
appropriate member is set in struct platform_device_info. So lets
make that be the case. This avoids a direct reference to the DMA
masks by this driver.
On Sat, Sep 21, 2013 at 09:00:00PM +0100, Russell King - ARM Linux wrote:
On Fri, Sep 20, 2013 at 07:26:27PM +0200, Heiko Stübner wrote:
Am Donnerstag, 19. September 2013, 23:49:01 schrieb Russell King:
The DMA API requires drivers to call the appropriate dma_set_mask()
functions before
Hi Alan,
On 09/23/2013 04:28 AM, Alan Stern wrote:
On Sun, 22 Sep 2013, Kurt Garloff wrote:
Well, this seems to be a question of terminology, no?
I saw the endpoint byte as consisting of endpoint index plus the direction
bit.
See the entry for Endpoint Address in Chapter 2 (Terms and
Commit 638c5115a7949(USBNET: support DMA SG) introduces DMA SG
if the usb host controller is capable of building packet from
discontinuous buffers, but missed handling padding packet when
building DMA SG.
This patch attachs the pre-allocated padding packet at the
end of the sg list, so padding
Hi Felipe,
On 09/18/2013 03:49 PM, Roger Quadros wrote:
usb_otg_ss_refclk960m is an optional functional clock to the
UBS_OTG_SS module. So manage it in the driver.
Just realized that usb_otg_ss_refclk960m is in fact functional clock to the
PHY and not USB_OTG_SS module. The name is
When transfer type is isochronous, the other bits (bits 5..2) of bmAttributes in
endpoint descriptor might not be set zero. So it's better to mask bmAttributes
with USB_ENDPOINT_XFERTYPE_MASK to judge the transfter type later.
Signed-off-by: Huang Rui ray.hu...@amd.com
---
Hi Robert,
On Monday, September 23, 2013 10:07:12 AM Robert Baldyga wrote:
This patch adds isochronous transfer support. It adds few modifications:
- Modify s3c_hsotg_write_fifo() function. It actually calculates transfer
size, taking into account Multi Count value, which indicates number
On Mon, 23 Sep 2013, Kumar Gaurav wrote:
Hi Alan,
I have one question just for knowledge. I was looking for the reason of
this bug but wasn't even able to identify which driver (ehci,xhci etc)
these devices are using. I tried inspecting with my USB mouse and found
out it was ehci (i
Move probe out of __init section and don't use platform_driver_probe
which cannot be used with deferred probing.
Since commit e9354576 (gpiolib: Defer failed gpio requests by default)
this driver might return -EPROBE_DEFER if a gpio_request fails.
Cc: David Woodhouse dw...@infradead.org
Cc: Josh
Deferred probing cannot be used with platform_driver_probe as by the
time probing is retried either the driver has been unregistered or its
probe function has been set to platform_drv_probe_fail.
With commit e9354576 (gpiolib: Defer failed gpio requests by default)
the gpio subsystem started
On Mon, 23 Sep 2013, Kurt Garloff wrote:
that qualifies as a bug or not. Maybe it should not claim to be a
HID device then?
Maybe not. This particular combination of bRequestType and bRequest
values (0x22, 0x09) is not defined in the HID 1.11 spec. Do you know
if it is defined
Move probe out of __init section and don't use platform_driver_probe
which cannot be used with deferred probing.
Since commit e9354576 (gpiolib: Defer failed gpio requests by default)
this driver might return -EPROBE_DEFER if the mmc_gpio_request_cd fails.
Cc: Nicolas Pitre n...@fluxnic.net
Cc:
Move probe out of __init section and don't use platform_driver_probe
which cannot be used with deferred probing.
Since commit e9354576 (gpiolib: Defer failed gpio requests by default)
and 04bf3011 (regulator: Support driver probe deferral) this driver
might return -EPROBE_DEFER if a gpio_request
Move probe out of __init section and don't use platform_driver_probe
which cannot be used with deferred probing.
Since commit e9354576 (gpiolib: Defer failed gpio requests by default)
this driver might return -EPROBE_DEFER if a gpio_request fails.
Cc: Jean-Christophe PLAGNIOL-VILLARD
Move probe out of __init section and don't use platform_driver_probe
which cannot be used with deferred probing.
Since commit e9354576 (gpiolib: Defer failed gpio requests by default)
this driver might return -EPROBE_DEFER if a gpio_request fails.
Cc: Eric Miao eric.y.m...@gmail.com
Cc: Russell
Move probe out of __init section and don't use platform_driver_probe
which cannot be used with deferred probing.
Since commit e9354576 (gpiolib: Defer failed gpio requests by default)
this driver might return -EPROBE_DEFER if a gpio_request fails.
Cc: Richard Purdie rpur...@rpsys.net
Cc: Jingoo
Prevent drivers relying on platform_driver_probe from requesting
deferred probing in order to avoid further futile probe attempts (either
the driver has been unregistered or its probe function has been set to
platform_drv_probe_fail when probing is retried).
Note that several platform drivers
On Mon, 23 Sep 2013, Huang Rui wrote:
When transfer type is isochronous, the other bits (bits 5..2) of bmAttributes
in
endpoint descriptor might not be set zero. So it's better to mask bmAttributes
with USB_ENDPOINT_XFERTYPE_MASK to judge the transfter type later.
Signed-off-by: Huang Rui
On 09/23/2013 06:17 AM, Vinod Koul wrote:
Looks fine, Sebastian cna you test it pls
Just noticed that you already applied some of them. I just got back
after a few weeks of. Will review test as soon as I get to it.
~Vinod
Sebastian
--
To unsubscribe from this list: send the line
On 09/20/2013 05:45 PM, Felipe Balbi wrote:
Acked-by: Felipe Balbi ba...@ti.com
Those four patches went already in, for instance:
commit 781f17983015dae33324e34d1bb831e715fa04d4
Author: Sebastian Andrzej Siewior bige...@linutronix.de
AuthorDate: Tue Aug 20 18:35:49 2013 +0200
Commit:
On Fri, 20 Sep 2013, Mehresh Ramneek-B31383 wrote:
From: Alan Stern [mailto:st...@rowland.harvard.edu]
Sent: Thursday, September 19, 2013 7:03 PM
To: Mehresh Ramneek-B31383
Cc: linux-usb@vger.kernel.org
Subject: Re: [PATCH]fsl/usb: Workarourd for USB erratum-A005697
On Thu, 19 Sep 2013,
On Mon, Sep 23, 2013 at 04:27:25PM +0200, Johan Hovold wrote:
Deferred probing cannot be used with platform_driver_probe as by the
time probing is retried either the driver has been unregistered or its
probe function has been set to platform_drv_probe_fail.
With commit e9354576 (gpiolib:
On Mon, Sep 23, 2013 at 10:32:30AM -0400, Alan Stern wrote:
On Mon, 23 Sep 2013, Huang Rui wrote:
When transfer type is isochronous, the other bits (bits 5..2) of
bmAttributes in
endpoint descriptor might not be set zero. So it's better to mask
bmAttributes
with
On Mon, Sep 23, 2013 at 04:50:29PM +0200, Sascha Hauer wrote:
On Mon, Sep 23, 2013 at 04:27:25PM +0200, Johan Hovold wrote:
Deferred probing cannot be used with platform_driver_probe as by the
time probing is retried either the driver has been unregistered or its
probe function has been set
On Mon, Sep 23, 2013 at 05:20:18PM +0200, Johan Hovold wrote:
On Mon, Sep 23, 2013 at 04:50:29PM +0200, Sascha Hauer wrote:
On Mon, Sep 23, 2013 at 04:27:25PM +0200, Johan Hovold wrote:
Deferred probing cannot be used with platform_driver_probe as by the
time probing is retried either the
When transfer type is isochronous, the other bits (bits 5..2) of
bmAttributes in endpoint descriptor might not be set zero. So it's better
to use usb_endpoint_type routine to mask bmAttributes with
USB_ENDPOINT_XFERTYPE_MASK to judge the transfter type later.
Signed-off-by: Huang Rui
On 23/09/2013 16:27, Johan Hovold :
Move probe out of __init section and don't use platform_driver_probe
which cannot be used with deferred probing.
Since commit e9354576 (gpiolib: Defer failed gpio requests by default)
this driver might return -EPROBE_DEFER if a gpio_request fails.
Cc:
It looks like your system did not load the ohci-pci driver. Is
CONFIG_USB_OHCI_HCD_PCI enabled?
Thanks my problem was there. As I do not have PCI card (Peripheral
Component Interconnect) I had not enabled this option thinking I didn't
need that...
Thank you very much for your help and for
Thanks Florian. I was waiting for after the 3.12 merge window to close
to send Greg bug fixes. I'm queuing this up for test today, and will
send it out once it passes.
Sarah Sharp
On Sun, Sep 22, 2013 at 09:09:54PM +0200, Florian Wolter wrote:
Hi Sarah,
the described Problem also exisits
On Tue, 24 Sep 2013, Huang Rui wrote:
When transfer type is isochronous, the other bits (bits 5..2) of
bmAttributes in endpoint descriptor might not be set zero. So it's better
to use usb_endpoint_type routine to mask bmAttributes with
USB_ENDPOINT_XFERTYPE_MASK to judge the transfter type
The following changes since commit 272b98c6455f00884f0350f775c5342358ebb73f:
Linux 3.12-rc1 (2013-09-16 16:17:51 -0400)
are available in the git repository at:
git://git.kernel.org/pub/scm/linux/kernel/git/gregkh/usb.git/
tags/usb-3.12-rc2
for you to fetch changes up to
On Mon, 16 Sep 2013, Huang Rui wrote:
Hi Greg, Sarah, Alan,
The following patches are required to resolve remote wake issues with
certain devices.
Issue description:
If the remote wake is issued from the device in a specific timing
condition while the system is entering sleep state then
On 09/23/2013 07:45 PM, Sarah Sharp wrote:
On Fri, Sep 20, 2013 at 07:45:53PM +0300, Xenia Ragiadakou wrote:
The function pci_write_config_dword() sets the appropriate byteordering
internally so the value argument should not be converted to little-endian.
This bug was found by sparse.
Can you
Hi Felipe,
There is an issue with this patch and is shown below.
I will send a v3 for this.
On 08/15/2013 01:18 PM, Roger Quadros wrote:
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.
* Pali Rohár pali.ro...@gmail.com [130920 12:29]:
On Sunday 08 September 2013 10:50:39 Pali Rohár wrote:
This patch will register bq24150a charger in RX-51 board data.
Patch also adding platform function between isp1704 and
bq2415x drivers for detecting charger type.
So finally
I've been getting this on several recent kernel revisions. Is it
interesting? If so, I'm happy to help diagnose it. If not, can the
message be killed or severely ratelimited? I'm getting so much of
this that it tends to overflow the log ring.
[ 287.344991] ehci-pci :00:1d.0: power state
On Mon, Sep 23, 2013 at 02:27:39PM -0400, Alan Stern wrote:
On Thu, 19 Sep 2013, Russell King wrote:
The correct way for a driver to specify the coherent DMA mask is
not to directly access the field in the struct device, but to use
dma_set_coherent_mask(). Only arch and bus code should
On Mon, 23 Sep 2013, Andy Lutomirski wrote:
I've been getting this on several recent kernel revisions. Is it
interesting? If so, I'm happy to help diagnose it. If not, can the
message be killed or severely ratelimited? I'm getting so much of
this that it tends to overflow the log ring.
Hi,
I had a lot of USB errors on i.mx28. I could reproduce it most easily
with USB-serial adapters, and USB modems (CDC and WWAN drivers). If I
sent some data to the TTY port with the echo command in a loop (so
basically open the port, send data, and close the port), all of the
devices were
mainline commit b0d7ffd44ba9cd2dfbf299674418193a5f9ed21a
We cannot request an IRQ with spinlocks held
as that would trigger a sleeping inside
spinlock warning.
Cc: sta...@vger.kernel.org # v3.10 v3.11
Reported-by: Stephen Boyd sb...@codeaurora.org
Signed-off-by: Felipe Balbi ba...@ti.com
---
Hi,
On Thu, Sep 05, 2013 at 08:07:11PM -0400, Behan Webster wrote:
Replying to my patch email just in case it was missed before.
I remember there was a discussion of not dropping variable length array
support, wasn't there ?
--
balbi
signature.asc
Description: Digital signature
Hi,
On Tue, Aug 20, 2013 at 12:56:03PM +0300, Ivan T. Ivanov wrote:
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
Hi,
On Wed, Aug 21, 2013 at 04:29:45PM +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
Hi,
On Wed, Aug 21, 2013 at 04:29:44PM +0300, Ivan T. Ivanov wrote:
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
On Mon, Aug 26, 2013 at 06:08:33PM +0300, Roger Quadros wrote:
Split USB2 PHY and USB3 PHY into separate omap-control-usb
nodes. Get rid of ti,type property.
CC: Benoit Cousson bcous...@baylibre.com
Signed-off-by: Roger Quadros rog...@ti.com
Benoit ? ping here too...
--
balbi
On Mon, 23 Sep 2013, Robert Hodaszi wrote:
Hi,
I had a lot of USB errors on i.mx28. I could reproduce it most easily
with USB-serial adapters, and USB modems (CDC and WWAN drivers). If I
sent some data to the TTY port with the echo command in a loop (so
basically open the port, send
On 09/23/13 14:30, Felipe Balbi wrote:
Hi,
On Thu, Sep 05, 2013 at 08:07:11PM -0400, Behan Webster wrote:
Replying to my patch email just in case it was missed before.
I remember there was a discussion of not dropping variable length array
support, wasn't there ?
There was mostly an objection
On Mon, Sep 23, 2013 at 12:30 PM, Felipe Balbi ba...@ti.com wrote:
I remember there was a discussion of not dropping variable length array
support, wasn't there ?
We should definitely drop it. The feature is an abomination. I thought
gcc only allowed them at the end of structs, in the middle
Hi,
On Mon, Aug 26, 2013 at 06:08:32PM +0300, Roger Quadros wrote:
Split otghs_ctrl and USB2 PHY power down into separate
omap-control-usb nodes. Get rid of ti,type property.
Also get rid of ti,has-mailbox property from usb_otg_hs
node and provide the ctrl-module phandle.
CC: Benoit
On 09/23/13 15:08, Linus Torvalds wrote:
On Mon, Sep 23, 2013 at 12:30 PM, Felipe Balbi ba...@ti.com wrote:
I remember there was a discussion of not dropping variable length array
support, wasn't there ?
We should definitely drop it. The feature is an abomination. I thought
gcc only allowed
Hi,
On Thu, Aug 01, 2013 at 09:35:44PM -0400, beh...@converseincode.com wrote:
From: Behan Webster beh...@converseincode.com
The use of variable length arrays in structs (VLAIS) in the Linux Kernel code
precludes the use of compilers which don't implement VLAIS (for instance the
Clang
On Thu, Sep 19, 2013 at 08:38:23PM +0800, Peter Chen wrote:
On Thu, Sep 19, 2013 at 09:24:15AM +0200, Daniele Forsi wrote:
2013/9/19 Peter Chen:
+ milliseconds to increase successive wakup delays);
there's a typo: s/wakup/wakeup/
Thanks, I think I need check more
Hi,
On Sun, Sep 22, 2013 at 01:43:58AM +0400, 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
On Mon, Sep 23, 2013 at 09:06:54PM +0300, Xenia Ragiadakou wrote:
On 09/23/2013 07:45 PM, Sarah Sharp wrote:
On Fri, Sep 20, 2013 at 07:45:53PM +0300, Xenia Ragiadakou wrote:
The function pci_write_config_dword() sets the appropriate byteordering
internally so the value argument should not be
Hello.
On 09/24/2013 12:42 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
Here is the third version of the microframe scheduler patch. This
version removes the NAK holdoff patch from the series, since it
was effectively a no-op as pointed out by Matthijs. It also splits
out into a separate patch one hunk which was not part of the
downstream patch. It also acknowledges
From: Dom Cobley popcorn...@gmail.com
The transfer scheduler in the dwc2 driver is pretty basic, not to
mention buggy. It works fairly well with just a couple of devices
plugged in, but if you add, say, multiple devices with periodic
endpoints, the scheduler breaks down and can't even enumerate
Hi,
recently I was working on porting EHCI HCD bus glue driver from the
vendors kernel tree to the mainline [1]. I've got the storage (USB
stick and USB external hard drive) working and was happy. However it
does not work completely. Specifically something goes wrong if WiFi
module is talked to.
[+cc Rafael, linux-pm]
On Mon, Sep 23, 2013 at 1:36 PM, Alan Stern st...@rowland.harvard.edu wrote:
On Mon, 23 Sep 2013, Andy Lutomirski wrote:
I've been getting this on several recent kernel revisions. Is it
interesting? If so, I'm happy to help diagnose it. If not, can the
message be
On Mon, Sep 23, 2013 at 3:49 PM, Greg KH g...@kroah.com wrote:
On Mon, Sep 23, 2013 at 09:06:54PM +0300, Xenia Ragiadakou wrote:
On 09/23/2013 07:45 PM, Sarah Sharp wrote:
On Fri, Sep 20, 2013 at 07:45:53PM +0300, Xenia Ragiadakou wrote:
The function pci_write_config_dword() sets the
Hi,
On Mon, Sep 23, 2013 at 02:06:12PM -0700, Greg KH wrote:
On Mon, Sep 23, 2013 at 02:26:29PM -0500, Felipe Balbi wrote:
mainline commit b0d7ffd44ba9cd2dfbf299674418193a5f9ed21a
We cannot request an IRQ with spinlocks held
as that would trigger a sleeping inside
spinlock warning.
On 09/23/2013 01:32 PM, Felipe Balbi wrote:
Hi,
On Wed, Aug 21, 2013 at 04:29:44PM +0300, Ivan T. Ivanov wrote:
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
On 09/23/13 16:24, Felipe Balbi wrote:
Hi,
On Thu, Aug 01, 2013 at 09:35:44PM -0400, beh...@converseincode.com wrote:
From: Behan Webster beh...@converseincode.com
The use of variable length arrays in structs (VLAIS) in the Linux Kernel code
precludes the use of compilers which don't
From: Mark Charlebois charl...@gmail.com
The use of variable length arrays in structs (VLAIS) in the Linux Kernel code
precludes the use of compilers which don't implement VLAIS (for instance the
Clang compiler). This patch removes the use of VLAIS in the gadget driver.
This version has been
On Monday, September 23, 2013 04:28:49 PM Bjorn Helgaas wrote:
[+cc Rafael, linux-pm]
On Mon, Sep 23, 2013 at 1:36 PM, Alan Stern st...@rowland.harvard.edu wrote:
On Mon, 23 Sep 2013, Andy Lutomirski wrote:
I've been getting this on several recent kernel revisions. Is it
interesting?
On 09/23/13 18:53, charl...@gmail.com wrote:
From: Mark Charlebois charl...@gmail.com
The use of variable length arrays in structs (VLAIS) in the Linux Kernel code
precludes the use of compilers which don't implement VLAIS (for instance the
Clang compiler). This patch removes the use of VLAIS
Patch 4 is the only interesting one and adds support for the default
enumeration scheme used by legacy hosts, details in the changelog. The
others are just random cleanup items.
The original discussion for patch 4 can be found here:
http://marc.info/?l=linux-usbm=135906806229309w=2
This is all
Remove a few extra lines and make it clear that all implementations
disable the port by sharing the same line of code.
Cc: Alan Stern st...@rowland.harvard.edu
Signed-off-by: Dan Williams dan.j.willi...@intel.com
---
drivers/usb/core/hub.c | 11 ---
1 files changed, 4 insertions(+), 7
Perform an unconditional toggle of the cycle bit with 'xor'.
Signed-off-by: Dan Williams dan.j.willi...@intel.com
---
drivers/usb/host/xhci-ring.c |2 +-
1 files changed, 1 insertions(+), 1 deletions(-)
diff --git a/drivers/usb/host/xhci-ring.c b/drivers/usb/host/xhci-ring.c
index
Only used for debug output, so we don't need to save it.
Signed-off-by: Dan Williams dan.j.willi...@intel.com
---
drivers/usb/host/xhci.c | 10 ++
drivers/usb/host/xhci.h |2 --
2 files changed, 2 insertions(+), 10 deletions(-)
diff --git a/drivers/usb/host/xhci.c
Change the enumeration scheme for xhci attached devices from:
SetAddress
GetDescriptor(8)
GetDescriptor(18)
...to:
GetDescriptor(64)
SetAddress
GetDescriptor(18)
...as some devices misbehave when encountering a SetAddress command
prior to GetDescriptor. There are known
On Mon, Sep 23, 2013 at 02:23:32PM -0700, Paul Zimmerman wrote:
There were some style-related comments from Dan Carpenter, but I
would prefer to have those as an additional patch, once we have
this known-good code added to the driver.
Sure. Just add a link to the TODO list so we don't
On Mon, Sep 23, 2013 at 12:43:15PM -0400, Alan Stern wrote:
This version of the patch set looks good.
Alan Stern
Looks fine to me as well.
Acked-by: Sarah Sharp sarah.a.sh...@linux.intel.com
--
To unsubscribe from this list: send the line unsubscribe linux-usb in
the body of a message to
Add TODO file for DWC2 driver
Signed-off-by: Paul Zimmerman pa...@synopsys.com
---
Greg, this should be applied after the microframe scheduler patch,
since it assumes that one has already been applied.
drivers/staging/dwc2/TODO | 33 +
1 file changed, 33
On Mon, Sep 23, 2013 at 02:49:07PM -0700, Greg KH wrote:
On Mon, Sep 23, 2013 at 04:38:22PM -0500, Bjorn Helgaas wrote:
On Mon, Sep 23, 2013 at 3:49 PM, Greg KH g...@kroah.com wrote:
On Mon, Sep 23, 2013 at 09:06:54PM +0300, Xenia Ragiadakou wrote:
I had in mind that the pci_ops .read and
Adding Peter and Marek.
On Mon, Sep 23, 2013 at 4:58 PM, Alan Stern st...@rowland.harvard.edu wrote:
On Mon, 23 Sep 2013, Robert Hodaszi wrote:
Hi,
I had a lot of USB errors on i.mx28. I could reproduce it most easily
with USB-serial adapters, and USB modems (CDC and WWAN drivers). If I
On Mon, Sep 23, 2013 at 05:23:07PM -0700, Sarah Sharp wrote:
On Mon, Sep 23, 2013 at 02:49:07PM -0700, Greg KH wrote:
On Mon, Sep 23, 2013 at 04:38:22PM -0500, Bjorn Helgaas wrote:
On Mon, Sep 23, 2013 at 3:49 PM, Greg KH g...@kroah.com wrote:
On Mon, Sep 23, 2013 at 09:06:54PM +0300,
The reason was an mx28 errata: ENGR119653 USB: ARM to USB register
error issue
Peter, does this erratum only affect mx28?
Yes
Freescale issued a patch for 2.6.35 to workaround this problem last
year. I ported this patch. However, it is not totally device tree
compatible. I mean,
Hi Greg,
The this serial includes PHY operation change (move to common
code) and low power mode supported, it is based on:
http://marc.info/?l=linux-usbm=137939293826025w=2.
Peter Chen (3):
usb: chipidea: move PHY operation to core
usb: chipidea: imx: remove PHY operations
usb: chipidea:
Signed-off-by: Peter Chen peter.c...@freescale.com
---
drivers/usb/chipidea/usbmisc_imx.c | 71 +---
1 files changed, 34 insertions(+), 37 deletions(-)
diff --git a/drivers/usb/chipidea/usbmisc_imx.c
b/drivers/usb/chipidea/usbmisc_imx.c
index ac5a461..545efbf
To reflect source file name change
Signed-off-by: Peter Chen peter.c...@freescale.com
---
.../devicetree/bindings/usb/ci13xxx-imx.txt| 31
.../devicetree/bindings/usb/ci_hdrc_imx.txt| 31
This API is used to let the PHY enter/leave low power mode.
Before the controller going to work(at probe/resume), it needs to let
the PHY leave low power mode.
After the controller stopping working(at remove/suspend), it needs to
let the PHY enter low power mode to save power consumption.
PHY operations are common, so move them to core.
Signed-off-by: Peter Chen peter.c...@freescale.com
---
drivers/usb/chipidea/core.c | 57 ++
drivers/usb/chipidea/udc.c | 39 +
2 files changed, 52 insertions(+), 44
Since the PHY operations are moved to core, delete the related
code at glue layer.
Signed-off-by: Peter Chen peter.c...@freescale.com
---
drivers/usb/chipidea/ci_hdrc_imx.c | 21 -
1 files changed, 4 insertions(+), 17 deletions(-)
diff --git
On Tue, Sep 24, 2013 at 12:46:52PM +0800, Peter Chen wrote:
Sorry, sending wrongly, please skip it
--
Best Regards,
Peter Chen
--
To unsubscribe from this list: send the line unsubscribe linux-usb in
the body of a message to majord...@vger.kernel.org
More majordomo info at
On Tue, Sep 24, 2013 at 12:46:53PM +0800, Peter Chen wrote:
Sorry, sending wrongly, please skip it
Signed-off-by: Peter Chen peter.c...@freescale.com
---
drivers/usb/chipidea/usbmisc_imx.c | 71
+---
1 files changed, 34 insertions(+), 37 deletions(-)
99 matches
Mail list logo
