The dwm-158 interface 4 and 5 doesn't answer to the AT commands
and doesn't appears a option interface.
Tested on openwrt distribution (kernel 4.14 using the old blacklist
definitions).
Signed-off-by: Giuseppe Lippolis
---
drivers/usb/serial/option.c | 3 ++-
1 file changed, 2 insertions(+), 1 d
The dwm-158 interface 4 and 5 doesn't answer to the AT commands
and doesn't appears a option interface.
Tested on openwrt distribution (kernel 4.14 using the old blacklist
definitions).
Signed-off-by: Giuseppe Lippolis
---
drivers/usb/serial/option.c | 3 ++-
1 file changed, 2 insertions(+), 1 d
Hi Stefan,
On 4/18/2018 1:11 AM, Stefan Wahren wrote:
> Hi Grigor,
>
>> Grigor Tovmasyan hat am 16. April 2018 um
>> 12:16 geschrieben:
>>
>>
>> In dwc2_gadget_init() we allocate EP0 request via
>> dwc2_hsotg_ep_alloc_request(). After that there are
>> usb_add_gadget_udc() call and if it failed
On 4/23/2018 14:03, Giuseppe Lippolis wrote:
The dwm-158 interface 4 and 5 doesn't answer to the AT commands
and doesn't appears a option interface.
Tested on openwrt distribution (kernel 4.14 using the old blacklist
definitions).
Signed-off-by: Giuseppe Lippolis
---
drivers/usb/serial/option
On Fri, 20 Apr 2018 09:35:54 + Peter Chen wrote:
>
> > >
> > > Sorry to reply late, are you really care 2KB code side? Since many
> > > users use EXTCON to handle vbus and id, it is hard just delete it. I
> > > could accept patch for your specific platforms, like:
> > >
> > > + select EXTCON
On Sun, Apr 22, 2018 at 09:41:56PM +0200, Martin Blumenstingl wrote:
> Hi Greg,
>
> On Sun, Apr 22, 2018 at 3:01 PM, Greg KH wrote:
> > On Wed, Apr 18, 2018 at 09:39:51PM +0200, Martin Blumenstingl wrote:
> >> This clarifies the license of the code. While here also add an include
> >> guard to th
On 22 April 2018 21:58, Adam Thomson wrote:
> On 22 April 2018 15:05, Greg Kroah-Hartman wrote:
>
> > On Fri, Mar 23, 2018 at 10:12:20AM +, Adam Thomson wrote:
> > > This commit adds code to handle requesting of PPS APDOs. Switching
> > > between standard PDOs and APDOs, and re-requesting an
On Fri, Apr 20, 2018 at 10:26:08AM -0700, Guenter Roeck wrote:
> On Wed, Apr 18, 2018 at 03:34:09PM +0300, Heikki Krogerus wrote:
> > If the I2C adapter that the PD controller is attached to
> > does not support SMBus protocol, the driver needs to handle
> > block reads separately. The first byte r
On Mon, Apr 23, 2018 at 07:49:38AM +, Adam Thomson wrote:
> On 22 April 2018 21:58, Adam Thomson wrote:
>
> > On 22 April 2018 15:05, Greg Kroah-Hartman wrote:
> >
> > > On Fri, Mar 23, 2018 at 10:12:20AM +, Adam Thomson wrote:
> > > > This commit adds code to handle requesting of PPS APD
On Mon, Apr 23, 2018 at 02:14:01PM +0700, Lars Melin wrote:
> On 4/23/2018 14:03, Giuseppe Lippolis wrote:
> > The dwm-158 interface 4 and 5 doesn't answer to the AT commands
> > and doesn't appears a option interface.
> > Tested on openwrt distribution (kernel 4.14 using the old blacklist
> > defi
Am 23.04.2018 um 09:05 schrieb Grigor Tovmasyan:
Hi Stefan,
On 4/18/2018 1:11 AM, Stefan Wahren wrote:
Hi Grigor,
Grigor Tovmasyan hat am 16. April 2018 um 12:16
geschrieben:
In dwc2_gadget_init() we allocate EP0 request via
dwc2_hsotg_ep_alloc_request(). After that there are
usb_add_gad
Hello!
s/optrion/option/ in the subject. And please add spaces after each colon.
MBR, Sergei
--
To unsubscribe from this list: send the line "unsubscribe linux-usb" in
the body of a message to majord...@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
On Mon, Apr 23, 2018 at 11:58:18AM +0300, Sergei Shtylyov wrote:
> Hello!
>
> s/optrion/option/ in the subject. And please add spaces after each colon.
Yeah, I fixed that up myself before applying this time.
Thanks,
Johan
--
To unsubscribe from this list: send the line "unsubscribe linux-usb
hi,
On 2018-04-04 19:28, Greg KH wrote:
On Wed, Apr 04, 2018 at 06:41:41PM +0530, tnim...@codeaurora.org wrote:
On 2018-04-04 18:07, Greg KH wrote:
> On Wed, Apr 04, 2018 at 05:14:50PM +0530, tnim...@codeaurora.org wrote:
> > Hi Oliver/Greg,
> >
> > I am able to duplicated the UAS issue on 4.16
Hello,
I would like to inform you about a bug that Gentoo bug-wranglers can't handle:
bugs(dot)gentoo(dot)org(slash)612704
Sincerely,
Stefan Kalis
PS
It's possible that I could be of service in solving the issue because
I got the respective hardware.
--
To unsubscribe from this list: send the
On Mon, Apr 23, 2018 at 12:08:21PM +0200, Stefan Kalis wrote:
> Hello,
>
> I would like to inform you about a bug that Gentoo bug-wranglers can't handle:
>
> bugs(dot)gentoo(dot)org(slash)612704
That's really hard, if not impossible, to follow.
Please just post the needed information here, don'
On 23 April 2018 09:25, Greg Kroah-Hartman wrote:
> On Mon, Apr 23, 2018 at 07:49:38AM +, Adam Thomson wrote:
> > On 22 April 2018 21:58, Adam Thomson wrote:
> >
> > > On 22 April 2018 15:05, Greg Kroah-Hartman wrote:
> > >
> > > > On Fri, Mar 23, 2018 at 10:12:20AM +, Adam Thomson wrote:
On Mon, Apr 23, 2018 at 11:06:25AM +, Adam Thomson wrote:
> On 23 April 2018 09:25, Greg Kroah-Hartman wrote:
>
> > On Mon, Apr 23, 2018 at 07:49:38AM +, Adam Thomson wrote:
> > > On 22 April 2018 21:58, Adam Thomson wrote:
> > >
> > > > On 22 April 2018 15:05, Greg Kroah-Hartman wrote:
>
OK.
I own a Renesas PCI-Card that offers 4 USB3-Ports and that worked well
with Linux-Kernels up to 4.8. Beginning with kernel 4.9 it was not
correctly initialized anymore and the problem still persists with
kernel 4.16.2 that I have recently tested.
After a failed start the PCI-situation looks li
On 23 April 2018 12:28, Greg Kroah-Hartman wrote:
> On Mon, Apr 23, 2018 at 11:06:25AM +, Adam Thomson wrote:
> > On 23 April 2018 09:25, Greg Kroah-Hartman wrote:
> >
> > > On Mon, Apr 23, 2018 at 07:49:38AM +, Adam Thomson wrote:
> > > > On 22 April 2018 21:58, Adam Thomson wrote:
> > >
Am Donnerstag, den 19.04.2018, 20:18 +0530 schrieb Tushar Nimkar:
> On 2018-04-19 14:15, Oliver Neukum wrote:
> > Am Mittwoch, den 18.04.2018, 12:44 +0530 schrieb Tushar Nimkar:
> > > On 2018-04-17 12:03, Tushar Nimkar wrote:
> >
> > Hi,
> >
> > > I have doubt that sequential scan(scsi_sequential
In preparation to enabling -Wimplicit-fallthrough, mark switch cases
where we are expecting to fall through.
Addresses-Coverity-ID: 1468266 ("Missing break in switch")
Signed-off-by: Gustavo A. R. Silva
---
drivers/usb/core/hcd.c | 1 +
1 file changed, 1 insertion(+)
diff --git a/drivers/usb/co
hi,
On 2018-04-23 18:20, Oliver Neukum wrote:
Am Donnerstag, den 19.04.2018, 20:18 +0530 schrieb Tushar Nimkar:
On 2018-04-19 14:15, Oliver Neukum wrote:
> Am Mittwoch, den 18.04.2018, 12:44 +0530 schrieb Tushar Nimkar:
> > On 2018-04-17 12:03, Tushar Nimkar wrote:
>
> Hi,
>
> > I have doubt th
On Mon, Apr 23, 2018 at 12:47:47PM +, Adam Thomson wrote:
> On 23 April 2018 12:28, Greg Kroah-Hartman wrote:
>
> > On Mon, Apr 23, 2018 at 11:06:25AM +, Adam Thomson wrote:
> > > On 23 April 2018 09:25, Greg Kroah-Hartman wrote:
> > >
> > > > On Mon, Apr 23, 2018 at 07:49:38AM +, Adam
Hi,
could this patch be picked up, please? Or if for some reason it cannot
be, could the commit that introduced the regression be reverted?
It's causing some tests in KernelCI to fail:
https://storage.kernelci.org/next/master/next-20180423/arm/multi_v7_defconfig/lab-collabora/sleep-r
On Mon, Apr 23, 2018 at 11:14:55AM +0530, Tushar Nimkar wrote:
> On 2018-04-21 00:03, Bin Liu wrote:
> >Hi,
> >
> >On Tue, Mar 20, 2018 at 02:28:00PM -0700, Paul Zimmerman wrote:
> >>Forgot to CC linux-usb.
> >>
> >>
> >> Forwarded Message
> >>Subject: Re: howto debug xhci driver?
From: Johan Hovold
Since commit 39cee200c23e ("usb: musb: core: call init and shutdown for
the usb phy") the musb USB phy is initialised by musb_core, but the
original initialisation in the dsps-glue init callback was left in
place resulting in two calls to phy init during probe (and similarly,
t
Hi Greg,
Here are musb fixes for v4.17-rc3, which fix two bugs in phy handling. Please
let me know if any change is needed.
Regards,
-Bin.
Johan Hovold (2):
USB: musb: dsps: drop duplicate phy initialisation
USB: musb: host: prevent core phy initialisation
drivers/usb/musb/musb_dsps.c
From: Johan Hovold
Set the new HCD flag which prevents USB core from trying to manage our
phys.
This is needed to be able to associate the controller platform device
with the glue device device-tree node on the BBB which uses legacy USB
phys. Otherwise, the generic phy lookup in usb_phy_roothub_
Hi,
On 2018-04-23 18:58, Bin Liu wrote:
On Mon, Apr 23, 2018 at 11:14:55AM +0530, Tushar Nimkar wrote:
On 2018-04-21 00:03, Bin Liu wrote:
>Hi,
>
>On Tue, Mar 20, 2018 at 02:28:00PM -0700, Paul Zimmerman wrote:
>>Forgot to CC linux-usb.
>>
>>
>> Forwarded Message
>>Subject: Re:
On Mon, Apr 23, 2018 at 07:21:12PM +0530, Tushar Nimkar wrote:
> Hi,
>
> On 2018-04-23 18:58, Bin Liu wrote:
> >On Mon, Apr 23, 2018 at 11:14:55AM +0530, Tushar Nimkar wrote:
> >>On 2018-04-21 00:03, Bin Liu wrote:
> >>>Hi,
> >>>
> >>>On Tue, Mar 20, 2018 at 02:28:00PM -0700, Paul Zimmerman wrote:
This commit adds a power_supply class instance to represent a
PD source's voltage and current properties. This provides an
interface for reading these properties from user-space or other
drivers.
For PPS enabled Sources, this also provides write access to set
the current and voltage and allows for
This commit adds the 'usb_type' property to represent USB supplies
which can report a number of different types based on a connection
event.
Examples of this already exist in drivers whereby the existing 'type'
property is updated, based on an event, to represent what was
connected (e.g. USB, USB_
This commit adds sink side support for Get_Status, Status,
Get_PPS_Status and PPS_Status handling. As there's the
potential for a partner to respond with Not_Supported,
handling of this message is also added. Sending of
Not_Supported is added to handle messagescreceived but not
yet handled.
Signed
Currently there's no error checking of this parameter in the
registration function and it's blindly added to psy class and
subsequently used as is. For example if this is NULL the call
to psy_register_thermal() will try to dereference the pointer
thus causing a kernel dump.
This commit updates the
This patch set adds sink side support for the PPS feature introduced in the
USB PD 3.0 specification.
The source PPS supply is represented using the Power Supply framework to provide
access and control APIs for dealing with it's operating voltage and current,
and switching between a standard PDO a
This commit adds generic ABI information regarding power_supply
properties. This is an initial attempt to try and align the usage
of these properties between drivers. As part of this commit,
common Battery and USB related properties have been listed.
Signed-off-by: Adam Thomson
---
Documentation
This commit adds code to handle requesting of PPS APDOs. Switching
between standard PDOs and APDOs, and re-requesting an APDO to
modify operating voltage/current will be triggered by an
external call into TCPM.
Signed-off-by: Adam Thomson
Acked-by: Heikki Krogerus
Reviewed-by: Guenter Roeck
---
Initialization for SoCs with dual role phy is being bypassed since
FSL_USB2_PHY_UTMI_DUAL macro is not being evaluated in the FSL gadget
driver. In this state a controller configured in peripheral mode will
not work as a gadget. This patch addresses this issue.
Tested on 4.14.32 using a hardware w
Introduce FSL_USB2_PHY_UTMI_DUAL in gadget driver for setting
phy in SOCs with utmi dual phy
Signed-off-by: Nikhil Badola
Tested-by: Tiago Brusamarello
---
Changes since v1:
* Removed Freescale internal information from commit message
drivers/usb/gadget/udc/fsl_udc_core.c | 1 +
1 file chang
On 22.04.2018 09:29, russianneuroman...@ya.ru wrote:
Hello!
So far I tested attached patch but didn't tried to revert commit yet,
will do next week.
Result of running patched kernel with recommended debug options:
https://paste.fedoraproject.org/paste/UpezexD~tDmQthoxV2BFbg
Logs show there i
On Mon, 23 Apr 2018, Mathias Nyman wrote:
> On 22.04.2018 09:29, russianneuroman...@ya.ru wrote:
> > Hello!
> >
> > So far I tested attached patch but didn't tried to revert commit yet,
> > will do next week.
> >
> > Result of running patched kernel with recommended debug options:
> > https://pa
On Mon, Apr 23, 2018 at 11:03:09AM +0300, Heikki Krogerus wrote:
> On Fri, Apr 20, 2018 at 10:26:08AM -0700, Guenter Roeck wrote:
> > On Wed, Apr 18, 2018 at 03:34:09PM +0300, Heikki Krogerus wrote:
> > > If the I2C adapter that the PD controller is attached to
> > > does not support SMBus protocol
On Mon, 2018-04-23 at 14:14 +0700, Lars Melin wrote:
> On 4/23/2018 14:03, Giuseppe Lippolis wrote:
> > The dwm-158 interface 4 and 5 doesn't answer to the AT commands
> > and doesn't appears a option interface.
> > Tested on openwrt distribution (kernel 4.14 using the old blacklist
> > definitions
Hi,
Here are several patches backported to v4.9+ to fix runtime PM problems in musb
drivers.
Regards,
-Bin.
Andreas Kemnade (1):
usb: musb: fix enumeration after resume
Merlijn Wajer (2):
usb: musb: call pm_runtime_{get,put}_sync before reading vbus registers
usb: musb: Fix external
From: Merlijn Wajer
commit df6b074dbe248d8c43a82131e8fd429e401841a5 upstream.
Without pm_runtime_{get,put}_sync calls in place, reading
vbus status via /sys causes the following error:
Unhandled fault: external abort on non-linefetch (0x1028) at 0xfa0ab060
pgd = b333e822
[fa0ab060] *pgd=4801145
From: Andreas Kemnade
commit 17539f2f4f0b7fa906b508765c8ada07a1e45f52 upstream.
On dm3730 there are enumeration problems after resume.
Investigation led to the cause that the MUSB_POWER_SOFTCONN
bit is not set. If it was set before suspend (because it
was enabled via musb_pullup()), it is set in
From: Merlijn Wajer
commit 94e46a4f2d5eb14059e42f313c098d4854847376 upstream.
This fixes an oops on unbind / module unload (on the musb omap2430
platform).
musb_remove function now calls musb_platform_exit before disabling
runtime pm.
Cc: sta...@vger.kernel.org # v4.9+
Signed-off-by: Merlijn W
Hello,
On Thu, Apr 19, 2018 at 1:03 PM, Masahiro Yamada
wrote:
> Historically, the clocks and resets are handled on the glue layer
> side instead of the DWC3 core. For simple cases, dwc3-of-simple.c
> takes care of arbitrary number of clocks and resets. The DT node
> structure typically looks l
Hello,
I have a somewhat strange request: how to break Linux USB support and disable some
validation.
Recently I have become a "lucky" owner of the badly designed hardware (ZWO 120MM astronomy
camera to be specific) and stumbled upon classic issue: hardware was designed not
according to spe
On Mon, 23 Apr 2018, Elvinas wrote:
> Hello,
>
> I have a somewhat strange request: how to break Linux USB support and disable
> some
> validation.
>
> Recently I have become a "lucky" owner of the badly designed hardware (ZWO
> 120MM astronomy
> camera to be specific) and stumbled upon cl
HI,
On 4/19/2018 4:03 AM, Masahiro Yamada wrote:
> In the current design of DWC3 driver,
> the DT typically becomes a nested structure like follows:
>
> dwc3-glue {
> compatible = "foo,dwc3";
> ...
>
> dwc3 {
> compatible = "snps,dwc3";
>
2018-04-24 2:44 GMT+09:00 Martin Blumenstingl
:
> Hello,
>
> On Thu, Apr 19, 2018 at 1:03 PM, Masahiro Yamada
> wrote:
>> Historically, the clocks and resets are handled on the glue layer
>> side instead of the DWC3 core. For simple cases, dwc3-of-simple.c
>> takes care of arbitrary number of clo
2018-04-24 9:11 GMT+09:00 Manu Gautam :
> HI,
>
>
> On 4/19/2018 4:03 AM, Masahiro Yamada wrote:
>> In the current design of DWC3 driver,
>> the DT typically becomes a nested structure like follows:
>>
>> dwc3-glue {
>> compatible = "foo,dwc3";
>> ...
>>
>> dwc3 {
>>
This patch fix dma unaligned problem and data lost problem for
isoc split in transfer.
Test on rk3288 platform, use an usb hs Hub (GL852G-12) and an usb
fs audio device (Plantronics headset) to capture and playback.
William Wu (2):
usb: dwc2: alloc dma aligned buffer for isoc split in
usb: dw
The commit 3bc04e28a030 ("usb: dwc2: host: Get aligned DMA in
a more supported way") rips out a lot of code to simply the
allocation of aligned DMA. However, it also introduces a new
issue when use isoc split in transfer.
In my test case, I connect the dwc2 controller with an usb hs
Hub (GL852G-12
If isoc split in transfer with no data (the length of DATA0
packet is 0), we can't simply return immediately. Because the
DATA0 can be the first transaction or the second transaction for
the isoc split in transaction. If the DATA0 packet with on data
is in the first transaction, we can return immed
The usb_add_gadget_udc() will set the gadget state as
USB_STATE_NOTATTACHED, so we needn't set it again.
Signed-off-by: Chunfeng Yun
---
drivers/usb/mtu3/mtu3_gadget.c | 8 ++--
1 file changed, 2 insertions(+), 6 deletions(-)
diff --git a/drivers/usb/mtu3/mtu3_gadget.c b/drivers/usb/mtu3/mt
There is an error dialog popped up in PC when test TEST_J/K
by EHSETT tool, due to not waiting for the completion of
control transfer. Here fix it by entering test mode after
Status Stage finish.
Signed-off-by: Chunfeng Yun
---
drivers/usb/mtu3/mtu3_gadget_ep0.c | 10 ++
1 file changed,
When boot on the platform with the USB cable connected to Win7,
the Win7 will pop up an error dialog: "USB Device not recognized",
but finally the Win7 can enumerate it successfully.
The root cause is as the following:
When the xHCI driver set PORT_POWER of the OTG port, and if both
IDPIN and VBUS_
In fact the driver depends on EXTCON only when it's configed as
USB_MTU3_DUAL_ROLE, so make USB_MTU3_DUAL_ROLE depend on EXTCON but
not USB_MTU3.
Signed-off-by: Chunfeng Yun
---
drivers/usb/mtu3/Kconfig | 3 ++-
1 file changed, 2 insertions(+), 1 deletion(-)
diff --git a/drivers/usb/mtu3/Kconfi
The variable of 'count' is declared as u8, this will cause an issue
due to value truncated when works in SS or SSP mode and data length
is greater than 255, so change it as u32.
Signed-off-by: Chunfeng Yun
---
drivers/usb/mtu3/mtu3_gadget_ep0.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(
On 4/23/2018 23:54, Dan Williams wrote:
MI_00 D-Link Mobile Broadband Device (cdc_ether)
MI_02 D-Link HSPA+DataCard Diagnostics Interface (also ppp m
MI_03 D-Link HSPA+DataCard NMEA Device
MI_04 D-Link HSPA+DataCard Speech Port
Any idea what format this port speaks? Some Huawei Qualcomm-base
On Tue, 2018-04-24 at 09:55 +0700, Lars Melin wrote:
> On 4/23/2018 23:54, Dan Williams wrote:
>
> > > MI_00 D-Link Mobile Broadband Device (cdc_ether)
> > > MI_02 D-Link HSPA+DataCard Diagnostics Interface (also ppp m
> > > MI_03 D-Link HSPA+DataCard NMEA Device
> > > MI_04 D-Link HSPA+DataCard
I've tried to bisect kernels from 4.13 to 4.14 and didn't find the reason. Then
I found that with upstream 4.13 the issue is still present on Ubuntu 18.04, so
there should be something more than just a kernel.
Eventually, I found that issue is somehow related to USB hub I use for my
periferals
65 matches
Mail list logo
