* Kishon Vijay Abraham I [150819 23:38]:
> Hi,
>
> On Thursday 06 August 2015 02:17 PM, Tony Lindgren wrote:
> > * Kishon Vijay Abraham I [150805 07:10]:
> >> On Wednesday 05 August 2015 01:31 PM, Tony Lindgren wrote:
> >>>
> >>> We don't have syscon-otghs and to me it seems we need a PHY driver
On 21.08.2015 04:26, Daurnimator wrote:
Description:
After upgrading from linux kernel 4.1.4 to 4.1.5 I'm having trouble
with my USB devices.
First boot: my external keyboard wasn't working
Second boot: my external mouse wasn't working
Third boot: my internal touchpad wasn't working
Additional
On 21 August 2015 at 17:39, Mathias Nyman wrote:
> I can't directly see what would cause it. Only theory for now is if one
> those changes left
> some port change event uncleared, blocking port status change events and
> thus maybe also
> command completion event, and thus causing timeout.
>
>
On Thu, Aug 20, 2015 at 04:58:13PM -0400, Alan Stern wrote:
> On Thu, 20 Aug 2015, Felipe Balbi wrote:
>
> > > > Doesn't Peter need to cope with differentiating protocol vs non-protocol
> > > > stalls ?
> > >
> > > Those matter only for ep0, not for bulk/interrupt.
> >
> > huh ? usbtest send Set
This patch fixes possible regression introduced by patch reworking endpoint
claiming mechanism. It restores setring ep->driver_data to NULL in
usb_ep_autoconfig_reset(), which was removed by patch [1].
[1] commit cc476b42a39d ("usb: gadget: encapsulate endpoint claiming
mechanism")
Reported-b
On Thu, Aug 20, 2015 at 12:41:26PM -0500, Felipe Balbi wrote:
> Hi,
>
>
> > > > > > pass USB CV2.0 MSC TEST. (othwerwise, "Command Set Test - Device
> > > > > > Configured"
> > > > > > will fail)
> > > > >
> > > > > Why would a pending struct usb_request in your queue fail USB CV ?
> > > >
> >
On 20/08/2015 18:46, Felipe Balbi wrote:
> On Thu, Aug 20, 2015 at 06:35:17PM +0200, Gregory CLEMENT wrote:
>> Hi Felipe,
>>
>> On 18/08/2015 16:13, Felipe Balbi wrote:
>>> Hi,
>>>
>>> On Tue, Aug 18, 2015 at 02:36:13PM +0200, Gregory CLEMENT wrote:
Hi again Felipe,
I sent this email
Hi all,
On 20/08/2015 18:12, Gregory CLEMENT wrote:
> According to the OTG specification after a timeout of
> OTG_TIME_A_WAIT_VRISE (the maximum value is 100ms) the driver must
> move from the state a_wait_vrise to the state a_wait_bcon. However,
> the dsps version of musb does not handle this cas
tem tree
patch 4-7: USB gadget subsystem tree
Patches have been prepared on top of linux-next from 20150821.
Best regards
Marek Szyprowski
Samsung R&D Institute Poland
Patch summary:
Marek Szyprowski (7):
phy: exynos-usb2: add vbus regulator support
arm: dts: exynos: add vbus regula
Exynos USB2 PHY driver now supports VBUS regulator, so add it to all
boards which have it available. This also fixes commit
7eec1266751bd3a25e35ce88686634c768fedc24 ("ARM: dts: Add Maxim 77693
PMIC to exynos4412-trats2"), which added new regulators to Trats2 board,
but without linking them to the c
During typical gadget operation, dwc2 clock was enabled 3 times: from
dwc2_gadget_init(), s3c_hsotg_udc_start() and s3c_hsotg_pullup(), and then
disabled in s3c_hsotg_pullup(), s3c_hsotg_udc_stop() and
s3c_hsotg_remove(). This really makes no sense, so leave clock control
code only in dwc2_gadget_i
Exynos USB2 PHY has separate power supply, which is usually provided by
VBUS regulator. This patch adds support for it. VBUS regulator is
optional, to keep compatibility with boards, which have VBUS provided
from some always-on power source.
Signed-off-by: Marek Szyprowski
---
.../devicetree/bin
Even when DWC2 is in (internal) suspended state, it should disable PHY
in suspend and then enable it in resume. This patch fixes unbalanced PHY
control sequence.
Signed-off-by: Marek Szyprowski
---
drivers/usb/dwc2/platform.c | 2 --
1 file changed, 2 deletions(-)
diff --git a/drivers/usb/dwc2/
MAX77693 based regulators are used by USB gadget subsystem, which
doesn't support deferred probe, so the driver should be registered
before USB gadget drivers get probed.
Signed-off-by: Marek Szyprowski
---
drivers/regulator/max77693.c | 12 +++-
1 file changed, 11 insertions(+), 1 delet
DWC2 module on some platforms needs three additional hardware
resources: phy controller, clock and power supply. All of them must be
enabled/activated to properly initialize and operate. This was initially
handled in s3c-hsotg driver, which has been converted to 'gadget' part
of dwc2 driver. Unfort
This patch removes doubled call to s3c_hsotg_of_probe() function.
Signed-off-by: Marek Szyprowski
---
drivers/usb/dwc2/gadget.c | 2 --
1 file changed, 2 deletions(-)
diff --git a/drivers/usb/dwc2/gadget.c b/drivers/usb/dwc2/gadget.c
index 3ee5b4c77a1f..47960787f572 100644
--- a/drivers/usb/dwc
Hi,
On Friday 21 August 2015 06:08 PM, Marek Szyprowski wrote:
> Exynos USB2 PHY has separate power supply, which is usually provided by
> VBUS regulator. This patch adds support for it. VBUS regulator is
> optional, to keep compatibility with boards, which have VBUS provided
> from some always-on
On Thu, 20 Aug 2015, Roland Weber wrote:
> [1.] One line summary of the problem:
> "lsusb -v" as root freezes the kernel on Acer ES1-111M
>
> [2.] Full description of the problem/report:
> As root, "lsusb -v" against USB devices "003:001" or "003:002"
> of my Acer ES1-111M netbook freezes the ker
On Fri, 21 Aug 2015, Peter Chen wrote:
> Thanks, Alan and Felipe.
>
> My problem should be the chipidea udc driver does not support functional
> stall well, it fixes the handling between functional and protocol stall.
>
> My understanding for these two stalls:
>
> - Functional stall, the host s
Fix two occurrences of the Sparse warning:
warning: symbol XXX shadows an earlier one
Signed-off-by: Kris Borer
---
drivers/usb/core/hub.c | 3 +--
1 file changed, 1 insertion(+), 2 deletions(-)
diff --git a/drivers/usb/core/hub.c b/drivers/usb/core/hub.c
index 431839b..a0db6a4 100644
--- a/dr
On Fri, Aug 21, 2015 at 10:26:00AM -0400, Kris Borer wrote:
> Fix two occurrences of the Sparse warning:
>
> warning: symbol XXX shadows an earlier one
>
> Signed-off-by: Kris Borer
Reviewed-by: Felipe Balbi
> ---
> drivers/usb/core/hub.c | 3 +--
> 1 file changed, 1 insertion(+), 2 deletion
On Fri, 21 Aug 2015, Peter Chen wrote:
> Thanks.
>
> I don't have much time to debug this problem deeply today. Below
> are some information:
>
> - The parameter 'stall' is y for g_mass_storage
> - The stall bulk-IN is from the line 1571 at f_mass_storage.c
>
> If I do not stall this bulk-IN, a
On Fri, Aug 21, 2015 at 11:01:29AM +0200, Robert Baldyga wrote:
> This patch fixes possible regression introduced by patch reworking endpoint
> claiming mechanism. It restores setring ep->driver_data to NULL in
> usb_ep_autoconfig_reset(), which was removed by patch [1].
>
> [1] commit cc476b42a39
Hi Laura,
On Mon, Aug 10, 2015 at 05:26:12PM -0700, Laura Abbott wrote:
> v2: Created a proper queue for events instead of just dropping them
How long does it take for the queue to exhaust your memory if you keep
bombarding the driver with requests?
I do not think you need a queue. I believe the
Hello Alan,
> Can you use "git bisect" between 3.17 and 3.18 to find the commit that
> caused the problem to start?
I was afraid I'd have to do that... it's been years since I compiled kernels.
There's a good description on how to do it though. So yes, I should manage.
I have to do it on a netbo
Hi,
On Fri, Aug 21, 2015 at 10:00:50AM -0500, Felipe Balbi wrote:
> On Fri, Aug 21, 2015 at 11:01:29AM +0200, Robert Baldyga wrote:
> > This patch fixes possible regression introduced by patch reworking endpoint
> > claiming mechanism. It restores setring ep->driver_data to NULL in
> > usb_ep_auto
add xHCI and phy drivers for MT8173-EVB
Signed-off-by: Chunfeng Yun
---
arch/arm64/boot/dts/mediatek/mt8173-evb.dts | 16 +++
arch/arm64/boot/dts/mediatek/mt8173.dtsi| 44 +
2 files changed, 60 insertions(+)
diff --git a/arch/arm64/boot/dts/mediatek/mt817
>From 4cab60015fd73f37b7c970ba56c2625fe346fcf3 Mon Sep 17 00:00:00 2001
From: Chunfeng Yun
Date: Sat, 22 Aug 2015 09:35:14 +0800
Subject: [PATCH v6 0/5] Mediatek xHCI support
The patch supports MediaTek's xHCI controller.
There are some differences from xHCI spec:
1. The interval is specified in
MTK xhci host controller defines some extra SW scheduling
parameters for HW to minimize the scheduling effort for
synchronous and interrupt endpoints. The parameters are
put into reseved DWs of slot context and endpoint context
Signed-off-by: Chunfeng Yun
---
drivers/usb/host/Kconfig|
add a DT binding documentation of xHCI host controller for the
MT8173 SoC from Mediatek.
Signed-off-by: Chunfeng Yun
---
.../devicetree/bindings/usb/mt8173-xhci.txt| 52 ++
1 file changed, 52 insertions(+)
create mode 100644 Documentation/devicetree/bindings/usb/mt81
add a DT binding documentation of usb3.0 phy for MT65xx
SoCs from Mediatek.
Signed-off-by: Chunfeng Yun
---
.../devicetree/bindings/phy/phy-mt65xx-usb.txt | 69 ++
1 file changed, 69 insertions(+)
create mode 100644 Documentation/devicetree/bindings/phy/phy-mt65xx-usb.tx
support usb3.0 phy of mt65xx SoCs
Signed-off-by: Chunfeng Yun
---
drivers/phy/Kconfig | 9 +
drivers/phy/Makefile | 1 +
drivers/phy/phy-mt65xx-usb3.c | 456 ++
3 files changed, 466 insertions(+)
create mode 100644 drivers/phy/phy-m
On Thu, Aug 20, 2015 at 4:20 PM, David Laight wrote:
> From: Vaishali Thakkar
>> Sent: 19 August 2015 06:31
>> To: Felipe Balbi
>> Cc: Greg Kroah-Hartman; linux-usb@vger.kernel.org;
>> linux-ker...@vger.kernel.org
>> Subject: [PATCH] usb: gadget: f_uac1: Convert use of __constant_cpu_to_le16
>>
33 matches
Mail list logo
