Hi Minas,
Thanks for your reply. I did some more playing with this, and found that
I can cause kernel oops and reboot even with just one camera and by just
probing it with v4l2-ctl.
for each in `ls -1 /dev/video* /dev/v4l/by-id/* /dev/v4l/by-path/*`; do
echo "scan: $each"
v4l2-ctl --d
Hi Heikki,
Please help review these two changes which adds support for
VirtualLink display altmode devices using NVIDIA GPU.
You had shared the first patch during our offline discussion.
The second patch adds NVIDIA display altmode driver.
This set is created against latest Linus's kernel and pa
From: Heikki Krogerus
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 manu
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
---
drivers/usb/typec/altmodes/Kconfig | 10 +++
drivers/usb/typec/altmodes/Makefile | 2 ++
driver
Hi Heikki,
I love your patch! Perhaps something to improve:
[auto build test WARNING on usb/usb-testing]
[also build test WARNING on v5.1-rc4 next-20190410]
[if your patch is applied to the wrong git tree, please drop us a note to help
improve the system]
url:
https://github.com/0day-ci
On Mi, 2019-04-10 at 09:37 +, Jisheng Zhang wrote:
> On Tue, 9 Apr 2019 09:28:16 + Minas Harutyunyan wrote:
Hi,
> > dwc2 in host mode enable SOF interrupts if any periodic EP are in use.
> > So, 8000 interrupts per second is expectant behavior.
>
> Makes sense. 8 microframes each 1ms, so
On Tue, 9 Apr 2019 09:28:16 + Minas Harutyunyan wrote:
>
> Hi Stefan,
>
> > Hi Minas,
> >
> > Am 09.04.19 um 08:54 schrieb Jisheng Zhang:
> >> On Mon, 8 Apr 2019 16:05:51 +0800 Jisheng Zhang wrote:
> >>
> >>> Hi Stefan,
> >>>
> >>> On Mon, 8 Apr 2019 09:57:14 +0200 Stefan Wahren wrote:
On 4/5/2019 5:36 PM, Jules Maselbas wrote:
> Hi,
>
> Theses patches tries to clean a bit dwc2's phy initialization and
> fix an issue in gadget mode where the utmi phy width is set
> regardless of utmi being used or not.
>
> I believe that when using ulpi a phy width of 8 bits must be used,
> but
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
Hi Greg,
Here are the remaining patches from me and Ajay for the UCSI driver. I
took the liberty of collecting them for you, and resending everything
together.
There are two patches from Ajay adding support for firmware upgrading
with the Cypress CCGx controllers [1], and two patches from me
enab
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.
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
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
13 matches
Mail list logo
