Hi Sarah,
I built:
- current kernel git with SUSE config
- libgphoto2 with the clear_halt reenabled
- rebooted
gphoto2 now hangs on the second try
- only applied both patches referenced.
I need to whack them a bit as xhci_giveback_urb_in_irq got a new parameter
- rebuilt, rebooted
gphoto2
Add notify_suspend and notify_resume according to different SoCs.
Signed-off-by: Peter Chen
---
drivers/usb/phy/phy-mxs-usb.c | 73 +
1 files changed, 73 insertions(+), 0 deletions(-)
diff --git a/drivers/usb/phy/phy-mxs-usb.c b/drivers/usb/phy/phy-mxs-
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
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/
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
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
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 831b13e..e0b0de0 10
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
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 87ba429..831b13e 100
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.
Hi Shawn,
The last four ar
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
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,
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
On Wed, Oct 09, 2013 at 12:57:45PM +0200, Johan Hovold wrote:
> On Wed, Sep 25, 2013 at 11:53:00AM +0200, Andrew Lunn wrote:
> > TODO
> > Custom resume function
>
> You have to implement a custom resume function as usb-serial will use
> the incompatible generic one otherwise. Model it after the g
Hi,
> After adding IC fixes bits, some PHY bugs are fixed by
> IC logic.
Can you please elaborate what those bits do exactly ? They seem like a magic
stuff to me thus far, which is not exactly helpful . I can't find them in the
datasheet either.
> Signed-off-by: Peter Chen
> ---
> drivers/us
Dear Peter Chen,
> Add notify_suspend and notify_resume according to different SoCs.
>
> Signed-off-by: Peter Chen
> ---
> drivers/usb/phy/phy-mxs-usb.c | 73
> + 1 files changed, 73
> insertions(+), 0 deletions(-)
>
> diff --git a/drivers/usb/phy/phy-m
Dear Peter Chen,
> 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, w
Dear Peter Chen,
> 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/bi
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
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] adds some common PHY APIs,
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
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 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
Add property for supporting runtime power management
Signed-off-by: Peter Chen
---
.../devicetree/bindings/usb/ci13xxx-imx.txt|2 ++
1 files changed, 2 insertions(+), 0 deletions(-)
diff --git a/Documentation/devicetree/bindings/usb/ci13xxx-imx.txt
b/Documentation/devicetree/bindin
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
- 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
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 | 99 ++-
1 files changed, 96 insertions(+), 3 deletions(-)
diff --git a/drivers/usb/chipidea/ci_hdrc_imx.c
b/drivers/usb/chipi
Enable runtime power management support for usbotg and usb host 1.
Signed-off-by: Peter Chen
---
arch/arm/boot/dts/imx6qdl-sabresd.dtsi |2 ++
1 files changed, 2 insertions(+), 0 deletions(-)
diff --git a/arch/arm/boot/dts/imx6qdl-sabresd.dtsi
b/arch/arm/boot/dts/imx6qdl-sabresd.dtsi
index
It is used to enable USB wakeup
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(-)
diff --git a/drivers/usb/chipidea/ci_hdrc_imx.h
b/drivers
Hi,
On Friday 11 October 2013 10:52 PM, Arokux X wrote:
>> I think you should have a wrapper driver to EHCI/OHCI to handle this reset.
>
> Thank you Kishon and Peter for the quick replies. Is there any good
> example of such a wrapper driver in the kernel already?
can you explain how your IP act
Whitespace fixes, including:
- Whitespace after if-keyword
- Spaces to Tabs
Other coding style fixes:
- Added braces for if-else blocks where missing
Signed-off-by: Matthias Beyer
---
drivers/usb/core/devio.c | 40 +---
1 file changed, 21 insertions(+), 19
Added braces around switch statement as the styleguide tells us.
Indented the switch-block for it and split a function call
(driver->unlocked_ioctl() on line 1876) arguments to several lines to
fit the 80-column convention.
Signed-off-by: Matthias Beyer
---
drivers/usb/core/devio.c | 63
Thomas Schäfer writes:
> Am Samstag, 12. Oktober 2013, 00:13:59 schrieb Bjørn Mork:
>> Thomas Schäfer writes:
>> > Bjørn writes:
>> >> Could be the driver. I don't know if it is ever tested with IPv6, and
>> >> it does a bit of header magic so it is possible to screw up. Of course,
>> >> the sa
Bjørn Mork writes:
> Do those packets (the RA and NS from the firmware) show up in a normal
> IP packet dump from the wwan interface? Do you see any replies? I
> guess you don't. We set NOARP on the interface because MBIM really
> doesn't have any L2 headers. But here we see that the firmware
On Sat, 2013-10-12 at 14:24 +0800, Wei Yongjun wrote:
> From: Wei Yongjun
>
> Fix to return -ENOMEM in the padding pkt alloc fail error handling
> case instead of 0, as done elsewhere in this function.
>
> Signed-off-by: Wei Yongjun
Acked-by: Oliver Neukum
--
To unsubscribe from this list: s
Am Samstag, 12. Oktober 2013, 13:46:19 schrieb Bjørn Mork:
> > happens:
> > ifconfig wwan0 arp
>
> Nope, that won't make any difference. At least on a proper ethernet
> interface we still answer NS for our addresses, even if we disable
> sending them.
>
> So the questions still are: Do you se
On Sat, 12 Oct 2013, Peter Chen wrote:
> Add property for supporting runtime power management
>
> Signed-off-by: Peter Chen
> ---
> .../devicetree/bindings/usb/ci13xxx-imx.txt|2 ++
> 1 files changed, 2 insertions(+), 0 deletions(-)
>
> diff --git a/Documentation/devicetree/binding
Dear Peter Chen,
On Sat, 12 Oct 2013 17:09:45 +0800, Peter Chen wrote:
> 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 dele
Hello.
On 12-10-2013 13:01, Matthias Beyer wrote:
Whitespace fixes, including:
- Whitespace after if-keyword
- Spaces to Tabs
Other coding style fixes:
- Added braces for if-else blocks where missing
Signed-off-by: Matthias Beyer
---
drivers/usb/core/devio.c | 40
Am Samstag, 12. Oktober 2013, 13:46:19 schrieben Sie:
> So the questions still are: Do you see those solicitatins going from the
> driver to the IP layer? And do you see any Neighbor Advertisement
> replies from the IP layer? If the respective answers are yes/no, then
> you should look elsewhere
Hi,
With v3.12-rc4 I can no longer connect to N800 (OMAP2) with USB
(peripheral, g_ether).
According to git bisect this is caused by:
9b0a1de3c85d99d881c86a29b3d52da7b9c7bd61 is the first bad commit
commit 9b0a1de3c85d99d881c86a29b3d52da7b9c7bd61
Author: Bin Liu
Date: Tue Sep 17 15:33:35 2013
Hi,
On Sun, Oct 13, 2013 at 12:46:18AM +0300, Aaro Koskinen wrote:
> With v3.12-rc4 I can no longer connect to N800 (OMAP2) with USB
> (peripheral, g_ether).
To clarify, I was running v3.12-rc4 on N800/peripheral side and that's
where the problem is; on host side I'm running some old Debian kerne
44 matches
Mail list logo