I tried applying this patch on linux-next and it applies well.
i used
git apply --apply
On Saturday 31 August 2013 11:02 PM, Kumar Gaurav wrote:
This patch redefine function xhci_readl. xhci_readl function doesn't use
xhci_hcd argument.
Hence there is no need of keeping it in the function
On Tue, Sep 03, 2013 at 09:52:52AM +0800, Huang Rui wrote:
> On Tue, Sep 03, 2013 at 02:14:14AM +0800, Giovanni wrote:
> > > On Sat, Aug 31, 2013 at 12:11:49AM
> > > +0800, Giovanni wrote:
> > > >
> > >
> > > I drafted a patch, please have a test and enable
> > > CONFIG_XHCI_HCD_DEBUGGING in kern
On Tue, Sep 03, 2013 at 02:14:14AM +0800, Giovanni wrote:
> > On Sat, Aug 31, 2013 at 12:11:49AM
> > +0800, Giovanni wrote:
> > >
> >
> > I drafted a patch, please have a test and enable
> > CONFIG_XHCI_HCD_DEBUGGING in kernel configuration at same
> > time.
> >
> > 8<-- cut
On 09/02/2013 06:07 PM, Greg KH wrote:
On Mon, Sep 02, 2013 at 05:46:58PM -0500, Daniel Santos wrote:
Hello guys. I didn't get a response the last time so hopefully with
3.11 out I'll get one this time.
I need to be able to generate interrupts from a USB device driver while
servicing the compl
The following changes since commit b36f4be3de1b123d8601de062e7dbfc904f305fb:
Linux 3.11-rc6 (2013-08-18 14:36:53 -0700)
are available in the git repository at:
git://git.kernel.org/pub/scm/linux/kernel/git/gregkh/usb.git/
tags/usb-3.12-rc1
for you to fetch changes up to b9a1048137f4ae43ee9
On Mon, Sep 02, 2013 at 05:46:58PM -0500, Daniel Santos wrote:
> Hello guys. I didn't get a response the last time so hopefully with
> 3.11 out I'll get one this time.
>
> I need to be able to generate interrupts from a USB device driver while
> servicing the complete() function of an interrupt
Hello guys. I didn't get a response the last time so hopefully with
3.11 out I'll get one this time.
I need to be able to generate interrupts from a USB device driver while
servicing the complete() function of an interrupt URB. While I realize
that this may seem strange, the purpose is for a
> On Sat, Aug 31, 2013 at 12:11:49AM
> +0800, Giovanni wrote:
> > Hi Rui,
> >
> > >Hi,
> > >
> > >Can you give us a detail kernel top commit and
> config which you built,
> > >in order to locate the break line (address offset)
> accurately like below:
> > >
> > >I built on top v3.10, but it lo
> On Sat, Aug 31, 2013 at 12:11:49AM
> +0800, Giovanni wrote:
> > Hi Rui,
> >
> > >Hi,
> > >
> > >Can you give us a detail kernel top commit and
> config which you built,
> > >in order to locate the break line (address offset)
> accurately like below:
> > >
> > >I built on top v3.10, but it lo
Hello.
On 09/02/2013 05:58 PM, Pavel Machek wrote:
checkpatch.pl has some valid complaints about style in s3c-hsotg.c :
macro with if should be really enclosed in do {} while, and puts is
going to be slightly faster.
Here's suggested patch. I don't have the hardware, so it is completely
unte
According to Prolific, several (unauthorized) cheap and less functional
clones of the PL2303HX chip are in circulation. [1]
I've had the chance to test such a cloned device and it turned out that
it doesn't support any baud rates above 115200 baud (original: 6 Mbaud)
It also doesn't support the div
On Mon, 2013-09-02 at 13:25 +0200, Gerd Hoffmann wrote:
> xhci maintains a radix tree for each stream endpoint because it must
> be able to map a trb address to the stream ring. Each ring segment
> must be added to the ring for this to work. Currently xhci sticks
> only the first segment of each
There can be systems which does not have a external usb_phy, so get
usb_phy only if usb-phy property is added in the case of dt boot or if
platform_data indicates the presence of PHY. Also remove checking if
return value is -ENXIO since it's now changed to always enable usb_phy layer.
Signed-off-b
Adapted dwc3 core to use the Generic PHY Framework. So for init, exit,
power_on and power_off the following APIs are used phy_init(), phy_exit(),
phy_power_on() and phy_power_off().
However using the old USB phy library wont be removed till the PHYs of all
other SoC's using dwc3 core is adapted to
Since now we have a separate folder for phy, move the PHY dt binding
documentation of OMAP to that folder.
Signed-off-by: Kishon Vijay Abraham I
---
.../devicetree/bindings/{usb/usb-phy.txt => phy/omap-phy.txt}|2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
rename Documentation
Adapted omap-usb3 PHY driver to Generic PHY Framework and moved phy-omap-usb3
driver in drivers/usb/phy to drivers/phy and also renamed the file to
phy-omap-pipe3 since this same driver will be used for SATA PHY and
PCIE PHY.
Signed-off-by: Kishon Vijay Abraham I
---
Documentation/devicetree/bin
No functional change. Moved omap_usb.h from linux/usb/ to linux/phy/.
Also removed the unused members of struct omap_usb (after phy-omap-pipe3
started using it's own header file)
Signed-off-by: Kishon Vijay Abraham I
---
drivers/phy/phy-omap-usb2.c |2 +-
drivers/usb/phy/phy-twl603
Signed-off-by: Kishon Vijay Abraham I
---
arch/arm/boot/dts/omap5.dtsi |5 -
1 file changed, 4 insertions(+), 1 deletion(-)
diff --git a/arch/arm/boot/dts/omap5.dtsi b/arch/arm/boot/dts/omap5.dtsi
index 94abef5..9fe71ff 100644
--- a/arch/arm/boot/dts/omap5.dtsi
+++ b/arch/arm/boot/dts/om
renamed struct omap_control_usb to struct omap_control_phy since it can
be used to control PHY of USB, SATA and PCIE. Also moved the driver and
include files under *phy* and made the corresponding changes in the users
of phy-omap-control.
Signed-off-by: Kishon Vijay Abraham I
---
drivers/phy/Kco
Modified dwc3 core to find PHYs only if the platform indicates that it has
to use a PHY. Adapted DWC3 and USB3 PHY to use Generic PHY framework. Also
changed the name of USB3 PHY driver to PIPE3 PHY driver since the same driver
has to be used for SATA and PCIE too.
This series also includes a bunc
On Mon, 2 Sep 2013, Bjørn Mork wrote:
> Thanks for the pointer. I see that there are quite a number of attempts
> (2 * 2 * 4) to read the device descriptor using the default 5 second
> control message timeout, which accounts for most of the 82.5 second
> delay.
>
> The number of repetitions of a
Alan Stern writes:
> On Sun, 1 Sep 2013, Bjørn Mork wrote:
>
>> Sep 1 12:32:39 nemi kernel: [174042.120072] usb 1-6: device descriptor
>> read/64, error -110
>> Sep 1 12:32:39 nemi kernel: [174057.336066] usb 1-6: device descriptor
>> read/64, error -110
>> Sep 1 12:32:39 nemi kernel: [174057
Hi!
checkpatch.pl has some valid complaints about style in s3c-hsotg.c :
macro with if should be really enclosed in do {} while, and puts is
going to be slightly faster.
Here's suggested patch. I don't have the hardware, so it is completely
untested.
Signed-off-by: Pavel Machek,
diff --git a/d
On Monday 02 September 2013 13:59:52 Jürgen Liebmann wrote:
> Hi Laurent, in the attachment you find the output of lsusb.
Thank you. I've updated the supported devices list on the uvcvideo driver's
web page.
--
Regards,
Laurent Pinchart
--
To unsubscribe from this list: send the line "unsubsc
Hi Laurent, in the attachment you find the output of lsusb.
Regards, Jürgen
Am 02.09.2013 12:23, schrieb Laurent Pinchart:
Hi Jürgen,
On Monday 02 September 2013 11:45:33 Jürgen Liebmann wrote:
Laurent, please forget my last question. I have found a solution by myself.
I created a file /etc/m
On 26 August 2013 16:49, Alan Stern wrote:
> 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 an interrupt handler that uses a m
On Fr, 2013-08-30 at 09:48 -0700, Sarah Sharp wrote:
> Hi Gerd,
>
> Thanks for catching this! I have a UAS device now, but won't have time
> to test it for a week or so.
>
> Can you please Cc me on patches to the xHCI driver in the future?
> Otherwise it gets lost in the other linux-usb mailing
This patch prepares for the addition of another list and renames the
work list lock and the list_head field in struct uas_cmd_info.
Signed-off-by: Gerd Hoffmann
---
drivers/usb/storage/uas.c | 50 +++
1 file changed, 25 insertions(+), 25 deletions(-)
xhci maintains a radix tree for each stream endpoint because it must
be able to map a trb address to the stream ring. Each ring segment
must be added to the ring for this to work. Currently xhci sticks
only the first segment of each stream ring into the radix tree.
Result is that things work ini
This patch adds a new list where all requests which are canceled are
added to, so we don't loose them. Then, after killing all inflight
urbs on bus reset (and disconnect) we'll walk over the list and clean
them up.
Without this we can end up with aborted requests lingering around in
case of statu
xhci streams support is fixed, unblock usb attached scsi.
Signed-off-by: Gerd Hoffmann
---
drivers/usb/storage/Kconfig | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/drivers/usb/storage/Kconfig b/drivers/usb/storage/Kconfig
index 8470e1b..4761a28 100644
--- a/drivers/usb/sto
Signed-off-by: Gerd Hoffmann
---
drivers/usb/storage/uas.c | 6 ++
1 file changed, 6 insertions(+)
diff --git a/drivers/usb/storage/uas.c b/drivers/usb/storage/uas.c
index d966b59..f89202f 100644
--- a/drivers/usb/storage/uas.c
+++ b/drivers/usb/storage/uas.c
@@ -85,6 +85,8 @@ static int uas
Hi,
This patch series enables uas support in the linux kernel. First patch
fixes usb3 streams support in xhci, patches 2-4 improve uas error
handling and patch 5 removes BROKEN from the uas kernel config.
cheers,
Gerd
Gerd Hoffmann (5):
xhci: fix usb3 streams
uas: properly reinitialize
Hi Jürgen,
On Monday 02 September 2013 11:45:33 Jürgen Liebmann wrote:
> Laurent, please forget my last question. I have found a solution by myself.
> I created a file /etc/modprobe.d/uvcvideo.conf with this content:
>
> options uvcvideo quirks=0x100
>
> Now the webcam workes porperly.
> What a
They are only called by '__ref' function multi_bind(), and they will
call '__init' functions, so recommend to let them '__ref' too.
The related warnings:
WARNING: drivers/usb/gadget/g_multi.o(.text+0xded6): Section mismatch in
reference from the variable .LM2921 to the variable .init.text:_rnd
Laurent, please forget my last question. I have found a solution by myself.
I created a file /etc/modprobe.d/uvcvideo.conf with this content:
options uvcvideo quirks=0x100
Now the webcam workes porperly.
What a simple solution, but what a long way to here!
See the history here:
https://bugs.lau
On Sat, Aug 31, 2013 at 12:11:49AM +0800, Giovanni wrote:
> Hi Rui,
>
> >Hi,
> >
> >Can you give us a detail kernel top commit and config which you built,
> >in order to locate the break line (address offset) accurately like below:
> >
> >I built on top v3.10, but it looks like line 1399 isn't
Hi Michael,
On 08/30/2013 08:59 PM, Michael Trimarchi wrote:
> Hi Roger
>
> On Thu, Jul 4, 2013 at 10:53 AM, Michael Trimarchi
> wrote:
>> Hi
>>
>> On 07/02/2013 05:03 PM, Roger Quadros wrote:
>>>
>>> On 07/02/2013 05:49 PM, Michael Trimarchi wrote:
Hi Roger
On 07/02/2013 04:42 PM
38 matches
Mail list logo
