On Thu, Nov 19, 2015 at 11:26:50AM -0500, Alan Stern wrote:
> On Thu, 19 Nov 2015, Philipp Zabel wrote:
>
> > On Wed, Oct 21, 2015 at 10:39:00AM +0800, Peter Chen wrote:
> > > On Tue, Oct 20, 2015 at 02:09:38PM -0200, Fabio Estevam wrote:
> > > > Hi Peter,
> > > >
> > > > On Mon, Oct 19, 2015 at
This patch adds documentation for the optional syscon-tcsr property in the
Qualcomm DWC3 node. The syscon-tcsr specifies the register and bit used to
configure the TCSR USB phy mux register.
Signed-off-by: Andy Gross
---
Documentation/devicetree/bindings/usb/qcom,dwc3.txt | 11 +++
1 fi
This set of patches adds support for the QCOM DWC3 phys found on various
Qualcomm platforms. The PHY portion of this set was originally part of:
https://lkml.org/lkml/2014/9/12/597
The applicable review comments were fixed and additional changes were made to
accomodate the TCSR phy mux selection
This patch adds a new driver for the Qualcomm USB 3.0 PHY that exists on some
Qualcomm platforms. This driver uses the generic PHY framework and will
interact with the DWC3 controller.
Signed-off-by: Andy Gross
---
drivers/phy/Kconfig | 11 +
drivers/phy/Makefile| 1 +
driver
This patch adds Qualcomm DWC3 USB nodes to device tree to enable support for the
DWC3 controller found on IPQ8064/AP148 platforms.
Signed-off-by: Andy Gross
---
arch/arm/boot/dts/qcom-ipq8064-ap148.dts | 24 +
arch/arm/boot/dts/qcom-ipq8064.dtsi | 89
This patch adds automatic configuration of the TCSR phy mux register based on
the syscon-tcsr devicetree entry. This configuration is optional, as some
platforms may not require the mux selection.
Signed-off-by: Andy Gross
---
drivers/usb/dwc3/dwc3-qcom.c | 25 +
1 file
Am Freitag, den 20.11.2015, 16:05 +0800 schrieb Peter Chen:
> On Thu, Nov 19, 2015 at 11:26:50AM -0500, Alan Stern wrote:
> > On Thu, 19 Nov 2015, Philipp Zabel wrote:
> >
> > > On Wed, Oct 21, 2015 at 10:39:00AM +0800, Peter Chen wrote:
> > > > On Tue, Oct 20, 2015 at 02:09:38PM -0200, Fabio Este
Hello,
This is a resurrection of the patches initially submitted by Ruslan
Bilovol in the following thread: https://lkml.org/lkml/2015/6/22/554
The changes since the original submission (v5) includes rebase onto
latest linux-next branch, simplification of the code requested by Alan
Stern and Feli
From: Ruslan Bilovol
Now when last user of usb_udc_attach_driver() is switched
to passing UDC name via usb_gadget_driver struct, it's safe
to remove this function
Tested-by: Maxime Ripard
Signed-off-by: Ruslan Bilovol
Signed-off-by: Marek Szyprowski
---
drivers/usb/gadget/udc/udc-core.c | 26
From: Ruslan Bilovol
Introduce new 'udc_name' member to usb_gadget_driver structure.
The 'udc_name' is a name of UDC that usb_gadget_driver should
be bound to. If udc_name is NULL, it will be bound to any
available UDC.
Tested-by: Maxime Ripard
Signed-off-by: Ruslan Bilovol
Signed-off-by: Mare
From: Ruslan Bilovol
Change behavior during registration of gadgets and
gadget drivers in udc-core. Instead of previous
approach when for successful probe of usb gadget driver
at least one usb gadget should be already registered
use another one where gadget drivers and gadgets
can be registered i
From: Ruslan Bilovol
Now when udc-core supports binding to specific UDC by passing
its name via 'udc_name' member of usb_gadget_driver struct,
switch to this generic approach.
Tested-by: Maxime Ripard
Signed-off-by: Ruslan Bilovol
Signed-off-by: Marek Szyprowski
---
drivers/usb/gadget/config
On Thu, Nov 19, 2015 at 08:26:22PM +0100, Felipe Balbi wrote:
>
> Hi,
>
> Gregory Herrero writes:
> > From: Mian Yousaf Kaukab
> >
> > As descriptor dma mode does not support split transfers, it can't be
> > enabled for high speed devices. Add a core parameter to enable it for
> > full speed de
Hi,
I have read various forum posts and some of the archive from this list
about the following error message:
Not enough host controller resources for new device state
Some people have had success with disabling XHCI at the BIOS level.
That seems to be an unnecessary work around to me given we
On Fri, Nov 20, 2015 at 09:54:09AM +0100, Marek Szyprowski wrote:
> From: Ruslan Bilovol
>
> Introduce new 'udc_name' member to usb_gadget_driver structure.
> The 'udc_name' is a name of UDC that usb_gadget_driver should
> be bound to. If udc_name is NULL, it will be bound to any
> available UDC.
On Fri, Nov 20, 2015 at 09:54:10AM +0100, Marek Szyprowski wrote:
> From: Ruslan Bilovol
>
> Now when udc-core supports binding to specific UDC by passing
> its name via 'udc_name' member of usb_gadget_driver struct,
> switch to this generic approach.
>
> Tested-by: Maxime Ripard
> Signed-off-b
On Fri, Nov 20, 2015 at 09:54:12AM +0100, Marek Szyprowski wrote:
> From: Ruslan Bilovol
>
> Change behavior during registration of gadgets and
> gadget drivers in udc-core. Instead of previous
> approach when for successful probe of usb gadget driver
> at least one usb gadget should be already r
Hello,
On 2015-11-20 10:26, Peter Chen wrote:
On Fri, Nov 20, 2015 at 09:54:12AM +0100, Marek Szyprowski wrote:
From: Ruslan Bilovol
Change behavior during registration of gadgets and
gadget drivers in udc-core. Instead of previous
approach when for successful probe of usb gadget driver
at le
> >>
> > And it seems can't apply for felipe's testing/next which I just
> > rebased on it.
>
> I really have no idea why it fails for You. The patchset applies correctly on
> both
> Felipe's 'next' and 'testing/next' branches from today.
>
I may know the reason, it may be because I changed
Hi Felipe,
Am 19.11.2015 um 20:54 schrieb Felipe Balbi:
Hi John,
John Youn writes:
Fixes commit 09a75e85
"usb: dwc2: refactor common low-level hw code to platform.c"
these two lines should be placed ...
The above commit consolidated the low-level phy access into a common
location. This
From: Mian Yousaf Kaukab
As descriptor dma mode does not support split transfers, it can't be
enabled for high speed devices. Add a core parameter to enable it for
full speed devices.
Ensure frame list and descriptor list are correctly freed during
disconnect.
Acked-by: John Youn
Signed-off-by
Kmem caches help to get correct boundary for descriptor buffers
which need to be 512 bytes aligned for dwc2 controller.
Two kmem caches are needed for generic descriptors and for
hs isochronous descriptors which doesn't have same size.
Acked-by: John Youn
Signed-off-by: Gregory Herrero
---
driv
From: Mian Yousaf Kaukab
Masks for HCDMA.CTD and HCDMA.DMAAddr are incorrect. As we always
start from first descriptor, no need to mask the address anyway.
Acked-by: John Youn
Signed-off-by: Mian Yousaf Kaukab
Signed-off-by: Gregory Herrero
---
drivers/usb/dwc2/core.c | 10 +++---
driver
Use Streaming DMA mappings to handle cache coherency of frame list and
descriptor list. Cache are always flushed before controller access it
or before cpu access it.
Acked-by: John Youn
Signed-off-by: Gregory Herrero
---
drivers/usb/dwc2/core.c | 3 ++
drivers/usb/dwc2/core.h | 2 +
On 17.11.2015 11:18, Chunfeng Yun wrote:
From 577f68d9c0ca1531d5f9cae0dcbea2ba116c8551 Mon Sep 17 00:00:00 2001
From: Chunfeng Yun
Date: Tue, 17 Nov 2015 17:09:05 +0800
Subject: [PATCH v12 0/3] Mediatek xHCI support
The patch supports MediaTek's xHCI controller.
There are some differences fro
On Wed, Nov 18, 2015 at 11:38:17AM +0100, Hans de Goede wrote:
> Hi,
>
> On 18-11-15 10:46, Philipp Zabel wrote:
> >Hi Hans,
> >
> >Am Montag, den 16.11.2015, 18:13 +0100 schrieb Hans de Goede:
> >>On 16-11-15 18:01, Philipp Zabel wrote:
> >>>If there are two devices sharing the same reset line th
On Mon, Nov 16, 2015 at 10:36:02AM +0800, Chen-Yu Tsai wrote:
> On Mon, Nov 16, 2015 at 3:46 AM, Hans de Goede wrote:
> > From: Reinder de Haan
> >
> > The H3 has a usb-phy clk register which is similar to that of earlier
> > SoCs, but with support for a larger number of phys. So we can simply ad
On Thu, Nov 19, 2015 at 11:46:20AM +0100, Johan Hovold wrote:
> On Mon, Nov 16, 2015 at 01:34:14PM +0100, Jonas Jonsson wrote:
> > Some modems, such as the Telit UE910, are using an Infineon Flash Loader
> > utility. It has two interfaces, 2/2/0 (Abstract Modem) and 10/0/0 (CDC
> > Data). The latte
On Thu, Nov 19, 2015 at 11:54:06AM +0100, Johan Hovold wrote:
> On Mon, Nov 16, 2015 at 01:34:15PM +0100, Jonas Jonsson wrote:
> > This has been seen on a Telit UE910 modem.
>
> Please expand this message as well and mention why this is not a CDC
> device so we do not forget.
Sure.
> > + {
On Fri, Nov 20, 2015 at 02:40:55PM +0100, Jonas Jonsson wrote:
> On Thu, Nov 19, 2015 at 11:46:20AM +0100, Johan Hovold wrote:
> > On Mon, Nov 16, 2015 at 01:34:14PM +0100, Jonas Jonsson wrote:
> > > Some modems, such as the Telit UE910, are using an Infineon Flash Loader
> > > utility. It has two
On 17.11.2015 08:38, Lu Baolu wrote:
This patch adds a sysfs file for users to check 1) whether the debug
capability is implemented by hardware; 2) if supported, which state
does it stay at.
With a host that supports debug port, a file named "debug_port_state"
will be created under the device sy
On Fri, Nov 20, 2015 at 02:35:09AM -0600, Andy Gross wrote:
> This patch adds documentation for the optional syscon-tcsr property in the
> Qualcomm DWC3 node. The syscon-tcsr specifies the register and bit used to
> configure the TCSR USB phy mux register.
>
> Signed-off-by: Andy Gross
Acked-by
Hi,
On 17-11-15 17:12, Jens Kuske wrote:
Enable the 2 USB host controllers used on the Orange Pi Plus
and add the necessary regulators.
Signed-off-by: Reinder de Haan
Signed-off-by: Hans de Goede
Signed-off-by: Jens Kuske
---
Hi Hans,
with these regulators USB works on the Orange Pi Plus t
Hi,
Andy Gross writes:
> This patch adds automatic configuration of the TCSR phy mux register based on
> the syscon-tcsr devicetree entry. This configuration is optional, as some
> platforms may not require the mux selection.
>
> Signed-off-by: Andy Gross
just when I find a way to make a gene
Hi,
Andy Gross writes:
> This patch adds documentation for the optional syscon-tcsr property in the
> Qualcomm DWC3 node. The syscon-tcsr specifies the register and bit used to
> configure the TCSR USB phy mux register.
>
> Signed-off-by: Andy Gross
> ---
> Documentation/devicetree/bindings/u
Hi,
John Youn writes:
> On 11/19/2015 11:04 AM, Felipe Balbi wrote:
>>
>> Hi,
>>
>> Zhangfei Gao writes:
>>> Support hisilicon,hi6220-usb for HiKey board
>>>
>>> Signed-off-by: Zhangfei Gao
>>
>> doesn't apply:
>>
>> Applying: usb: dwc2: add support of hi6220
>> error: drivers/usb/dwc2/pla
Hi,
Stefan Wahren writes:
> Hi Felipe,
>
> Am 19.11.2015 um 20:54 schrieb Felipe Balbi:
>>
>> Hi John,
>>
>> John Youn writes:
>>> Fixes commit 09a75e85
>>> "usb: dwc2: refactor common low-level hw code to platform.c"
>>
>> these two lines should be placed ...
>>
>>>
>>> The above commit consol
On Fri, Nov 20, 2015 at 12:51:39AM -0600, Jimmy Berry wrote:
> On Thu, Nov 19, 2015 at 6:26 PM, Greg KH wrote:
> > On Tue, Nov 17, 2015 at 12:40:12AM -0600, Jimmy Berry wrote:
> >> Without quirk keyboard repeats '6' until volume control is used since it
> >> indicates the key is pressed without ev
Hi,
Douglas Anderson writes:
> In general it is wise to clear interrupts before processing them. If
> you don't do that, you can get:
> 1. Interrupt happens
> 2. You look at system state and process interrupt
> 3. A new interrupt happens
> 4. You clear interrupt without processing it.
>
> T
Hi,
Peter Chen writes:
> On Thu, Nov 19, 2015 at 12:24:28PM -0600, Felipe Balbi wrote:
>>
>> Hi,
>>
>> Peter Chen writes:
>> > Add both bulk and iso depth of queue for sourcesink.
>> >
>> > Signed-off-by: Peter Chen
>> > ---
>> > Documentation/usb/gadget-testing.txt | 2 ++
>> > 1 file chan
On Fri, Nov 20, 2015 at 09:08:46AM -0600, Felipe Balbi wrote:
>
> Hi,
>
> Andy Gross writes:
> > This patch adds documentation for the optional syscon-tcsr property in the
> > Qualcomm DWC3 node. The syscon-tcsr specifies the register and bit used to
> > configure the TCSR USB phy mux register.
On Fri, Nov 20, 2015 at 09:06:33AM -0600, Felipe Balbi wrote:
>
> Hi,
>
> Andy Gross writes:
> > This patch adds automatic configuration of the TCSR phy mux register based
> > on
> > the syscon-tcsr devicetree entry. This configuration is optional, as some
> > platforms may not require the mux
On Fri, 20 Nov 2015, Dmitry Katsubo wrote:
> From: Dmitry Katsubo
>
> The patch extends the family of SATA-to-USB JMicron adapters that need
> FUA to be disabled and applies the same policy for uas driver.
> See details in http://unix.stackexchange.com/questions/237204/
>
> Signed-off-by: Dmitr
On Fri, 20 Nov 2015, Peter Chen wrote:
> > > > Hi Alan, we have several designs that the on-board HUB need to
> > > > be reset by gpio pin and its clock is also from the board or
> > > > the SoC. Any suggestions how to add these platform information
> > > > for HUB device?
> > >
> > > How about p
Hi Felipe,
I just realized this patch miss "dma_desc_fs_enable" property in
params_hi6220. (drivers/usb/dwc2/platform.c:57)
You need to apply this patch:
diff --git a/drivers/usb/dwc2/platform.c b/drivers/usb/dwc2/platform.c
index d5102c4..2dfdae3 100644
--- a/drivers/usb/dwc2/platform.c
+++ b/d
Hi Felipe,
Am 20.11.2015 um 16:27 schrieb Felipe Balbi:
Hi,
Stefan Wahren writes:
Hi Felipe,
Am 19.11.2015 um 20:54 schrieb Felipe Balbi:
Hi John,
John Youn writes:
Fixes commit 09a75e85
"usb: dwc2: refactor common low-level hw code to platform.c"
these two lines should be placed ...
On Fri, 20 Nov 2015, Patrick Shirkey wrote:
> Hi,
>
> I have read various forum posts and some of the archive from this list
> about the following error message:
>
> Not enough host controller resources for new device state
>
> Some people have had success with disabling XHCI at the BIOS level.
Appears to be a cdc_ether driver bug. See Bugzilla for more followup info
Begin forwarded message:
Date: Fri, 20 Nov 2015 11:11:26 +
From: "bugzilla-dae...@bugzilla.kernel.org"
To: "shemmin...@linux-foundation.org"
Subject: [Bug 108201] New: Can connect with Huawei E3131-s2 (Hi-Link) 3G mo
On Fri, 20 Nov 2015, Marek Szyprowski wrote:
> From: Ruslan Bilovol
>
> Change behavior during registration of gadgets and
> gadget drivers in udc-core. Instead of previous
> approach when for successful probe of usb gadget driver
> at least one usb gadget should be already registered
> use anot
Felipe,
On Fri, Nov 20, 2015 at 7:40 AM, Felipe Balbi wrote:
>
> Hi,
>
> Douglas Anderson writes:
>> In general it is wise to clear interrupts before processing them. If
>> you don't do that, you can get:
>> 1. Interrupt happens
>> 2. You look at system state and process interrupt
>> 3. A ne
Patrick Shirkey wrote:
> I have read various forum posts and some of the archive from this list
> about the following error message:
>
> Not enough host controller resources for new device state
>
> Some people have had success with disabling XHCI at the BIOS level.
>
> That seems to be an unnec
Hi,
On Fri, Nov 20, 2015 at 8:49 AM, Doug Anderson wrote:
> Felipe,
>
> On Fri, Nov 20, 2015 at 7:40 AM, Felipe Balbi wrote:
>>
>> Hi,
>>
>> Douglas Anderson writes:
>>> In general it is wise to clear interrupts before processing them. If
>>> you don't do that, you can get:
>>> 1. Interrupt h
The dwc2_hcd_reset_func() function is only ever called directly by a
delayed work function. As such no locks are already held when the
function is called.
Doing a read-modify-write of CPU registers and setting fields in the
main hsotg data structure is a bad idea without locks. Let's add
locks.
In general it is wise to clear interrupts before processing them. If
you don't do that, you can get:
1. Interrupt happens
2. You look at system state and process interrupt
3. A new interrupt happens
4. You clear interrupt without processing it.
This patch was actually a first attempt to fix m
Hi,
Stefan Wahren writes:
> Hi Felipe,
>
> Am 20.11.2015 um 16:27 schrieb Felipe Balbi:
>>
>> Hi,
>>
>> Stefan Wahren writes:
>>> Hi Felipe,
>>>
>>> Am 19.11.2015 um 20:54 schrieb Felipe Balbi:
Hi John,
John Youn writes:
> Fixes commit 09a75e85
> "usb: dwc2: refacto
"Herrero, Gregory" writes:
> Hi Felipe,
>
> I just realized this patch miss "dma_desc_fs_enable" property in
> params_hi6220. (drivers/usb/dwc2/platform.c:57)
>
> You need to apply this patch:
>
> diff --git a/drivers/usb/dwc2/platform.c b/drivers/usb/dwc2/platform.c
> index d5102c4..2dfdae3 1006
On Sat, November 21, 2015 3:46 am, Peter Stuge wrote:
> Patrick Shirkey wrote:
>> I have read various forum posts and some of the archive from this list
>> about the following error message:
>>
>> Not enough host controller resources for new device state
>>
>> Some people have had success with dis
This patch improves the usbfs_snoop debugging facility by adding
messages for a couple of significant events which, up to now, have not
been logged. The events are reaping and discarding (i.e.,
cancelling) an URB. The debugging messages include the userspace
address of the URB being reaped or dis
The usbfs_snoop facility can be very useful for debugging problems
involving usbfs. However, it always prints out the entire contents of
every URB. When dealing with large quantities of data, this can be
less than helpful.
This patch ameliorates the situation by adding a module parameter to
usbc
This patch adds a new warning message to ehci-hcd. The warning is
triggered whenever the driver finds that the hardware has set the
Active bit in a QH at a time when the driver expects the QH to be
completely idle. Such bugs have been observed by users in the past,
and since they can lead to seri
This patch enhances the "async" debugfs file in ehci-hcd by printing
out several additional fields in the hardware-accessible data
structures. These fields are important for determining the hardware's
view of the async schedule, in particular, the addresses of the
current and next qTDs for each QH
On Sun, 2015-11-15 at 20:46 +0100, Hans de Goede wrote:
> From: Reinder de Haan
>
> Note this commit only adds support for phys 1-3, phy 0, the otg phy,
> is
> not yet (fully) supported after this commit.
This patch seems to be causing following compile warning:
In file included from include/l
On Thu, 19 Nov 2015 22:34:18 +0100 (CET)
Jiri Kosina wrote:
> Could you please reformulate the changelog in this respect and resubmit?
Yes, of course, I tried to reformulate the problem and solution as clear and
succint as I could in v2, which I'll send shortly.
Thank you very much for your pati
The critical section protected by usbhid->lock in hid_ctrl() is too
big and because of this it causes a recursive deadlock. "Too big" means
the case statement and the call to hid_input_report() do not need to be
protected by the spinlock (no URB operations are done inside them).
The deadlock happe
On 11/3/2015 9:49 AM, Bin Liu wrote:
> Some USB phy drivers have different handling for the controller in each
> dr_mode. But the phy driver does not have visibility to the dr_mode of
> the controller.
>
> This adds an api to return the dr_mode of the controller which
> associates the given phy no
On 11/20/2015 1:19 PM, John Youn wrote:
> On 11/3/2015 9:49 AM, Bin Liu wrote:
>> Some USB phy drivers have different handling for the controller in each
>> dr_mode. But the phy driver does not have visibility to the dr_mode of
>> the controller.
>>
>> This adds an api to return the dr_mode of the
Hi,
John Youn writes:
>> +enum usb_dr_mode of_usb_get_dr_mode_by_phy(struct device_node *phy_np)
>> +{
>> +return USB_DR_MODE_UNKNOWN;
>> +}
>> static inline bool of_usb_host_tpl_support(struct device_node *np)
>> {
>> return false;
>>
>
>
> Hi Felipe,
>
> This commit in your testing
Hi,
On 11/20/2015 03:24 PM, John Youn wrote:
On 11/20/2015 1:19 PM, John Youn wrote:
On 11/3/2015 9:49 AM, Bin Liu wrote:
Some USB phy drivers have different handling for the controller in each
dr_mode. But the phy driver does not have visibility to the dr_mode of
the controller.
This adds an
Hi,
Bin Liu writes:
+enum usb_dr_mode of_usb_get_dr_mode_by_phy(struct device_node *phy_np);
bool of_usb_host_tpl_support(struct device_node *np);
int of_usb_update_otg_caps(struct device_node *np,
struct usb_otg_caps *otg_caps);
#else
+enum
qset_fill_page_list() do not check for dma mapping errors.
Found by Linux Driver Verification project (linuxtesting.org).
Signed-off-by: Alexey Khoroshilov
---
drivers/usb/host/whci/qset.c | 4
1 file changed, 4 insertions(+)
diff --git a/drivers/usb/host/whci/qset.c b/drivers/usb/host/wh
hi,
On 11/20/2015 03:35 PM, Felipe Balbi wrote:
Hi,
Bin Liu writes:
+enum usb_dr_mode of_usb_get_dr_mode_by_phy(struct device_node *phy_np);
bool of_usb_host_tpl_support(struct device_node *np);
int of_usb_update_otg_caps(struct device_node *np,
struct usb_otg_c
On 11/20/2015 1:38 PM, Bin Liu wrote:
> hi,
>
> On 11/20/2015 03:35 PM, Felipe Balbi wrote:
>>
>> Hi,
>>
>> Bin Liu writes:
>> +enum usb_dr_mode of_usb_get_dr_mode_by_phy(struct device_node *phy_np);
>>bool of_usb_host_tpl_support(struct device_node *np);
>>int of_usb_update_o
Hi,
John Youn writes:
> On 11/20/2015 1:38 PM, Bin Liu wrote:
>> hi,
>>
>> On 11/20/2015 03:35 PM, Felipe Balbi wrote:
>>>
>>> Hi,
>>>
>>> Bin Liu writes:
>>> +enum usb_dr_mode of_usb_get_dr_mode_by_phy(struct device_node *phy_np);
>>>bool of_usb_host_tpl_support(struct device_node
To prevent VBUS contention, the am335x MUSB phy senses VBUS first before
transitioning to host mode. However, for host-only mode, VBUS could be
directly tied to 5V power rail which could prevent MUSB transitions to
host mode.
This change receives dr_mode of the controller then bypass the first
VBU
The filename of am35x-phy-control.h is confusing. The header is used
by the am335x phy driver, but the filename refers to am35x. Even worse
there is indeed another device called am35x but it does not use this
header at all.
Signed-off-by: Bin Liu
---
v2: no change
drivers/usb/phy/phy-am335x-con
Patrick Shirkey wrote:
> > You essentially have to educate yourself on silicon level (ie. what
> > hardware IP is being used in which consumer products) to sustain a
> > dependency on 127 possible devices per bus.
> >
> > I guess you'll find that there are only very few xHCI IPs out there,
> > prob
On 11/16/2015 09:21 AM, Felipe Balbi wrote:
>
> Hi,
>
> Peter Chen writes:
>> On Wed, Nov 11, 2015 at 09:48:00AM -0800, Tim Bird wrote:
>>>
>>>
>>> On 11/10/2015 07:14 PM, Peter Chen wrote:
On Tue, Nov 10, 2015 at 04:46:51PM -0800, Tim Bird wrote:
> This fixes a bug where if you disco
Add support for async_irq to wake up driver from low power mode.
Without this, the power management code never calls resume.
Remove a spurious interrupt enable in the driver resume function.
Signed-off-by: Tim Bird
---
drivers/usb/phy/phy-msm-usb.c | 17 -
include/linux/usb/msm_h
Register the chipidea driver with the phy, so that the phy
driver can kick the gadget driver when it resumes from low power.
The phy-msm-usb (Qualcomm) driver requires this in order to
recover gadget operation after you disconnect the USB cable
and reconnect it.
Signed-off-by: Tim Bird
---
drive
Add optional async_irq to msm_hsusb binding doc.
Signed-off-by: Tim Bird
Acked-by: Rob Herring
---
Documentation/devicetree/bindings/usb/msm-hsusb.txt | 10 --
1 file changed, 8 insertions(+), 2 deletions(-)
diff --git a/Documentation/devicetree/bindings/usb/msm-hsusb.txt
b/Documentat
Hello.
On 11/21/2015 01:37 AM, Tim Bird wrote:
Add optional async_irq to msm_hsusb binding doc.
Signed-off-by: Tim Bird
Acked-by: Rob Herring
---
Documentation/devicetree/bindings/usb/msm-hsusb.txt | 10 --
1 file changed, 8 insertions(+), 2 deletions(-)
diff --git a/Documentatio
On 11/20/2015 9:06 AM, Douglas Anderson wrote:
> The dwc2_hcd_reset_func() function is only ever called directly by a
> delayed work function. As such no locks are already held when the
> function is called.
>
> Doing a read-modify-write of CPU registers and setting fields in the
> main hsotg dat
On Friday 20 November 2015 14:37:16 Tim Bird wrote:
> +- interrupt-names: Should contain the following:
> + "core_irq"USB core interrupt
> + "async_irq" Asynchronous interrupt to wake up from low power mode
> +(optional)
>
>
Sorry for the bike-shedding but how about just
On 11/20/2015 9:06 AM, Douglas Anderson wrote:
> In general it is wise to clear interrupts before processing them. If
> you don't do that, you can get:
> 1. Interrupt happens
> 2. You look at system state and process interrupt
> 3. A new interrupt happens
> 4. You clear interrupt without proce
On 11/20/2015 02:44 PM, Arnd Bergmann wrote:
> On Friday 20 November 2015 14:37:16 Tim Bird wrote:
>> +- interrupt-names: Should contain the following:
>> + "core_irq"USB core interrupt
>> + "async_irq" Asynchronous interrupt to wake up from low power mode
>> +(optional)
>
Register the chipidea driver with the phy, so that the phy
driver can kick the gadget driver when it resumes from low power.
The phy-msm-usb (Qualcomm) driver requires this in order to
recover gadget operation after you disconnect the USB cable
and reconnect it.
Signed-off-by: Tim Bird
---
drive
Add support for async_irq to wake up driver from low power mode.
Without this, the power management code never calls resume.
Remove a spurious interrupt enable in the driver resume function.
Signed-off-by: Tim Bird
---
drivers/usb/phy/phy-msm-usb.c | 17 -
include/linux/usb/msm_h
Add optional async_irq to msm_hsusb binding doc.
Signed-off-by: Tim Bird
Acked-by: Rob Herring
---
Documentation/devicetree/bindings/usb/msm-hsusb.txt | 10 --
1 file changed, 8 insertions(+), 2 deletions(-)
diff --git a/Documentation/devicetree/bindings/usb/msm-hsusb.txt
b/Documentat
On 11/20/2015 03:20 PM, Tim Bird wrote:
> Add optional async_irq to msm_hsusb binding doc.
>
> Signed-off-by: Tim Bird
> Acked-by: Rob Herring
I probably should have taken this Acked-by by Rob off. Sorry about that.
-- Tim
> ---
> Documentation/devicetree/bindings/usb/msm-hsusb.txt | 10
On Friday 20 November 2015 15:20:39 Tim Bird wrote:
> +- interrupt-names: Should contain the following:
> + "core"USB core interrupt
> + "async" Asynchronous interrupt to wake up from low power mode
> +(optional)
>
> - clocks: A list of phandle + clock-speci
On 11/20/2015 03:22 PM, Arnd Bergmann wrote:
> On Friday 20 November 2015 15:20:39 Tim Bird wrote:
>> +- interrupt-names: Should contain the following:
>> + "core"USB core interrupt
>> + "async" Asynchronous interrupt to wake up from low power mode
>> +(optional)
>
Add optional async_irq to msm_hsusb binding doc.
Signed-off-by: Tim Bird
---
Documentation/devicetree/bindings/usb/msm-hsusb.txt | 10 --
1 file changed, 8 insertions(+), 2 deletions(-)
diff --git a/Documentation/devicetree/bindings/usb/msm-hsusb.txt
b/Documentation/devicetree/bindings
Register the chipidea driver with the phy, so that the phy
driver can kick the gadget driver when it resumes from low power.
The phy-msm-usb (Qualcomm) driver requires this in order to
recover gadget operation after you disconnect the USB cable
and reconnect it.
Signed-off-by: Tim Bird
---
drive
Add support for async_irq to wake up driver from low power mode.
Without this, the power management code never calls resume.
Remove a spurious interrupt enable in the driver resume function.
Signed-off-by: Tim Bird
---
drivers/usb/phy/phy-msm-usb.c | 17 -
include/linux/usb/msm_h
Hi,
Am 20.11.2015 um 18:18 schrieb Felipe Balbi:
Hi,
Stefan Wahren writes:
Hi Felipe,
Am 20.11.2015 um 16:27 schrieb Felipe Balbi:
Hi,
Stefan Wahren writes:
Hi Felipe,
Am 19.11.2015 um 20:54 schrieb Felipe Balbi:
Hi John,
John Youn writes:
Fixes commit 09a75e85
"usb: dwc2: refact
Hi,
Stefan Wahren writes:
> Hi,
>
> Am 20.11.2015 um 18:18 schrieb Felipe Balbi:
>>
>> Hi,
>>
>> Stefan Wahren writes:
>>> Hi Felipe,
>>>
>>> Am 20.11.2015 um 16:27 schrieb Felipe Balbi:
Hi,
Stefan Wahren writes:
> Hi Felipe,
>
> Am 19.11.2015 um 20:54 schrieb F
Hi,
Tim Bird writes:
> On 11/16/2015 09:21 AM, Felipe Balbi wrote:
>>
>> Hi,
>>
>> Peter Chen writes:
>>> On Wed, Nov 11, 2015 at 09:48:00AM -0800, Tim Bird wrote:
On 11/10/2015 07:14 PM, Peter Chen wrote:
> On Tue, Nov 10, 2015 at 04:46:51PM -0800, Tim Bird wrote:
>> T
Hi,
On Fri, 2015-11-20 at 13:20 +0200, Mathias Nyman wrote:
> On 17.11.2015 11:18, Chunfeng Yun wrote:
> > From 577f68d9c0ca1531d5f9cae0dcbea2ba116c8551 Mon Sep 17 00:00:00 2001
> > From: Chunfeng Yun
> > Date: Tue, 17 Nov 2015 17:09:05 +0800
> > Subject: [PATCH v12 0/3] Mediatek xHCI support
> >
On Sat, November 21, 2015 9:35 am, Peter Stuge wrote:
> Patrick Shirkey wrote:
>> > You essentially have to educate yourself on silicon level (ie. what
>> > hardware IP is being used in which consumer products) to sustain a
>> > dependency on 127 possible devices per bus.
>> >
>> > I guess you'll
Hi,
I have a libusb (USB-2.0_ tree with the following layout:
HOST (USB 2.0) -> 5 port hub (master) -> 5 x 10 port hub -> 50 x USB devices
It is a 50 unit mobile device charger and also enables USB data comms to
the individual devices. Each node is independently powered. The devices
are all the
1 - 100 of 101 matches
Mail list logo
