When the port goes to suspend or finishes resme, it needs to
notify PHY, it is not a standard EHCI operation, so we add a
quirk for it.
Signed-off-by: Peter Chen
---
drivers/usb/chipidea/host.c | 129 ++
include/linux/usb/chipidea.h |1 +
2 files cha
When the controller is at suspend mode, it can be waken up by
external events (like vbus, dp/dm or id change). Once we receive
the wakeup interrupt, we need to resume the controller first, eg
open clocks, disable some wakeup settings, etc. After that, the
controller can receive the normal USB inter
If the PHY has .notify_suspend and .notify_resume, it means this
imx usb controller needs to add quirks for standard ehci routine.
Signed-off-by: Peter Chen
---
drivers/usb/chipidea/ci_hdrc_imx.c |5 +
1 files changed, 5 insertions(+), 0 deletions(-)
diff --git a/drivers/usb/chipidea/ci
Add system and runtime power management support for imx gluy layer.
Signed-off-by: Peter Chen
---
drivers/usb/chipidea/ci_hdrc_imx.c | 94 ++-
1 files changed, 91 insertions(+), 3 deletions(-)
diff --git a/drivers/usb/chipidea/ci_hdrc_imx.c
b/drivers/usb/chipi
Hi Greg,
This serial adds power management (system & runtime) for chipidea core.
With this, the chipidea controller can be at low power mode when it is not in
use, and the chipidea controller can be the system wakeup source.
It needs to depend on my patch[1], since [1]-"Add power management suppor
For chipidea controller, it does not follow ehci spec strictly.
Taking resume signal as an example, it will stop resume signal about
20-21ms later automatically, but standard ehci spec says, the resume
signal is controlled by software (clear portsc.PORT_RESUME).
This operation causes some remote w
This commit adds runtime and system power management support for
chipidea core. The runtime pm support is controlled by glue
layer, it can be enabled by flag CI_HDRC_SUPPORTS_RUNTIME_PM.
Signed-off-by: Peter Chen
---
drivers/usb/chipidea/ci.h|2 +
drivers/usb/chipidea/core.c | 119
Currently, only imx6 SoC serial adds wakeup logic, so only
enable runtime pm for imx6.
Signed-off-by: Peter Chen
---
drivers/usb/chipidea/ci_hdrc_imx.c |5 +
1 files changed, 5 insertions(+), 0 deletions(-)
diff --git a/drivers/usb/chipidea/ci_hdrc_imx.c
b/drivers/usb/chipidea/ci_hdrc_
- Disable wakeup after probe
- Enable wakeup during the suspend
- Disable wakeup after controller is active
Signed-off-by: Peter Chen
---
drivers/usb/chipidea/ci_hdrc_imx.c | 36
1 files changed, 36 insertions(+), 0 deletions(-)
diff --git a/drivers/usb/ch
It is used to enable USB wakeup, currently only imx6 SoC serial
usb's wakeup is enabled.
Signed-off-by: Peter Chen
---
drivers/usb/chipidea/ci_hdrc_imx.h |1 +
drivers/usb/chipidea/usbmisc_imx.c | 41
2 files changed, 42 insertions(+), 0 deletions(-)
d
Currently, the usbmisc is just an API supplier for controller
driver, the controller calls related APIs to handle different
things among the SoCs, before calling it, the clock must
be on. So the clock operation is useless for usbmisc, it also
increases the difficulties to manage the clock, especial
When we need the PHY can be waken up by external signals,
we can call this API. Besides, we call mxs_phy_disconnect_line
at this API to close the connection between USB PHY and
controller, after that, the line state from controller is SE0.
Once the PHY is out of power, without calling mxs_phy_disco
Submit these, not individually as single patches, but as a patch set,
the first one with subject "[PATCH 1/2]" and the second with
subject "[PATCH 2/2]"
You have to do this, because it is absolutely essentially to let
me know which patch gets applies first and which one gets applied
second. The
This property is used to disconnect line between USB PHY and
USB controller.
Signed-off-by: Peter Chen
---
Documentation/devicetree/bindings/usb/mxs-phy.txt |4
1 files changed, 4 insertions(+), 0 deletions(-)
diff --git a/Documentation/devicetree/bindings/usb/mxs-phy.txt
b/Documentat
Add notify_suspend and notify_resume according to different SoCs.
Signed-off-by: Peter Chen
---
drivers/usb/phy/phy-mxs-usb.c | 91 +++--
1 files changed, 87 insertions(+), 4 deletions(-)
diff --git a/drivers/usb/phy/phy-mxs-usb.c b/drivers/usb/phy/phy-mxs-
When the vbus is not there and the PHY is out of power, we need to
disconnect connection between USB PHY and USB controller, otherwise
the unexpected USB wakeup will occur due to dp/dm change at device
mode.
Signed-off-by: Peter Chen
---
arch/arm/boot/dts/imx6qdl.dtsi |1 +
1 files changed,
We need this to keep PHY's power on or off during the system
suspend mode. If we need to enable USB wakeup, then we
must keep PHY's power being on during the system suspend mode.
Otherwise, we need to keep PHY's power being off to save power.
Signed-off-by: Peter Chen
---
drivers/usb/phy/phy-mxs
It is needed by mx6 SoC serial, but not for mx23 and mx28.
Signed-off-by: Peter Chen
---
drivers/usb/phy/phy-mxs-usb.c | 17 -
1 files changed, 16 insertions(+), 1 deletions(-)
diff --git a/drivers/usb/phy/phy-mxs-usb.c b/drivers/usb/phy/phy-mxs-usb.c
index 87ba429..6d48bde 10
This API is used to set wakeup enable at PHY registers, in that
case, the PHY can be waken up from suspend due to external events,
like vbus change, dp/dm change and id change.
Signed-off-by: Peter Chen
---
include/linux/usb/phy.h | 16
1 files changed, 16 insertions(+), 0 del
After adding IC fixes bits, some PHY bugs are fixed by
IC logic.
Signed-off-by: Peter Chen
---
drivers/usb/phy/phy-mxs-usb.c | 10 ++
1 files changed, 10 insertions(+), 0 deletions(-)
diff --git a/drivers/usb/phy/phy-mxs-usb.c b/drivers/usb/phy/phy-mxs-usb.c
index 4416ed6..af2a9cf 100
Add anatop phandle for usbphy
Signed-off-by: Peter Chen
---
arch/arm/boot/dts/imx6qdl.dtsi |2 ++
1 files changed, 2 insertions(+), 0 deletions(-)
diff --git a/arch/arm/boot/dts/imx6qdl.dtsi b/arch/arm/boot/dts/imx6qdl.dtsi
index ef51342..145ece2 100644
--- a/arch/arm/boot/dts/imx6qdl.dtsi
Add anatop phandle which is used to access anatop registers to
control PHY's power and other USB operations.
Signed-off-by: Peter Chen
---
Documentation/devicetree/bindings/usb/mxs-phy.txt |2 ++
1 files changed, 2 insertions(+), 0 deletions(-)
diff --git a/Documentation/devicetree/bindings
They are used to notify PHY that the controller enters suspend
or finishes resume.
Signed-off-by: Peter Chen
---
include/linux/usb/phy.h | 23 +++
1 files changed, 23 insertions(+), 0 deletions(-)
diff --git a/include/linux/usb/phy.h b/include/linux/usb/phy.h
index 6c0b1c5
The mxs-phy has three versions until now, each versions have
some differences among PHY operations. the 1st version is
for mx23/mx28 SoC, The 2nd version is for mx6q and mx6dl, the
3rd version is for mx6sl and later mx6 platform.
Signed-off-by: Peter Chen
---
drivers/usb/phy/phy-mxs-usb.c | 65
With the auto setting, the PHY's clock and power can be
recovered correctly from low power mode, it is ganranteed by IC logic.
Signed-off-by: Peter Chen
---
drivers/usb/phy/phy-mxs-usb.c | 20 +---
1 files changed, 17 insertions(+), 3 deletions(-)
diff --git a/drivers/usb/phy/
Hi Felipe,
The serial adds power management support for MXS PHY, it includes:
- Add three common PHY API, .set_wakeup, .notify_suspend, notify_resume.
- Related above API implementation at mxs phy driver
- misc changes for mxs phy to support low power mode and wakeup.
Changes for v2:
Since there are three mxs PHY versions, using three compatible
strings for them.
Signed-off-by: Peter Chen
---
Documentation/devicetree/bindings/usb/mxs-phy.txt |6 +-
1 files changed, 5 insertions(+), 1 deletions(-)
diff --git a/Documentation/devicetree/bindings/usb/mxs-phy.txt
b/Docu
On Mon, Oct 21, 2013 at 07:23:11AM -0500, Felipe Balbi wrote:
> Hi,
>
> On Sat, Oct 19, 2013 at 02:17:52PM -0700, Greg KH wrote:
> > On Thu, Oct 17, 2013 at 01:55:02PM +0530, Sachin Kamat wrote:
> > > 'of_match_ptr' is defined in linux/of.h. Include it explicitly to
> > > avoid build breakage in t
Like http://marc.info/?l=linux-usb&m=138200449428874&w=2 said:
two more things are needed to be done:
- If host_start fails, the host_stop should not be called, so we
add check that ci->hcd is not NULL.
- if the host_start fails at the beginning, we need to consider
regulator mismatch issue.
Sign
Hi,
> It looks like you didn't add the dump_stack() call to the UDC driver's
> queue function. You need to add it.
The attached is the log of dump_stack() call in the UDC driver queue
function, for the last few USB request in the USBCV "device descriptor
test – addressed state". From the log, af
From: Freddy Xin
Add VID:DID for Samsung USB Ethernet Adapter.
Signed-off-by: Freddy Xin
---
drivers/net/usb/ax88179_178a.c | 19 ++-
1 file changed, 18 insertions(+), 1 deletion(-)
diff --git a/drivers/net/usb/ax88179_178a.c b/drivers/net/usb/ax88179_178a.c
index 3569293..3
From: Freddy Xin
Correct the definition of AX_RXHDR_CRC_ERR and
AX_RXHDR_DROP_ERR. They are BIT29 and BIT31 in pkt_hdr
seperately.
Signed-off-by: Freddy Xin
---
drivers/net/usb/ax88179_178a.c |4 ++--
1 file changed, 2 insertions(+), 2 deletions(-)
diff --git a/drivers/net/usb/ax88179_178
From: fre...@asix.com.tw
Date: Mon, 21 Oct 2013 14:37:40 +0800
> From: Freddy Xin
>
> Correct the definition of AX_RXHDR_CRC_ERR and
> AX_RXHDR_DROP_ERR. They are BIT29 and BIT31 in pkt_hdr
> seperately.
> Add VID:DID for Samsung USB Ethernet Adapter.
>
> Signed-off-by: Freddy Xin
Do not do t
Hi George,
On 10/15/2013 01:40 PM, George Cherian wrote:
> Laxman/Chanwoo/Kishon,
>
> Any comments on this!!
> Regards
> -George
> On 10/11/2013 12:18 AM, George Cherian wrote:
>> Always cross check with the ID state and the source of interrupt.
>> Also add a case in which ID Source is ID_GND but
On Mon, Oct 21, 2013 at 11:40 AM, Alan Stern wrote:
> On Sat, 19 Oct 2013, Andiry Xu wrote:
>
>> Hi Sarah, nice to see you again:) I'm still working on my PhD degree
>> at UC San Diego. I'm working with storage devices on Linux, but not on
>> driver. With fast non-volatile storage - perhaps as fas
On Saturday, October 19, 2013 2:22 PM, Greg KH wrote:
> On Thu, Oct 17, 2013 at 01:29:11PM -0700, H Hartley Sweeten wrote:
>> Convert ep93xx to use the OHCI platform driver and remove the
>> ohci-ep93xx bus glue driver.
>>
>> Enable CONFIG_OHCI_HCD_PLATFORM in the ep93xx_defconfig so that USB
>> i
Convert ep93xx to use the OHCI platform driver and remove the
ohci-ep93xx bus glue driver.
Enable CONFIG_OHCI_HCD_PLATFORM in the ep93xx_defconfig so that USB
is still enabled by default on the EP93xx platform.
Signed-off-by: H Hartley Sweeten
Acked-by: Alan Stern
Cc: Ryan Mallon
Cc: Lennert B
On Sat, 19 Oct 2013, Andiry Xu wrote:
> Hi Sarah, nice to see you again:) I'm still working on my PhD degree
> at UC San Diego. I'm working with storage devices on Linux, but not on
> driver. With fast non-volatile storage - perhaps as fast as DRAM, all the
> software overhead is significant, incl
On Saturday, October 19, 2013 2:22 PM, Greg KH wrote:
> On Thu, Oct 17, 2013 at 01:29:11PM -0700, H Hartley Sweeten wrote:
>> Convert ep93xx to use the OHCI platform driver and remove the
>> ohci-ep93xx bus glue driver.
>>
>> Enable CONFIG_OHCI_HCD_PLATFORM in the ep93xx_defconfig so that USB
>> i
On Sat, 19 Oct 2013, Vishal Annapurve wrote:
> Hi,
>
> Attaching the new patch which will replace all the occurrences of DID_ABORT
> with DID_TIMOUT in USB Storage whenever it sees US_FLIDX_TIMED_OUT bit
> is set.
It seems okay, but you forgot to update the isd200.c and
cypress_atacb.c files.
A
On Mon, Oct 21, 2013 at 11:50:39AM -0400, Alan Stern wrote:
> On Mon, 21 Oct 2013, Huang Rui wrote:
>
> > In Test 9 of usbtest module, it is used for performing chapter 9 tests N
> > times. This patch adds to support getting bos descriptor test scenario for
> > USB 3.0.
> >
> > Signed-off-by: Hua
On Mon, 21 Oct 2013, Huang Rui wrote:
> In Test 9 of usbtest module, it is used for performing chapter 9 tests N
> times.
>
> USB2.0 Extension descriptor is one of the generic device-level capbility
> descriptors which added in section 9.6.2.1 of USB 3.0 spec.
>
> This patch adds to support gett
On Mon, 21 Oct 2013, Huang Rui wrote:
> In Test 9 of usbtest module, it is used for performing chapter 9 tests N
> times. This patch adds to support getting bos descriptor test scenario for
> USB 3.0.
>
> Signed-off-by: Huang Rui
> ---
> drivers/usb/misc/usbtest.c | 13 +
> 1 file c
Script checkpatch.pl always complains incorrect code style like below:
WARNING: sizeof *udev->bos->desc should be sizeof(*udev->bos->desc)
This patch fixes the warning for usbtest module.
Signed-off-by: Huang Rui
---
drivers/usb/misc/usbtest.c | 16
1 file changed, 8 insertion
On Mon, 21 Oct 2013, Teemu Ojansivu wrote:
> On 21 October 2013 00:13, Alan Stern wrote:
> > On Sun, 20 Oct 2013, Teemu Ojansivu wrote:
> >
> >> Somewhere after kernel 3.2.0 my usb started acting weird and not
> >> working correctly.
> >> For example, 'sudo lsusb -v' makes dmesg say:
> >> [ 717.
Suspend scenario in case of ohci-at91 glue was not properly handled
as it was not suspending generic part of ohci controller. Alan Stern
suggested, properly handle ohci-at91 suspend scenario.
Calling explicitly the ohci_suspend() routine in ohci_hcd_at91_drv_suspend()
will ensure proper handling o
On Sun, 20 Oct 2013, Sarah Sharp wrote:
> > > So it means xHCI driver should clear wakeup flags for suspended ports
> > > in this case, just like ehci driver does. Correct?
> >
> > Yes, I agree.
> >
> > Sarah, is this worth reporting to the Intel chipset engineers as a bug?
>
> I'm not sure. I
Suspend scenario in case of OHCI was not properly
handled in ochi_suspend()routine. Alan Stern
suggested, properly handle OHCI suspend scenario.
This does generic proper handling of suspend
scenario to all OHCI SOC.
Signed-off-by: Manjunath Goudar
Acked-by: Alan Stern
Cc: Greg KH
Cc: linux-us
Suspend scenario in case of ohci-s3c2410 glue was not
properly handled as it was not suspending generic part
of ohci controller. Alan Stern suggested, properly handle
ohci-s3c2410 suspend scenario.
Calling explicitly the ohci_suspend()
routine in ohci_hcd_s3c2410_drv_suspend() will ensure
proper h
Suspend scenario in case of ohci-spear glue was not
properly handled as it was not suspending generic part
of ohci controller. Alan Stern suggested, properly handle
ohci-spear suspend scenario.
Calling explicitly the ohci_suspend() routine in
spear_ohci_hcd_drv_suspend() will ensure proper
handli
Suspend scenario in case of ohci-exynos glue was not
properly handled as it was not suspending generic part
of ohci controller. Alan Stern suggested, properly handle
ohci-exynos suspend scenario.
Calling explicitly the ohci_suspend() routine in
exynos_ohci_suspend() will ensure proper handling of
Hi,
On Wednesday 16 October 2013 07:10 PM, Roger Quadros wrote:
> Hi,
>
> On 10/15/2013 10:54 PM, Kishon Vijay Abraham I wrote:
>> Adapted omap-usb3 PHY driver to Generic PHY Framework and moved phy-omap-usb3
>> driver in drivers/usb/phy to drivers/phy and also renamed the file to
>> phy-ti-pipe3
Hi,
On Monday 21 October 2013 04:49 PM, Arokux X wrote:
> Dear Kishon,
>
> thank you for the answer, no problem it was late! Your understanding
> is almost correct.
>
>> From whatever I could understand, you have a USB HOST controller (each HOST
>> controller has an EHCI controller and a compani
Hi,
On Sat, Oct 19, 2013 at 02:17:52PM -0700, Greg KH wrote:
> On Thu, Oct 17, 2013 at 01:55:02PM +0530, Sachin Kamat wrote:
> > 'of_match_ptr' is defined in linux/of.h. Include it explicitly to
> > avoid build breakage in the future.
>
> Why, what is going to happen in the "future"?
>
> Kernel
On 10/21/2013 02:55 PM, Kishon Vijay Abraham I wrote:
> Hi,
>
> On Wednesday 16 October 2013 07:53 PM, Roger Quadros wrote:
>> On 10/16/2013 04:52 PM, Kishon Vijay Abraham I wrote:
>>> Hi,
>>>
>>> On Wednesday 16 October 2013 06:48 PM, Roger Quadros wrote:
Hi,
On 10/15/2013 10:54 PM
Hi,
On Thursday 17 October 2013 10:08 PM, Felipe Balbi wrote:
> Hi,
>
> On Wed, Oct 16, 2013 at 01:24:11AM +0530, Kishon Vijay Abraham I wrote:
>> There can be systems which does not have a external usb_phy, so get
>> usb_phy only if dt data indicates the presence of PHY in the case of dt boot
>
Hi,
On Wednesday 16 October 2013 07:53 PM, Roger Quadros wrote:
> On 10/16/2013 04:52 PM, Kishon Vijay Abraham I wrote:
>> Hi,
>>
>> On Wednesday 16 October 2013 06:48 PM, Roger Quadros wrote:
>>> Hi,
>>>
>>> On 10/15/2013 10:54 PM, Kishon Vijay Abraham I wrote:
Adapted dwc3 core to use the G
Hi Greg,
Here's a large set of patches for v3.13 merge window. All patches have
been pending in linux-usb for quite a while and soaked in linux-next
for a bit too.
Please consider merging on top of your usb-next branch or let me know
which changes you may want.
cheers
The following changes sinc
Dear Kishon,
thank you for the answer, no problem it was late! Your understanding
is almost correct.
> From whatever I could understand, you have a USB HOST controller (each HOST
> controller has an EHCI controller and a companion OHCI controller?). There are
> separate clocks for each of EHCI an
On Tuesday 15 October 2013 10:10 AM, George Cherian wrote:
Laxman/Chanwoo/Kishon,
Any comments on this!!
Regards
-George
On 10/11/2013 12:18 AM, George Cherian wrote:
Always cross check with the ID state and the source of interrupt.
Also add a case in which ID Source is ID_GND but LATCH state i
In Test 9 of usbtest module, it is used for performing chapter 9 tests N
times.
SuperSpeed USB Device Capability descriptor is one of the generic
device-level capbility descriptors which added in section 9.6.2.2 of USB
3.0 spec.
This patch adds to support getting SuperSpeed USB Device Capability
In Test 9 of usbtest module, it is used for performing chapter 9 tests N
times.
Container ID descriptor is one of the generic device-level capbility
descriptors which added in section 9.6.2.3 of USB 3.0 spec.
This patch adds to support getting Container ID descriptor test scenario
for USB 3.0.
S
In Test 9 of usbtest module, it is used for performing chapter 9 tests N
times. This patch adds to support getting bos descriptor test scenario for
USB 3.0.
Signed-off-by: Huang Rui
---
drivers/usb/misc/usbtest.c | 13 +
1 file changed, 13 insertions(+)
diff --git a/drivers/usb/misc
Hi all,
The following patches implement Binary Device Object Store (BOS) descriptor
set tests in section 9.6.2 of USB 3.0 SPEC. At current usbtest module, it
only supports USB 2.0 chapter 9 tests, so this updates extend the testing
scope to cover the USB 3.0 new descriptors.
Thanks,
Rui
Huang Ru
In Test 9 of usbtest module, it is used for performing chapter 9 tests N
times.
USB2.0 Extension descriptor is one of the generic device-level capbility
descriptors which added in section 9.6.2.1 of USB 3.0 spec.
This patch adds to support getting usb2.0 extension descriptor test
scenario for USB
On Friday 18 October 2013 07:42 PM, Matt Porter wrote:
> This is a summary of an unresolved issue resulting from this thread:
> http://www.spinics.net/lists/arm-kernel/msg277700.html
>
> The BCM281xx family of SoCs contain an OTG subsystem consisting of a
> DWC2 HSOTG controller and an internal UT
+Roman
Hi,
Sorry for the late reply..
On Monday 14 October 2013 11:47 PM, Arokux X wrote:
> Dear Kishon,
>
> On Sat, Oct 12, 2013 at 12:07 PM, Kishon Vijay Abraham I
> wrote:
>> Hi,
>>
>> On Friday 11 October 2013 10:52 PM, Arokux X wrote:
I think you should have a wrapper driver to EHCI
On Thu, 2013-10-17 at 20:49 +0200, Hans de Goede wrote:
> The uas driver is only capable of dealing with an usb-reset it has triggered
> itself, fix the pre and post reset return values to reflect this.
What happens if you get an external reset? This is bad, because we
cannot rule it out, for exam
From: Freddy Xin
Correct the definition of AX_RXHDR_CRC_ERR and
AX_RXHDR_DROP_ERR. They are BIT29 and BIT31 in pkt_hdr
seperately.
Add VID:DID for Samsung USB Ethernet Adapter.
Signed-off-by: Freddy Xin
---
drivers/net/usb/ax88179_178a.c | 23 ---
1 file changed, 20 inser
69 matches
Mail list logo
