From: Stephen Warren <swarren@wwwdotorg.org>
To: u-boot@lists.denx.de
Subject: [U-Boot] [PATCH] ARM: tegra: enable STDIO deregistration
Date: Mon, 13 Apr 2015 13:17:29 -0600 [thread overview]
Message-ID: <552C1649.5000109@wwwdotorg.org> (raw)
In-Reply-To: <CAPnjgZ1VwBT09pviw5Q9DyTOnvuk_K+cjdRhEEcdNAfKf7_aOg@mail.gmail.com>
On 04/13/2015 11:22 AM, Simon Glass wrote:
> Hi Stephen,
>
> On 13 April 2015 at 11:11, Stephen Warren <swarren@wwwdotorg.org> wrote:
>> From: Stephen Warren <swarren@nvidia.com>
>>
>> At the very least when USB keyboard support is enabled, we need to enable
>> CONFIG_SYS_STDIO_DEREGISTER, so the "usb reset" is able to re-scan USB
>> ports and find new devices.
>>
>> Signed-off-by: Stephen Warren <swarren@nvidia.com>
>> ---
>> This feels like a nice fix for the upcoming release if possible. Even if
>> this causes horrible fallout (which I do not expect), it'll only affect
>> Seaboard and Ventana boards, both of which have quite limited
>> distribution.
>
> Reviewed-by: Simon Glass <sjg@chromium.org>
>
> I wonder whether you might want to (post-release) enable this always
> on Tegra, except for SPL?
Was that referring to CONFIG_SYS_STDIO_DEREGISTER or USB keyboard
support? I suspect we should simply enable USB keyboard support
everywhere, since most systems don't have built-in keyboards? It's
certainly missing from devices like Trimslice that need it. Or would you
rather only enable keyboard support on devices without a keyboard, and
enable CONFIG_SYS_STDIO_DEREGISTER everywhere?
next prev parent reply other threads:[~2015-04-13 19:17 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-04-13 17:11 [U-Boot] [PATCH] ARM: tegra: enable STDIO deregistration Stephen Warren
2015-04-13 17:22 ` Simon Glass
2015-04-13 19:17 ` Stephen Warren [this message]
2015-04-13 20:19 ` Simon Glass
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=552C1649.5000109@wwwdotorg.org \
--to=swarren@wwwdotorg.org \
--cc=u-boot@lists.denx.de \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.