Hi All.
We are using Sierra's USB-to-WWAN driver on Ubuntu-14 for Sierra's
MC8090 modem, and we have a requirement wherein we need to have access
to the modem-serial-port (from our user-application that is).
Right now, we see that /usr/sbin/ModemManager is always connected to
/dev/ttyUSB3 (which
Hi,
On Mon, 2016-08-08 at 15:10 +0200, Greg Kroah-Hartman wrote:
> On Fri, Jun 10, 2016 at 03:32:41PM +0800, Chunfeng Yun wrote:
> > --- /dev/null
> > +++ b/drivers/usb/mtu3/Makefile
> > @@ -0,0 +1,20 @@
> > +
> > +#ifeq ($(CONFIG_USB_DEBUG),y)
> > + ccflags-y += -DDEBUG
> > +#endif
>
> Th
USB3 DRD driver is added for MT8173-EVB, and xHCI driver
becomes its subnode
Signed-off-by: Chunfeng Yun
---
arch/arm64/boot/dts/mediatek/mt8173-evb.dts | 46 +--
arch/arm64/boot/dts/mediatek/mt8173.dtsi| 29 +
2 files changed, 66 insertions(+), 9
add a DT binding doc for MediaTek USB3 DRD driver
Signed-off-by: Chunfeng Yun
Acked-by: Rob Herring
---
.../devicetree/bindings/usb/mt8173-mtu3.txt| 87
1 file changed, 87 insertions(+)
create mode 100644 Documentation/devicetree/bindings/usb/mt8173-mtu3.txt
dif
Make IPPC register optional to support host side of dual-role mode,
due to it is moved into common glue layer for simplification.
Signed-off-by: Chunfeng Yun
---
drivers/usb/host/xhci-mtk.c | 36 +---
1 file changed, 29 insertions(+), 7 deletions(-)
diff --git
These patches introduce the MediaTek USB3 dual-role controller
driver.
The driver can be configured as Dual-Role Device (DRD),
Peripheral Only and Host Only (xHCI) modes. It works well
with Mass Storage, RNDIS and g_zero on FS/HS and SS. And it is
tested on MT8173 platform which only contains USB2
Some resources, such as IPPC register etc, shared with device
driver are moved into common glue layer when xHCI driver is the
host side of dual-role mode and they should be changed as optional
properties if they are required ones before. For clarity, add
a new part of binding to support host side o
This patch adds support for the MediaTek USB3 controller
integrated into MT8173. It can be configured as Dual-Role
Device (DRD), Peripheral Only and Host Only (xHCI) modes.
Signed-off-by: Chunfeng Yun
---
drivers/usb/Kconfig|2 +
drivers/usb/Makefile |1 +
d
On Tue, Aug 09, 2016 at 04:07:56PM +0800, yonglong.wu wrote:
> Hi,
> On Tue, 2016-08-09 at 14:29 +0800, Peter Chen wrote:
>
> On Tue, Aug 9, 2016 at 11:31 AM, Yonglong Wu
> wrote:
> > From: Yonglong Wu
> >
> > According to USB30 specification, the Function Remote Wakeup field ca
On Tue, Aug 09, 2016 at 12:48:12PM +0530, Ajay Garg wrote:
> Hi All.
>
> We are using Sierra's USB-to-WWAN driver on Ubuntu-14 for Sierra's
> MC8090 modem, and we have a requirement wherein we need to have access
> to the modem-serial-port (from our user-application that is).
>
> Right now, we se
On Tue, Aug 9, 2016 at 4:25 PM, Greg Kroah-Hartman
wrote:
> On Tue, Aug 09, 2016 at 04:07:56PM +0800, yonglong.wu wrote:
>> Hi,
>> On Tue, 2016-08-09 at 14:29 +0800, Peter Chen wrote:
>>
>> On Tue, Aug 9, 2016 at 11:31 AM, Yonglong Wu
>> wrote:
>> > From: Yonglong Wu
>> >
>> > A
>> On Fri, Aug 05, 2016 at 02:46:00PM -0700, Stephen Boyd wrote:
>> > Quoting Peter Chen (2016-07-08 02:25:35)
>> > >
>> > > How you handle the code for PHY getting at probe?
>> > >
>> >
>> > Which probe? Glue layer probe? In my case I'm not using the phy
>> > until the RESET/STOPPED event so I j
Hi,
Lu Baolu writes:
> In sg_timeout(), req->status is set to "-ETIMEDOUT" before calling
> into usb_sg_cancel(). usb_sg_cancel() will do nothing and return
> directly if req->status has been set to a non-zero value. This will
> cause driver hang as soon as transfer time out is triggered.
>
> In
Hi,
robert.f...@collabora.com writes:
> From: Andrew Bresticker
>
> Enable runtime PM for the xhci-plat device so that the parent device
> may implement runtime PM.
>
> Signed-off-by: Andrew Bresticker
> Tested-by: Robert Foss
> Signed-off-by: Robert Foss
> ---
> drivers/usb/host/xhci-plat.c
When the usb device has entered suspend state by runtime suspend method, and
the sustem also try to enter suspend state by issuing usb_dev_suspend(), it
will issue pm_runtime_resume() function to deal with wrong wakeup setting in
choose_wakeup() function.
But if usb device resumes failed due to xh
On 08/08/2016 09:11 AM, Greg KH wrote:
> On Sun, Aug 07, 2016 at 06:55:36PM +0200, stéphane bryant wrote:
>> Hi
>>
>> We are working on a project where a user-space application (a device
>> emulator) creates a USB device on the host machine (thus allowing the
>> emulated device to emulate a USB s
On Tue, Aug 09, 2016 at 05:33:33PM +0800, Baolin Wang wrote:
> When the usb device has entered suspend state by runtime suspend method, and
> the sustem also try to enter suspend state by issuing usb_dev_suspend(), it
> will issue pm_runtime_resume() function to deal with wrong wakeup setting in
>
On Mon, 2016-08-08 at 11:48 -0400, robert.f...@collabora.com wrote:
> From: Robert Foss
>
> Implemented queued response handling. This queue is processed every time the
> WDM_READ flag is cleared.
>
> In case of a read error, userspace may not actually read the data, since the
> driver returns a
Although the SEAD3 board has already made some minimal use of device
tree, until now most peripherals have been left probed by platform code.
This series converts all SEAD3 peripherals to instead be probed from
device tree. The amount of platform code is significantly reduced
leaving SEAD3 primed
Now that the SEAD3 board is probing the EHCI controller using device
tree, remove the non-DT support from the probe function.
Signed-off-by: Paul Burton
---
drivers/usb/host/ehci-sead3.c | 16
1 file changed, 4 insertions(+), 12 deletions(-)
diff --git a/drivers/usb/host/ehci-
Introduce support for probing the SEAD3 EHCI driver using device tree.
Signed-off-by: Paul Burton
---
drivers/usb/host/ehci-sead3.c | 29 +++--
1 file changed, 23 insertions(+), 6 deletions(-)
diff --git a/drivers/usb/host/ehci-sead3.c b/drivers/usb/host/ehci-sead3.c
in
On Wed, Jul 27, 2016 at 02:39:16PM +0530, Bhaktipriya Shridhar wrote:
> alloc_ordered_workqueue replaces the deprecated
> create_singlethread_workqueue.
>
> The workqueue "workqueue" has multiple workitems which may require
> ordering. Hence, a dedicated ordered workqueue has been used.
> Since th
On Tue, Jul 12, 2016 at 02:35:19PM +0200, Rafał Miłecki wrote:
> When working with Device Tree we may need to reference controllers
> (their nodes) and query for HCDs. This is useful for getting some
> runtime info about host controllers like e.g. assigned bus number.
>
> Signed-off-by: Rafał Miłe
On Fri, Jul 15, 2016 at 07:18:50AM +0200, Rafał Miłecki wrote:
> Probing function was using &dev->dev and dev->dev.of_node over 20 times
> so I believe it made sense to use helper variables for both of them.
> To avoid some uncommon variable name for struct device I first replaced
> existing dev va
On Fri, Jul 15, 2016 at 07:05:56AM +0200, Rafał Miłecki wrote:
> Probing function was using &dev->dev and dev->dev.of_node over 20 times
> so I believe it made sense to use helper variables for both of them.
> To avoid some uncommon variable name for struct device I first replaced
> existing dev va
On Mon, 8 Aug 2016, Martin K. Petersen wrote:
> > "Oliver" == Oliver Neukum writes:
>
> Oliver> Some SATA to USB bridges fail to cooperate with some drives
> Oliver> resulting in no cache being present being reported to the
> Oliver> host. That causes the host to skip sending a command to
>
On Wed, Jun 29, 2016 at 04:38:36PM +0300, Heikki Krogerus wrote:
> Hi,
>
> The USB Type-C class is meant to provide unified interface to the
> userspace to present the USB Type-C ports in a system.
>
> Changes since v3:
> - Documentation cleanup as proposed by Roger Quadros
> - Setting partner al
On Mon, Aug 01, 2016 at 09:15:48PM +0300, Tal Shorer wrote:
> struct ulpi_ops is defined as follows:
>
> struct ulpi_ops {
> struct device *dev;
> int (*read)(struct ulpi_ops *ops, u8 addr);
> int (*write)(struct ulpi_ops *ops, u8 addr, u8 val);
> };
>
> Upon calling ulpi_
On Fri, Jul 08, 2016 at 04:15:22PM +0800, Peter Chen wrote:
> It can simplify root Kconfig
Why does it matter?
--
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-inf
On Mon, Aug 08, 2016 at 11:48:52AM -0400, robert.f...@collabora.com wrote:
> From: Robert Foss
>
> Implemented queued response handling. This queue is processed every time the
> WDM_READ flag is cleared.
>
> In case of a read error, userspace may not actually read the data, since the
> driver re
Hi,
On 9 August 2016 at 14:35, Paul Burton wrote:
> Introduce support for probing the SEAD3 EHCI driver using device tree.
>
> Signed-off-by: Paul Burton
> ---
>
> drivers/usb/host/ehci-sead3.c | 29 +++--
> 1 file changed, 23 insertions(+), 6 deletions(-)
>
> diff --git
On Mon, Jul 18, 2016 at 01:29:05PM +0100, David Binderman wrote:
> Hello there,
>
> drivers/usb/usbip/vudc_rx.c:145:27: warning: result of ‘11 << 30’
> requires 35 bits to represent, but ‘int’ only has 32 bits
> [-Wshift-overflow=]
>
> Source code is
>
> urb_p->urb->pipe &= ~(11 << 30);
>
>
On Mon, Jul 11, 2016 at 11:57:48AM +0800, Huang, Huki wrote:
> When end user inserts a usb3 device and put dut to s3.
> Then hotplug the usb3 disk under s3.
> The device will be lost upon resuming from s3.
>
> There is a corner case that the hub->change_bits for
> the usb3 port is not set when usb
On Fri, Jul 08, 2016 at 04:15:23PM +0800, Peter Chen wrote:
> The ULPI bus is not only for host, but for device mode too, so move
> it out from host's Kconfig.
>
> Cc: Heikki Krogerus
> Signed-off-by: Peter Chen
> ---
> drivers/usb/common/Kconfig | 21 +
> drivers/usb/core/K
On Tue, 9 Aug 2016, Felipe Balbi wrote:
>
> Hi,
>
> Lu Baolu writes:
> > In sg_timeout(), req->status is set to "-ETIMEDOUT" before calling
> > into usb_sg_cancel(). usb_sg_cancel() will do nothing and return
> > directly if req->status has been set to a non-zero value. This will
> > cause driv
On Mon, Jun 13, 2016 at 11:33:41AM +0900, Nobuo Iwata wrote:
> Modification to the userspace tools including usbip/libsrc and
> usbip/src.
>
> Changed corresponding to new vhci_sysfs.c.
>
> nports in sysfs is used to get total number of ports.
>
> Old get_nports() ignores the last status line
On Tue, 9 Aug 2016, Paul Burton wrote:
> Now that the SEAD3 board is probing the EHCI controller using device
> tree, remove the non-DT support from the probe function.
>
> Signed-off-by: Paul Burton
> ---
>
> drivers/usb/host/ehci-sead3.c | 16
> 1 file changed, 4 insertions(
On Mon, Jun 13, 2016 at 11:33:42AM +0900, Nobuo Iwata wrote:
> Modification for dynamic device registration and unregistration.
As I didn't take patch 2/3, can you resend this one as well after fixing
up that patch?
thanks,
greg k-h
--
To unsubscribe from this list: send the line "unsubscribe li
On 2016-08-09 09:51 AM, Greg KH wrote:
On Mon, Aug 08, 2016 at 11:48:52AM -0400, robert.f...@collabora.com wrote:
From: Robert Foss
Implemented queued response handling. This queue is processed every time the
WDM_READ flag is cleared.
In case of a read error, userspace may not actually read
On Mon, Jul 11, 2016 at 04:23:26PM +0900, Nobuo Iwata wrote:
> Dear all,
>
> This series of patches adds exporting device operation to USB/IP.
I would _really_ like someone else to review this code and get them to
ack it before I accept it. It does a lot of different things here, and
changes t
Add support for the I2C bus functionality of the TI SM-USB-DIG.
Signed-off-by: Andrew F. Davis
---
drivers/i2c/busses/Kconfig | 10 ++
drivers/i2c/busses/Makefile | 1 +
drivers/i2c/busses/i2c-ti-smusbdig.c | 189 +++
3 files changed, 200 ins
Hello all,
This series adds initial support for the TI SM-USB-DIG, this is a USB
to I2C/SPI/1Wire/GPIO adapter, we only add support for I2C here, drivers
for the other protocols are still in the works.
Thanks,
Andrew
Changes from v3:
- Rebased on v4.8-rc1
- Added this cover letter to track ser
The TI SM-USB-DIG is a USB to SPI/I2C/1Wire/GPIO adapter.
Add MFD core support.
Signed-off-by: Andrew F. Davis
---
drivers/mfd/Kconfig | 9 +++
drivers/mfd/Makefile| 2 +
drivers/mfd/ti-smusbdig.c | 138
include/linux/mfd
On Tue, 09 Aug 2016, Andrew F. Davis wrote:
> The TI SM-USB-DIG is a USB to SPI/I2C/1Wire/GPIO adapter.
> Add MFD core support.
>
> Signed-off-by: Andrew F. Davis
> ---
> drivers/mfd/Kconfig | 9 +++
> drivers/mfd/Makefile| 2 +
> drivers/mfd/ti-smusbdig.c | 13
On 2016-08-09 05:19 AM, Felipe Balbi wrote:
Hi,
robert.f...@collabora.com writes:
From: Andrew Bresticker
Enable runtime PM for the xhci-plat device so that the parent device
may implement runtime PM.
Signed-off-by: Andrew Bresticker
Tested-by: Robert Foss
Signed-off-by: Robert Foss
--
From: Andrew Bresticker
USB host controllers can take a significant amount of time to suspend
and resume, adding several hundred miliseconds to the kernel resume
time. Since the XHCI controller has no outside dependencies (other than
clocks, which are suspended late/resumed early), allow it to su
From: Robert Foss
This series enables runtime PM and asynchronous resume/suspend support for
xhci-plat devices.
Changes since v1:
- Added Signed-off-by: Robert Foss
- Added proper metadata tags to series
Changes since v2:
- Added missing changelog to cover-letter
- Added error checking to pm_r
From: Robert Foss
Enable runtime PM for the xhci-plat device so that the parent device
may implement runtime PM.
Signed-off-by: Robert Foss
Tested-by: Robert Foss
---
drivers/usb/host/xhci-plat.c | 26 --
1 file changed, 24 insertions(+), 2 deletions(-)
diff --git a/
On Tue, Aug 9, 2016 at 5:04 PM, Greg KH wrote:
> On Mon, Aug 01, 2016 at 09:15:48PM +0300, Tal Shorer wrote:
>> struct ulpi_ops is defined as follows:
>>
>> struct ulpi_ops {
>> struct device *dev;
>> int (*read)(struct ulpi_ops *ops, u8 addr);
>> int (*write)(struct ulpi_o
Hello,
At some stage USB peripherals negotiate how much current they are
allocated. For e.g. USB2 starts at 100mA and then negotiating 500mA.
I presume similar happens for USB3 with different amount of current available.
Is there a mechanism for driver to tell the hardware what current limit to
On Tue, Aug 09, 2016 at 04:01:53PM +0200, Greg KH wrote:
> On Wed, Jun 29, 2016 at 04:38:36PM +0300, Heikki Krogerus wrote:
> > Hi,
> >
> > The USB Type-C class is meant to provide unified interface to the
> > userspace to present the USB Type-C ports in a system.
> >
> > Changes since v3:
> > -
Hi Robert,
[auto build test WARNING on usb/usb-testing]
[also build test WARNING on v4.8-rc1 next-20160809]
[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/linux/commits/robert-foss-collabora-com/usb-xhci
From: Robert Foss
This series enables runtime PM and asynchronous resume/suspend support for
xhci-plat devices.
Changes since v1:
- Added Signed-off-by: Robert Foss
- Added proper metadata tags to series
Changes since v2:
- Added missing changelog to cover-letter
- Added error checking to pm_r
From: Robert Foss
Enable runtime PM for the xhci-plat device so that the parent device
may implement runtime PM.
Signed-off-by: Robert Foss
Tested-by: Robert Foss
---
drivers/usb/host/xhci-plat.c | 29 +++--
1 file changed, 27 insertions(+), 2 deletions(-)
diff --git
From: Andrew Bresticker
USB host controllers can take a significant amount of time to suspend
and resume, adding several hundred miliseconds to the kernel resume
time. Since the XHCI controller has no outside dependencies (other than
clocks, which are suspended late/resumed early), allow it to su
On Tue, Aug 09, 2016 at 09:37:23PM +0530, Muni Sekhar wrote:
> Hello,
>
>
> At some stage USB peripherals negotiate how much current they are
> allocated. For e.g. USB2 starts at 100mA and then negotiating 500mA.
> I presume similar happens for USB3 with different amount of current available.
Ha
On Tue, Aug 09, 2016 at 06:55:18PM +0300, Tal Shorer wrote:
> On Tue, Aug 9, 2016 at 5:04 PM, Greg KH wrote:
> > On Mon, Aug 01, 2016 at 09:15:48PM +0300, Tal Shorer wrote:
> >> struct ulpi_ops is defined as follows:
> >>
> >> struct ulpi_ops {
> >> struct device *dev;
> >> int (*r
On Tue, 9 Aug 2016, Muni Sekhar wrote:
> Hello,
>
>
> At some stage USB peripherals negotiate how much current they are
> allocated. For e.g. USB2 starts at 100mA and then negotiating 500mA.
> I presume similar happens for USB3 with different amount of current available.
>
>
> Is there a mecha
On 07/11/2016 09:23 AM, Nobuo Iwata wrote:
> Dear all,
>
> This series of patches adds exporting device operation to USB/IP.
>
> 1. Overview
>
> Exporting devices may not be a new idea. The request and response PDU
> have been defined in tools/usbip/usbip/src/usbip_network.h.
> #define OP_EXP
This driver make assumptions about the value of the direction flags.
So better use them in comparisons to improve the readability.
Signed-off-by: Stefan Wahren
---
drivers/usb/chipidea/udc.c | 18 +-
1 file changed, 9 insertions(+), 9 deletions(-)
Changes in V2:
- Use correct
Krzysztof Opasiak writes:
> As far as I can see, our main use case is to bypass the firewall but I
> don't understand why you don't want to solve this problem simply in
> userspace?
That was my immediate reaction, too. So I tried asking about it in
January and got this explanation:
| > You
From: Dinh Nguyen
Allow for platforms that have a reset controller driver in place to bring
the USB IP out of reset.
Signed-off-by: Dinh Nguyen
Acked-by: John Youn
Tested-by: Stefan Wahren
---
Hi Felipe,
Can you please take this patch through your USB tree? This patch was dependent
on "168d7
Hi Peter,
On 08/08/2016 01:52 AM, Peter Chen wrote:
> The current dts describes USB HUB's property at USB controller's
> entry, it is improper. The USB HUB should be the child node
> under USB controller, and power sequence properties are under
> it.
>
> Signed-off-by: Peter Chen
> ---
> arch/ar
Quoting Peter Chen (2016-08-08 01:52:10)
> From: Peter Chen
>
> At device tree, we have no device node for chipidea core,
> the glue layer's node is the parent node for host and udc
> device. But in related driver, the parent device is chipidea
> core. So, in order to let the common driver get pa
> This patch does not apply to my tree, can you refresh the series and resend
> it please?
Yes, I will send update.
Thank you,
n.iwata
//
> -Original Message-
> From: Greg KH [mailto:gre...@linuxfoundation.org]
> Sent: Tuesday, August 09, 2016 11:21 PM
> To: fx IWATA NOBUO
> Cc: valentin
On Tue, Aug 09, 2016 at 04:06:31PM +0200, Greg KH wrote:
> On Fri, Jul 08, 2016 at 04:15:23PM +0800, Peter Chen wrote:
> > The ULPI bus is not only for host, but for device mode too, so move
> > it out from host's Kconfig.
> >
> > Cc: Heikki Krogerus
> > Signed-off-by: Peter Chen
> > ---
> > dr
On Tue, Aug 09, 2016 at 04:06:22PM +0200, Greg KH wrote:
> On Fri, Jul 08, 2016 at 04:15:22PM +0800, Peter Chen wrote:
> > It can simplify root Kconfig
>
> Why does it matter?
>
When I try to move ulpi Kconfig from usb host out, I need to find some place
to put it, it is ok to put ulpi Kconfig a
On Tue, Aug 09, 2016 at 06:24:45PM +, Stefan Wahren wrote:
> This driver make assumptions about the value of the direction flags.
> So better use them in comparisons to improve the readability.
>
> Signed-off-by: Stefan Wahren
> ---
> drivers/usb/chipidea/udc.c | 18 +-
> 1
Hello,
At v7, userspace transmission and WebSocket command/daemon have been
removed from this series because I accepted comments that it can be
done by userspace proxy.
Best Regards,
n.iwata
//
> -Original Message-
> From: Bjørn Mork [mailto:bj...@mork.no]
> Sent: Wednesday, August 10, 2
Thank you for your comments,
> I know that usbip is insecure but personally I think that this series
> makes it much more insecure.
> 1) usbipa ... start daemon
> your server is opened for connecting any random device from the net.
Yes, I think so too.
> For now I see at least one simple solutio
Hi Greg,
On 9 August 2016 at 18:26, Greg KH wrote:
> On Tue, Aug 09, 2016 at 05:33:33PM +0800, Baolin Wang wrote:
>> When the usb device has entered suspend state by runtime suspend method, and
>> the sustem also try to enter suspend state by issuing usb_dev_suspend(), it
>> will issue pm_runtime
On Tue, Aug 09, 2016 at 04:33:35PM -0700, Joshua Clayton wrote:
> Hi Peter,
>
> On 08/08/2016 01:52 AM, Peter Chen wrote:
> > The current dts describes USB HUB's property at USB controller's
> > entry, it is improper. The USB HUB should be the child node
> > under USB controller, and power sequenc
On Tue, Aug 09, 2016 at 05:15:36PM -0700, Stephen Boyd wrote:
> Quoting Peter Chen (2016-08-08 01:52:10)
> > From: Peter Chen
> >
> > At device tree, we have no device node for chipidea core,
> > the glue layer's node is the parent node for host and udc
> > device. But in related driver, the pare
Ok Greg :)
On Tue, Aug 9, 2016 at 1:44 PM, Greg KH wrote:
> On Tue, Aug 09, 2016 at 12:48:12PM +0530, Ajay Garg wrote:
>> Hi All.
>>
>> We are using Sierra's USB-to-WWAN driver on Ubuntu-14 for Sierra's
>> MC8090 modem, and we have a requirement wherein we need to have access
>> to the modem-seri
74 matches
Mail list logo
