On Thu, May 08, 2014 at 10:07:25AM -0400, Alan Stern wrote:
> On Thu, 8 May 2014, Hans de Goede wrote:
>
> > Hi,
> >
> > On 05/08/2014 12:00 AM, Maxime Ripard wrote:
> > > On Wed, May 07, 2014 at 10:25:55AM -0400, Alan Stern wrote:
> > >> On Tue, 6 May 2014, Maxime Ripard wrote:
> > >>
> > >>> Fr
On Thu, 2014-05-08 at 14:11 -0400, Alan Stern wrote:
> On Thu, 8 May 2014, Dan Williams wrote:
>
> > > Also, instead of adding another #ifdef here, you could add a #else
> > > section to the existing #ifdef in which you define an inline version of
> > > hub_handle_remote_wakeup() (or a macro versi
On Thu, 2014-05-08 at 15:14 -0400, Alan Stern wrote:
> On Thu, 8 May 2014, Dan Williams wrote:
>
> > On Thu, May 8, 2014 at 11:09 AM, Alan Stern
> > wrote:
> > > On Thu, 8 May 2014, Dan Williams wrote:
> > >
> > >> On Thu, May 8, 2014 at 9:09 AM, Alan Stern
> > >> wrote:
> > >> > On Thu, 8 May
Are there any new patches to test or news regarding "xhci_drop_endpoint"-issue?
Thanks, Bernhard
On 2014-03-25 19:53 CEST (UTC+2), baumber wrote:
Thank you for your patch, but the same problems occur with the patch applied.
=> log attached
=> "xHCI xhci_drop_endpoint called with disabled ep"-
Sounds good. I was reading here (https://lwn.net/Articles/434833/)
about the dev_dbg() function. Any ideas what I should do to enable
this type of debugging on Debian Linux? I should mention that I've
never built the kernel from source before. :)
Thanks,
--
To unsubscribe from this list: send
On Mon, 5 May 2014, Amit Virdi wrote:
> Interrupt endpoints behave quite similar to the bulk endpoints with the
> difference that the endpoints expect data sending/reception request at
> particular intervals till the whole data has not been transmitted.
>
> The interrupt EP support is added to ga
Hi, Blake
I am afraid that you may need to enable the debug function: dev_dbg(),
it will help people diagnose this problem. From the existing log, in
the first case, the probe() function is only called once, but in the
second case, the probe() function is called twice. Maybe more debug
information
Dear all,
I got two new Intenso 3.5" Memory Box with 3TB in the metallic edition
with USB 3.0 interface.
Please see the attached output of `lsusb -vvv -d 2109:0701` with
redacted iSerial. If anyone needs the S/N, please contact me off-list.
If you need any non-serial number info, please contact
Hi,
On Thu, May 08, 2014 at 11:38:43PM -0007, Amit Uttamchandani wrote:
> Should I send the driver as a git patch directly to you or to the
> mailing list?
always mailing list, I don't merge anybody's branches
--
balbi
signature.asc
Description: Digital signature
From: Bjørn Mork
Date: Fri, 9 May 2014 14:45:00 +0200
> This driver maps 802.1q VLANs to MBIM sessions. The mapping is based on
> a bogus assumption that all tagged frames will use the acceleration API
> because we enable NETIF_F_HW_VLAN_CTAG_TX. This fails for e.g. frames
> tagged in userspace
On Thu, 8 May 2014, Paul Zimmerman wrote:
> > That doesn't handle the problem I described above. When the dwc3
> > driver gets the late delayed status response, it will think it is a
> > response to the new SETUP packet, and so it will carry out a bogus
> > transfer. It won't know that the statu
Add a new driver for the USB 3.0 PHY on Exynos5 series of SoCs.
The new driver uses the generic PHY framework and will interact
with DWC3 controller present on Exynos5 series of SoCs.
Also, created a new header file in linux/mfd/syscon/ for
Exynos5 SoCs and put the required PMU offset definitions
Adding support to enable/disable VBUS controlled by a
regulator, to enable vbus supply on the port.
Signed-off-by: Vivek Gautam
---
Changes from v7:
- Rebased on top of [PATCH v8 1/2] phy: Add new Exynos5 USB 3.0 PHY driver.
drivers/phy/phy-exynos5-usbdrd.c | 32
On Fri, May 9, 2014 at 4:21 PM, Vivek Gautam wrote:
> Hi Sylwester,
>
>
> On Fri, May 9, 2014 at 3:43 PM, Sylwester Nawrocki
> wrote:
>> Hi Vivek,
>>
>> On 08/05/14 11:03, Vivek Gautam wrote:
>> diff --git a/Documentation/devicetree/bindings/phy/samsung-phy.txt
>> b/Documentation/devicet
From: Kamil Debski
Add support to PHY of USB2 of the Exynos 5250 SoC.
Signed-off-by: Kamil Debski
[gautam.vi...@samsung.com: Split the usb phy entries from
syscon entries from earlier patch: dts: Add usb2phy to Exynos 5250]
[gautam.vi...@samsung.com: Added phy entry for OHCI also along with EHC
This patch adds sysreg-syscon node to exynos5250 and exynos5420 device
tree, to access System Register's registers using syscon driver.
Signed-off-by: Kamil Debski
[gautam.vi...@samsung.com: Split this syreg-syscon dts entry from
dts: Add usb2phy to Exynos 5250 patch]
[gautam.vi...@samsung.com: a
Based on 'for-next' branch of Kgene's linux-samsung tree.
These patches are as per discussions on the driver side patches
which have already been acked. [1]
Changes from v1:
- Rebase on 'for-next' branch.
- Removed 'phy-names' property as per discuusion in the driver patches. [1]
V1 of this ser
Add required device node for ehci and ohci controllers to
enable USB 2.0 support.
Signed-off-by: Vivek Gautam
---
Changes from v1:
- Removed 'phy-names' property from the 'port'.
- Added node references for the nodes.
arch/arm/boot/dts/exynos5420.dtsi | 30 ++
1
Add required device node for usb2phy to let enable USB 2.0
support.
Signed-off-by: Vivek Gautam
---
Changes from v1:
- Added node references for the phy node.
arch/arm/boot/dts/exynos5420.dtsi | 10 ++
1 file changed, 10 insertions(+)
diff --git a/arch/arm/boot/dts/exynos5420.dtsi
I'm running next-20140508 kernel on imx6q-sabresd board with USB
mouse/keyboard connected to OTG port. It works well on 3.15-rc but
is broken on recent linux-next kernel with the message like below.
...
usb 1-1: device v413c p2107 is not supported
hub 1-0:1.0: unable to enumerate USB device on p
From: Philippe De Swert
Readlink can return the total length of the buffer (here 4096), so we do not
want to dereference target[4096] as that would give an off by one error.
Signed-off-by: Philippe De Swert
---
src/usbg.c | 7 ---
1 file changed, 4 insertions(+), 3 deletions(-)
diff --git
From: Philippe De Swert
Avoid calling usbg_read_string with a 40 byte long buffer, which in turn is
filled in
by usbg_read_buf which uses a maximum of USBG_MAX_LENGTH which is 256 bytes.
Signed-off-by: Philippe De Swert
---
src/usbg.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
dif
From: Philippe De Swert
We check if func is NULL, so if the allocation function failed we should
not dereference or handle it anymore, so we jump straight to the end.
Signed-off-by: Philippe De Swert
---
src/usbg.c | 1 +
1 file changed, 1 insertion(+)
diff --git a/src/usbg.c b/src/usbg.c
ind
From: Philippe De Swert
This patch series fixes a number of issues found with coverity in libusbg
A pull request has also be made:
https://github.com/libusbg/libusbg/pull/4
There is one potential remaing potential memory leak in the
usbg_add_config_function.
We could leak b there, but I am not
This driver maps 802.1q VLANs to MBIM sessions. The mapping is based on
a bogus assumption that all tagged frames will use the acceleration API
because we enable NETIF_F_HW_VLAN_CTAG_TX. This fails for e.g. frames
tagged in userspace using packet sockets. Such frames will erroneously
be considered
Hi Felipe,
Could you please pull the following three patches for v3.16 ? They've been
reviewed on the linux-media and linux-usb mailing list.
The following changes since commit c9eaa447e77efe77b7fa4c953bd62de8297fd6c5:
Linux 3.15-rc1 (2014-04-13 14:18:35 -0700)
are available in the git repos
Hi,
On Fri, May 09, 2014 at 09:07:00AM +, suresh.gu...@freescale.com wrote:
> > Are you really sure we can't get async VBUS state change notifications
> > until controller has USB_CMD_RUN_STOP bit set (and the same bit actually
> > controls internal 1.5k dataline pullup)? If yes, I guess it me
Hi Sylwester,
On Fri, May 9, 2014 at 3:43 PM, Sylwester Nawrocki
wrote:
> Hi Vivek,
>
> On 08/05/14 11:03, Vivek Gautam wrote:
> diff --git a/Documentation/devicetree/bindings/phy/samsung-phy.txt
> b/Documentation/devicetree/bindings/phy/samsung-phy.txt
> >>> index b422e38..51efe4c
Hi Vivek,
On 08/05/14 11:03, Vivek Gautam wrote:
diff --git a/Documentation/devicetree/bindings/phy/samsung-phy.txt
b/Documentation/devicetree/bindings/phy/samsung-phy.txt
>>> index b422e38..51efe4c 100644
>>> --- a/Documentation/devicetree/bindings/phy/samsung-phy.txt
>>
On 06/05/2014 17:16, Alexandre Belloni :
> Found using smatch: drivers/usb/gadget/atmel_usba_udc.c:1689 usba_udc_irq()
> error: we previously assumed 'udc->driver' could be null (see line 1636)
>
> Always test udc->driver before using its members.
>
> Signed-off-by: Alexandre Belloni
Acked-by:
[CCing DT maintainers]
On 08.05.2014 11:03, Vivek Gautam wrote:
> On Thu, May 8, 2014 at 11:35 AM, Vivek Gautam
> wrote:
>> Hi Sylwester,
>>
>>
>> On Tue, May 6, 2014 at 7:57 PM, Sylwester Nawrocki
>> wrote:
>>> On 28/04/14 08:17, Vivek Gautam wrote:
Add a new driver for the USB 3.0 PHY on
> -Original Message-
> From: Paul Fertser [mailto:fercer...@gmail.com]
> Sent: Friday, May 09, 2014 1:44 AM
> To: Gupta Suresh-B42813
> Cc: ba...@ti.com; Li Yang-Leo-R58472; linux-usb@vger.kernel.org; linux-
> ker...@vger.kernel.org
> Subject: Re: [PATCH] usb: gadget: fsl: check vbus pres
Hi Vivek,
On 05.05.2014 07:02, Vivek Gautam wrote:
> From: Kamil Debski
>
> Add the phy provider, supplied by new Exynos-usb2phy using
> Generic phy framework.
> Keeping the support for older USB phy intact right now, in order
> to prevent any functionality break in absence of relevant
> device
Hi Vivek,
On 05.05.2014 07:02, Vivek Gautam wrote:
> Add support to consume phy provided by Generic phy framework.
> Keeping the support for older usb-phy intact right now, in order
> to prevent any functionality break in absence of relevant
> device tree side change for ohci-exynos.
> Once we mov
I can't see how this relates to Julius patch though, and I'm not sure yet why it
only triggers when devices are connected to SS ports. Maybe just unlucky timing?
I think the non-SS ports are connected to the EHCI controllers rather
than the XHCI controllers. So that explains at least one detai
35 matches
Mail list logo
