On Wed, Jul 23, 2014 at 05:37:43PM -0700, Linus Torvalds wrote:
> On Wed, Jul 23, 2014 at 2:53 AM, Borislav Petkov wrote:
> >
> > Well, it looks like we f*cked up something after -rc5 since I'm starting
> > to see lockdep splats all over the place which I didn't see before. I'm
> > running rc6 + t
On Thu, Jul 24, 2014 at 04:30:21PM +1000, ress...@ausics.net wrote:
> On 2014-07-23 10:14, Greg KH wrote:
> >On Wed, Jul 23, 2014 at 10:05:23AM +1000, ress...@ausics.net wrote:
> >>Hi,
> >>I am not familiar with git or code writting, I have no idea where to
> >>start.
> >
> >You installed your own
On 2014-07-23 10:14, Greg KH wrote:
On Wed, Jul 23, 2014 at 10:05:23AM +1000, ress...@ausics.net wrote:
Hi,
I am not familiar with git or code writting, I have no idea where to
start.
You installed your own kernels from kernel.org, right?
FTP'd the gz file, I extract, copy .config from pr
On Thu, Jul 24, 2014 at 10:06 AM, Greg KH wrote:
>> This reverts commit a9232076374334ca2bc2a448dfde96d38a54349a.
>
> Any reason you didn't cc: the people on that patch, nor the people that
> get_maintainer.pl says to?
>
> Odds are Felipe will miss this one...
jeff.westf...@ni.com has been Cced,
On Thursday, July 24, 2014 4:11 AM, Dinh Nguyen wrote:
> On 7/23/14, 1:03 PM, Paul Zimmerman wrote:
> >> From: Dinh Nguyen [mailto:dinh.li...@gmail.com]
> >> Sent: Wednesday, July 23, 2014 8:12 AM
> >>
> >> On 07/16/2014 04:27 PM, Paul Zimmerman wrote:
> From: dingu...@altera.com [mailto:dingu
On Thu, Jul 24, 2014 at 09:49:06AM +0800, roy.qing...@gmail.com wrote:
> From: Li RongQing
>
> This reverts commit a9232076374334ca2bc2a448dfde96d38a54349a.
Any reason you didn't cc: the people on that patch, nor the people that
get_maintainer.pl says to?
Odds are Felipe will miss this one...
On Wed, 23 Jul 2014, Linus Torvalds wrote:
> > Well, it looks like we f*cked up something after -rc5 since I'm starting
> > to see lockdep splats all over the place which I didn't see before. I'm
> > running rc6 + tip/master.
> >
> > There was one in r8169 yesterday:
> >
> > https://lkml.kernel.or
From: Li RongQing
This reverts commit a9232076374334ca2bc2a448dfde96d38a54349a.
It introduced a dead lock, and did not fix anything.
it made netif_tx_lock() be called in IRQ context, but in softirq context,
the same lock is locked without disabling IRQ. In fact, the commit a923207637
did not fi
On Wed, Jul 23, 2014 at 2:53 AM, Borislav Petkov wrote:
>
> Well, it looks like we f*cked up something after -rc5 since I'm starting
> to see lockdep splats all over the place which I didn't see before. I'm
> running rc6 + tip/master.
>
> There was one in r8169 yesterday:
>
> https://lkml.kernel.o
On Wed, Jul 23, 2014 at 08:27:16AM +0200, Patrick Riphagen wrote:
> - Annotate the current Xsens PID assigments
> - Add support for new Xsens devices
>
> Cc: Johan Hovold
> Cc: Greg Kroah-Hartman
> Cc: stable
> Cc: Frans Klaver
>
> Patrick Riphagen (2):
> Annotate the current Xsens PID assi
Dan Williams writes:
> On Wed, 2014-07-23 at 14:33 +, Stanescu Victor wrote:
>> /dev/cdc-wdm2 doesn't work. Further more, instead of freezing at cat, it
>> freezes from echo.
>>
>> Ctrl-c doesn't stop the frozen echo.
>
> I'm pretty sure this device does not expose QMI at all, from looking a
There appears to be a bug in the USB host driver for the AM3517 in the
3.16 kernel. When the AM3517 board boots with a USB device plugged in
the host it detects and works fines as long as it is plugged in.
The board does not detect any device that is hotplugged and the kernel
message report nothin
On 7/23/14, 1:03 PM, Paul Zimmerman wrote:
>> From: Dinh Nguyen [mailto:dinh.li...@gmail.com]
>> Sent: Wednesday, July 23, 2014 8:12 AM
>>
>> On 07/16/2014 04:27 PM, Paul Zimmerman wrote:
From: dingu...@altera.com [mailto:dingu...@altera.com]
Sent: Wednesday, July 16, 2014 1:33 PM
>
OK, will do.
Thanks
Jim
--
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 http://vger.kernel.org/majordomo-info.html
On Wed, 23 Jul 2014, James Michels wrote:
> I must disagree, the device driver most certainly does guess. See the
> code snipet below. Particularly the part about "guessed" and "try to
> fix". FWIW, it's the "try to fix" part that doesn't catch this
> scenario.
You didn't read what I wrote in con
I must disagree, the device driver most certainly does guess. See the
code snipet below. Particularly the part about "guessed" and "try to
fix". FWIW, it's the "try to fix" part that doesn't catch this
scenario.
/* Fix up bInterval values outside the legal range. Use 32 ms if no
* proper value can
> From: Dinh Nguyen [mailto:dinh.li...@gmail.com]
> Sent: Wednesday, July 23, 2014 8:12 AM
>
> On 07/16/2014 04:27 PM, Paul Zimmerman wrote:
> >> From: dingu...@altera.com [mailto:dingu...@altera.com]
> >> Sent: Wednesday, July 16, 2014 1:33 PM
> >>
> >> Puts back "samsung,s3c6400-hsotg" into the
On Wed, 23 Jul 2014, James Michels wrote:
> The Razer reports a bInterval of 8 which the current driver ultimately
> interprets as 16ms. The keyboard is an anti-ghosting gaming keyboard
> and needs to be polled at 1ms. This corresponds to a corrected
> bInterval of 4.
Okay, that's reasonable. A
A: No.
Q: Should I include quotations after my reply?
http://daringfireball.net/2007/07/on_top
On Wed, Jul 23, 2014 at 11:48:48AM -0400, James Michels wrote:
> The Razer reports a bInterval of 8 which the current driver ultimately
> interprets as 16ms. The keyboard is an anti-ghosting gaming keyb
On Wed, Jul 23, 2014 at 08:56:10AM -0400, Sasha Levin wrote:
> Revert since the commit message is incorrect and the original author refuses
> to fix/maintain it because "it's in the kernel already".
How can someone "fix" a commit message that is already in the tree? You
can't. The code part is c
On Wed, Jul 23, 2014 at 05:03:14PM +0100, One Thousand Gnomes wrote:
> > + if (gpiochip_remove(&spriv->gpio->gpio_chip))
> > + dev_err(&serial->interface->dev, "unable to remove
> > gpio_chip?\n");
> > + kfree(spriv->gpio);
> > + }
> > +#endif
> > kfree(
> --- a/drivers/usb/serial/pl2303.c
> +++ b/drivers/usb/serial/pl2303.c
> @@ -28,6 +28,9 @@
> #include
> #include
> #include
> +#ifdef CONFIG_USB_SERIAL_PL2303_GPIO
> +#include
> +#endif
> #include "pl2303.h"
Just include the file anyway it does no harm
>
>
> @@ -143,9 +146,27 @@ stru
On Wed, 2014-07-23 at 14:33 +, Stanescu Victor wrote:
> /dev/cdc-wdm2 doesn't work. Further more, instead of freezing at cat, it
> freezes from echo.
>
> Ctrl-c doesn't stop the frozen echo.
I'm pretty sure this device does not expose QMI at all, from looking at
through the drivers. The dri
On Wed, 23 Jul 2014, Peter Griffin wrote:
> This patch adds the ST glue logic to manage the DWC3 HC
> on STiH407 SoC family. It manages the powerdown signal,
> and configures the internal glue logic and syscfg registers.
>
> Signed-off-by: Giuseppe Cavallaro
> Signed-off-by: Peter Griffin
> ---
The Razer reports a bInterval of 8 which the current driver ultimately
interprets as 16ms. The keyboard is an anti-ghosting gaming keyboard
and needs to be polled at 1ms. This corresponds to a corrected
bInterval of 4.
I'm not sure why this doesn't make sense to you, but I do agree that
there is r
On Wed, 23 Jul 2014, Peter Griffin wrote:
> This patch documents the device tree documentation required for
> the ST usb3 controller glue layer found in STiH407 devices.
>
> Signed-off-by: Giuseppe Cavallaro
> Signed-off-by: Peter Griffin
> ---
> Documentation/devicetree/bindings/usb/dwc3-st.t
On Wed, 23 Jul 2014, Peter Griffin wrote:
> Signed-off-by: Peter Griffin
> ---
> MAINTAINERS | 1 +
> 1 file changed, 1 insertion(+)
Acked-by: Lee Jones
>
> diff --git a/MAINTAINERS b/MAINTAINERS
> index 702ca10..269ad3b 100644
> --- a/MAINTAINERS
> +++ b/MAINTAINERS
> @@ -1325,6 +1325,7 @@ F
On Wed, 23 Jul 2014, Adam Borowski wrote:
> On Tue, Jul 22, 2014 at 04:28:03PM -0400, Alan Stern wrote:
> > Adam, your problem seems to be completely different.
>
> Not surprising, as this doesn't look like Intel USB to me:
>
> 00:14.5 USB controller: Advanced Micro Devices, Inc. [AMD/ATI]
> SB7
On 07/16/2014 04:27 PM, Paul Zimmerman wrote:
From: dingu...@altera.com [mailto:dingu...@altera.com]
Sent: Wednesday, July 16, 2014 1:33 PM
Puts back "samsung,s3c6400-hsotg" into the dwc2_of_match_table[].
Why?
This compatible binding was originally in the gadget driver. Don't I
want to
On 07/16/2014 04:26 PM, Paul Zimmerman wrote:
From: dingu...@altera.com [mailto:dingu...@altera.com]
Sent: Wednesday, July 16, 2014 1:33 PM
Update gadget.c to use the dwc2_hsotg and new placement of the gadget
data structure that has been moved into the common structure. Along
with the updatin
On Mon, Jul 21, 2014 at 4:46 AM, Wang YanQing wrote:
> PL2303HX has two GPIOs, this patch add interface for it.
>
> Signed-off-by: Wang YanQing
> ---
> Changes v2-v3:
> 1: fix errors and warnings reported by Daniele Forsi checked with
> checkpatch.pl
> 2: fix missing GPIOLIB dependence in Kc
This patch adds the ST glue logic to manage the DWC3 HC
on STiH407 SoC family. It manages the powerdown signal,
and configures the internal glue logic and syscfg registers.
Signed-off-by: Giuseppe Cavallaro
Signed-off-by: Peter Griffin
---
drivers/usb/dwc3/Kconfig | 9 ++
drivers/usb/dwc3/M
This patch documents the device tree documentation required for
the ST usb3 controller glue layer found in STiH407 devices.
Signed-off-by: Giuseppe Cavallaro
Signed-off-by: Peter Griffin
---
Documentation/devicetree/bindings/usb/dwc3-st.txt | 69 +++
1 file changed, 69 inser
This series adds support for the ST glue logic which wraps the DWC3 controller
on STiH407 SoC family chipsets.
Changes since v2
- Use dr_mode for host/device static configuration
- Manage shared reset signal to usbss to avoid hang if probing before usb3 phy
- Remove DT checks and make driver de
Signed-off-by: Peter Griffin
---
MAINTAINERS | 1 +
1 file changed, 1 insertion(+)
diff --git a/MAINTAINERS b/MAINTAINERS
index 702ca10..269ad3b 100644
--- a/MAINTAINERS
+++ b/MAINTAINERS
@@ -1325,6 +1325,7 @@ F:drivers/pinctrl/pinctrl-st.c
F: drivers/media/rc/st_rc.c
F: driver
On Tue, 22 Jul 2014, James P Michels III wrote:
> This patch adds usb quirks to improve support for devices
> with non standard bInterval values. Quirks are added to support devices with
> bInterval values expressed as microframes or frames. The quirks cause the
> parse endpoint function to mod
Unfortunately this did nothing. Not even some dmesg output.
I have tried restarting network-manager but there was also nothing.
I don't have a wwan interface by default. Only when manually loading
usbserial I can wwdial using pppd (manually).
On 07/23/2014 12:29 PM, Bjørn Mork wrote:
> Stanescu
Hi Felipe,
Thanks for reviewing, see my comments inline: -
> > > Just use {read,write}l_relaxed() directly.
> >
> > Ok, unabstracted in v3
>
> no, no... all other glues add their own local helpers for register
> access. This is good for tracing, it's very easy to add a tracepoint to
> this sort
/dev/cdc-wdm2 doesn't work. Further more, instead of freezing at cat, it
freezes from echo.
Ctrl-c doesn't stop the frozen echo.
On 07/23/2014 12:45 PM, Bjørn Mork wrote:
> Stanescu Victor writes:
>
>> root@victor-laptop:~# modprobe qmi_wwan
>> root@victor-laptop:~# dmesg
>> [ 6005.900671] usbc
Hi Sarah,
Thank you very much for your answer. I bought three same all-in-one, low-energy
and space effective computers from ASUS. There isn’t any possibility to add an
additional extension PCIe card. There is only the option to upgrade the memory
and hard drive (which I already did it).
Revert since the commit message is incorrect and the original author refuses
to fix/maintain it because "it's in the kernel already".
Signed-off-by: Sasha Levin
---
drivers/usb/core/hcd.c | 4
1 file changed, 4 insertions(+)
diff --git a/drivers/usb/core/hcd.c b/drivers/usb/core/hcd.c
inde
On Tue, Jul 15, 2014 at 04:39:08PM +0200, Antoine Ténart wrote:
> Hi all,
>
> This is an attempt to add more common USB code aware of the generic PHY
> framework, while keeping the compatibility for the USB PHY one. It does
> not add the full support, some USB PHY specific functions not being
> av
On Tue, Jul 15, 2014 at 04:39:14PM +0200, Antoine Ténart wrote:
> This patch modify the generic code handling PHYs to allow them to be
> supplied from the drivers. This adds checks to ensure no PHY was already
> there when looking for one in the generic code. This also makes sure we
> do not modify
On Sun, Jul 20, 2014 at 09:22:52PM -0700, Linus Torvalds wrote:
> So go get the latest rc and kick the tires, to see that nothing has
> fallen through the cracks, ok?
Well, it looks like we f*cked up something after -rc5 since I'm starting
to see lockdep splats all over the place which I didn't se
Stanescu Victor writes:
> root@victor-laptop:~# modprobe qmi_wwan
> root@victor-laptop:~# dmesg
> [ 6005.900671] usbcore: registered new interface driver cdc_wdm
> [ 6005.902682] usbcore: registered new interface driver qmi_wwan
> root@victor-laptop:~# echo "03f0 521d" >
> /sys/bus/usb/drivers/q
On Wed, Jul 23, 2014 at 2:48 PM, Jingoo Han wrote:
> On Wednesday, July 23, 2014 4:38 PM, Kiran Padwal wrote:
>>
>> Make of_device_id array const, because all OF functions handle it as const.
>
> Hi Kiran Padwal,
>
> The same patch was already submitted and merged to USB tree.
> Thank you.
Thanks
root@victor-laptop:~# modprobe qmi_wwan
root@victor-laptop:~# dmesg
[ 6005.900671] usbcore: registered new interface driver cdc_wdm
[ 6005.902682] usbcore: registered new interface driver qmi_wwan
root@victor-laptop:~# echo "03f0 521d" >
/sys/bus/usb/drivers/qmi_wwan/new_id
root@victor-laptop:~# d
Stanescu Victor writes:
> victor@victor-laptop:~$ lsusb -vd 03f0:521d
[..]
> Interface Descriptor:
>bLength 9
>bDescriptorType 4
>bInterfaceNumber4
>bAlternateSetting 1
>bNumEndpoints 3
Yup, there's th
On Tue, Jul 22, 2014 at 04:28:03PM -0400, Alan Stern wrote:
> Adam, your problem seems to be completely different.
Not surprising, as this doesn't look like Intel USB to me:
00:14.5 USB controller: Advanced Micro Devices, Inc. [AMD/ATI]
SB7x0/SB8x0/SB9x0 USB OHCI2 Controller
So my and Toralf's p
On Wed, Jul 23, 2014 at 5:11 PM, Thomas Gleixner wrote:
>
> So what's the fix?
revert it, I think netif_stop_queue() did not free the resources, so
this commit does not
fix anything; if no one objects, I will send a patch to revert it.
-Roy
--
To unsubscribe from this list: send the line "unsu
On Wednesday, July 23, 2014 4:38 PM, Kiran Padwal wrote:
>
> Make of_device_id array const, because all OF functions handle it as const.
Hi Kiran Padwal,
The same patch was already submitted and merged to USB tree.
Thank you.
Best regards,
Jingoo Han
>
> Signed-off-by: Kiran Padwal
> ---
>
victor@victor-laptop:~$ lsusb -vd 03f0:521d
Bus 002 Device 007: ID 03f0:521d Hewlett-Packard
Device Descriptor:
bLength18
bDescriptorType 1
bcdUSB 2.00
bDeviceClass 255 Vendor Specific Class
bDeviceSubClass 2
bDeviceProtocol
Stanescu Victor writes:
> Hello,
>
> As I have started this discussion, I'd like to assure you that I'm
> willing to do any tests you want/need in order to clarify it.
Great! Thanks. If you have the qmi_wwan driver (and a recent kernel -
don't remember exactly how recent...), then should be a
On Wed, 23 Jul 2014, Li RongQing wrote:
> This commit introduced this bug
>
> commit a9232076374334ca2bc2a448dfde96d38a54349a
> Author: Jeff Westfahl
> Date: Thu May 29 09:49:41 2014 +0300
>
> usb: gadget: u_ether: synchronize with transmit when stopping queue
>
> When disconnecting,
Stanescu Victor writes:
> Hello,
>
> This device works perfectly with usbserial generic, loaded with forced
> vendor/product parameters. Can you please add it to the proper driver?
>
> T: Bus=02 Lev=01 Prnt=01 Port=05 Cnt=02 Dev#= 7 Spd=480 MxCh= 0
> D: Ver= 2.00 Cls=ff(vend.) Sub=02 Prot=01
Hi Felipe,
On Monday 21 July 2014 08:45 PM, Felipe Balbi wrote:
> Hi,
>
> On Mon, Jul 21, 2014 at 05:04:57PM +0200, Laurent Pinchart wrote:
>> Hi Felipe,
>>
>> What happened to these two patches ?
>
> looks like I lost them.
>
>> On Monday 16 December 2013 17:48:29 Felipe Balbi wrote:
>>> On Mo
Hello,
As I have started this discussion, I'd like to assure you that I'm
willing to do any tests you want/need in order to clarify it. Even a
teamviewer session can be an option if needed.
Thanks,
Victor
On 07/23/2014 11:52 AM, Bjørn Mork wrote:
> Lars Melin writes:
>> On 2014-07-23 04:17, D
Lars Melin writes:
> On 2014-07-23 04:17, Dan Williams wrote:
>> On Tue, 2014-07-22 at 14:02 +, Stanescu Victor wrote:
>>> Hello,
>>>
>>> This device works perfectly with usbserial generic, loaded with forced
>>> vendor/product parameters. Can you please add it to the proper driver?
>>>
>>> T:
Make of_device_id array const, because all OF functions handle it as const.
Signed-off-by: Kiran Padwal
---
drivers/usb/phy/phy-msm-usb.c |2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/drivers/usb/phy/phy-msm-usb.c b/drivers/usb/phy/phy-msm-usb.c
index 78cc870..e4108ee 10
This commit introduced this bug
commit a9232076374334ca2bc2a448dfde96d38a54349a
Author: Jeff Westfahl
Date: Thu May 29 09:49:41 2014 +0300
usb: gadget: u_ether: synchronize with transmit when stopping queue
When disconnecting, it's possible that another thread has already made it
Hi,
On Tue, Jul 22, 2014 at 04:33:54PM -0500, Bin Liu wrote:
> On Wed, Jul 9, 2014 at 5:17 AM, Antoine Ténart
> wrote:
> > diff --git a/drivers/usb/chipidea/debug.c b/drivers/usb/chipidea/debug.c
> > index 7cccab6ff308..9a9702773e43 100644
> > --- a/drivers/usb/chipidea/debug.c
> > +++ b/drivers/
61 matches
Mail list logo
