On Tue, 03 Oct 2017 19:42:21 +0200,
Greg Kroah-Hartman wrote:
>
> On Tue, Oct 03, 2017 at 12:50:08PM -0400, Alan Stern wrote:
> > On Tue, 3 Oct 2017, Takashi Iwai wrote:
> >
> > > > It's a dev_WARN because it indicates a potentially serious error in the
> > > > driver: The driver has submitted a
Hi,
On Tuesday 03 October 2017 06:29 PM, Andrzej Pietrasiewicz wrote:
> Hi all,
>
> This is the second version of patches in this thread.
>
> The series fixes problems with enumerating of SuperSpeed devices
> on an Odroid XU3. There was a patch series from Vivek Gautam in
> circulation, but it g
From: Bjørn Mork
Date: Tue, 03 Oct 2017 16:01:15 +0200
> We can pretty much ignore the USB-IF and any specs, since that is what
> the vendors appear to do. They provide device specific drivers for
> Windows, so all they care about is that their device "works" with their
> driver.
>
> But in Lin
Hi,
On 9/11/2017 12:42 AM, Felipe Balbi wrote:
>
> Hi,
>
> Thinh Nguyen writes:
>>> Felipe Balbi writes:
Thinh Nguyen writes:
> Hi Felipe,
>
> On 9/7/2017 12:16 AM, Felipe Balbi wrote:
> drivers/usb/dwc3/gadget.c | 8 +---
> 1 file changed, 5
On Tue, Oct 03, 2017 at 12:50:08PM -0400, Alan Stern wrote:
> On Tue, 3 Oct 2017, Takashi Iwai wrote:
>
> > > It's a dev_WARN because it indicates a potentially serious error in the
> > > driver: The driver has submitted an interrupt URB to a bulk endpoint.
> > > That may not sound bad, but the
On Tue, 3 Oct 2017, Takashi Iwai wrote:
> > It's a dev_WARN because it indicates a potentially serious error in the
> > driver: The driver has submitted an interrupt URB to a bulk endpoint.
> > That may not sound bad, but the same check gets triggered if a driver
> > submits a bulk URB to an i
On Tue, 03 Oct 2017 16:21:57 +0200,
Alan Stern wrote:
>
> On Tue, 3 Oct 2017, Takashi Iwai wrote:
>
> > On Mon, 25 Sep 2017 14:39:51 +0200,
> > Andrey Konovalov wrote:
> > >
> > > Hi!
> > >
> > > I've got the following report while fuzzing the kernel with syzkaller.
> > >
> > > On commit e19b2
On Tue, Oct 3, 2017 at 4:51 PM, Kristian Evensen
wrote:
> Disabling the timer caused a different error to be triggered. Instead
> of "HC died...", I now get the following message looping over and
> over:
>
> [16870.871935] qmi_wwan 4-1:1.4: Tx URB error: -19
I was not thinking clearly when I wrot
Hi,
On Tue, Oct 3, 2017 at 11:16 AM, Kristian Evensen
wrote:
> Messing with the driver is no problem :) Thanks for this pointer, I am
> testing stopping the timer now and will let you know how it goes.
Disabling the timer caused a different error to be triggered. Instead
of "HC died...", I now g
On Tue, 3 Oct 2017, David Laight wrote:
> From: Felipe Balbi
> > Sent: 03 October 2017 09:17
> > This keyboard doesn't implement Get String descriptors properly even
> > though string indexes are valid. What happens is that when requesting
> > for the String descriptor, the device disconnects and
On Tue, 3 Oct 2017, Takashi Iwai wrote:
> On Mon, 25 Sep 2017 14:39:51 +0200,
> Andrey Konovalov wrote:
> >
> > Hi!
> >
> > I've got the following report while fuzzing the kernel with syzkaller.
> >
> > On commit e19b205be43d11bff638cad4487008c48d21c103 (4.14-rc2).
> >
> > It seems that there'
David Miller writes:
> From: Aleksander Morgado
> Date: Wed, 27 Sep 2017 23:31:03 +0200
>
>> I'm not sure if binding this logic to a specific vid:pid (1410:9030)
>> would be more appropriate here, or if it's ok to just bind
>> class/subclass/protocol (as in the activesync case). Let me know
>>
Hi Josh,
On Mon, Oct 02, 2017 at 04:31:09PM -0500, Josh Poimboeuf wrote:
On Mon, Oct 02, 2017 at 04:26:54PM -0500, Josh Poimboeuf wrote:
Fengguang, assuming it's reliably recreatable, any chance you could
recreate with the following patch?
Sorry, here's a version which actually compiles.
dif
On Fri, Sep 29, 2017 at 12:39:51PM +0800, Shrirang Bagul wrote:
> Dell Wireless 5819/5818 devices are re-branded Sierra Wireless MC74
> series which will by default boot with vid 0x413c and pid's 0x81cf,
> 0x81d0, 0x81d1,0x81d2.
>
> Signed-off-by: Shrirang Bagul
Now applied.
Don't you want to a
On Tue, Oct 03, 2017 at 11:45:38AM +0800, Fengguang Wu wrote:
> Hi Josh,
>
> On Mon, Oct 02, 2017 at 04:31:09PM -0500, Josh Poimboeuf wrote:
> > On Mon, Oct 02, 2017 at 04:26:54PM -0500, Josh Poimboeuf wrote:
> > > Fengguang, assuming it's reliably recreatable, any chance you could
> > > recreate
W dniu 03.10.2017 o 14:59, Andrzej Pietrasiewicz pisze:
Hi all,
This is the second version of patches in this thread.
I have lost the subject of the cover letter.
Should be "dwc3 on XU3". I did not resend the series in order
not to spam the recipients. Sorry for confusion.
Andrzej
--
To unsu
Hi all,
This is the second version of patches in this thread.
The series fixes problems with enumerating of SuperSpeed devices
on an Odroid XU3. There was a patch series from Vivek Gautam in
circulation, but it got lost somehow. Please see:
https://lkml.org/lkml/2014/9/2/166
https://lkml.org/lkm
Some quirky UDCs (like dwc3 on exynos) need to have heir phys calibrated
e.g. for using super speed.
Signed-off-by: Andrzej Pietrasiewicz
---
drivers/phy/phy-core.c | 14 ++
include/linux/phy/phy.h | 10 ++
2 files changed, 24 insertions(+)
diff --git a/drivers/phy/phy-core
From: Vivek Gautam
Adding phy calibration sequence for USB 3.0 DRD PHY present on
Exynos5420/5800 systems.
This calibration facilitates setting certain PHY parameters viz.
the Loss-of-Signal (LOS) Detector Threshold Level, as well as
Tx-Vboost-Level for Super-Speed operations.
Additionally we als
Hello Yoshihiro Shimoda,
The patch c41442474a26: "usb: gadget: R8A66597 peripheral controller
support." from Aug 19, 2009, leads to the following static checker
warning:
drivers/usb/gadget/udc/r8a66597-udc.c:1942 r8a66597_probe()
warn: integer overflow: (-1) * 2
drivers/usb/gadge
The following changes since commit 2bd6bf03f4c1c59381d62c61d03f6cc3fe71f66e:
Linux 4.14-rc1 (2017-09-16 15:47:51 -0700)
are available in the git repository at:
git://git.kernel.org/pub/scm/linux/kernel/git/gregkh/usb.git/
tags/usb-4.14-rc4
for you to fetch changes up to 80c82ffebd2ec3f91a2
Apologies, I don't know if I replied to this in the end. Nothing on
dmesg - the mouse just freezes.
Is it maybe not a driver issue but somewhere in the translation to X?
Sorry - I'm the diet coke of technical.
On 28/09/17 15:41, Oliver Neukum wrote:
Am Mittwoch, den 27.09.2017, 20:49 +1000 s
This patch unifies the Gen2 and Gen3 pipe_config setting on
usbhs_parse_dt().
Signed-off-by: Yoshihiro Shimoda
---
drivers/usb/renesas_usbhs/common.c | 13 -
1 file changed, 4 insertions(+), 9 deletions(-)
diff --git a/drivers/usb/renesas_usbhs/common.c
b/drivers/usb/renesas_usbhs/
This patch adds support for R-Car D3. This SoC needs to release
the PLL reset by the UGCTRL register. So, since this is not the same
as other R-Car Gen3 SoCs, this patch adds a new type as
"USBHS_TYPE_RCAR_GEN3_WITH_PLL".
Signed-off-by: Yoshihiro Shimoda
---
.../devicetree/bindings/usb/renesas_u
This patch set is based on the latest Felipe's usb.git / testing/next branch
(commit id = af846d7ab55c846af6d6f150e9af96295101e068)
Yoshihiro Shimoda (2):
usb: renesas_usbhs: unify Gen2/3 pipe_config setting
usb: renesas_usbhs: add support for R-Car D3
.../devicetree/bindings/usb/renesas_usb
Hi,
On Am33xx I am using a bluetooth adapter over musb host using cppi41.
I'm doing some Bluetooth Audio using a USB adapter. It using RFCOMM and
SCO (the former uses bulk transfer the latter uses isochronous
transfers), i am missing a packet in a bulk transfer after the
isochronous transfer
On 9/20/2017 11:57 PM, John Stultz wrote:
> It has been noticed that the dwc2 udc state reporting doesn't
> seem to work (at least on HiKey boards). Where after the initial
> setup, the sysfs /sys/class/udc/f72c.usb/state file would
> report "configured" no matter the state of the OTG port.
>
>
On 9/20/2017 11:57 PM, John Stultz wrote:
> We've found that while in host mode, using Android, if one runs
> the command:
> stop adbd
>
> The existing usb devices being utilized in host mode are disconnected.
> This is most visible with usb networking devices.
>
> This seems to be due to adbd cl
On 9/30/2017 9:13 PM, John Youn wrote:
> On 09/20/2017 12:57 PM, John Stultz wrote:
>> So here are a few dwc2 fixes that I've been using with HiKey.
>> I'm not totally sure these are all ideal, but they avoid edge case
>> issues that we have been running into with switching between
>> gadget mode a
On Fri, Sep 29, 2017 at 10:37:55AM +0200, Greg Kroah-Hartman wrote:
> On Thu, Sep 28, 2017 at 07:57:46PM +0200, Andrey Konovalov wrote:
> > Hi!
> >
> > I've got the following report while fuzzing the kernel with syzkaller.
> >
> > On commit dc972a67cc54585bd83ad811c4e9b6ab3dcd427e (4.14-rc2+).
>
Hi Mathias,
Thank you very much for your reply.
On Tue, Oct 3, 2017 at 10:28 AM, Mathias Nyman
wrote:
> For temporary workarounds:
> if xhci is a module then unload and reload in using modprobe
>
> Or then unbind/rebind the driver and device.
> on a Intel PCI based xhci it would be something lik
On Fri, Sep 29, 2017 at 09:01:45AM +0900, Chanwoo Choi wrote:
> The extcon has two type of extcon devices as following.
> - 'extcon provider deivce' adds new extcon device and detect the
>state/properties of external connector. Also, it notifies the
>state/properties to the extcon consumer
On 02.10.2017 22:44, Kristian Evensen wrote:
Hello,
I am currently working on a custom Armada 385-based board running
kernel 4.9.52. I have a USB 2.0 LTE modem connected to USB 3.0, and
the modem sometimes crashes due to various internal (on the modem)
reasons. The board supports restarting the
On Tue, Oct 03, 2017 at 08:19:52AM +, David Laight wrote:
> From: Felipe Balbi
> > Sent: 03 October 2017 09:17
> > This keyboard doesn't implement Get String descriptors properly even
> > though string indexes are valid. What happens is that when requesting
> > for the String descriptor, the de
From: Felipe Balbi
> Sent: 03 October 2017 09:17
> This keyboard doesn't implement Get String descriptors properly even
> though string indexes are valid. What happens is that when requesting
> for the String descriptor, the device disconnects and
> reconnects. Without this quirk, this loop will co
This keyboard doesn't implement Get String descriptors properly even
though string indexes are valid. What happens is that when requesting
for the String descriptor, the device disconnects and
reconnects. Without this quirk, this loop will continue forever.
Cc: Alan Stern
Reported-by: Владимир Ма
On Mon, 2017-10-02 at 14:44 +0200, Greg KH wrote:
> On Mon, Oct 02, 2017 at 02:35:08PM +0200, Jerome Brunet wrote:
> > On Sun, 2017-10-01 at 22:32 +0200, Martin Blumenstingl wrote:
> > > Hello Greg, Hello Mathias,
> > >
> > > On Mon, Sep 18, 2017 at 10:49 AM, Greg KH
> > > wrote:
> > > > On Sun,
Hi,
(we don't top-post here :-)
Владимир Мартьянов writes:
> Oh, I didn't know about quirks.c. Your code solved the problem, thank you!
alright, I'll send it as a proper patch and add yourself as "Reported-by".
--
balbi
signature.asc
Description: PGP signature
On Tue, Oct 3, 2017 at 4:22 AM, Jérémy Lefaure
wrote:
> On Mon, 2 Oct 2017 16:07:36 +0300
> Andy Shevchenko wrote:
>
>> > + {&gainctrl_lut_core0_rev0, ARRAY_SIZE(gainctrl_lut_core0_rev0),
>> > 26, 192,
>> > +32},
>>
>> For all such cases I would rather put on one line disregard che
On Mon, 25 Sep 2017 14:39:51 +0200,
Andrey Konovalov wrote:
>
> Hi!
>
> I've got the following report while fuzzing the kernel with syzkaller.
>
> On commit e19b205be43d11bff638cad4487008c48d21c103 (4.14-rc2).
>
> It seems that there's no check of the endpoint type.
>
> usb 1-1: BOGUS urb xfer
40 matches
Mail list logo
