Issue: When the USB controller is configured as a USB device
mode, the device initiates low power when an ACK is pending for a
data packet (DP). When operating in SuperSpeed mode and when the
internal condition for low power (u1/u2) is satisfied, the device
initiates u1/u2 even though it has just r
Hi,
On 2017년 09월 29일 11:03, Yoshihiro Shimoda wrote:
> Hi,
>
>> From: Chanwoo Choi
>> Sent: Friday, September 29, 2017 9:02 AM
>>
> < snip >
>> drivers/phy/renesas/phy-rcar-gen3-usb2.c | 2 +-
> < snip >
>> drivers/usb/gadget/udc/renesas_usb3.c | 2 +-
>
> These two drivers need
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
---
drivers/usb/serial/qcserial.c | 4
1 file changed, 4 insertions(+)
diff --git a/drivers/usb/seria
Hi all, this is Philip who maintains the 0-Day kernel test service. Thanks for
subscribing to 0-Day kernel testing. We will have lab power down from Oct 1
to Oct 5, so that the service will be shut down from Asia Pacific Time Sep 30
3PM
and will recover from Oct 6 as soon as we can. Sorry for any
Hi,
> From: Chanwoo Choi
> Sent: Friday, September 29, 2017 9:02 AM
>
< snip >
> drivers/phy/renesas/phy-rcar-gen3-usb2.c | 2 +-
< snip >
> drivers/usb/gadget/udc/renesas_usb3.c | 2 +-
These two drivers need the modification.
But...
< snip >
> diff --git a/drivers/usb/renesas
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 device.
- 'extcon consumer device' gets the change state/properties
Hello,
I just saw a post about VIA controllers triggering IOMMU errors.
Just want to also point out that the ax88179 will also trigger PTE read
errors when using the vendor's driver.
I'm nowhere near an expert but I remember seeing that 'TD fragment' is
supported now or some such, which I take
Grant,
On Thu, Sep 28, 2017 at 11:35 AM, Grant Grundler wrote:
> This linksys dongle by default comes up in cdc_ether mode.
> This patch allows r8152 to claim the device:
>Bus 002 Device 002: ID 13b1:0041 Linksys
>
> Signed-off-by: Grant Grundler
> ---
> drivers/net/usb/cdc_ether.c | 10 +++
Hi,
On Thu, Sep 28, 2017 at 3:28 PM, Rustad, Mark D wrote:
>
>> On Sep 27, 2017, at 9:39 AM, Grant Grundler wrote:
>>
>> On Wed, Sep 27, 2017 at 12:15 AM, Oliver Neukum wrote:
>>> Am Dienstag, den 26.09.2017, 08:19 -0700 schrieb Doug Anderson:
I know that for at least some of the adap
> On Sep 27, 2017, at 9:39 AM, Grant Grundler wrote:
>
> On Wed, Sep 27, 2017 at 12:15 AM, Oliver Neukum wrote:
>> Am Dienstag, den 26.09.2017, 08:19 -0700 schrieb Doug Anderson:
>>>
>>> I know that for at least some of the adapters in the CDC Ethernet
>>> blacklist it was claimed that the CDC
On Thu, 28 Sep 2017 14:09:04 +0300
Felipe Balbi wrote:
>
>
> Actually, I think we should go the other way around:
>
> psic = read_psic_from_register();
>
> if (psic)
> setup_supported_speeds_based_on_psic(xhci, psic);
> else
> setup_supported_speeds_using_default_mappings(xhci);
>
This linksys dongle by default comes up in cdc_ether mode.
This patch allows r8152 to claim the device:
Bus 002 Device 002: ID 13b1:0041 Linksys
Signed-off-by: Grant Grundler
---
drivers/net/usb/cdc_ether.c | 10 ++
drivers/net/usb/r8152.c | 2 ++
2 files changed, 12 insertions(+
Hi!
I've got the following report while fuzzing the kernel with syzkaller.
On commit dc972a67cc54585bd83ad811c4e9b6ab3dcd427e (4.14-rc2+).
There's no check on the connection_info->num_ports value when
iterating over ports.
usb 1-1: Handspring Visor / Palm OS: port 162, is for unknown use
usb 1-
On Thu, 28 Sep 2017, Andrey Konovalov wrote:
> Hi!
>
> I've got the following report while fuzzing the kernel with syzkaller.
>
> On commit dc972a67cc54585bd83ad811c4e9b6ab3dcd427e (4.14-rc2+).
>
> It seems that out pointer ends up being NULL and kernel crashes on
> access to out->desc.bEndpoin
Hi Manu,
On Thu, Sep 28, 2017 at 09:30:38AM +0530, Manu Gautam wrote:
> On 9/28/2017 12:46 AM, Jack Pham wrote:
> > On Wed, Sep 27, 2017 at 10:57:41AM -0700, Jack Pham wrote:
> >> On Wed, Sep 27, 2017 at 02:29:10PM +0530, Manu Gautam wrote:
> >>> VBUS signal coming from PHY must be asserted in dev
Hi,
On Wed, Sep 27, 2017 at 5:07 PM, Grant Grundler wrote:
>>> #define DELL_VENDOR_ID 0x413C
>>> #define REALTEK_VENDOR_ID 0x0bda
>>> #define SAMSUNG_VENDOR_ID 0x04e8
>>> +#define LINKSYS_VENDOR_ID 0x13b1
>>> #define LENOVO_VENDOR_ID 0x17ef
>>
>> Slight nit that "
From: Maciej Purski
Currently MHL chip must be turned on permanently to detect MHL cable. It
duplicates micro-USB controller's (MUIC) functionality and consumes
unnecessary power. Lets use extcon attached to MUIC to enable MHL chip
only if it detects MHL cable.
Signed-off-by: Maciej Purski
Sign
Since extcon property is not allowed in DT, extcon subsystem requires
another way to get extcon device. Lets try the simplest approach - get
edev by of_node.
Signed-off-by: Andrzej Hajda
---
drivers/extcon/extcon.c | 44 ++--
include/linux/extcon.h | 6 +
Hi,
This patchset introduces USB connector bindings, together with working example.
I have added comments in relevant patches to describe possible issues.
Regards
Andrzej
Andrzej Hajda (3):
dt-bindings: add bindings for USB physical connector
arm64: dts: exynos: add micro-USB connector node
Since USB connector bindings are available we can describe it on TM2(e).
Signed-off-by: Andrzej Hajda
---
.../boot/dts/exynos/exynos5433-tm2-common.dtsi | 47 --
1 file changed, 44 insertions(+), 3 deletions(-)
diff --git a/arch/arm64/boot/dts/exynos/exynos5433-tm2-commo
These bindings allows to describe most known standard USB connectors
and it should be possible to extend it if necessary.
USB connectors, beside USB can be used to route other protocols,
for example UART, Audio, MHL. In such case every device passing data
through the connector should have appropria
On Thu, Sep 28, 2017 at 03:22:35PM +0300, Felipe Balbi wrote:
> Heikki Krogerus writes:
> > +MODULE_DESCRIPTION("DisplayPort Alternate Mode");
>
> huh?
Copy paste :-)
Cheers,
--
heikki
--
To unsubscribe from this list: send the line "unsubscribe linux-usb" in
the body of a message to majord.
Hi,
Heikki Krogerus writes:
> +MODULE_DESCRIPTION("DisplayPort Alternate Mode");
huh?
--
balbi
signature.asc
Description: PGP signature
Hi Oliver
That tells us practically nothing. If you press any button nothing
happens? Anything in dmesg?
Regards
Oliver
There is nothing on dmesg. I used dmesg -wH to view output as/when
anything was occuring and nothing did. Once I use a DPI switch the
cursor stops
Example alternate mode driver.
Meant only to give an idea how a real alternate mode driver
*could* look like!
Signed-off-by: Heikki Krogerus
---
drivers/usb/typec/Kconfig | 2 +
drivers/usb/typec/Makefile | 1 +
drivers/usb/typec/altmodes/Kconfig | 9 +++
drivers/usb/t
Bus for binding SVID specific drivers to the altnernate mode
devices.
Signed-off-by: Heikki Krogerus
---
drivers/usb/typec/Makefile | 2 +
drivers/usb/typec/altmode.c| 249 +
drivers/usb/typec/altmode.h| 46 ++
drivers/us
Hi guys,
The bus allows SVID specific communication with the partners to be
handled in separate drivers for each alternate mode.
Alternate mode handling happens with two separate logical devices:
1. Partner alternate mode devices which represent the alternate modes
on the partner. The driver f
I've been getting xhci_hcd probe failures since 4.13, seemingly caused by DMAR
faults:
xhci_hcd :03:00.0: xHCI Host Controller
xhci_hcd :03:00.0: new USB bus registered, assigned bus number 2
DMAR: DRHD: handling fault status reg 3
DMAR: [DMA Read] Request device [03:00.0]
Hi!
I've got the following report while fuzzing the kernel with syzkaller.
On commit dc972a67cc54585bd83ad811c4e9b6ab3dcd427e (4.14-rc2+).
It seems that out pointer ends up being NULL and kernel crashes on
access to out->desc.bEndpointAddress.
gadgetfs: bound to dummy_udc driver
usb 1-1: new fu
Hi,
Mathias Nyman writes:
[snip]
>> Like I said, while I patched my kernel and now my xHCI controllers
>> are recognized as supporting 10 Gb/s, the SSDs with USB-SATA bridges
>> that I have connected are still not recognized as also supporting 10
>> Gb/s. I believe that the problem is caused b
On 27.09.2017 23:15, Adrian Bocaniciu wrote:
On Wed, 27 Sep 2017 11:03:41 +0300
Mathias Nyman wrote:
Ok, please let me know which register you refer to, I'd like to get this fixed
as soon as possible.
Based on what you say I suspect that you talk about the SBRN (Serial bus
release number).
The hid descriptor identifies the length and type of subordinate
descriptors for a device. If the received hid descriptor is smaller than
the size of the struct hid_descriptor, it is possible to cause
out-of-bounds.
In addition, if bNumDescriptors of the hid descriptor have an incorrect
value, thi
Hi,
On 28/09/2017 at 11:46:19 +0200, Romain Izard wrote:
> While the core of the backup mode for SAMA5D2 has been integrated in
> v4.13, it is far from complete. Individual controllers in the chip have
> drivers that do not support the reset of the registers during suspend,
> and they need to be a
The contents of the System Clock Status Register (SCSR) needs to be
restored into the System Clock Enable Register (SCER).
As the bootloader will restore some clocks by itself, the issue can be
missed as only the USB controller, the LCD controller, the Image Sensor
controller and the programmable
From: Romain Izard
When an AT91 programmable clock is declared in the device tree, register
it into the Power Management Controller driver. On entering suspend mode,
the driver saves and restores the Programmable Clock registers to support
the backup mode for these clocks.
Signed-off-by: Romain
Wait for the syncronization of all clocks when resuming, not only the
UPLL clock. Do not use regmap_read_poll_timeout, as it will call BUG()
when interrupts are masked, which is the case in here.
Signed-off-by: Romain Izard
Acked-by: Ludovic Desroches
Acked-by: Nicolas Ferre
---
drivers/clk/at
The atmel serial port driver reported the following warning on suspend:
atmel_usart f802.serial: ttyS1: Unable to drain transmitter
As the ATMEL_US_TXEMPTY status bit in ATMEL_US_CSR is always cleared
when the transmitter is disabled, we need to know the transmitter's
state to return the real
The controller used by a flexcom module is configured at boot, and left
alone after this. As the configuration will be lost after backup mode,
restore the state of the flexcom driver on resume.
Signed-off-by: Romain Izard
Acked-by: Nicolas Ferre
Tested-by: Nicolas Ferre
---
drivers/mfd/atmel-f
When an Atmel SoC is suspended with the backup mode, the USB bus will be
powered down. As this is expected, do not return an error to the driver
core when ehci_resume detects it.
Signed-off-by: Romain Izard
Acked-by: Nicolas Ferre
---
drivers/usb/host/ehci-atmel.c | 3 ++-
1 file changed, 2 ins
During backup mode, the contents of all registers will be cleared as the
SoC will be completely powered down. For a product that boots on NAND
Flash memory, the bootloader will obviously use the related controller
to read the Flash and correct any detected error in the memory, before
handling back
Save and restore registers for the PWM on suspend and resume, which
makes hibernation and backup modes possible.
Signed-off-by: Romain Izard
Acked-by: Nicolas Ferre
---
drivers/pwm/pwm-atmel-tcb.c | 63 +++--
1 file changed, 61 insertions(+), 2 deletions(
While the core of the backup mode for SAMA5D2 has been integrated in
v4.13, it is far from complete. Individual controllers in the chip have
drivers that do not support the reset of the registers during suspend,
and they need to be adapted to handle it.
The first patch uses the clock wakeup code f
Hi,
Kees Cook writes:
> The .data assignment appears to be redundant to the WORK_STOP bit for
> stopping the timer. Also, it appears this timer is entirely unused
> as it is only ever started under #define VERBOSE, which is explicitly
> undefined.
>
> Cc: Felipe Balbi
> Cc: Greg Kroah-Hartman
Kees Cook writes:
> If the probe fails, udc_remove() will not be called, so there is no
> reason to make del_timer_sync() calls conditional. As a result, use of
> the .data field can be dropped, in support of making removing this field
> entirely from struct timer_list.
>
> Cc: Felipe Balbi
> Cc
Hi,
Alan Stern writes:
> Felipe and Greg:
>
> In the following series of changes for the dummy-hcd driver, the first
> three patches correct issues that are serious enough to merit inclusion
> in the -stable kernels:
>
> 1/5 fixes a bug that prevents g_mass_storage from working
> co
2017-09-27 23:29 GMT+09:00 Alan Stern :
> On Wed, 27 Sep 2017, Michel Hermier wrote:
>
>> Le 27 sept. 2017 07:42, "Alan Stern" a écrit :
>
>> > - for (n = 0; n < hdesc->bNumDescriptors; n++)
>> > + num_descriptors = min_t(int, hdesc->bNumDescriptors,
>> > +
46 matches
Mail list logo
