From: Timur Mehrvarz <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: Mon, 07 Jan 2013 18:19:34 +0100 [thread overview]
Message-ID: <50EB03A6.9040509@riseup.net> (raw)
In-Reply-To: <50E71272.5090107-3lzwWm7+Weoh9ZMKESR00Q@public.gmane.org>
On 01/04/2013 06:33 PM, Stephen Warren wrote:
> On 01/03/2013 04:52 AM, Timur wrote:
> ...
>> 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.
> Isn't USB host mode by definition internally powered, and USB device
> mode by definition externally powered? An externally powered USB host
> mode sounds quite non-standard. If you allow that mode, how does the
> system know whether it should be a host or a device when external power
> is applied; it sounds like this new mode completely breaks the ability
> to connect the tablet to a PC and use it for Android application
> development, or MTP (Media Transfer Protocol) to download pictures/movies.
What I am proposing does not result in any loss of original
functionality (ADB, MTP, etc.). Also, the described added functionality
is fully standard when I look at it. No typical PC needs to switch to
battery power, only to connect USB slave devices. You can operate a
Nexus 7 on external power. But in order to connect USB slave devices,
you *have* to switch to internal battery. Not being able to run USB host
mode at all, while using external power, is a serious shortcoming. One
that is only caused by the installed kernel. In December, I was having
this last difficulty: preserving USB host operations through LP0 phases.
But this problem has been solved. Really wanted to clarify this.
>
>> 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.
> Sorry, I don't know what kernel they're using; the best place to ask
> would be the Ubuntu project itself.
No, I did not ask what kernel they are using.
next prev parent reply other threads:[~2013-01-07 17:19 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
[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 [this message]
[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=50EB03A6.9040509@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