From: Stephen Warren <swarren-3lzwWm7+Weoh9ZMKESR00Q@public.gmane.org>
To: Richard Leitner <me-M/VWbR8SM2SsTnJN9+BGXg@public.gmane.org>
Cc: linux-tegra-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
Subject: Re: Question about "missing" tegra features
Date: Mon, 21 Jul 2014 09:18:13 -0600 [thread overview]
Message-ID: <53CD2F35.4000804@wwwdotorg.org> (raw)
In-Reply-To: <c3a33a3d722302b1f4d877649d485d2f-n3SY6/QrmYUdxdNa7N5bz2CGZHFJa5fA29i0knmqyyNx9qoA87EPLA@public.gmane.org>
On 07/03/2014 01:11 AM, Richard Leitner wrote:
> Hello folks,
> I've a general question regarding the linux-tegra development:
> Why are there tegra features which are available in NVIDIA's kernel tree
> [1], but not included in mainline (or at least your tegra tree)?
> I've just noticed that for the USB device controller
> (drivers/usb/gadget/tegra_udc.{c,h}), but it seems there are more such
> "cases".
Just like I think Marc already responded, It's simply a matter of
resources; the upstreaming team isn't as large as the product team.
> Is there any documentation on what is supported/included in mainline
> already and what not?
I don't believe so, no.
The main features I can think of are:
* Various power/performance optimizations.
* Various IO controllers on newer chips (such as SATA, Tegra124 PCIe,
USB3), although there are patches sent for all of these now. NOR flash,
I2C/SPI slave mode, one-wire, perhaps a few other minor IO controllers.
* Various features in supported IO controllers (e.g. high-speed eMMC/SD
modes, USB2 bus suspend, ...)
* USB device mode.
prev parent reply other threads:[~2014-07-21 15:18 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-07-03 7:11 Question about "missing" tegra features Richard Leitner
[not found] ` <c3a33a3d722302b1f4d877649d485d2f-n3SY6/QrmYUdxdNa7N5bz2CGZHFJa5fA29i0knmqyyNx9qoA87EPLA@public.gmane.org>
2014-07-03 7:41 ` Marc Dietrich
2014-07-21 15:18 ` Stephen Warren [this message]
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=53CD2F35.4000804@wwwdotorg.org \
--to=swarren-3lzwwm7+weoh9zmkesr00q@public.gmane.org \
--cc=linux-tegra-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
--cc=me-M/VWbR8SM2SsTnJN9+BGXg@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