Hi Hal,
On 4/19/2019 11:41 PM, Hal Emmerich wrote:
Hello all,
I have a ar9271 wireless dongle which is known to not work well with dwc2.
When inserted, it may initialize properly if the system was just
rebooted but after that will error out.
With dwc2 verbose debug enabled, I see a bulk tra
Hi Greg,
Ajay noticed that I was not considering earlier releases of the UCSI
specification with a specific UCSI command, GET_CURRENT_CAM, in v3.
The definition for the command was changed in UCSI specification v1.1.
The issue is now fixed.
v3 cover letter.
This is the third version of this coll
From: Ajay Gupta
Adding device property "ccgx,firmware-build" for the CCGx
device, so the CCGx driver knows which firmware binary to
use for a specific vendor.
Suggested-by: Heikki Krogerus
Signed-off-by: Ajay Gupta
Signed-off-by: Heikki Krogerus
---
drivers/i2c/busses/i2c-nvidia-gpu.c | 7 +
From: Ajay Gupta
Function is to get the details of ccg firmware and device version.
It will be useful in debugging and also during firmware update.
Signed-off-by: Ajay Gupta
Signed-off-by: Heikki Krogerus
---
drivers/usb/typec/ucsi/ucsi_ccg.c | 66 ++-
1 file chang
With UCSI the alternate modes, just like everything else
related to USB Type-C connectors, are handled in firmware.
The operating system can see the status and is allowed to
request certain things, for example entering and exiting the
modes, but the support for alternate modes is very limited
in UC
From: Ajay Gupta
CCGx has two copies of the firmware in addition to the bootloader.
If the device is running FW1, FW2 can be updated with the new version.
Dual firmware mode allows the CCG device to stay in a PD contract and
support USB PD and Type-C functionality while a firmware update is in
pr
From: Ajay Gupta
VirtualLink standard extends the DisplayPort Alt Mode by
utilizing also the USB 2 pins on the USB Type-C connector.
It uses the same messages as DisplayPort, but not the DP
SVID. At the time of writing, USB IF has not assigned a
Standard ID (SID) for VirtualLink, so the manufactu
From: Ajay Gupta
Latest NVIDIA GPUs support VirtualLink device. Since USBIF
has not assigned a Standard ID (SID) for VirtualLink
so using NVIDA VID 0x955 as SVID.
Signed-off-by: Ajay Gupta
Signed-off-by: Heikki Krogerus
---
drivers/usb/typec/altmodes/Kconfig | 10 +++
drivers/usb/typec/a
This makes it possible to bind a driver to a DisplayPort
alt mode adapter devices.
The driver attempts to cope with the limitations of UCSI by
"emulating" behaviour and attempting to guess things when
ever possible in order to satisfy the requirements the
standard DisplayPort alt mode driver has.
On Mon, 2019-04-01 at 16:22 -0400, Alan Stern wrote:
> Mayuresh:
>
> Whatever happened to this discussion? Did you reach a decision on
> whether the proposed API addition would suit your needs?
>
> Alan Stern
Hi Alan,
Apologies for not being able to respond to this email thread before.
Around
The syzkaller USB fuzzer found a general-protection-fault bug in the
yurex driver. The fault occurs when a device has been unplugged; the
driver's interrupt-URB handler logs an error message referring to the
device by name, after the device has been unregistered and its name
deallocated.
This pro
On 4/14/19 4:00 AM, Malte Leip wrote:
Change the validation of number_of_packets in get_pipe to compare the
number of packets to a fixed maximum number of packets allowed, set to
be 1024. This number was chosen due to it being used by other drivers as
well, for example drivers/usb/host/uhci-q.c
12 matches
Mail list logo
