Some ehci compatible controllers have more than one reset signal lines,
e.g., Synopsys DWC USB2.0 Host-AHB Controller has two resets hreset_i_n
and phy_rst_i_n. Two more resets are added in this patch in order for
this kind of controller to use this driver directly.
Signed-off-by: Jiancheng Xue
-
Hi,
Alan Stern writes:
> On Mon, 2 May 2016, Mathias Nyman wrote:
>
>> The current implemenentation restart the sent pattern for each entry in
>> the sg list. The receiving end expects a continuous pattern, and test
>> will fail unless scatterilst entries happen to be aligned with the
>> pattern
Hi,
"gre...@linuxfoundation.org" writes:
> On Mon, May 02, 2016 at 09:22:57AM +0300, Felipe Balbi wrote:
>>
>> Hi,
>>
>> 刘磊 writes:
>> > dear linuxfoundation:
>> > I am liulei come from ZTEMT. We need add some device ID to linux
>> > kernel, We need some help from yours.
>> > Looking f
Hi,
"Susmita/Rajib Bandopadhyay" writes:
> knoppix@Microknoppix:~$ sudo dmesg -c
> [ 421.080059] usb 1-6: new high-speed USB device number 3 using ehci-pci
> [ 421.205730] usb 1-6: New USB device found, idVendor=14cd, idProduct=6700
> [ 421.205744] usb 1-6: New USB device strings: Mfr=1, Prod
In testing with HiKey, we found that since commit 3f30b158eba5c60
(asix: On RX avoid creating bad Ethernet frames), we're seeing lots of
noise during network transfers:
[ 239.027993] asix 1-1.1:1.0 eth0: asix_rx_fixup() Data Header
synchronisation was lost, remaining 988
[ 239.037310] asix 1-1.1
On Tue, May 3, 2016 at 9:00 AM, Baolin Wang wrote:
> Integrate with the newly added USB charger interface to limit the current
> we draw from the USB input based on the input device configuration
> identified by the USB stack, allowing us to charge more quickly from high
> current inputs without d
When the usb gadget supporting for usb charger is ready, the usb charger
can implement the usb_charger_plug_by_gadget() function and usb_charger_exit()
function by getting 'struct usb_charger' from 'struct gadget'.
Signed-off-by: Baolin Wang
---
drivers/usb/gadget/udc/charger.c | 39 ++
This patch introduces the usb charger driver based on usb gadget that
makes an enhancement to a power driver. It works well in practice but
that requires a system with suitable hardware.
The basic conception of the usb charger is that, when one usb charger
is added or removed by reporting from the
Integrate with the newly added USB charger interface to limit the current
we draw from the USB input based on the input device configuration
identified by the USB stack, allowing us to charge more quickly from high
current inputs without drawing more current than specified from others.
Signed-off-
Currently the Linux kernel does not provide any standard integration of this
feature that integrates the USB subsystem with the system power regulation
provided by PMICs meaning that either vendors must add this in their kernels
or USB gadget devices based on Linux (such as mobile phones) may not b
For supporting the usb charger, it adds the usb_charger_init() and
usb_charger_exit() functions for usb charger initialization and exit.
It will report to the usb charger when the gadget state is changed,
then the usb charger can do the power things.
Signed-off-by: Baolin Wang
---
drivers/usb/g
From: "Du, Changbin"
Add the usage of new binding mode 'any'.
$ echo any > UDC
Signed-off-by: Du, Changbin
Signed-off-by: Du, Changbin
---
Documentation/usb/gadget_configfs.txt | 6 --
1 file changed, 4 insertions(+), 2 deletions(-)
diff --git a/Documentation/usb/gadget_configfs.txt
b/D
From: "Du, Changbin"
On most platforms, there is only one device controller available.
In this case, we desn't care the UDC's name. So let's ignore the
name by setting 'UDC' to 'any'. And also we can change UDC name
at any time if it is not binded (no need set to "" first).
Signed-off-by: Du, Ch
From: "Du, Changbin"
When I am configuring Gadget Configfs, I need found a exactly UDC name before
I can start my gadget. But, really I doesn't care about which UDC name is used,
because I have only controller. "any" is a good option.
Du, Changbin (2):
usb: configfs: allow UDC binding rule con
On 02/05/2016, Greg KH wrote:
...
[snipped]
Before plugging in:
knoppix@Microknoppix:~$ sudo dmesg -c
[1.370778] ehci-pci :00:02.1: EHCI Host Controller
[1.370828] ehci-pci :00:02.1: new USB bus registered, assigned
bus number 1
[1.370895] ehci-pci :00:02.1: debug port 1
[
Hi,
On 05/02/2016 07:00 PM, Mark Brown wrote:
> On Fri, Apr 29, 2016 at 02:26:32PM +0800, Lu Baolu wrote:
>
>> +gpiod = gpiod_get(dev, "vbus_en", GPIOD_ASIS);
>> +if (IS_ERR(gpiod))
>> +return PTR_ERR(gpiod);
> This is clearly an inappropriate name for the signal in generic cod
On 2016-05-02 20:43, gre...@linuxfoundation.org wrote:
On Mon, May 02, 2016 at 09:22:57AM +0300, Felipe Balbi wrote:
Hi,
刘磊 writes:
dear linuxfoundation:
I am liulei come from ZTEMT. We need add some device ID to linux kernel,
We need some help from yours.
Looking forward to you reply
urb->status is set when endpoint csr RXSTALL, H_ERROR, DATAERROR or
INCOMPRX bit is set. Those bits mean a broken pipe, so don't start next
urb when any of these bits is set by checking urb->status.
To minimize the risk of regression, only do so for RX, until we have a
test case to understand the
The MUSB Programming Guide states that the driver should clear RXCSR
bit2 when the controller sets the bit.
Signed-off-by: Bin Liu
---
drivers/usb/musb/musb_host.c | 3 +++
1 file changed, 3 insertions(+)
diff --git a/drivers/usb/musb/musb_host.c b/drivers/usb/musb/musb_host.c
index 2f8ad7f..93
Hi Johan,
Thanks for your review.
> Looks like this code could use a few vid/pid temporaries.
> I'm not sure it makes sense to try to load a "ti_usb-v110a-p1150.fw"
> firmware before requesting the moxa firmware. Avoids a confusing:
> usb 1-2.2: Direct firmware load for ti_usb-v110a-p1150.fw fa
On Mon, May 02, 2016 at 10:41:24PM +0530, Susmita/Rajib Bandopadhyay wrote:
> Dear Sirs,
> I am a FOSS enthusiast.
> Recently, I have run into a problem. Although it is a long-standing
> problem, this is a special case of the issue.
> I placed the queries on Debian and Knoppix forums with sufficie
> -Original Message-
> From: Johan Hovold [mailto:jhov...@gmail.com] On Behalf Of Johan Hovold
> Sent: Sunday, May 01, 2016 10:20
> To: Konstantin Shkolnyy
> Cc: Johan Hovold; Valentin Yakovenkov; linux-usb@vger.kernel.org
> Subject: Re: [EXT] Re: [PATCH] Add DCD line support to CP210x driv
Dear Sirs,
I am a FOSS enthusiast.
Recently, I have run into a problem. Although it is a long-standing
problem, this is a special case of the issue.
I placed the queries on Debian and Knoppix forums with sufficient information.
The issue is this:
How to back up data of SIM Card with its Reader?
L
On Mon, May 02, 2016 at 11:26:01AM -0400, Alan Stern wrote:
> On Mon, 2 May 2016, Greg Kroah-Hartman wrote:
>
> > On Mon, May 02, 2016 at 11:13:10AM -0400, Alan Stern wrote:
> > > On Mon, 2 May 2016, Johan Hovold wrote:
> > >
> > > > This reverts commit e3345db85068ddb937fc0ba40dfc39c293dad977, w
On Mon, 2 May 2016, Greg Kroah-Hartman wrote:
> On Mon, May 02, 2016 at 11:13:10AM -0400, Alan Stern wrote:
> > On Mon, 2 May 2016, Johan Hovold wrote:
> >
> > > This reverts commit e3345db85068ddb937fc0ba40dfc39c293dad977, which
> > > broke system resume for a large class of devices.
> > >
> >
On Mon, May 02, 2016 at 11:13:10AM -0400, Alan Stern wrote:
> On Mon, 2 May 2016, Johan Hovold wrote:
>
> > This reverts commit e3345db85068ddb937fc0ba40dfc39c293dad977, which
> > broke system resume for a large class of devices.
> >
> > Devices that after having been reset during resume need to
On Mon, 2 May 2016, Mathias Nyman wrote:
> On 29.04.2016 22:25, Alan Stern wrote:
> > When a USB driver is bound to an interface (either through probing or
> > by claiming it) or is unbound from an interface, the USB core always
> > disables Link Power Management during the transition and then
> >
On Mon, 2 May 2016, Johan Hovold wrote:
> This reverts commit e3345db85068ddb937fc0ba40dfc39c293dad977, which
> broke system resume for a large class of devices.
>
> Devices that after having been reset during resume need to be rebound
> due to a missing reset_resume callback, are now left in a s
On Mon, 2 May 2016, Mathias Nyman wrote:
> The current implemenentation restart the sent pattern for each entry in
> the sg list. The receiving end expects a continuous pattern, and test
> will fail unless scatterilst entries happen to be aligned with the
> pattern
Ah. We didn't spot this earlie
On 28.04.2016 11:33, Roger Quadros wrote:
Mathias,
On 22/04/16 21:00, Gabriel Krisman Bertazi wrote:
Mathias Nyman writes:
Nice catch, and moving xhci_mem_cleanup() until second hcd (primary) is
removed is one way to solve it.
Thank you and Roger for your suggestions!
But I don't think w
On 29.04.2016 22:25, Alan Stern wrote:
When a USB driver is bound to an interface (either through probing or
by claiming it) or is unbound from an interface, the USB core always
disables Link Power Management during the transition and then
re-enables it afterward. The reason is because the drive
On Fri, Apr 29, 2016 at 05:11:13PM +0200, Grigori Goronzy wrote:
> On 2016-04-29 14:16, Johan Hovold wrote:
> > On Fri, Apr 15, 2016 at 11:14:04PM +0200, Grigori Goronzy wrote:
> >> This may fail, do not assume it always works.
> >>
> >> Signed-off-by: Grigori Goronzy
> >> ---
> >> drivers/usb/s
On Mon, May 02, 2016 at 09:22:57AM +0300, Felipe Balbi wrote:
>
> Hi,
>
> 刘磊 writes:
> > dear linuxfoundation:
> > I am liulei come from ZTEMT. We need add some device ID to linux
> > kernel, We need some help from yours.
> > Looking forward to you reply, thanks!
> >
> >
> > Signed-off-by
On 05/02/2016 03:40 PM, Hans Verkuil wrote:
>>> Anyway, after disabling that config option I was finally able to test your
>>> patch
>>> series:
>>>
>>> Tested-by: Hans Verkuil
>
> BTW, one thing I noticed is that to have u-boot detect the network device I
> need to call 'usb reset' twice. This
On 05/01/16 18:42, Krzysztof Kozlowski wrote:
> On Sun, May 01, 2016 at 06:01:08PM +0200, Hans Verkuil wrote:
>>> Sorry, I meant the hanging issue I got in 4.6, not the ethernet issue.
>>> I get the same problem with linux-next. Can you mail me the .config you are
>>> using?
>>
>> Never mind.
>>
>
This reverts commit e3345db85068ddb937fc0ba40dfc39c293dad977, which
broke system resume for a large class of devices.
Devices that after having been reset during resume need to be rebound
due to a missing reset_resume callback, are now left in a suspended
state. This specifically broke resume of c
Hi,
This series centralizes OTG/Dual-role functionality in the kernel.
As of now I've got Dual-role functionality working pretty reliably on
dra7-evm and am437x-gp-evm.
DWC3 controller and platform related patches will be sent separately.
Series is based on v4.6-rc1 and depends on first 2 patche
Let's use CONFIG_USB_OTG as a single config option to enable
USB OTG and the OTG FSM. This makes things a lot less confusing.
Update all users of CONFIG_USB_OTG_FSM to CONFIG_USB_OTG.
Signed-off-by: Roger Quadros
---
Documentation/usb/chipidea.txt | 2 +-
drivers/usb/chipidea/Makefile | 2 +-
From: Yoshihiro Shimoda
Since some host controller (e.g. EHCI) needs a companion host controller
(e.g. OHCI), this patch adds such a configuration to use it in the OTG
core.
Signed-off-by: Yoshihiro Shimoda
Signed-off-by: Roger Quadros
---
Documentation/devicetree/bindings/usb/generic.txt |
The OTG controller and the USB controller an be linked via the
'otg-controller' property in the USB controller's device node.
of_usb_get_otg() can be used to get the OTG controller device
from the USB controller's device node.
Signed-off-by: Roger Quadros
---
Documentation/devicetree/bindings/u
When using the OTG/drd library we can call hcd_add/remove
consecutively without calling usb_put_hcd/usb_create_hcd in between
so hcd->flags can be stale.
If the HC dies due to whatever reason then without this
patch we get the below error on next hcd_add.
[ 91.494257] xhci-hcd xhci-hcd.0.auto:
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 controller device. If otg_dev is NULL
then the device tree node's otg-controller property is used to
get the otg_dev device.
The OTG core will use struct otg_hcd_ops to interface
with the HCD controller.
The main purpose of this interface is to avoid directly
calling HCD APIs from the OTG core as they
wouldn't be defined in the built-in symbol table if
CONFIG_USB is m.
Signed-off-by: Roger Quadros
Acked-by: Peter Chen
It provides APIs for the following tasks
- Registering an OTG/dual-role capable controller
- Registering Host and Gadget controllers to OTG core
- Providing inputs to and kicking the OTG state machine
Provide a dual-role device (DRD) state machine.
DRD mode is a reduced functionality OTG mode. In
Host controllers that are part of an OTG/dual-role instance
need to somehow pass the OTG controller device information
to the HCD core.
We use platform data to pass the OTG controller device.
Signed-off-by: Roger Quadros
---
drivers/usb/host/xhci-plat.c | 35
Now that we have a device reference in struct usb_otg
let's use dev_dbg() for debug messages.
Signed-off-by: Roger Quadros
---
drivers/usb/common/usb-otg-fsm.c | 19 +++
1 file changed, 7 insertions(+), 12 deletions(-)
diff --git a/drivers/usb/common/usb-otg-fsm.c b/drivers/usb/
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 drivers
to register a gadget controller that is part of an OTG instance.
Register with OTG core when gadget functio
Move otg_fsm into usb_otg and use usb_otg wherever possible
in the usb_otg APIs.
Signed-off-by: Roger Quadros
Acked-by: Peter Chen
---
drivers/usb/chipidea/ci.h| 1 -
drivers/usb/chipidea/core.c | 14 +--
drivers/usb/chipidea/debug.c | 2 +-
drivers/usb/chipidea/otg_fsm.c
If usb/otg-fsm.h and usb/composite.h are included together
then it results in the build warning [1].
Prevent that by defining VDBG locally.
Also get rid of MPC_LOC which doesn't seem to be used
by anyone.
[1] - warning fixed by this patch:
In file included from drivers/usb/dwc3/core.h:33,
fr
The OTG core will use struct otg_gadget_ops to
start/stop the gadget controller.
The main purpose of this interface is to avoid directly
calling usb_gadget_start/stop() from the OTG core as they
wouldn't be defined in the built-in symbol table if
CONFIG_USB_GADGET is m.
Signed-off-by: Roger Quadr
This is to prevent missing symbol build error if OTG is
enabled (built-in) and HCD core (CONFIG_USB) is module.
Signed-off-by: Roger Quadros
Acked-by: Peter Chen
---
drivers/usb/chipidea/otg_fsm.c | 7 +++
drivers/usb/common/usb-otg-fsm.c | 15 +++
drivers/usb/phy/phy-fsl-usb
Allow for SS+
Signed-off-by: Oliver Neukum
---
drivers/usb/misc/sisusbvga/sisusb.c | 4 ++--
1 file changed, 2 insertions(+), 2 deletions(-)
diff --git a/drivers/usb/misc/sisusbvga/sisusb.c
b/drivers/usb/misc/sisusbvga/sisusb.c
index a22de52..15666ad 100644
--- a/drivers/usb/misc/sisusbvga/sis
Allow for SS+
Signed-off-by: Oliver Neukum
---
drivers/usb/misc/sisusbvga/sisusb.c | 4 ++--
1 file changed, 2 insertions(+), 2 deletions(-)
diff --git a/drivers/usb/misc/sisusbvga/sisusb.c
b/drivers/usb/misc/sisusbvga/sisusb.c
index a22de52..15666ad 100644
--- a/drivers/usb/misc/sisusbvga/sis
Allow for SS+ USB
Signed-off-by: Oliver Neukum
---
drivers/net/wireless/broadcom/brcm80211/brcmfmac/usb.c | 4 +++-
1 file changed, 3 insertions(+), 1 deletion(-)
diff --git a/drivers/net/wireless/broadcom/brcm80211/brcmfmac/usb.c
b/drivers/net/wireless/broadcom/brcm80211/brcmfmac/usb.c
index
Allow for SS+ USB
Signed-off-by: Oliver Neukum
---
drivers/net/usb/r8152.c | 3 ++-
1 file changed, 2 insertions(+), 1 deletion(-)
diff --git a/drivers/net/usb/r8152.c b/drivers/net/usb/r8152.c
index d1f78c2..3f9f6ed 100644
--- a/drivers/net/usb/r8152.c
+++ b/drivers/net/usb/r8152.c
@@ -3366,7
Allow for SS+ USB
Signed-off-by: Oliver Neukum
---
drivers/net/usb/usbnet.c | 1 +
1 file changed, 1 insertion(+)
diff --git a/drivers/net/usb/usbnet.c b/drivers/net/usb/usbnet.c
index 4f08426..bc46ef9 100644
--- a/drivers/net/usb/usbnet.c
+++ b/drivers/net/usb/usbnet.c
@@ -355,6 +355,7 @@ void
On Fri, Apr 29, 2016 at 02:26:32PM +0800, Lu Baolu wrote:
> + gpiod = gpiod_get(dev, "vbus_en", GPIOD_ASIS);
> + if (IS_ERR(gpiod))
> + return PTR_ERR(gpiod);
This is clearly an inappropriate name for the signal in generic code,
it's specific to your use case.
signature.asc
On Mon, May 02, 2016 at 11:49:12AM +0200, Krzysztof Kozlowski wrote:
> This VDD regulator supply actually is not a usb3503 USB HUB regulator
> supply... but a supply to the LAN attached to this HUB. Regulator off/on
> is needed for LAN to show up. The hub will show up with typical reset
> (which i
On 05/02/2016 11:49 AM, Krzysztof Kozlowski wrote:
> On 04/29/2016 06:44 PM, Mark Brown wrote:
>> On Fri, Apr 29, 2016 at 01:55:14PM +0200, Krzysztof Kozlowski wrote:
>>> On 04/29/2016 01:30 PM, Mark Brown wrote:
>>
Supplies are only optional if they may be physically absent. In this
cas
Allow for SS+
Signed-off-by: Oliver Neukum
---
drivers/usb/misc/sisusbvga/sisusb.c | 4 ++--
1 file changed, 2 insertions(+), 2 deletions(-)
diff --git a/drivers/usb/misc/sisusbvga/sisusb.c
b/drivers/usb/misc/sisusbvga/sisusb.c
index a22de52..15666ad 100644
--- a/drivers/usb/misc/sisusbvga/sis
Hi,
Mathias Nyman writes:
> The current implemenentation restart the sent pattern for each entry in
^^^
restarts
> the sg list. The receiving end expects a continuous pattern, and test
> will fail unless scatterilst entries happe
Allow for SS+
Signed-off-by: Oliver Neukum
---
drivers/usb/misc/sisusbvga/sisusb.c | 4 ++--
1 file changed, 2 insertions(+), 2 deletions(-)
diff --git a/drivers/usb/misc/sisusbvga/sisusb.c
b/drivers/usb/misc/sisusbvga/sisusb.c
index a22de52..15666ad 100644
--- a/drivers/usb/misc/sisusbvga/sis
On 04/29/2016 06:44 PM, Mark Brown wrote:
> On Fri, Apr 29, 2016 at 01:55:14PM +0200, Krzysztof Kozlowski wrote:
>> On 04/29/2016 01:30 PM, Mark Brown wrote:
>
>>> Supplies are only optional if they may be physically absent. In this
>>> case it's possible that on device regulators may be used ins
On 29/04/16 11:24, Dirk Gouders wrote:
> If choices consist of choice_values of type tristate that depend on
> symbols set to 'm', those choice_values are not set to 'n' if the
> choice is changed from 'm' to 'y' (in which case only one active
> choice_value is allowed). Those values are also writt
The current implemenentation restart the sent pattern for each entry in
the sg list. The receiving end expects a continuous pattern, and test
will fail unless scatterilst entries happen to be aligned with the
pattern
Fix this by calculating the pattern byte based on total sent size
instead of just
65 matches
Mail list logo
