On 18/04/16 05:09, Peter Chen wrote:
> On Fri, Apr 15, 2016 at 02:00:46PM +0300, Roger Quadros wrote:
>> On 15/04/16 12:25, Peter Chen wrote:
>>> On Tue, Apr 05, 2016 at 05:05:12PM +0300, Roger Quadros wrote:
+ * usb_otg_register() - Register the OTG/dual-role device to OTG core
+ * @dev:
On 18/04/16 09:59, Peter Chen wrote:
> On Tue, Apr 05, 2016 at 05:05:14PM +0300, Roger Quadros wrote:
>> The OTG state machine needs a mechanism to start and
>> stop the gadget controller. Add usb_gadget_start()
>> and usb_gadget_stop().
>>
>> Introduce usb_otg_add_gadget_udc() to allow controller
On 19/04/16 11:14, Peter Chen wrote:
> On Mon, Apr 18, 2016 at 02:29:37PM +0800, Peter Chen wrote:
>> On Tue, Apr 05, 2016 at 05:05:13PM +0300, Roger Quadros wrote:
>>> Introduce usb_otg_add/remove_hcd() for use by host
>>> controllers that are part of OTG/dual-role port.
>>>
>>> Non Device tree pl
On 18/04/16 09:29, Peter Chen wrote:
> On Tue, Apr 05, 2016 at 05:05:13PM +0300, Roger Quadros wrote:
>> Introduce usb_otg_add/remove_hcd() for use by host
>> controllers that are part of OTG/dual-role port.
>>
>> Non Device tree platforms can use the otg_dev argument
>> to specify the OTG controll
Hi,
On 19/04/16 21:13, Gabriel Krisman Bertazi wrote:
> Under stress occasions some TI devices might not return early when
> reading the status register during the quirk invocation of xhci_irq made
> by usb_hcd_pci_remove. This means that instead of returning, we end up
> handling this interrupti
From: Fei Yang
In case host sends us an unsupported test mode, we
*must* stall this request. This will tell the host
that the selector is invalid and we won't put the
controller in unsupported test modes which could
have undetermined side-effects.
Signed-off-by: Fei Yang
Signed-off-by: Felipe B
Hi,
> From: Peter Chen
> Sent: Tuesday, April 19, 2016 6:18 PM
>
> On Fri, Apr 15, 2016 at 10:03:16AM +, Yoshihiro Shimoda wrote:
> > Hi,
> >
> > > From: Yoshihiro Shimoda
> > > Sent: Friday, April 15, 2016 6:59 PM
> > >
> > > Hi,
> > >
> > > > From: Roger Quadros
> > > > Sent: Thursday, Apri
Add a new compatible string for "mt2701"
Signed-off-by: Chunfeng Yun
Reviewed-by: Matthias Brugger
---
.../devicetree/bindings/phy/phy-mt65xx-usb.txt |4 +++-
1 file changed, 3 insertions(+), 1 deletion(-)
diff --git a/Documentation/devicetree/bindings/phy/phy-mt65xx-usb.txt
b/Documen
Add a new OF device ID for mt2701
Some register settings to avoid RX sensitivity level degradation
which may arise on mt8173 platform are separated from other
platforms.
Signed-off-by: Chunfeng Yun
---
drivers/phy/Kconfig |5 ++-
drivers/phy/phy-mt65xx-usb3.c | 77 ++
Oliver Neukum writes:
> This introduces the common parser for extra CDC headers now that it no longer
> depends on usbnet.
>
> Signed-off-by: Oliver Neukum
> ---
> drivers/usb/class/cdc-acm.c | 60
> +++--
> 1 file changed, 3 insertions(+), 57 deletions(
Oliver Neukum writes:
> after trying to use the common parser drivers which don't depend on usbnet
> I ended up in dependency hell. Having this code live in usbnet just
> doesn't make sense. I toyed with the idea of turning it into a module
> of its own, but that collides with the purpose of savi
Oliver Neukum writes:
> Now that the common parser resides in USB core, it can
> be used for CDC-WDM.
>
> Signed-off-by: Oliver Neukum
> ---
> drivers/usb/class/cdc-wdm.c | 29 +
> 1 file changed, 5 insertions(+), 24 deletions(-)
>
> diff --git a/drivers/usb/class/cd
When using asynchronous read or write operations on the USB endpoints the
issuer of the IO request is notified by calling the ki_complete() callback
of the submitted kiocb when the URB has been completed.
Calling this ki_complete() callback will free kiocb. Make sure that the
structure is no longe
Under stress occasions some TI devices might not return early when
reading the status register during the quirk invocation of xhci_irq made
by usb_hcd_pci_remove. This means that instead of returning, we end up
handling this interruption in the middle of a shutdown. Since
xhci->event_ring has alr
On Tuesday 19 April 2016 10:26 PM, Alex Henrie wrote:
2016-04-19 10:44 GMT-06:00 Sudip Mukherjee :
On Tuesday 19 April 2016 06:52 AM, Greg KH wrote:
On Mon, Apr 18, 2016 at 06:11:51PM -0600, Alex Henrie wrote:
Hi,
I recently bought an MCS7715 USB-attached parallel port,[1] but there
seem to
2016-04-19 10:44 GMT-06:00 Sudip Mukherjee :
> On Tuesday 19 April 2016 06:52 AM, Greg KH wrote:
>>
>> On Mon, Apr 18, 2016 at 06:11:51PM -0600, Alex Henrie wrote:
>>>
>>> Hi,
>>>
>>> I recently bought an MCS7715 USB-attached parallel port,[1] but there
>>> seem to be a couple of problems using it
On Tuesday 19 April 2016 06:52 AM, Greg KH wrote:
On Mon, Apr 18, 2016 at 06:11:51PM -0600, Alex Henrie wrote:
Hi,
I recently bought an MCS7715 USB-attached parallel port,[1] but there
seem to be a couple of problems using it with Linux:
1. The lp, parport, and parport_pc kernel modules are no
Hi,
I got more patches to improve throughput
but I cannot test them.
Regards
From b32c2f840c1ff0d0e93b627eb07b2fdc11f37bb5 Mon Sep 17 00:00:00 2001
From: Oliver Neukum
Date: Thu, 25 Feb 2016 12:20:12 +0100
Subject: [PATCH 1/4] chaoskey: O_NONBLOCK in concurrent reads
This changes the
On 04/19/2016 05:34 PM, Michal Nazarewicz wrote:
> On Thu, Apr 14 2016, Lars-Peter Clausen wrote:
>> Calling the ki_complete() callback will free the underlying data structure.
>> Make sure that it is no longer accessed beyond that point, otherwise
>> undefined behaviour might occur.
>>
>> Fixes: 2
On Thu, Apr 14 2016, Lars-Peter Clausen wrote:
> Calling the ki_complete() callback will free the underlying data structure.
> Make sure that it is no longer accessed beyond that point, otherwise
> undefined behaviour might occur.
>
> Fixes: 2e4c7553cd6f ("usb: gadget: f_fs: add aio support")
> Sig
On 04/19/2016 05:29 PM, Michal Nazarewicz wrote:
> On Thu, Apr 14 2016, Lars-Peter Clausen wrote:
>> Calling the ki_complete() callback will free the underlying data structure.
>> Make sure that it is no longer accessed beyond that point, otherwise
>> undefined behaviour might occur.
>
> To be hon
On Thu, Apr 14 2016, Lars-Peter Clausen wrote:
> Calling the ki_complete() callback will free the underlying data structure.
> Make sure that it is no longer accessed beyond that point, otherwise
> undefined behaviour might occur.
To be honest I have trouble tracking what ki_complete is. Could yo
On Mon, Apr 18 2016, Andrzej Pietrasiewicz wrote:
> The function responsible for verifying if a symlink can be made is in
> drivers/usb/gadget/configfs.c: config_usb_cfg_link()
>
> There is a comment from the author:
>
>* Also a function instance can only be linked once.
>
> This is the cod
Now that the common parser resides in USB core, it can
be used for CDC-WDM.
Signed-off-by: Oliver Neukum
---
drivers/usb/class/cdc-wdm.c | 29 +
1 file changed, 5 insertions(+), 24 deletions(-)
diff --git a/drivers/usb/class/cdc-wdm.c b/drivers/usb/class/cdc-wdm.c
in
Hi,
after trying to use the common parser drivers which don't depend on usbnet
I ended up in dependency hell. Having this code live in usbnet just
doesn't make sense. I toyed with the idea of turning it into a module
of its own, but that collides with the purpose of saving space.
--
To unsubscrib
A small update to unify error handling during probe().
Signed-off-by: Oliver Neukum
---
drivers/usb/class/cdc-acm.c | 8 +++-
1 file changed, 3 insertions(+), 5 deletions(-)
diff --git a/drivers/usb/class/cdc-acm.c b/drivers/usb/class/cdc-acm.c
index 6d82257..8268860 100644
--- a/drivers/us
The dependencies were impossible to handle preventing
drivers for CDC devices not which are not network drivers
from using the common parser.
Signed-off-by: Oliver Neukum
---
drivers/net/usb/usbnet.c | 138
drivers/usb/core/message.c | 153 +
This introduces the common parser for extra CDC headers now that it no longer
depends on usbnet.
Signed-off-by: Oliver Neukum
---
drivers/usb/class/cdc-acm.c | 60 +++--
1 file changed, 3 insertions(+), 57 deletions(-)
diff --git a/drivers/usb/class/cdc-a
On Tue, 19 Apr 2016, Felipe Balbi wrote:
> Hi,
>
> Peter Chen writes:
> > Hi all,
> >
> > When I review the patch [1] for adding companion controller support for
> > OTG framework, I am puzzled several concepts, like shared hcd and
> > companion controller, companion hcd, companion port, would s
our parent device is the one which was initialized
by either PCI or DeviceTree and that's the one which
is configured properly for DMA access.
Instead of copying DMA bits from parent to child,
let's just rely on parent device for the entire DMA
API.
Signed-off-by: Felipe Balbi
---
drivers/usb/d
Hi,
David Woodhouse writes:
> On Tue, 2016-04-19 at 14:38 +0300, Felipe Balbi wrote:
>>
>> The reason for that I'm using a manually created platform_device and
>> that misses dev->archdata which the underlying/parent PCI device has.
>
> Typically we'd expect you to use the parent device for DMA
Добрый день.
Я изготавливаю шкафы купе по необходимым размерам в собственной мастерской, а
также их последующим монтажом.
Расценки у меня гораздо ниже большинства фирм-посредников. И качество ни чуть
не уступает.
Предлагаю изготовить:
- Корпусный шкаф-купе
- Встроенный шкаф-купе
- Угловой шкаф
On Tue, 2016-04-19 at 14:38 +0300, Felipe Balbi wrote:
>
> The reason for that I'm using a manually created platform_device and
> that misses dev->archdata which the underlying/parent PCI device has.
Typically we'd expect you to use the parent device for DMA, as in your
second option.
That said,
Kirill Dronov writes:
no changes whatsoever
>>> 2 changes:
>>> 1) added platform drivers in linux/drivers/platform/
>>> should not influence dwc3
>>> 2) the only dwc3 -related change is in dwc3_pci_quirks():
>>> I need different "baytrail" quirk - smsc 3310 does not have CS. So I
>>> request
On 04/19/2016 02:55 PM, Felipe Balbi wrote:
Hi,
Kirill Dronov writes:
> irq/19-dwc3-96[000] d..2 825.229265: dwc3_event: event 0301
Link change U3 [3] -> U0 [0]
Host reports: " new high-speed USB device number XX using ehci-pci"
Host Sends USB_REQ_GET_DESCRIPTOR 3 times, ge
Hi,
Kirill Dronov writes:
> irq/19-dwc3-96[000] d..2 825.229265: dwc3_event: event
0301
>>> Link change U3 [3] -> U0 [0]
>>> Host reports: " new high-speed USB device number XX using ehci-pci"
>>> Host Sends USB_REQ_GET_DESCRIPTOR 3 times, gets r=-71. No events
>>> de
On 04/19/2016 02:10 PM, Felipe Balbi wrote:
Hi,
Kirill Dronov writes:
Is something definitely wrong with initialization and enumeration traces?
I'll go read them
> irq/19-dwc3-96[000] d..2 824.785778: dwc3_event: event 00150301
Link State change -> RX.Detect
> irq/19-d
Hi folks,
Today I noticed two issues with dwc3 on PCI-based systems which, while
debugging, I uncovered some details which we might want to change,
however I need a little guidance here.
The first problem is that when running with intel-iommu disable and
falling back to swiotlb, I can easily run
Hi,
Kirill Dronov writes:
Is something definitely wrong with initialization and enumeration traces?
>>> I'll go read them
>> > irq/19-dwc3-96[000] d..2 824.785778: dwc3_event: event 00150301
>>
>> Link State change -> RX.Detect
>>
>> > irq/19-dwc3-96[000] d..2 824.87
Requesting the only property that the driver needs using the
unified device property interface so it will be available
for all types of platforms, not just the ones using DT.
Signed-off-by: Heikki Krogerus
---
drivers/usb/host/xhci-plat.c | 5 ++---
1 file changed, 2 insertions(+), 3 deletions(-
No more users for it.
Signed-off-by: Heikki Krogerus
---
drivers/usb/host/xhci-plat.c | 5 +
include/linux/usb/xhci_pdriver.h | 27 ---
2 files changed, 1 insertion(+), 31 deletions(-)
delete mode 100644 include/linux/usb/xhci_pdriver.h
diff --git a/drivers/usb
Hi,
This depends on API change the device property framework in Rafael's
linux-pm tree.
Branch linux-next in
git://git.kernel.org/pub/scm/linux/kernel/git/rafael/linux-pm.git
Heikki Krogerus (3):
xhci: plat: adapt to unified device property interface
usb: dwc3: host: use build-in property i
This should allow xhci to remove handling of platform data.
Signed-off-by: Heikki Krogerus
Cc: Felipe Balbi
---
drivers/usb/dwc3/host.c | 18 +-
1 file changed, 9 insertions(+), 9 deletions(-)
diff --git a/drivers/usb/dwc3/host.c b/drivers/usb/dwc3/host.c
index c679f63..67f90d7
No more users for it.
Signed-off-by: Heikki Krogerus
---
drivers/usb/dwc3/core.c | 35 --
drivers/usb/dwc3/platform_data.h | 53
2 files changed, 88 deletions(-)
delete mode 100644 drivers/usb/dwc3/platform_data.h
diff -
This should allow the core driver to drop handling of
platform data and expect the platform specific details to
always come from properties.
The ACPI companion needs to be set before any build-in
properties are applied as setting it would otherwise
override the build-in properties. Therefore setti
Hi,
The API changes to the device property framework that I've been
waiting are now part of Rafael's linux-pm tree:
git://git.kernel.org/pub/scm/linux/kernel/git/rafael/linux-pm.git
So these depend on, I guess linux-next branch of that tree.
Heikki Krogerus (2):
usb: dwc3: pci: use build-in p
On Tue, 2016-04-19 at 17:44 +0800, Peter Chen wrote:
> Hi all,
>
> When I review the patch [1] for adding companion controller support for
> OTG framework, I am puzzled several concepts, like shared hcd and
> companion controller, companion hcd, companion port, would someone
> please explain them?
Hi,
On 04/19/2016 11:07 AM, Felipe Balbi wrote:
Hi,
Felipe Balbi writes:
Is something definitely wrong with initialization and enumeration traces?
I'll go read them
> irq/19-dwc3-96[000] d..2 824.785778: dwc3_event: event 00150301
Link State change -> RX.Detect
> irq/19-d
Hi,
Peter Chen writes:
> Hi all,
>
> When I review the patch [1] for adding companion controller support for
> OTG framework, I am puzzled several concepts, like shared hcd and
> companion controller, companion hcd, companion port, would someone
> please explain them? And why EHCI/OHCI do not us
Hi all,
When I review the patch [1] for adding companion controller support for
OTG framework, I am puzzled several concepts, like shared hcd and
companion controller, companion hcd, companion port, would someone
please explain them? And why EHCI/OHCI do not use shared hcd, but
xHCI uses it? Thank
On Fri, Apr 15, 2016 at 10:03:16AM +, Yoshihiro Shimoda wrote:
> Hi,
>
> > From: Yoshihiro Shimoda
> > Sent: Friday, April 15, 2016 6:59 PM
> >
> > Hi,
> >
> > > From: Roger Quadros
> > > Sent: Thursday, April 14, 2016 8:32 PM
> > >
> > > On 14/04/16 14:15, Yoshihiro Shimoda wrote:
> > > > H
On Wed, Apr 06, 2016 at 10:13:52AM +0300, Roger Quadros wrote:
> On 06/04/16 09:46, Peter Chen wrote:
> > On Tue, Apr 05, 2016 at 04:48:19PM +0300, Roger Quadros wrote:
> >> Peter,
> >>
> >> On 05/04/16 15:52, Roger Quadros wrote:
> >>> Peter,
> >>>
> >>> On 05/04/16 11:52, Peter Chen wrote:
>
On Mon, Apr 18, 2016 at 02:29:37PM +0800, Peter Chen wrote:
> On Tue, Apr 05, 2016 at 05:05:13PM +0300, Roger Quadros wrote:
> > Introduce usb_otg_add/remove_hcd() for use by host
> > controllers that are part of OTG/dual-role port.
> >
> > Non Device tree platforms can use the otg_dev argument
>
Hi,
kbuild test robot writes:
> tree: https://git.kernel.org/pub/scm/linux/kernel/git/balbi/usb.git next
> head: 761aa987a847e0e8b9a8d806f1be82217b88b0d3
> commit: ff96650d99902fd63d4511e6d9047e34e6aa37f2 [26/45] usb: dwc3: get rid
> of DWC3_TRB_MASK
> config: i386-randconfig-r0-201616 (att
On Tue, Apr 05, 2016 at 05:05:12PM +0300, Roger Quadros wrote:
> +/**
> + * usb_otg_start_host - start/stop the host controller
> + * @otg: usb_otg instance
> + * @on: true to start, false to stop
> + *
> + * Start/stop the USB host controller. This function is meant
> + * for use
Hi,
Felipe Balbi writes:
>> Is something definitely wrong with initialization and enumeration traces?
>
> I'll go read them
> irq/19-dwc3-96[000] d..2 824.785778: dwc3_event: event 00150301
Link State change -> RX.Detect
> irq/19-dwc3-96[000] d..2 824.877339: dwc3_event:
Hi,
On Friday 15 April 2016 12:05 AM, David Lechner wrote:
> This is a new phy driver for the SoC USB controllers on the TI DA8xx
> family of microcontrollers. The USB 1.1 PHY is just a simple on/off.
> The USB 2.0 PHY also allows overriding the VBUS and ID pins.
>
> Signed-off-by: David Lechner
On Mon, 2016-04-18 at 09:39 -0700, Guenter Roeck wrote:
> > Possibly. We have never gone that route. The obvious problems is
> that
> > I am not sure our alignment is known before boot.
> >
> Seems scary. I always thought that the alignment associated with
> cacheline_aligned would be the maxi
Hi,
Kirill Dronov writes:
> I'm not sure if I hit “run/stop metastability” issue [“STAR#9000525659:
> Clock Domain Crossing on DCTL in USB 2.0 Mode”]. I don't have DWC3
we have a workaround for that, you shouldn't hit it unless you removed
the workaround.
>>> No, I didn't.
>> y
From: Jasem Mutlaq
Adding VID:PID for Straizona Focusers to cp210x driver. Fixed white space issue.
Signed-off-by: Jasem Mutlaq
---
drivers/usb/serial/cp210x.c | 2 ++
1 file changed, 2 insertions(+)
diff --git a/drivers/usb/serial/cp210x.c b/drivers/usb/serial/cp210x.c
index dd47823..d0e4609
60 matches
Mail list logo
