On Tue, Jun 26, 2018 at 10:12:28PM +0800, Greg Kroah-Hartman wrote:
> On Tue, Jun 26, 2018 at 03:43:13PM +0200, Johan Hovold wrote:
> > Add a "tty_" prefix to the tty "flag" variable to avoid any future
> > mixups with the recently added irq-mask "flags" one.
> >
> > Signed-off-by: Johan Hovold
>
Where did patches 2 and 3 go? If this is the only USB serial patch, you
can send it on it's own.
Also, please use the common prefix for the subsystem you're changing
(see git log). In this case, add "USB: serial: pl2303: " to your
Subject.
On Tue, Jun 26, 2018 at 07:07:59PM -0500, Guy Chronister
On Mon, Jun 25, 2018 at 7:24 AM Fabio Estevam wrote:
>
> From: Fabio Estevam
>
> Since commit 03e6275ae381087bd8 ("usb: chipidea: Fix ULPI on imx51") the
> kernel hangs on a imx51-babbage board, when using the ULPI interface with
> the CONFIG_USB_CHIPIDEA_ULPI option unselected.
>
> Instead of ha
The current code is broken as it re-defines "req" inside the
if block, then goto out of it. Thus the request that ends
up being sent is not the one that was populated by the
code in question.
This fixes RNDIS driver autodetect by Windows 10 for me.
The bug was introduced by Chris rework to remove
A couple of bugs in the driver are preventing SETUP packets
with an OUT data phase from working properly.
Interestingly those are incredibly rare (RNDIS typically
uses them and thus is broken without this fix).
The main problem was an incorrect register offset being
applied for arming RX on EP0.
On 06/26/2018 04:45 PM, Li Jun wrote:
Move TCPCI(Typec port controller interface) driver and rt1711h
driver out of staging.
Signed-off-by: Li Jun
Reviewed-by: Guenter Roeck
---
drivers/staging/Kconfig| 2 --
drivers/staging/Makefile | 1 -
On 06/26/2018 04:45 PM, Li Jun wrote:
While set polarity, we should keep the disconnected cc line to be
open.
Reviewed-by: Heikki Krogerus
Signed-off-by: Li Jun
Reviewed-by: Guenter Roeck
---
drivers/staging/typec/tcpci.c | 18 ++
1 file changed, 14 insertions(+), 4 del
On 06/26/2018 04:45 PM, Li Jun wrote:
From: Peter Chen
With that we can clear any pending events and the port is registered
so driver can be ready to handle typec events once we request irq.
Reviewed-by: Heikki Krogerus
Signed-off-by: Peter Chen
Signed-off-by: Li Jun
Reviewed-by: Guenter
On 06/26/2018 04:45 PM, Li Jun wrote:
As tcpm_register_port() and tcpci_register_port() never return
NULL and NULL is not a success in this case, use IS_ERR() to check
the return value of both.
Reviewed-by: Heikki Krogerus
Signed-off-by: Li Jun
Reviewed-by: Guenter Roeck
---
drivers/sta
On 06/26/2018 04:45 PM, Li Jun wrote:
Since we will use config settings via device properties, so
remove the hard code tcpci_tcpc_config.
Reviewed-by: Heikki Krogerus
Signed-off-by: Li Jun
Reviewed-by: Guenter Roeck
---
drivers/staging/typec/tcpci.c | 7 ---
1 file changed, 7 delet
On 06/26/2018 04:45 PM, Li Jun wrote:
Add fwnode handle to get the fwnode so we can get typec configs
it contains.
Suggested-by: Heikki Krogerus
Reviewed-by: Heikki Krogerus
Signed-off-by: Li Jun
Reviewed-by: Guenter Roeck
---
drivers/staging/typec/tcpci.c | 7 +++
drivers/usb/typ
On 06/26/2018 04:45 PM, Li Jun wrote:
Add nxp ptn5110 typec controller compatible string: "nxp,ptn5110",
which is a standard tcpci chip with power delivery support. Meanwhile
remove "usb,tcpci" because it doesn't follow the binding format rule
and has not been used yet.
Reviewed-by: Heikki Kroge
Signed-off-by: Guy Chronister
---
drivers/usb/serial/pl2303.c | 4 ++--
drivers/usb/serial/pl2303.h | 6 +++---
2 files changed, 5 insertions(+), 5 deletions(-)
diff --git a/drivers/usb/serial/pl2303.c b/drivers/usb/serial/pl2303.c
index 5d1a193..5528764 100644
--- a/drivers/usb/serial/pl2303.c
While set polarity, we should keep the disconnected cc line to be
open.
Reviewed-by: Heikki Krogerus
Signed-off-by: Li Jun
---
drivers/staging/typec/tcpci.c | 18 ++
1 file changed, 14 insertions(+), 4 deletions(-)
diff --git a/drivers/staging/typec/tcpci.c b/drivers/staging/ty
We need regmap_update_bits to avoid touch any other bits when
enable or disable vconn.
Reviewed-by: Guenter Roeck
Reviewed-by: Heikki Krogerus
Signed-off-by: Li Jun
---
drivers/staging/typec/tcpci.c | 9 +++--
1 file changed, 3 insertions(+), 6 deletions(-)
diff --git a/drivers/staging/ty
TCPCI implementation may need SW to enable VBUS detection to generate
power status events.
Reviewed-by: Guenter Roeck
Reviewed-by: Heikki Krogerus
Signed-off-by: Li Jun
---
drivers/staging/typec/tcpci.c | 6 ++
1 file changed, 6 insertions(+)
diff --git a/drivers/staging/typec/tcpci.c b/d
As DRP port autonomously toggles the Rp/Rd need a start value to
begin with, so add one parameter for it in tcpm_start_drp_toggling.
Reviewed-by: Guenter Roeck
Reviewed-by: Heikki Krogerus
Signed-off-by: Li Jun
---
drivers/usb/typec/tcpm.c | 10 +-
1 file changed, 5 insertions(+), 5 de
Move TCPCI(Typec port controller interface) driver and rt1711h
driver out of staging.
Signed-off-by: Li Jun
---
drivers/staging/Kconfig| 2 --
drivers/staging/Makefile | 1 -
drivers/staging/typec/Kconfig | 22 -
From: Peter Chen
With that we can clear any pending events and the port is registered
so driver can be ready to handle typec events once we request irq.
Reviewed-by: Heikki Krogerus
Signed-off-by: Peter Chen
Signed-off-by: Li Jun
---
drivers/staging/typec/tcpci.c | 15 +--
1 file
As tcpm_register_port() and tcpci_register_port() never return
NULL and NULL is not a success in this case, use IS_ERR() to check
the return value of both.
Reviewed-by: Heikki Krogerus
Signed-off-by: Li Jun
---
drivers/staging/typec/tcpci.c | 4 ++--
1 file changed, 2 insertions(+), 2 deletions
This patch adds support of get typec and power delivery config from
firmware description.
Reviewed-by: Heikki Krogerus
Reviewed-by: Guenter Roeck
Signed-off-by: Li Jun
---
drivers/usb/typec/tcpm.c | 131 +++
1 file changed, 109 insertions(+), 22 dele
Since we will use config settings via device properties, so
remove the hard code tcpci_tcpc_config.
Reviewed-by: Heikki Krogerus
Signed-off-by: Li Jun
---
drivers/staging/typec/tcpci.c | 7 ---
1 file changed, 7 deletions(-)
diff --git a/drivers/staging/typec/tcpci.c b/drivers/staging/type
Add nxp ptn5110 typec controller compatible string: "nxp,ptn5110",
which is a standard tcpci chip with power delivery support. Meanwhile
remove "usb,tcpci" because it doesn't follow the binding format rule
and has not been used yet.
Reviewed-by: Heikki Krogerus
Signed-off-by: Li Jun
---
drivers
This patch adds 3 APIs to get the typec port power and data type,
and preferred power role by its name string.
Reviewed-by: Heikki Krogerus
Signed-off-by: Li Jun
---
drivers/usb/typec/class.c | 58 +++
include/linux/usb/typec.h | 3 +++
2 files chang
Add fwnode handle to get the fwnode so we can get typec configs
it contains.
Suggested-by: Heikki Krogerus
Reviewed-by: Heikki Krogerus
Signed-off-by: Li Jun
---
drivers/staging/typec/tcpci.c | 7 +++
drivers/usb/typec/tcpm.c | 1 +
include/linux/usb/tcpm.h | 2 ++
3 files change
This patch set attempts to move the tcpci drivers out of staging by fix
some tcpci driver issues and define typec and power delivery device
properties, the changes are verified on NXP PTN5110, which is a standard
tcpci typec port controller device with power delivery support, tested
power source an
Add bindings supported by current typec driver, so user can pass
all those properties via dt.
Reviewed-by: Rob Herring
Signed-off-by: Li Jun
---
.../bindings/connector/usb-connector.txt | 44 +++
include/dt-bindings/usb/pd.h | 62 +
TCPCI stands for typec port controller interface, its implementation
has full typec port control with power delivery support, it's a
standard i2c slave with GPIO input as irq interface, detail see spec
"Universal Serial Bus Type-C Port Controller Interface Specification
Revision 1.0, Version 1.1"
On 2018-06-25 11:15:06 [-0400], Alan Stern wrote:
> > @@ -1152,9 +1153,9 @@ static void ctrl_complete(struct urb *urb)
> >
> > if (u == urb || !u->dev)
> > continue;
> > - spin_unlock(&ctx->lock);
> > +
Hi
> -Original Message-
> From: Adam Thomson [mailto:adam.thomson.opensou...@diasemi.com]
> Sent: 2018年6月25日 18:46
> To: Jun Li ; robh...@kernel.org; gre...@linuxfoundation.org;
> heikki.kroge...@linux.intel.com; li...@roeck-us.net
> Cc: a.ha...@samsung.com; cw00.c...@samsung.com; shufan_..
On Tue, Jun 26, 2018 at 03:43:13PM +0200, Johan Hovold wrote:
> Add a "tty_" prefix to the tty "flag" variable to avoid any future
> mixups with the recently added irq-mask "flags" one.
>
> Signed-off-by: Johan Hovold
Reviewed-by: Greg Kroah-Hartman
--
To unsubscribe from this list: send the li
Add a "tty_" prefix to the tty "flag" variable to avoid any future
mixups with the recently added irq-mask "flags" one.
Signed-off-by: Johan Hovold
---
drivers/usb/serial/digi_acceleport.c | 12 ++--
1 file changed, 6 insertions(+), 6 deletions(-)
diff --git a/drivers/usb/serial/digi_ac
On Sun, Jun 24, 2018 at 12:32:11AM +0200, Sebastian Andrzej Siewior wrote:
> From: John Ogness
>
> The portdata spinlock can be taken in interrupt context (via
> sierra_outdat_callback()).
> Disable interrupts when taking the portdata spinlock.
Good catch!
As this fixes a potential deadlock, I'
On Sun, Jun 24, 2018 at 12:32:05AM +0200, Sebastian Andrzej Siewior wrote:
> From: John Ogness
>
> The USB completion callback does not disable interrupts while acquiring
> the lock. We want to remove the local_irq_disable() invocation from
> __usb_hcd_giveback_urb() and therefore it is required
On Tue, Jun 26, 2018 at 3:57 PM, Andy Shevchenko
wrote:
Just noticed you have sent v6.
I'm pretty fine with it, thanks!
--
With Best Regards,
Andy Shevchenko
--
To unsubscribe from this list: send the line "unsubscribe linux-usb" in
the body of a message to majord...@vger.kernel.org
More major
On Tue, Jun 26, 2018 at 2:51 PM, Loic Poulain wrote:
> On 26 June 2018 at 13:02, Andy Shevchenko wrote:
>> On Mon, Jun 25, 2018 at 3:35 PM, Loic Poulain
>> wrote:
>>> + unsigned char *buf = val;
>>
>> Btw, not sure why you need this now...
>
> Not needed indeed, just wanted to avoid ar
We accidentally return 1 instead instead the negative error codes.
Fixes: df44831ee2dd ("USB host: Add USB ehci support for nuvoton npcm7xx
platform")
Signed-off-by: Dan Carpenter
---
The original patch used the "USB host:" prefix. This is driver code and
not generic USB host code so that's not
Most of FTDI's devices have an EEPROM which records FTDI devices
configuration setting (e.g. the VID, PID, I/O config...) and user
data. For example, FT232R and FTX chips have 128-byte and 2048-byte
internal EEPROM respectively.
This patch adds support for FTDI EEPROM read/write via USB control
tr
On Tue, 2018-06-26 at 13:52 +0300, Heikki Krogerus wrote:
> On Tue, Jun 26, 2018 at 12:10:56PM +0200, Timur Krist?f wrote:
> > On Tue, 2018-06-26 at 11:29 +0300, Heikki Krogerus wrote:
> > > On Mon, Jun 25, 2018 at 01:09:32PM +0200, Timur Krist?f wrote:
> > > > On Mon, 2018-06-25 at 13:11 +0300, He
Aleksander Morgado writes:
> Being a Qualcomm based chipset, I believe qcserial would be more appropriate.
Plenty of Qualcomm devices are handled by option. IMHO, there is no
point in adding device specific interface matching to qcserial, unless
it is a reusable pattern like the ones we have the
> > So this doesn't really match the Sierra layout in qcserial, where the
> > QMI interface is documented as interface 8 (but perhaps we have other
> > examples of that already).
> >
> > Do you know what these serial ports are used for?
>
> You know what, I kind of missed that. This Dell device is
>> I believe Aleksander might be referring to usb_choose_configuration() in
>> drivers/usb/core/generic.c? It does some confusing things with
>> multi-function/multi-configuration devices, explained by this comment:
>>
>> /* From the remaining configs, choose the first one whose
>>
>>
>> This would be when running on configuration #1:
>>
>> T: Bus=04 Lev=03 Prnt=04 Port=02 Cnt=01 Dev#= 7 Spd=5000 MxCh= 0
>> D: Ver= 3.10 Cls=ef(misc ) Sub=02 Prot=01 MxPS= 9 #Cfgs= 2
>> P: Vendor=413c ProdID=81d7 Rev=03.18
>> S: Manufacturer=DELL
>> S: Product=DW5821e Snapdragon X20 LTE
Hi Andy,
On 26 June 2018 at 13:02, Andy Shevchenko wrote:
> On Mon, Jun 25, 2018 at 3:35 PM, Loic Poulain wrote:
>> Most of FTDI's devices have an EEPROM which records FTDI devices
>> configuration setting (e.g. the VID, PID, I/O config...) and user
>> data. For example, FT232R and FTX chips hav
Hi Peter,
On Mon, Jun 25, 2018 at 11:51 PM, Peter Chen wrote:
> Fabio, I wonder it may cause the USB not work at imx27 which
> do not use this configuration now. Any possibilities to test and verify it?
I don't have access to a mx27 board, but I can send a patch that
selects CONFIG_USB_CHIPIDEA
On Mon, Jun 25, 2018 at 3:35 PM, Loic Poulain wrote:
> Most of FTDI's devices have an EEPROM which records FTDI devices
> configuration setting (e.g. the VID, PID, I/O config...) and user
> data. For example, FT232R and FTX chips have 128-byte and 2048-byte
> internal EEPROM respectively.
>
> This
On Tue, Jun 26, 2018 at 12:10:56PM +0200, Timur Krist?f wrote:
> On Tue, 2018-06-26 at 11:29 +0300, Heikki Krogerus wrote:
> > On Mon, Jun 25, 2018 at 01:09:32PM +0200, Timur Krist?f wrote:
> > > On Mon, 2018-06-25 at 13:11 +0300, Heikki Krogerus wrote:
> > > > +Mika
> > > >
> > > > On Fri, Jun 22
On Tue, 2018-06-26 at 11:29 +0300, Heikki Krogerus wrote:
> On Mon, Jun 25, 2018 at 01:09:32PM +0200, Timur Krist?f wrote:
> > On Mon, 2018-06-25 at 13:11 +0300, Heikki Krogerus wrote:
> > > +Mika
> > >
> > > On Fri, Jun 22, 2018 at 10:12:10AM +0200, Timur Krist?f wrote:
> > > > Hi,
> > > >
> > >
After merge the patch
[PATCH] usb: dwc3: gadget: properly increment dequeue pointer on,
fixed the case.
Thank you so much.
Liang Shengjun
-邮件原件-
发件人: Felipe Balbi [mailto:felipe.ba...@linux.intel.com]
发送时间: 2018年6月25日 17:43
收件人: liangshengjun
抄送: sta...@vger.kernel.org; linux-usb@v
On Tue, Jun 26, 2018 at 09:40:24AM +0200, Bjørn Mork wrote:
> Johan Hovold writes:
> > On Sat, Jun 23, 2018 at 11:24:08PM +0200, Aleksander Morgado wrote:
> >> This module exposes two USB configurations: a QMI+AT capable setup on
> >> USB config #1 and a MBIM capable setup on USB config #2.
> >>
>
On Tue, Jun 26, 2018 at 09:32:32AM +0200, Aleksander Morgado wrote:
> On Tue, Jun 26, 2018 at 8:09 AM, Johan Hovold wrote:
> > On Sat, Jun 23, 2018 at 11:24:08PM +0200, Aleksander Morgado wrote:
> >> This module exposes two USB configurations: a QMI+AT capable setup on
> >> USB config #1 and a MBI
Hi Andy,
On 6/7/2018 2:00 PM, Vivek Gautam wrote:
>
>
> On 5/31/2018 4:17 PM, Manu Gautam wrote:
>> Move from dwc3-of-simple to dwc3-qcom glue driver to
>> support peripheral mode which requires qscratch wrapper
>> programming on VBUS event.
>>
>> Fixes: a4333c3a6ba9 ("usb: dwc3: Add Qualcomm DW
2018-06-22 2:23 GMT+01:00 Jaejoong Kim :
> Hi Michal,
>
> Could you check this patch?
Sorry about long delay, I haven’t settled in my new place yet (which
is also why I’m using Gmail).
> 2018년 6월 14일 (목) 오후 11:55, Alan Stern 님이 작성:
>>
>> On Thu, 14 Jun 2018, Jaejoong Kim wrote:
>>
>> > The refere
Getting rid of kref seems sensible to me. Reference counting used to
be needed because sharing of fsg_common among multiple USB function
instances was handled by fsg. Now this is handled by configfs layer
and I don’t think the kref is necessary any more.
2018-06-14 19:23 GMT+01:00 Jaejoong Kim :
>
Oliver Neukum writes:
> On Di, 2018-06-26 at 09:40 +0200, Bjørn Mork wrote:
>> This code can make Linux default to a MBIM configuration if the MBIM
>> function uses the first interface in that configuration, even if this
>> configuration is not the first one. Availability of a driver is not
>> c
Acked-by: Michal Nazarewicz
(Does Gmail still hates LKML? Guess we’ll see…)
2018-06-14 15:50 GMT+01:00 Alan Stern :
> On Thu, 14 Jun 2018, Jaejoong Kim wrote:
>
>> fsg_common_set_num_buffers() may fail due to ENOMEM. So add
>> error handling for fail case.
>>
>> Signed-off-by: Jaejoong Kim
>> -
On Mon, Jun 25, 2018 at 01:09:32PM +0200, Timur Krist?f wrote:
> On Mon, 2018-06-25 at 13:11 +0300, Heikki Krogerus wrote:
> > +Mika
> >
> > On Fri, Jun 22, 2018 at 10:12:10AM +0200, Timur Krist?f wrote:
> > > Hi,
> > >
> > > I have a Dell XPS 13 9370, which has just Type-C ports. Currently
> > >
On Di, 2018-06-26 at 09:40 +0200, Bjørn Mork wrote:
> This code can make Linux default to a MBIM configuration if the MBIM
> function uses the first interface in that configuration, even if this
> configuration is not the first one. Availability of a driver is not
> considered. Except for RNDIS, j
unsubscribe--
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, Jun 25, 2018 at 04:08:37PM +0800, Li Jun wrote:
> This patch adds 3 APIs to get the typec port power and data type,
> and preferred power role by its name string.
>
> Signed-off-by: Li Jun
Reviewed-by: Heikki Krogerus
> ---
> drivers/usb/typec/class.c | 58
> +
Add MAINTAINERS entry for USB CCID Gadget Device
Signed-off-by: Marcus Folkesson
---
Notes:
v4:
- No changes
v3:
- No changes
v2:
- No changes
MAINTAINERS | 8
1 file changed, 8 insertions(+)
diff --git a/MAINTAINERS b/MAINTAINERS
index 078fd80f664
On Mon, Jun 25, 2018 at 10:54:27PM +0800, Greg Kroah-Hartman wrote:
> On Mon, Jun 25, 2018 at 05:48:05PM +0300, Heikki Krogerus wrote:
> > On Mon, Jun 25, 2018 at 08:37:25PM +0800, Greg Kroah-Hartman wrote:
> > > On Thu, Jun 21, 2018 at 04:43:19PM +0300, Heikki Krogerus wrote:
> > > > According to
Aleksander Morgado writes:
> On Tue, Jun 26, 2018 at 8:09 AM, Johan Hovold wrote:
>> On Sat, Jun 23, 2018 at 11:24:08PM +0200, Aleksander Morgado wrote:
>>> This module exposes two USB configurations: a QMI+AT capable setup on
>>> USB config #1 and a MBIM capable setup on USB config #2.
>>>
>>>
Johan Hovold writes:
> On Sat, Jun 23, 2018 at 11:24:08PM +0200, Aleksander Morgado wrote:
>> This module exposes two USB configurations: a QMI+AT capable setup on
>> USB config #1 and a MBIM capable setup on USB config #2.
>>
>> By default the kernel will choose the MBIM capable configuration as
On Tue, Jun 26, 2018 at 8:09 AM, Johan Hovold wrote:
> On Sat, Jun 23, 2018 at 11:24:08PM +0200, Aleksander Morgado wrote:
>> This module exposes two USB configurations: a QMI+AT capable setup on
>> USB config #1 and a MBIM capable setup on USB config #2.
>>
>> By default the kernel will choose th
65 matches
Mail list logo
