Linux Tegra architecture development
 help / color / mirror / Atom feed
From: Timur <timur.mehrvarz-sGOZH3hwPm2sTnJN9+BGXg@public.gmane.org>
To: Stephen Warren <swarren-3lzwWm7+Weoh9ZMKESR00Q@public.gmane.org>
Cc: linux-tegra-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
Subject: Re: ehci-tegra issue with deep sleep
Date: Thu, 03 Jan 2013 12:52:17 +0100	[thread overview]
Message-ID: <50E570F1.4030706@riseup.net> (raw)
In-Reply-To: <50C8C47A.1080809-3lzwWm7+Weoh9ZMKESR00Q@public.gmane.org>

On 12.12.2012 18:52, Stephen Warren wrote:
> On 12/11/2012 03:23 PM, Timur wrote:
>> Hi. I discovered a problem with USB host mode on a Nexus 7 running
>> Android 4.2.x:
>
> Timur,
>
> This mailing list is intended for discussion of the mainline Linux
> kernel, rather than NVIDIA's modified (and older) downstream kernel, as
> used on shipping Android devices.
>
> Your best bet for support is to report the issue to
> linux-tegra-bugs-DDmLM1+adcqXj1p+fO2waQ@public.gmane.org It may help if you've tried the Ubuntu/L4T
> install described at:
>
> https://wiki.ubuntu.com/Nexus7
>
> ... and reproduced the issue there too; at least some people working on
> the downstream kernel do have access to Nexus 7s with that software setup.

Hi Stephen,

maybe you remember this brief conversation in December. I found the root 
cause of the reported issue (tegra specific) and I can provide a patch. 
The outcome is stable, externally powered USB host mode for Nexus 7.

Do you happen to know anyone responsible for the Ubuntu Nexus7 kernel? I 
would like to contribute the fix, as I think it would be beneficial to 
that implementation.

Thank you.
Timur

  parent reply	other threads:[~2013-01-03 11:52 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-12-11 22:23 ehci-tegra issue with deep sleep Timur
     [not found] ` <50C7B250.7020409-sGOZH3hwPm2sTnJN9+BGXg@public.gmane.org>
2012-12-12 17:52   ` Stephen Warren
     [not found]     ` <50C8C47A.1080809-3lzwWm7+Weoh9ZMKESR00Q@public.gmane.org>
2013-01-03 11:52       ` Timur [this message]
     [not found]         ` <50E570F1.4030706-sGOZH3hwPm2sTnJN9+BGXg@public.gmane.org>
2013-01-04 17:33           ` Stephen Warren
     [not found]             ` <50E71272.5090107-3lzwWm7+Weoh9ZMKESR00Q@public.gmane.org>
2013-01-07 17:19               ` Timur Mehrvarz
     [not found]                 ` <50EB03A6.9040509-sGOZH3hwPm2sTnJN9+BGXg@public.gmane.org>
2013-01-08 22:19                   ` Stephen Warren

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=50E570F1.4030706@riseup.net \
    --to=timur.mehrvarz-sgozh3hwpm2stnjn9+bgxg@public.gmane.org \
    --cc=linux-tegra-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
    --cc=swarren-3lzwWm7+Weoh9ZMKESR00Q@public.gmane.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox