Hi,
On Wed, Mar 06, 2013 at 08:44:25AM +0800, Greg Kroah-Hartman wrote:
On Wed, Mar 06, 2013 at 12:22:24AM +0200, Felipe Balbi wrote:
Hi,
On Tue, Mar 05, 2013 at 11:16:44PM +0100, Arnd Bergmann wrote:
1bf0cf6040 usb: gadget: omap_udc: convert to udc_start/udc_stop
made some trivial
Hi,
On Wed, Mar 06, 2013 at 10:11:41AM +0800, Chao Xie wrote:
3. For the revison register. It exists in some SOCes(pxa168), but for
some SOCes, the register dispears(pxa910, armada610). These SOCes are
developed by different desgin teams, and it need to be enhanced, but
for current products i
Ming Lei ming@canonical.com writes:
Here is one link I found:
http://marc.info/?l=linux-usbm=132557022902261w=2
Thanks. This section caught my eye:
The USB suspend/resume code is full of those crazy let's use one
function, and pass it as an *argument* what to do. It's a
On Wed, Mar 06, 2013 at 04:24:58PM +0800, Chao Xie wrote:
On Wed, Mar 6, 2013 at 4:10 PM, Felipe Balbi ba...@ti.com wrote:
Hi,
On Wed, Mar 06, 2013 at 10:11:41AM +0800, Chao Xie wrote:
3. For the revison register. It exists in some SOCes(pxa168), but for
some SOCes, the register
Hi,
On Wed, Mar 06, 2013 at 09:40:28AM +0800, Fabio Baltieri wrote:
Add transceiver notifier event handling to the ux500 driver to set vbus
on specific transceiver events.
Acked-by: Linus Walleij linus.wall...@linaro.org
Signed-off-by: Fabio Baltieri fabio.balti...@linaro.org
Hi,
On Tuesday 05 March 2013 08:09 PM, Felipe Balbi wrote:
Hi,
On Tue, Mar 05, 2013 at 08:07:03PM +0530, Kishon Vijay Abraham I wrote:
Add dwc3 core dt data as a subnode to dwc3 omap glue data in omap5 dt
data file. The information for the entered data node is available @
On Wed, Mar 6, 2013 at 4:53 PM, Felipe Balbi ba...@ti.com wrote:
On Wed, Mar 06, 2013 at 04:24:58PM +0800, Chao Xie wrote:
On Wed, Mar 6, 2013 at 4:10 PM, Felipe Balbi ba...@ti.com wrote:
Hi,
On Wed, Mar 06, 2013 at 10:11:41AM +0800, Chao Xie wrote:
3. For the revison register. It exists
Hi,
On Wed, Mar 06, 2013 at 02:25:48PM +0530, kishon wrote:
Hi,
On Tuesday 05 March 2013 08:09 PM, Felipe Balbi wrote:
Hi,
On Tue, Mar 05, 2013 at 08:07:03PM +0530, Kishon Vijay Abraham I wrote:
Add dwc3 core dt data as a subnode to dwc3 omap glue data in omap5 dt
data file. The
On Wed, Mar 06, 2013 at 05:02:28PM +0800, Chao Xie wrote:
On Wed, Mar 6, 2013 at 4:53 PM, Felipe Balbi ba...@ti.com wrote:
On Wed, Mar 06, 2013 at 04:24:58PM +0800, Chao Xie wrote:
On Wed, Mar 6, 2013 at 4:10 PM, Felipe Balbi ba...@ti.com wrote:
Hi,
On Wed, Mar 06, 2013 at 10:11:41AM
Hi Samuel,
On 02/27/2013 04:02 PM, Roger Quadros wrote:
Hi Samuel,
One of my patch that I sent for 3.9 introduces a bug that fails to
update the port mode hostconfig register. Because of that, the port modes will
always be 0 (i.e. EHCI PHY mode) and other modes will not work. PHY mode will
Hi Matthieu,
On 3/5/2013 16:52, Matthieu CASTET wrote:
Do you know which vendor did the ehci IP that is in your atmel SOC.
I am sorry, I don't know the vendor of the ehci IP.
Best Regards,
Bo Shen
--
To unsubscribe from this list: send the line unsubscribe linux-usb in
the body of a message
Implement struct usb_otg, In that way, calling otg_set_peripheral
will not be failed at udc.c.
Signed-off-by: Peter Chen peter.c...@freescale.com
---
drivers/usb/chipidea/Makefile |2 +-
drivers/usb/chipidea/ci.h |2 +
drivers/usb/chipidea/otg.c| 60
Changes for v11:
- mark ci_handle_vbus_change as static as it is only used at core.c
[3/9]
- Move the vbus operation for platform code to host code, as vbus
operation is common operation, and host is the only user for vbus.
When it is host mode, we need to open vbus, when it is out of host
mode,
vbus register is at otgsc, and vbus detect does not belong
to device function. Revert this patch, and will move
vbus detect function to drivers/usb/chipidea/udc.c
This reverts commit 8c4fc031954b4eb72daf13d3c907a985a3eee208.
Signed-off-by: Peter Chen peter.c...@freescale.com
---
The main design flow is the same with msm otg driver, that is the id and
vbus interrupt are handled at core driver, others are handled by
individual drivers.
- At former design, when switch usb role from device-host, it will call
udc_stop, it will remove the gadget driver, so when switch role
(change CI13XXX to CI13 to avoid junk email check)
Now, we have handled vbus session in core driver when the
vbus interrupt occurs, so our pullup operations are all
according to vbus.
Of cource, the software can still call .pullup when device connects
to host if it wants to connect/disconnect with
After moving vbus operation to host, we no matter need to delayed operation.
But, the connection notification to gadget is needed as gadget's start
is only enable vbus operation, but it doesn't need to delayed.
Signed-off-by: Peter Chen peter.c...@freescale.com
---
drivers/usb/chipidea/ci.h |
For boards which have board level vbus control (eg, gpio), we
need to operation vbus according to below rules:
- For host, the vbus should always be on.
- For otg, the vbus needs to be turned on/off when usb role switches.
We put vbus operation to host as host is the only vbus user,
When we are
Signed-off-by: Peter Chen peter.c...@freescale.com
---
drivers/usb/chipidea/ci13xxx_imx.c | 28 +---
1 files changed, 5 insertions(+), 23 deletions(-)
diff --git a/drivers/usb/chipidea/ci13xxx_imx.c
b/drivers/usb/chipidea/ci13xxx_imx.c
index 3ed119e..b2d8350 100644
---
When we rmmod gadget, the ci-driver needs to be cleared.
Otherwise, we plug in usb cable again, the driver will
consider gadget is there, in fact, it is removed.
Besides, consolidate the calling of ci-driver-disconnect, when
we do rmmod gadget, the gadget's disconnect should be called from
udc
Hi,
On Wed, Mar 06, 2013 at 05:56:39PM +0800, Peter Chen wrote:
Signed-off-by: Peter Chen peter.c...@freescale.com
---
drivers/usb/chipidea/ci13xxx_imx.c | 28 +---
1 files changed, 5 insertions(+), 23 deletions(-)
diff --git a/drivers/usb/chipidea/ci13xxx_imx.c
Hi,
This patch adds comments on interface driver suspend callback
to emphasize that the failure return value is ignored by
USB core in system sleep context, so do not try to recover
device for this case, otherwise the recovery things may confuse
resume().
Also fixes the USB serial, HID and
This patch adds comments on interface driver suspend callback
to emphasize that the failure return value is ignored by
USB core in system sleep context, so do not try to recover
device for this case and let resume/reset_resume callback
handle the suspend failure if needed.
Signed-off-by: Ming Lei
This patch kills traffic even though type-suspend returns
failure inside usb_serial_suspend from system sleep context
because USB core ignores the failiure and lets system sleep
go ahread, so the serial URB traffic need to be killed
in this case.
Cc: Johan Hovold jhov...@gmail.com
Signed-off-by:
If suspend callback fails in system sleep context, usb core will
ignore the failure and let the system sleep go ahead further, so this
patch doesn't recover device under this situation, otherwise
may cause resume() confused.
Cc: Jiri Kosina jkos...@suse.cz
Signed-off-by: Ming Lei
If suspend callback fails in system sleep context, usb core will
ignore the failure and let system sleep go ahead further, so
this patch doesn't recover device under this situation.
Cc: Bjørn Mork bj...@mork.no
Signed-off-by: Ming Lei ming@canonical.com
---
drivers/net/usb/cdc_mbim.c |2
If suspend callback fails in system sleep context, usb core will
ignore the failure and let system sleep go ahead further, so
this patch doesn't recover device under this situation.
Cc: Steve Glendinning steve.glendinn...@shawell.net
Signed-off-by: Ming Lei ming@canonical.com
---
If suspend callback fails in system sleep context, usb core will
ignore the failure and let system sleep go ahead further, so
this patch doesn't recover device under this situation.
Cc: Steve Glendinning steve.glendinn...@shawell.net
Signed-off-by: Ming Lei ming@canonical.com
---
If suspend callback fails in system sleep context, usb core will
ignore the failure and let system sleep go ahead further, so
this patch doesn't recover device under this situation.
Cc: Bjørn Mork bj...@mork.no
Signed-off-by: Ming Lei ming@canonical.com
---
drivers/net/usb/qmi_wwan.c |2
Hi,
Just noticed this in 3.9-rc1 on an iMX28 (ARM) board with a config
based on mxs_defconfig. I'm using the patchset Add tested id switch
and vbus connect detect support for Chipidea from Peter Chen in its
10th version [1], rebased on top of 3.9-rc1, but since this doesn't
modify the locks
Hi Paul,
Kishon has uncovered a possible 'situation' with dwc3 which we need to
clear up.
According to your commit 802fde98 (usb: dwc3: support new revisions of
DWC3 core), we don't need to suspend/resume the PHYs at all with any
version 1.94a, but what we observe is that SUSPHY bits are never
Hi,
On Wed, Mar 06, 2013 at 05:56:35PM +0800, Peter Chen wrote:
- During the connect/disconnect host, we need to pullup
and pulldown dp
- Make sure the dp is not pullup until the vbus is on when
flag CI13XXX_PULLUP_ON_VBUS is set
- Using hw_device_state when set run/stop bit
Hi,
On Wed, Mar 06, 2013 at 05:56:37PM +0800, Peter Chen wrote:
For boards which have board level vbus control (eg, gpio), we
need to operation vbus according to below rules:
- For host, the vbus should always be on.
- For otg, the vbus needs to be turned on/off when usb role switches.
We
Ming Lei ming@canonical.com writes:
If suspend callback fails in system sleep context, usb core will
ignore the failure and let system sleep go ahead further, so
this patch doesn't recover device under this situation.
Cc: Bjørn Mork bj...@mork.no
Signed-off-by: Ming Lei
Ming Lei ming@canonical.com writes:
If suspend callback fails in system sleep context, usb core will
ignore the failure and let system sleep go ahead further, so
this patch doesn't recover device under this situation.
Cc: Bjørn Mork bj...@mork.no
Signed-off-by: Ming Lei
From: Mikhail Kshevetskiy mikhail.kshevets...@gmail.com
Commit 032ec49f5351e9cb242b1a1c367d14415043ab95 (usb: musb: drop useless
board_mode usage) introduced a typo that breaks the build.
Signed-off-by: Mikhail Kshevetskiy mikhail.kshevets...@gmail.com
[Fixed commit message]
Signed-off-by:
Hi,
The company I work for is doing USB cameras, for which
I wrote the drivers (out of tree).
Raw camera data are transferred using isochronous transfer.
However when plugging the camera on an USB3 port, xhci spits the
following messages on URB submission :
[ 1704.989785] xhci_hcd
On 6 March 2013 12:33, Maxime Ripard maxime.rip...@free-electrons.com wrote:
Hi,
Just noticed this in 3.9-rc1 on an iMX28 (ARM) board with a config
based on mxs_defconfig. I'm using the patchset Add tested id switch
and vbus connect detect support for Chipidea from Peter Chen in its
10th
drivers/usb/phy/ should be compiled everytime
we have CONFIG_USB_OTG_UTILS enabled.
Signed-off-by: Felipe Balbi ba...@ti.com
---
Hi Greg,
phy/ should've been part of the build process based
on CONFIG_USB_OTG_UTILS, don't know where I had my head
when I allowed CONFIG_USB_COMMON there.
In fact
Hi Alexander,
Thanks for your reply.
Le 06/03/2013 14:43, Alexander Shishkin a écrit :
On 6 March 2013 12:33, Maxime Ripard
maxime.rip...@free-electrons.com wrote:
Just noticed this in 3.9-rc1 on an iMX28 (ARM) board with a config
based on mxs_defconfig. I'm using the patchset Add tested
Ming Lei ming@canonical.com writes:
On Wed, Mar 6, 2013 at 8:04 PM, Bjørn Mork bj...@mork.no wrote:
I believe the correct here is to document the fact that we require the
subdriver-suspend() callback to always return 0 if !PMSG_IS_AUTO(message).
That is best done with a comment. No need
On Tue, 5 Mar 2013, Sarah Sharp wrote:
static void compliance_mode_recovery(unsigned long arg)
{
...
for (i = 0; i xhci-num_usb3_ports; i++) {
temp = xhci_readl(xhci, xhci-usb3_ports[i]);
if ((temp PORT_PLS_MASK) == USB_SS_PORT_LS_COMP_MOD) {
On Wed, 6 Mar 2013, Ming Lei wrote:
This patch adds comments on interface driver suspend callback
to emphasize that the failure return value is ignored by
USB core in system sleep context, so do not try to recover
device for this case and let resume/reset_resume callback
handle the suspend
On Tue, Mar 05, 2013 at 03:14:10PM -0800, Sarah Sharp wrote:
*/
static void compliance_mode_recovery_timer_init(struct xhci_hcd *xhci)
{
+ if (timer_pending(xhci-comp_mode_recovery_timer)) {
+ xhci_dbg(xhci, Compliance Mode Recovery Timer already
active.\n);
+
On Wed, 6 Mar 2013, Don Zickus wrote:
On Tue, Mar 05, 2013 at 03:14:10PM -0800, Sarah Sharp wrote:
*/
static void compliance_mode_recovery_timer_init(struct xhci_hcd *xhci)
{
+ if (timer_pending(xhci-comp_mode_recovery_timer)) {
+ xhci_dbg(xhci, Compliance Mode
On Wed, 2013-03-06 at 09:44 +0800, Greg KH wrote:
On Wed, Mar 06, 2013 at 01:34:44AM +, Linlei (Lei Lin) wrote:
Hello Mork,
-- Because in the embedded linux system, Android, or Chrome OS,
etc. They don't integrate userspace usb_modeswitch utility for
switching.
Why
On 03/05/2013 11:32 PM, Peter Hurley wrote:
So I'm thinking about
something like this:
if (port-tty)
set_bit(TTY_IO_ERROR, port-tty-flags);
tty = port-tty; === take a snapshot
spin_unlock_irqrestore(port-lock, flags);
tty_port_shutdown(port, tty); === use the snapshot
From: Christian Schmiedl christian.schmi...@gemalto.com
/drivers/usb/serial/option.c: added support for Cinterion's products AH6 and
PLS8 by adding Product IDs and USB_DEVICE tuples
Signed-off-by: Christian Schmiedl christian.schmi...@gemalto.com
---
patch is against linux-3.2.40
---
On Tue, Mar 05, 2013 at 10:03:01AM +0800, Chao Xie wrote:
On Mon, Mar 4, 2013 at 10:21 PM, Felipe Balbi ba...@ti.com wrote:
On Wed, Feb 20, 2013 at 11:07:11PM -0500, Chao Xie wrote:
+ for (i = 0; i mv_phy-clks_num; i++) {
+ mv_phy-clks[i] = devm_clk_get(pdev-dev,
+
On Wed, Mar 06, 2013 at 04:24:58PM +0800, Chao Xie wrote:
The clock numbers and names are depent of SOCes,
No they aren't. The clock names used to describe them in your documentation
may vary, but their _purpose_ for the sake of the device will be fixed -
and you should name them appropriately
Hi Jiri,
On Tue, Mar 05, 2013 at 05:02:44PM +0100, Jiri Slaby wrote:
On 02/28/2013 09:57 PM, Peter Hurley wrote:
Hi Jiri,
Just wanted to make sure you saw this series.
Hi, thanks for letting me know. Johan, care to CC Alan Cox and me (or at
least LKML) when you're changing the TTY
On 6 March 2013 11:56, Peter Chen peter.c...@freescale.com wrote:
The main design flow is the same with msm otg driver, that is the id and
vbus interrupt are handled at core driver, others are handled by
individual drivers.
- At former design, when switch usb role from device-host, it will
hwparams2 holds the number of endpoints which
were selected during RTL generation, we can
use that on our driver.
Signed-off-by: Felipe Balbi ba...@ti.com
---
drivers/usb/dwc3/core.c | 13 +
drivers/usb/dwc3/core.h | 15 +++
2 files changed, 28 insertions(+)
diff --git
that way we will only tell gadget framework about
the endpoints we actually have.
Signed-off-by: Felipe Balbi ba...@ti.com
---
drivers/usb/dwc3/gadget.c | 39 +++
1 file changed, 35 insertions(+), 4 deletions(-)
diff --git a/drivers/usb/dwc3/gadget.c
Hello.
On 06-03-2013 21:47, Felipe Balbi wrote:
that way we will only tell gadget framework about
the endpoints we actually have.
Signed-off-by: Felipe Balbi ba...@ti.com
---
drivers/usb/dwc3/gadget.c | 39 +++
1 file changed, 35 insertions(+), 4
Hi,
On Wed, Mar 06, 2013 at 10:00:34PM +0400, Sergei Shtylyov wrote:
that way we will only tell gadget framework about
the endpoints we actually have.
Signed-off-by: Felipe Balbi ba...@ti.com
---
drivers/usb/dwc3/gadget.c | 39 +++
1 file changed, 35
On Wed, Mar 06, 2013 at 05:56:40PM +0800, Peter Chen wrote:
root@freescale ~$ ci_hdrc ci_hdrc.0: Connected to host
Unable to handle kernel paging request at virtual address 7f01171c
pgd = 80004000
[7f01171c] *pgd=4fa1e811, *pte=, *ppte=
Internal error: Oops: 7 [#1] SMP ARM
Hello.
On 06-03-2013 22:37, Felipe Balbi wrote:
that way we will only tell gadget framework about
the endpoints we actually have.
Signed-off-by: Felipe Balbi ba...@ti.com
---
drivers/usb/dwc3/gadget.c | 39 +++
1 file changed, 35 insertions(+), 4
On Wed, 2013-03-06 at 17:52 +0100, Johan Hovold wrote:
@@ -225,15 +232,13 @@ void tty_port_hangup(struct tty_port *port)
spin_lock_irqsave(port-lock, flags);
port-count = 0;
port-flags = ~ASYNC_NORMAL_ACTIVE;
- if (port-tty) {
+ if (port-tty)
From: Felipe Balbi [mailto:ba...@ti.com]
Sent: Wednesday, March 06, 2013 2:36 AM
To: Paul Zimmerman; Kishon Vijay Abraham I; Linux USB Mailing List
Subject: dwc3 PHY autosuspend feature
Hi Paul,
Kishon has uncovered a possible 'situation' with dwc3 which we need to
clear up.
Sorry for replying to myself, but I forgot to answer one question: No,
PHY autosuspend is not an optional feature, every core since 1.94a
has it.
--
Paul
From: Paul Zimmerman
Sent: Wednesday, March 06, 2013 11:23 AM
From: Felipe Balbi [mailto:ba...@ti.com]
Sent: Wednesday, March 06,
On Fri, 1 Mar 2013, Adrian Bassett wrote:
Finally, I don't see how this could possibly have any connection with
the 6e0c3339a6 commit (USB: EHCI: unlink one async QH at a time). If
necessary, we can try a diagnostic patch to see what's going on with
the async QH unlinking.
It does
Hi,
On Wed, Mar 06, 2013 at 10:49:54PM +0400, Sergei Shtylyov wrote:
Hello.
On 06-03-2013 22:37, Felipe Balbi wrote:
that way we will only tell gadget framework about
the endpoints we actually have.
Signed-off-by: Felipe Balbi ba...@ti.com
---
drivers/usb/dwc3/gadget.c | 39
Hi,
On Wed, Mar 06, 2013 at 07:22:33PM +, Paul Zimmerman wrote:
From: Felipe Balbi [mailto:ba...@ti.com]
Sent: Wednesday, March 06, 2013 2:36 AM
To: Paul Zimmerman; Kishon Vijay Abraham I; Linux USB Mailing List
Subject: dwc3 PHY autosuspend feature
Hi Paul,
Kishon has
From: Felipe Balbi [mailto:ba...@ti.com]
Sent: Wednesday, March 06, 2013 12:11 PM
On Wed, Mar 06, 2013 at 07:22:33PM +, Paul Zimmerman wrote:
From: Felipe Balbi [mailto:ba...@ti.com]
Sent: Wednesday, March 06, 2013 2:36 AM
To: Paul Zimmerman; Kishon Vijay Abraham I; Linux USB
From: Syam Sidhardhan s.s...@samsung.com
kfree on NULL pointer is a no-op.
Signed-off-by: Syam Sidhardhan s.s...@samsung.com
---
v1- Corrected the from address.
drivers/usb/otg/fsl_otg.c | 30 ++
1 file changed, 10 insertions(+), 20 deletions(-)
diff --git
From: Syam Sidhardhan s.s...@samsung.com
kfree on NULL pointer is a no-op.
Signed-off-by: Syam Sidhardhan s.s...@samsung.com
---
v1- Corrected the from address.
drivers/usb/serial/mos7840.c |3 +--
1 file changed, 1 insertion(+), 2 deletions(-)
diff --git a/drivers/usb/serial/mos7840.c
On Wed, Mar 06, 2013 at 10:12:14AM -0500, Alan Stern wrote:
On Tue, 5 Mar 2013, Sarah Sharp wrote:
static void compliance_mode_recovery(unsigned long arg)
{
...
for (i = 0; i xhci-num_usb3_ports; i++) {
temp = xhci_readl(xhci, xhci-usb3_ports[i]);
On Wed, 6 Mar 2013, Sarah Sharp wrote:
If xhci_suspend deletes the Compliance Mode Recovery timer then the
timer will never fire while the controller is in D3cold. The problem
won't arise.
Alex,
Can the USB 3.0 port go into the Inactive sate while the host is in
D3hot or D3cold?
From: Felipe Balbi [mailto:ba...@ti.com]
Sent: Wednesday, March 06, 2013 12:05 AM
...
looking at that loop, is it really necessary ? I mean, what you do is:
spin_lock_irqsave();
while (!list_empty(list) retry--) {
if (!retry) {
spin_unlock_irqrestore();
On Thu, Mar 7, 2013 at 12:48 AM, Russell King - ARM Linux
li...@arm.linux.org.uk wrote:
On Wed, Mar 06, 2013 at 04:24:58PM +0800, Chao Xie wrote:
The clock numbers and names are depent of SOCes,
No they aren't. The clock names used to describe them in your documentation
may vary, but their
From: Felipe Balbi [mailto:ba...@ti.com]
Sent: Tuesday, March 05, 2013 11:42 PM
On Mon, Mar 04, 2013 at 12:21:44PM -0800, Paul Zimmerman wrote:
+const char *usb_otg_state_string(enum usb_otg_state state)
+{
+ static const char *const names[] = {
+ [OTG_STATE_UNDEFINED] =
On Wed, Mar 06, 2013 at 10:54:46AM +0200, Felipe Balbi wrote:
are you sure this is correct ? you're not doing anything in case of
vbus event. Shouldn't you make sure your vbus is off ?
The implementation I'm taking as reference for this patches does not do
anything on VBUS event and
On Wed, Mar 6, 2013 at 11:25 PM, Alan Stern st...@rowland.harvard.edu wrote:
On Wed, 6 Mar 2013, Ming Lei wrote:
This patch adds comments on interface driver suspend callback
to emphasize that the failure return value is ignored by
USB core in system sleep context, so do not try to recover
On Wed, Mar 06, 2013 at 12:11:46PM +0200, Felipe Balbi wrote:
Hi,
On Wed, Mar 06, 2013 at 05:56:39PM +0800, Peter Chen wrote:
Signed-off-by: Peter Chen peter.c...@freescale.com
---
drivers/usb/chipidea/ci13xxx_imx.c | 28 +---
1 files changed, 5
On Wed, Mar 06, 2013 at 01:26:33PM +0200, Felipe Balbi wrote:
Hi,
On Wed, Mar 06, 2013 at 05:56:35PM +0800, Peter Chen wrote:
- During the connect/disconnect host, we need to pullup
and pulldown dp
- Make sure the dp is not pullup until the vbus is on when
flag CI13XXX_PULLUP_ON_VBUS
On Wed, Mar 06, 2013 at 01:29:16PM +0200, Felipe Balbi wrote:
Hi,
On Wed, Mar 06, 2013 at 05:56:37PM +0800, Peter Chen wrote:
For boards which have board level vbus control (eg, gpio), we
need to operation vbus according to below rules:
- For host, the vbus should always be on.
- For
On Wed, Mar 06, 2013 at 06:46:21PM +, Russell King - ARM Linux wrote:
On Wed, Mar 06, 2013 at 05:56:40PM +0800, Peter Chen wrote:
root@freescale ~$ ci_hdrc ci_hdrc.0: Connected to host
Unable to handle kernel paging request at virtual address 7f01171c
pgd = 80004000
[7f01171c]
Dear All：
As far as I know, except switching in kernel, there isn't any mode
switch solution on Android now.
Do you have any good ideas for the mode switch on Android system?
Best Regards,
Franko Fang
-Original Message-
From: Dan Williams [mailto:d...@redhat.com]
Sent:
Since kernel 3.8 Apple Cinema Display's usb hub spits errors randomly at
boot. (their count seems to be random, but the type of the error is
always the same)
As soon as I disconnect the usb extension cable the errors are gone.
Errors
journalctl
usb 1-2.2: can't set config #1, error -71
On Thu, Mar 07, 2013 at 02:54:38AM +, Fangxiaozhi (Franko) wrote:
Dear All：
As far as I know, except switching in kernel, there isn't any mode switch
solution on Android now.
Do you have any good ideas for the mode switch on Android system?
Please discuss this with the Android
Since kernel 3.8 Apple Cinema Display's usb hub spits errors randomly at
boot. (their count seems to be random, but the type of the error is
always the same)
As soon as I disconnect the usb extension cable the errors are gone.
Errors
journalctl
usb 1-2.2: can't set config #1, error -71
hub
UPDATE correction to the name of the device Apple Cinema HD Display (
A1082)
Since kernel 3.8 Apple Cinema Display's usb hub spits errors randomly at
boot. (their count seems to be random, but the type of the error is
always the same)
As soon as I disconnect the usb extension cable the
Update: added env version infos
Even though I am presented with a list of available networks, my system
with the rc1 kernel is not able to connect to any of them. It stops at
the point where it tries to obtain an IP address. I tried to delete the
Profile of my WiFi and recreate it but no
于 2013年03月05日 19:10, Felipe Balbi 写道:
no problem, take your time. Family is more important than a bugfix. I
don't have that HW anyway and can't test fixes to it.
I do not have either, but I should try (I need think ways to perform,
such as qemu kvm, or another ways)
welcome additional
On Thu, Feb 28, 2013 at 01:08:38PM -0700, Dave Tubbs wrote:
From: Dave Tubbs dave.tu...@portalislc.com
Make sure each c67x00 TD has been executed or retry using the existing
retry mechanism. Reference Cypress Semiconductor BIOS User's Manual 1.2,
page 3-16
Signed-off-by: Dave Tubbs
On Wed, Mar 06, 2013 at 07:09:34PM +0200, Alexander Shishkin wrote:
- start/stop API are used at otg id switch and probe routine
- Defer some gadget operations at ci's delayed work queue
When I asked you to reorder patches, I didn't mean squash them all
into one. Now you have a patch
Hi,
On Wed, Mar 06, 2013 at 08:14:34PM +, Paul Zimmerman wrote:
From: Felipe Balbi [mailto:ba...@ti.com]
Sent: Wednesday, March 06, 2013 12:11 PM
On Wed, Mar 06, 2013 at 07:22:33PM +, Paul Zimmerman wrote:
From: Felipe Balbi [mailto:ba...@ti.com]
Sent: Wednesday, March 06,
Hi,
On Thu, Mar 07, 2013 at 12:58:04AM +, Paul Zimmerman wrote:
From: Felipe Balbi [mailto:ba...@ti.com]
Sent: Tuesday, March 05, 2013 11:42 PM
On Mon, Mar 04, 2013 at 12:21:44PM -0800, Paul Zimmerman wrote:
+const char *usb_otg_state_string(enum usb_otg_state state)
+{
+
On Wed, Mar 06, 2013 at 11:26:08PM +, Paul Zimmerman wrote:
From: Felipe Balbi [mailto:ba...@ti.com]
Sent: Wednesday, March 06, 2013 12:05 AM
...
looking at that loop, is it really necessary ? I mean, what you do is:
spin_lock_irqsave();
while (!list_empty(list) retry--)
90 matches
Mail list logo
