1.289548] ohci-platform: OHCI generic platform driver
> [1.294884] usbcore: registered new interface driver usb-storage
> [1.301231] mousedev: PS/2 mouse device common for all mice
> [1.307197] rtc-efi rtc-efi: rtc core: registered rtc-efi as rtc0
>
> But this error goes off, if I d
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
From: Vivek Gautam
Add required device node for usb2phy to let enable USB 2.0
support.
Signed-off-by: Vivek Gautam
---
arch/arm/boot/dts/exynos5420.dtsi | 10 ++
1 file changed, 10 insertions(+)
diff --git a/arch/arm/boot/dts/exynos5420.dtsi
b/arch/arm/boot/dts/exynos5420.dtsi
inde
From: Vivek Gautam
Add required device node for ehci and ohci controllers to
enable USB 2.0 support.
Signed-off-by: Vivek Gautam
---
arch/arm/boot/dts/exynos5420.dtsi | 30 ++
1 file changed, 30 insertions(+)
diff --git a/arch/arm/boot/dts/exynos5420.dtsi
b/arch
patch]
[gautam.vi...@samsung.com: added similar syscon entry for exynos5420]
Signed-off-by: Vivek Gautam
[vikas.saj...@samsung.com: updated the binding document]
Signed-off-by: Vikas Sajjan
---
.../devicetree/bindings/arm/samsung/sysreg.txt | 11 +--
arch/arm/boot/dts/exynos5250
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 v2:
- Addressed kukjin's comments to update DT binding documentation for
sysreg.
- removed the version for each
Hi Alan,
On Mon, Dec 9, 2013 at 8:54 PM, Alan Stern wrote:
> On Mon, 9 Dec 2013, Vikas Sajjan wrote:
>
>> Does warm reset while activating SuperSpeed HUBs if the hub activate type
>> is HUB_RESET_RESUME.
>>
>> When we do Suspend-to-RAM with (any one of the 16, 32,
Hi Sarah,
On Mon, Dec 9, 2013 at 11:54 PM, Sarah Sharp
wrote:
> On Mon, Dec 09, 2013 at 10:24:52AM -0500, Alan Stern wrote:
>> On Mon, 9 Dec 2013, Vikas Sajjan wrote:
>>
>> > Does warm reset while activating SuperSpeed HUBs if the hub activate type
>> > is HUB_R
-review.googlesource.com/#/c/177132/
Tested on exynos5420 and exynos5250 with Transcend Jetflash USB 3.0 device
(8564:1000)
rebased on Greg Kroah-Hartman's usb-next
git://git.kernel.org/pub/scm/linux/kernel/git/gregkh/usb.git
Signed-off-by: Vikas Sajjan
---
drivers/usb/core/hub.c |
with DWC3 now passing full USB3 certification, I want
> to be very careful with patches I accept, specially related to PM ;-)
>
> --
> balbi
Will test both HOST and GADGET mode as per your suggestion and update you.
--
Thanks and Regards
Vikas Sajjan
--
To unsubscribe from this list:
Hi Felipe,
On 16 October 2012 15:36, Felipe Balbi wrote:
> Hi,
>
> On Tue, Oct 16, 2012 at 03:15:36PM +0530, Vikas Sajjan wrote:
>> Adds suspend and resume callbacks as part of the power management
>> support to DWC3 controller Driver.
>> This patch facilitates tr
Adds suspend and resume callbacks to exynos dwc3 driver as part of
power management support.
This change does gating of dwc3 clock during suspend/resume cycles.
Signed-off-by: Abhilash Kesavan
Signed-off-by: Vikas C Sajjan
CC: Doug Anderson
---
drivers/usb/dwc3/dwc3-exynos.c | 31 +++
Adds power management support to XHCI platform driver.
This patch facilitates the transition of xHCI host controller
between S0 and S3/S4 power states, during suspend/resume cycles.
Signed-off-by: Abhilash Kesavan
Signed-off-by: Vikas C Sajjan
CC: Doug Anderson
---
drivers/usb/host/xhci-plat.c
Adds suspend and resume callbacks as part of the power management
support to DWC3 controller Driver.
This patch facilitates transition of DWC3 controller between D0 and D3
power states during suspend/resume cycles.
Signed-off-by: Abhilash Kesavan
Signed-off-by: Vikas C Sajjan
CC: Doug Anderson
d USB detection and enumeration across multiple cycles of
suspend/resume using 2.0 and 3.0 devices on D-link SS hub.
Vikas Sajjan (3):
usb: dwc3: Add the suspend/resume functionality
usb: xhci: Add the suspend/resume functionality
exynos5: usb: dwc3: Add suspend/resume functionality
d
Adding the suspend and resume functionality to exynos dwc3 driver
Signed-off-by: Abhilash Kesavan
Signed-off-by: Vikas C Sajjan
CC: Doug Anderson
---
drivers/usb/dwc3/dwc3-exynos.c | 39 +++
1 files changed, 39 insertions(+), 0 deletions(-)
diff --git a/d
Adding the suspend and resume functionality for the XHCI driver
Signed-off-by: Abhilash Kesavan
Signed-off-by: Vikas C Sajjan
CC: Doug Anderson
---
drivers/usb/host/xhci-plat.c | 33 +
1 files changed, 33 insertions(+), 0 deletions(-)
diff --git a/drivers/usb
nd/resume using 2.0 and 3.0 devices on D-link SS hub.
Vikas Sajjan (3):
usb: dwc3: Add the suspend/resume functionality
usb: xhci: Add the suspend/resume functionality
exynos5: usb: dwc3: Add the suspend/resume functionality
drivers/usb/dwc3/core.
Adding the suspend and resume funtionality to DWC3 core.
Signed-off-by: Abhilash Kesavan
Signed-off-by: Vikas C Sajjan
CC: Doug Anderson
---
drivers/usb/dwc3/core.c | 54 +++
1 files changed, 54 insertions(+), 0 deletions(-)
diff --git a/drivers/u
Hi kishon,
On 12 October 2012 16:27, kishon wrote:
> Hi,
>
>
> On Wednesday 10 October 2012 07:35 PM, Vikas C Sajjan wrote:
>>
>> From: Vikas Sajjan
>>
>> Adding the suspend and resume funtionality to DWC3 core.
>>
>> Signed-off-by: Abhilash
Hi Felipe,
On 11 October 2012 13:17, Felipe Balbi wrote:
>
> Hi,
>
> On Wed, Oct 10, 2012 at 07:35:47PM +0530, Vikas C Sajjan wrote:
> > From: Vikas Sajjan
> >
> > Adding the suspend and resume funtionality to DWC3 core.
> >
> > Signed-off-by: Abhilash
Even though the mem region is requested from the Globals address
space (DWC3_GLOBALS_REGS_START), the offsets are given from the
starting of the xHCI address space.
By subtracting DWC3_GLOBALS_REGS_START from the offset ( as done in
dwc3_readl() and dwc3_writel() ) resolves the issue.
Signed-off-
s resolved.
Thanks and Regards
Vikas Sajjan
--- Original Message ---
Sender : VIKAS SAJJAN C Technical
Manager/SISO-Solution 1/Samsung Electronics
Date : Aug 20, 2012 15:53 (GMT+09:00)
Title : Re: Re: 3.0 device attached to USB 3.0 hub port doesn't respond
address device command
.
Regards
Vikas Sajjan
--- Original Message ---
Sender : Andiry Xu
Date : Aug 18, 2012 21:54 (GMT+09:00)
Title : Re: 3.0 device attached to USB 3.0 hub port doesn't respond address
device command after resume
On Sat, Aug 18, 2012 at 7:41 PM, VIKAS SAJJAN C
wrote:
>
> Hi All,
] usb 4-1.1: device not accepting address 3, error -62
i was referring this
http://www.spinics.net/lists/linux-usb/msg58474.html . but then i found that i
already have this patch. ( USB: Set hub depth after USB3 hub reset )
Regards
Vikas Sajjan
from
[<80327db4>] (xhci_register_plat+0x1c/0x24)
[5.034024] [<80327db4>] (xhci_register_plat+0x1c/0x24) from [<8072e0a4>]
(xhci_hcd_init+0x10/0x30)
[5.043052] [<8072e0a4>] (xhci_hcd_init+0x10/0x30) from [<8000869c>]
(do_one_initcall+0xa0/0x170)
[5.051904] [<8000869c>] (do_one_initcall+0xa0/0x170) from [<80711a48>]
(kernel_init+0xf8/0x1b4)
[5.060672] [<80711a48>] (kernel_init+0xf8/0x1b4) from [<8000fa48>]
(kernel_thread_exit+0x0/0x8)
How i wonder where is the problem in xhci_mem_cleanup()...
Regards
Vikas Sajjan
USB_S2R.patch
Description: Binary data
:59 (GMT+09:00)
Title : Re: usb 2.0 device connected on Super Speed HUB on USB 3.0 Port throws
error during enumeration on 3.4 kernel.
2012/7/13 Andiry Xu :
> On 07/13/2012 04:57 PM, VIKAS SAJJAN C wrote:
>>
>> Hi Andiry,
>>
>>
>> 1. xHCI root hub --- SS h
works
fine.
I dont have another SS hub to check with.
please find the attachement fot the log.
Regards
Vikas Sajjan
--- Original Message ---
Sender : Andiry Xu
Date : Jul 13, 2012 17:11 (GMT+09:00)
Title : Re: usb 2.0 device connected on Super Speed HUB on USB 3.0 Port throws
2.0 Device through a SS Hub
connected to USB 3.0 port (XHCI root hub).
Regards
Vikas Sajjan
--- Original Message ---
Sender : Andiry Xu
Date : Jul 13, 2012 16:29 (GMT+09:00)
Title : Re: usb 2.0 device connected on Super Speed HUB on USB 3.0 Port throws
error during enumeration on 3.4
Hi ,
I am working on 3.4 kernel , when i try to connect a USB 2.0 device on Super
Speed HUB , i get following error.
usb 3-1.1: Device not responding to set address.
usb 3-1.1: device not accepting address 3, error -71
any inputs will be of great help.
Thanks and Regards
Vikas Sajjan
30 matches
Mail list logo
