Hi Hans,
On Mon, Sep 03, 2018 at 04:59:51PM +0200, Hans de Goede wrote:
> Hi,
>
> On 03-09-18 15:36, Heikki Krogerus wrote:
> > PI3USB30532 is used for muxing the port to DisplayPort on
> > CHT platforms, so changing the connection ID so that the
> > mux will get assigned to the alternate mode de
On Mon, Sep 03, 2018 at 12:58:35PM -0700, Randy Dunlap wrote:
> From: Randy Dunlap
>
> Fix kernel-doc warning for missing function parameter 'mode' description:
>
> ../drivers/usb/typec/bus.c:268: warning: Function parameter or member 'mode'
> not described in 'typec_match_altmode'
>
> Also fi
HI,
On 04-09-18 09:37, Heikki Krogerus wrote:
Hi Hans,
On Mon, Sep 03, 2018 at 04:59:51PM +0200, Hans de Goede wrote:
Hi,
On 03-09-18 15:36, Heikki Krogerus wrote:
PI3USB30532 is used for muxing the port to DisplayPort on
CHT platforms, so changing the connection ID so that the
mux will get
On Tue, Sep 04, 2018 at 09:40:35AM +0200, Hans de Goede wrote:
> HI,
>
> On 04-09-18 09:37, Heikki Krogerus wrote:
> > Hi Hans,
> >
> > On Mon, Sep 03, 2018 at 04:59:51PM +0200, Hans de Goede wrote:
> > > Hi,
> > >
> > > On 03-09-18 15:36, Heikki Krogerus wrote:
> > > > PI3USB30532 is used for m
Hi,
On 04-09-18 09:44, Heikki Krogerus wrote:
On Tue, Sep 04, 2018 at 09:40:35AM +0200, Hans de Goede wrote:
HI,
On 04-09-18 09:37, Heikki Krogerus wrote:
Hi Hans,
On Mon, Sep 03, 2018 at 04:59:51PM +0200, Hans de Goede wrote:
Hi,
On 03-09-18 15:36, Heikki Krogerus wrote:
PI3USB30532 is u
For those people who run with panic_on_warn a WARN() triggered
from user space is a DOS. It is worth returning to dev_err()
Signed-off-by: Oliver Neukum
Fixes: 0cb54a3e47cb4baf0bc7463f0a64cfeae5e35697
Reported-by: syzbot+843efa30c8821bd69...@syzkaller.appspotmail.com
---
drivers/usb/core/urb.c |
Hi,
Ranran writes:
> On Mon, Sep 3, 2018 at 4:50 PM Ranran wrote:
>>
>> On Mon, Sep 3, 2018 at 4:22 PM Ranran wrote:
>> >
>> > On Mon, Sep 3, 2018 at 3:40 PM Greg KH wrote:
>> > >
>> > > On Mon, Sep 03, 2018 at 09:39:14AM +0300, Ranran wrote:
>> > > > Hello,
>> > > >
>> > > > I try to add ga
On Tue, Sep 04, 2018 at 10:44:41AM +0200, Oliver Neukum wrote:
> For those people who run with panic_on_warn a WARN() triggered
> from user space is a DOS. It is worth returning to dev_err()
I think this should be dev_warn() unless you want to bring back the
returning of errors on these conditions
On Di, 2018-09-04 at 11:31 +0200, Johan Hovold wrote:
> On Tue, Sep 04, 2018 at 10:44:41AM +0200, Oliver Neukum wrote:
> > For those people who run with panic_on_warn a WARN() triggered
> > from user space is a DOS. It is worth returning to dev_err()
>
> I think this should be dev_warn() unless yo
On Tue, Sep 04, 2018 at 12:21:09PM +0200, Oliver Neukum wrote:
> On Di, 2018-09-04 at 11:31 +0200, Johan Hovold wrote:
> > On Tue, Sep 04, 2018 at 10:44:41AM +0200, Oliver Neukum wrote:
> > > For those people who run with panic_on_warn a WARN() triggered
> > > from user space is a DOS. It is worth
Hi, thank you for quick answer.
i will try it, but afaik git bisect resets full git tree to the commit, right?
i need to do some adjustments to get system booting (config,swap mmc in dts).
is there another way to show more debug-messages?
i have a working 4.16-tree, maybe i can merge newer ver
This fixes potential "BUG: unable to handle kernel paging
request at ..." from happening.
Fixes: fde0aa6c175a ("usb: common: Small class for USB role switches")
Cc:
Signed-off-by: Heikki Krogerus
---
drivers/usb/common/roles.c | 15 ---
1 file changed, 12 insertions(+), 3 deletions(
The connections create clear dependency on the muxes.
fusb302 fails to probe unless we have the mux drivers
available.
Signed-off-by: Heikki Krogerus
---
drivers/platform/x86/Kconfig | 2 ++
1 file changed, 2 insertions(+)
diff --git a/drivers/platform/x86/Kconfig b/drivers/platform/x86/Kconfig
Hi,
These patches will introduce a few improvements to the USB Type-C
support on Intel CHT platform. In this series I'm preparing Intel CHT
mux handling for DisplayPort Alt Mode support, but please note that,
after these patches the DisplayPort alternate mode will still not work
out of the box on
Functions typec_mux_get() and typec_switch_get() already
make sure that the mux device reference count is
incremented, but the same must be done to the driver module
as well to prevent the drivers from being unloaded in the
middle of operation.
This fixes a potential "BUG: unable to handle kernel
We can register all device connection descriptors with a
single call to device_connections_add().
Signed-off-by: Heikki Krogerus
---
drivers/platform/x86/intel_cht_int33fe.c | 14 --
1 file changed, 4 insertions(+), 10 deletions(-)
diff --git a/drivers/platform/x86/intel_cht_int33fe
USB Type-C class driver now expects the muxes to be always
assigned to the ports and not controllers, so the
connections for the mux and fusb302 can be removed.
Signed-off-by: Heikki Krogerus
---
drivers/platform/x86/intel_cht_int33fe.c | 18 --
1 file changed, 4 insertions(+), 1
Introducing helpers for adding and removing multiple device
connection descriptions at once.
Signed-off-by: Heikki Krogerus
---
include/linux/device.h | 24
1 file changed, 24 insertions(+)
diff --git a/include/linux/device.h b/include/linux/device.h
index 8f882549edee.
It is not possible to use the parent of the port device when
requesting mux handles as the parent may be a multiport USB
Type-C or PD controller. The muxes must be assigned to the
ports, not the controllers.
This will also move the requesting of the muxes after the
port device is initialized.
Sig
Assigning the mux to the USB Type-C port on top of fusb302.
That will prepare this driver for the change in the USB
Type-C class code, where the class driver will assume the
muxes to be always assigned to the ports and not the
controllers.
Once the USB Type-C class driver has been updated, the
con
The debugfs needs to be initialized as the last step in
probe in this case. The struct dentry *rootdir can't be
pointing to anything unless driver probe really finishes
successfully.
It is also not necessary to clear the i2c clientdata if the
probe fails, so removing the extra label used for that.
Adding a connection for the DisplayPort alternate mode.
PI3USB30532 is used for muxing the port to DisplayPort on
CHT platforms. The connection allows the alternate mode
device to get handle to the mux, and therefore make it
possible to use the USB Type-C connector as DisplayPort.
Signed-off-by: H
Hello,
In gadgetfs documentation I find no mention of endpoints:
https://www.kernel.org/doc/Documentation/usb/gadget_configfs.txt
Is it possible to create endpoints using gadgetfs ?
Thank you,
ranran
On Tue, Sep 4, 2018 at 12:12 PM Felipe Balbi
wrote:
>
>
> Hi,
>
> Ranran writes:
> > On Mon, Sep 3, 2018 at 4:50 PM Ranran wrote:
> >>
> >> On Mon, Sep 3, 2018 at 4:22 PM Ranran wrote:
> >> >
> >> > On Mon, Sep 3, 2018 at 3:40 PM Greg KH
> >> > wrote:
> >> > >
> >> > > On Mon, Sep 03, 2018 at
On Tue, Sep 4, 2018 at 2:22 PM Heikki Krogerus
wrote:
>
> Hi,
>
> These patches will introduce a few improvements to the USB Type-C
> support on Intel CHT platform. In this series I'm preparing Intel CHT
> mux handling for DisplayPort Alt Mode support, but please note that,
> after these patches t
hi,
Ranran writes:
> > A fix for my last comment:
>> > usb device controller should be supported with conga-MA5 (contains
>> > Intel's appolo lake), so I am still not sure why I find /sys/class/udc
>> > empty.
>> > In congatec MA-5 document it is said:
>> > "The conga-MA5 offers six USB 2.0 int
On Tue, Sep 4, 2018 at 3:26 PM Felipe Balbi
wrote:
>
>
> hi,
>
> Ranran writes:
> > > A fix for my last comment:
> >> > usb device controller should be supported with conga-MA5 (contains
> >> > Intel's appolo lake), so I am still not sure why I find /sys/class/udc
> >> > empty.
> >> > In congatec
On Sat, Aug 04, 2018 at 12:17:15PM +0200, Loic Poulain wrote:
> Some FTDI devices like FTX or FT232R support CBUS Bit Bang mode on CBUS
> pins, allowing host to control them via simple USB control transfers.
> To make use of a CBUS pin in Bit Bang mode, the pin must be configured
> to I/O mode in t
On Tue, Sep 4, 2018 at 2:36 PM Ranran wrote:
>
> Hello,
>
> In gadgetfs documentation I find no mention of endpoints:
> https://www.kernel.org/doc/Documentation/usb/gadget_configfs.txt
>
> Is it possible to create endpoints using gadgetfs ?
>
The question need to be phrased differently:
Is it pos
Hi,
i got an info that my issue was caused by this commit:
https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=217491487c43892318c18b6dcafe33b6353efd40
Patch is in progress...
Regards Frank
Am 4. September 2018 13:16:12 MESZ schrieb Frank Wunderlich :
>Hi, thank you f
Hello,
Le jeu. 19 juil. 2018 à 09:24, Felipe Balbi
a écrit :
>
>
> Hi,
>
> lemag...@gmail.com writes:
> > From: Pierre Le Magourou
> >
> > We can't wait for END_OF_TRANSFER event in dwc3_gadget_ep_dequeue()
> > because it can be called in an interruption context.
> >
> > TRBs are now cleared aft
Hi,
Ranran writes:
>> Ranran writes:
>> > > A fix for my last comment:
>> >> > usb device controller should be supported with conga-MA5 (contains
>> >> > Intel's appolo lake), so I am still not sure why I find /sys/class/udc
>> >> > empty.
>> >> > In congatec MA-5 document it is said:
>> >> >
On 04.09.2018 16:14, Frank Wunderlich wrote:
Hi,
i got an info that my issue was caused by this commit:
https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=217491487c43892318c18b6dcafe33b6353efd40
Patch is in progress...
That patch has been there since 4.13
If 4.16
Hi,
On 04-09-18 14:13, Andy Shevchenko wrote:
On Tue, Sep 4, 2018 at 2:22 PM Heikki Krogerus
wrote:
Hi,
These patches will introduce a few improvements to the USB Type-C
support on Intel CHT platform. In this series I'm preparing Intel CHT
mux handling for DisplayPort Alt Mode support, but p
Hi,
On Fri, Aug 31, 2018 at 06:35:50AM +, Takashi Matsuzawa wrote:
> Hello.
> I just confirmed what I wanted to see.
> I could do lsusb to list A-device (from b_host) and B-device (from a_host).
> Suspending from either side kicked role change between A-device and B-device
> (in both directio
usb_hc_died() should only be called once, and with the primary HCD
as parameter. It will mark both primary and secondary hcd's dead.
Remove the extra call to usb_cd_died with the shared hcd as parameter.
Fixes: ff9d78b36f76 ("USB: Set usb_hcd->state and flags for shared roothubs")
Signed-off-by:
this fixes the issue:
adding the following lines to drivers/usb/host/xhci-mem.c line:1616
if (xhci->quirks & XHCI_MTK_HOST) {
in_ep_ctx->reserved[0] = out_ep_ctx->reserved[0];
in_ep_ctx->reserved[1] = out_ep_ctx->reserved[1];
}
commit below is wrong...i got the response:
This
On 04.09.2018 17:51, Frank Wunderlich wrote:
this fixes the issue:
adding the following lines to drivers/usb/host/xhci-mem.c line:1616
if (xhci->quirks & XHCI_MTK_HOST) {
in_ep_ctx->reserved[0] = out_ep_ctx->reserved[0];
in_ep_ctx->reserved[1] = out_ep_ctx->reserved[1];
}
com
Some hardware implementations require to configure pins differently
according to the USB role (host/device), this can be an update of the
pins routing or a simple GPIO value change.
This patch introduces new optional "host" and "device" pinctrls.
If these pinctrls are defined by the device, they a
Some hardware implementations require to configure pins differently
according to the USB role (host/device), this can be an update of the
pins routing or a simple GPIO value change.
This patch introduces new optional "host" and "device" pinctrls.
If these pinctrls are defined by the device, they a
The ChipIdea IRQ is disabled before scheduling the otg work and
re-enabled on otg work completion. However if the job is already
scheduled we have to undo the effect of disable_irq int order to
balance the IRQ disable-depth value.
Fixes: be6b0c1bd0be ("usb: chipidea: using one inline function to c
Phy power on/off cycle can happen several times during device life.
We then need to balance the extcon notifier registration accordingly.
Fixes: f0b5c2c96370 ("phy: qcom-usb-hs: Replace the extcon API")
Signed-off-by: Loic Poulain
---
v2: don't use devres version (power-on always followed by pow
At OTG work running time, it's possible that several events need to be
addressed (e.g. ID and VBUS events). The current implementation handles
only one event at a time which leads to ignoring the other one. Fix it.
Signed-off-by: Loic Poulain
---
v2: v3: no change
drivers/usb/chipidea/otg.c |
The Dragonboard-410c is able to act either as USB Host or Device.
The role can be determined at runtime via the USB_HS_ID pin which is
derived from the micro-usb port VBUS pin.
In Host role, SoC USB D+/D- are routed to the onboard USB 2.0 HUB.
In Device role, SoC USB D+/D- are routed to the USB 2.
Hi Alan,
Another question. According to the USB spec:
"""
The Data stage of a control transfer from an endpoint to the host is
complete when the endpoint does one of the following:
* Has transferred exactly the amount of data specified during the Setup stage
* Transfers a packet with a payload si
On Tue, 4 Sep 2018, Johan Hovold wrote:
> On Tue, Sep 04, 2018 at 12:21:09PM +0200, Oliver Neukum wrote:
> > On Di, 2018-09-04 at 11:31 +0200, Johan Hovold wrote:
> > > On Tue, Sep 04, 2018 at 10:44:41AM +0200, Oliver Neukum wrote:
> > > > For those people who run with panic_on_warn a WARN() trigg
On Tue, 4 Sep 2018, Ranran wrote:
> On Tue, Sep 4, 2018 at 2:36 PM Ranran wrote:
> >
> > Hello,
> >
> > In gadgetfs documentation I find no mention of endpoints:
> > https://www.kernel.org/doc/Documentation/usb/gadget_configfs.txt
> >
> > Is it possible to create endpoints using gadgetfs ?
> >
>
On Tue, 4 Sep 2018, Mathias Nyman wrote:
> usb_hc_died() should only be called once, and with the primary HCD
> as parameter. It will mark both primary and secondary hcd's dead.
>
> Remove the extra call to usb_cd_died with the shared hcd as parameter.
>
> Fixes: ff9d78b36f76 ("USB: Set usb_hcd-
On Tue, 4 Sep 2018, Andrey Konovalov wrote:
> Hi Alan,
>
> Another question. According to the USB spec:
>
> """
> The Data stage of a control transfer from an endpoint to the host is
> complete when the endpoint does one of the following:
> * Has transferred exactly the amount of data specified
On Mon, 3 Sep 2018, Mathias Nyman wrote:
> The steps taken by usb core to set a new interface is very different from
> what is done on the xHC host side.
>
> xHC hardware will do everything in one go. One command is used to set up
> new endpoints, free old endpoints, check bandwidth, and run the
tree: https://git.kernel.org/pub/scm/linux/kernel/git/jikos/hid.git
for-4.20/multitouch
head: 93c61d2e6bc4849a5527e32568479ff67154870e
commit: 93c61d2e6bc4849a5527e32568479ff67154870e [1/1] HID: multitouch:
simplify the application retrieval
config: x86_64-randconfig-x018-201835 (attached as
On Wed, 5 Sep 2018, kbuild test robot wrote:
> tree: https://git.kernel.org/pub/scm/linux/kernel/git/jikos/hid.git
> for-4.20/multitouch
> head: 93c61d2e6bc4849a5527e32568479ff67154870e
> commit: 93c61d2e6bc4849a5527e32568479ff67154870e [1/1] HID: multitouch:
> simplify the application retri
Hello.
>Is commit [1] reverted or not in this experiment?
In fact I noticed I am looking into TI kernel which is distributed in official
debian image for pocketbeagle.
So, the behavior may not be the same as mainline kernel code.
I think I continue look into what I have now, and later check main
> v2: v3: no change
>
> drivers/usb/chipidea/otg.c | 9 ++---
> 1 file changed, 6 insertions(+), 3 deletions(-)
>
> diff --git a/drivers/usb/chipidea/otg.c b/drivers/usb/chipidea/otg.c index
> db4ceff..f25d482 100644
> --- a/drivers/usb/chipidea/otg.c
> +++ b/drivers/usb/chipidea/otg.c
>
Hi Johan,
On 4 September 2018 at 14:47, Johan Hovold wrote:
> On Sat, Aug 04, 2018 at 12:17:15PM +0200, Loic Poulain wrote:
>> Some FTDI devices like FTX or FT232R support CBUS Bit Bang mode on CBUS
>> pins, allowing host to control them via simple USB control transfers.
>> To make use of a CBUS
Hi Raghu,
Am 04.09.2018 um 06:29 schrieb raghuramchary.jallipa...@microchip.com:
>> +// SPDX-License-Identifier: GPL-2.0+
>> +/* Copyright (C) 2015 Microchip Technology */
> Can we merge both in single comment line?
i don't think we can do this. I'm simply following this guideline [1].
How abou
> i don't think we can do this. I'm simply following this guideline [1].
>
> How about this:
>
> // SPDX-License-Identifier: GPL-2.0+
> /*
> * Copyright (C) 2015 Microchip Technology
> */
>
> [1] - https://www.kernel.org/doc/html/v4.18/process/license-rules.html
>
Thank you.
Looks good to me.
On Mon, Sep 03, 2018 at 12:51:59PM -0700, Randy Dunlap wrote:
> From: Randy Dunlap
>
> Fix kernel-doc warning for missing struct member description:
>
> ../include/linux/mod_devicetable.h:763: warning: Function parameter or member
> 'driver_data' not described in 'typec_device_id'
>
> Fixes: 8
Hi All,
Ping!
Just thought of giving a friendly remainder for this patch series. Does these
patches looks okay, can we proceed with them? Please provide me your valuable
suggestions.
Thanks,
Anurag Kumar Vulisha
>-Original Message-
>From: Anurag Kumar Vulisha [mailto:anurag.kumar.vuli.
Hello!
On 9/4/2018 5:44 AM, Jaejoong Kim wrote:
Many drivers with tty use the tty_stand_install(). But, there is no
need to handle the error, since it always returns 0. So, change the
return type of tty_standard_install() and tty_port_install() to void
type and remove unnecessary exception hand
On Sat, Aug 25, 2018 at 10:47:44PM +0200, Karoly Pados wrote:
> This patch uses the CBUS bitbang mode of the device, so there is
> no conflict between the GPIO and VCP functionality.
Please make the commit message self-contained (e.g. don't rely on the
summary, or mail Subject, even if you feel li
On 30.08.2018 04:09, Chunfeng Yun wrote:
Hi,
On Wed, 2018-08-29 at 12:13 +0300, Sergei Shtylyov wrote:
On 8/29/2018 5:55 AM, Chunfeng Yun wrote:
Give USB3 devices a better chance to enumerate at USB3 speeds if
they are connected to a suspended host.
Porting from "671ffdf xhci: resume USB 3 roo
There is no need for this strcpy because alloc_etherdev() already
does this job.
Signed-off-by: Stefan Wahren
Reviewed-by: Raghuram Chary Jallipalli
---
drivers/net/usb/lan78xx.c | 1 -
1 file changed, 1 deletion(-)
diff --git a/drivers/net/usb/lan78xx.c b/drivers/net/usb/lan78xx.c
index 3f70b
This patch series contains some minor improvements for the lan78xx
driver.
Changes in V2:
- Keep Copyright comment as multi-line
- Add Raghuram's Reviewed-by
Stefan Wahren (4):
net: lan78xx: Bail out if lan78xx_get_endpoints fails
net: lan78xx: Drop unnecessary strcpy in lan78xx_probe
net:
We need to bail out if lan78xx_get_endpoints() fails, otherwise the
result is overwritten.
Fixes: 55d7de9de6c3 ("Microchip's LAN7800 family USB 2/3 to 10/100/1000
Ethernet")
Signed-off-by: Stefan Wahren
Reviewed-by: Raghuram Chary Jallipalli
---
drivers/net/usb/lan78xx.c | 5 +
1 file chan
Adopt the SPDX license identifier headers to ease license compliance
management.
Signed-off-by: Stefan Wahren
---
drivers/net/usb/lan78xx.c | 14 +-
drivers/net/usb/lan78xx.h | 14 +-
2 files changed, 2 insertions(+), 26 deletions(-)
diff --git a/drivers/net/usb/lan78xx.
This patch makes some declaration more consistent.
Signed-off-by: Stefan Wahren
Reviewed-by: Raghuram Chary Jallipalli
---
drivers/net/usb/lan78xx.c | 14 +++---
1 file changed, 7 insertions(+), 7 deletions(-)
diff --git a/drivers/net/usb/lan78xx.c b/drivers/net/usb/lan78xx.c
index e1c
Thanks for the review, I am on the road most of this week, but I will submit
a new patch this weekend with all your feedback incorporated. Until then here
are my inputs / answers to some of your points.
> Actually, after thinking about this some more, it may be better to just
> configure all pins
>>> + priv->gc.ngpio = 4;
>>
>> Shouldn't this be handled the other way round? IIRC there are two FTX
>> device types with four pins, and one type where only one pin is
>> accessible.
>
> There are 4 devices with 1 GPIO, 1 device with 2 GPIOs, 2 devices with 4
> GPIOs,
> and 1 device with 6 GPIO
Hello,
syzbot found the following crash on:
HEAD commit:420f51f4ab6b Merge tag 'arm64-fixes' of git://git.kernel.o..
git tree: upstream
console output: https://syzkaller.appspot.com/x/log.txt?x=126a6f0e40
kernel config: https://syzkaller.appspot.com/x/.config?x=531a917630d2a492
da
From: "Gustavo A. R. Silva"
Date: Mon, 3 Sep 2018 13:48:45 -0500
> In preparation to enabling -Wimplicit-fallthrough, mark switch cases
> where we are expecting to fall through.
>
> Addresses-Coverity-ID: 1077614 ("Missing break in switch")
> Signed-off-by: Gustavo A. R. Silva
Applied, thank y
This is a series of patches that implements a driver for the control
peripheral, EUD (Embedded USB Debugger). The EUD is a mini-USB hub
implemented on chip to support the USB-based debug and trace capabilities.
Apart from debug capabilities, EUD has a control peripheral. Control
Peripheral is on
Add support for control peripheral of EUD (Embedded USB Debugger) to
listen to events such as USB attach/detach, charger enable/disable, pet
EUD to indicate software is functional.
Signed-off-by: Satya Durga Srinivasu Prabhala
Signed-off-by: Prakruthi Deepak Heragu
---
drivers/soc/qcom/Kconfig
Documentation for Embedded USB Debugger (EUD) device tree bindings.
Signed-off-by: Satya Durga Srinivasu Prabhala
Signed-off-by: Prakruthi Deepak Heragu
---
.../devicetree/bindings/soc/qcom/qcom,msm-eud.txt | 41 ++
1 file changed, 41 insertions(+)
create mode 100644 Docum
Hi Anurag,
On 8/17/2018 5:25 AM, Anurag Kumar Vulisha wrote:
> Availability of TRB's are calculated using dwc3_calc_trbs_left(), which
> determines available TRB's based on the HWO bit set in a TRB.
>
> __dwc3_prepare_one_trb() is called with a TRB which needs to be prepared
> for transfer. This _
On 8/17/2018 5:26 AM, Anurag Kumar Vulisha wrote:
> To start transfer with another stream id, controller needs to free
> previously allocated transfer resource. This will be automatically
> done by the controller at the time of XferComplete Event. This
> patch updates the code to issue XferComplete
On 09/05/2018, 03:08 AM, Jaejoong Kim wrote:
> > @@ -688,7 +688,7 @@ extern int tty_port_close_start(struct
> tty_port *port,
> > extern void tty_port_close_end(struct tty_port *port, struct
> tty_struct *tty);
> > extern void tty_port_close(struct tty_port *port,
> >
On 8/17/2018 5:25 AM, Anurag Kumar Vulisha wrote:
> According to dwc3 databook when streams are used, it may be possible
> for the host and device become out of sync, where device may wait for
> host to issue prime transcation and host may wait for device to issue
> erdy. To avoid such deadlock, ti
78 matches
Mail list logo
