From: olof@lixom.net (Olof Johansson)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH] ARM: tegra: update defconfig
Date: Mon, 5 Mar 2012 14:25:21 -0800 [thread overview]
Message-ID: <20120305222521.GA30240@quad.lixom.net> (raw)
In-Reply-To: <1330983838-25327-1-git-send-email-swarren@nvidia.com>
On Mon, Mar 05, 2012 at 02:43:58PM -0700, Stephen Warren wrote:
> Refresh tegra_defconfig:
>
> New options enabled:
> * PERF_EVENTS
> * Tegra EMC scaling
> * Support for all 4 CPUs on Tegra30
> * AUTO_ZRELADDR for unified Tegra20+Tegra30 images
> * CPU_FREQ/CPU_IDLE
> * BLK_DEV_SR
> * INPUT_EVDEV
> * Regulators, including fixed, GPIO, TPS6586x
> * Audio for Tegra+ALC5632 (for Paz00/Toshiba AC100)
> * NVEC (staging, for Paz00/Toshiba AC100)
> * IOMMU for Tegra20's GART and Tegra30's SMMU
> * TEGRA_AES
>
> Signed-off-by: Stephen Warren <swarren@nvidia.com>
> ---
> This is slightly late for 3.4, but hopefully can just squeak in.
Yeah, timing is OK for this, no worries.
I was planning on doing one patch as well, since I want to turn on EXT4 (for
eMMC/SD it's a good idea to use trim). Care to do that in your patch instead so
we only have one update?
Thanks,
-Olof
next prev parent reply other threads:[~2012-03-05 22:25 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-03-05 21:43 [PATCH] ARM: tegra: update defconfig Stephen Warren
2012-03-05 22:25 ` Olof Johansson [this message]
-- strict thread matches above, loose matches on Subject: below --
2012-04-16 16:54 Stephen Warren
2011-10-13 3:56 Olof Johansson
2011-10-13 15:55 ` Stephen Warren
2011-10-13 16:25 ` Olof Johansson
2011-10-13 16:03 ` Stephen Warren
2011-10-13 16:25 ` Olof Johansson
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=20120305222521.GA30240@quad.lixom.net \
--to=olof@lixom.net \
--cc=linux-arm-kernel@lists.infradead.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