2010-01-22 08:53:02 +08:00
|
|
|
if ARCH_TEGRA
|
|
|
|
|
|
|
|
|
|
comment "NVIDIA Tegra options"
|
|
|
|
|
|
|
|
|
|
config ARCH_TEGRA_2x_SOC
|
2011-12-14 23:03:25 +08:00
|
|
|
bool "Enable support for Tegra20 family"
|
2010-03-16 10:40:06 +08:00
|
|
|
select ARCH_REQUIRE_GPIOLIB
|
2012-02-15 04:39:39 +08:00
|
|
|
select ARM_ERRATA_720789
|
|
|
|
|
select ARM_ERRATA_742230
|
|
|
|
|
select ARM_ERRATA_751472
|
|
|
|
|
select ARM_ERRATA_754327
|
2012-08-16 17:36:04 +08:00
|
|
|
select ARM_ERRATA_764369 if SMP
|
ARM: config: sort select statements alphanumerically
As suggested by Andrew Morton:
This is a pet peeve of mine. Any time there's a long list of items
(header file inclusions, kconfig entries, array initalisers, etc) and
someone wants to add a new item, they *always* go and stick it at the
end of the list.
Guys, don't do this. Either put the new item into a randomly-chosen
position or, probably better, alphanumerically sort the list.
lets sort all our select statements alphanumerically. This commit was
created by the following perl:
while (<>) {
while (/\\\s*$/) {
$_ .= <>;
}
undef %selects if /^\s*config\s+/;
if (/^\s+select\s+(\w+).*/) {
if (defined($selects{$1})) {
if ($selects{$1} eq $_) {
print STDERR "Warning: removing duplicated $1 entry\n";
} else {
print STDERR "Error: $1 differently selected\n".
"\tOld: $selects{$1}\n".
"\tNew: $_\n";
exit 1;
}
}
$selects{$1} = $_;
next;
}
if (%selects and (/^\s*$/ or /^\s+help/ or /^\s+---help---/ or
/^endif/ or /^endchoice/)) {
foreach $k (sort (keys %selects)) {
print "$selects{$k}";
}
undef %selects;
}
print;
}
if (%selects) {
foreach $k (sort (keys %selects)) {
print "$selects{$k}";
}
}
It found two duplicates:
Warning: removing duplicated S5P_SETUP_MIPIPHY entry
Warning: removing duplicated HARDIRQS_SW_RESEND entry
and they are identical duplicates, hence the shrinkage in the diffstat
of two lines.
We have four testers reporting success of this change (Tony, Stephen,
Linus and Sekhar.)
Acked-by: Jason Cooper <jason@lakedaemon.net>
Acked-by: Tony Lindgren <tony@atomide.com>
Acked-by: Stephen Warren <swarren@nvidia.com>
Acked-by: Linus Walleij <linus.walleij@linaro.org>
Acked-by: Sekhar Nori <nsekhar@ti.com>
Signed-off-by: Russell King <rmk+kernel@arm.linux.org.uk>
2012-10-07 00:12:25 +08:00
|
|
|
select ARM_GIC
|
|
|
|
|
select CPU_FREQ_TABLE if CPU_FREQ
|
|
|
|
|
select CPU_V7
|
|
|
|
|
select PINCTRL
|
|
|
|
|
select PINCTRL_TEGRA20
|
2012-02-15 04:39:39 +08:00
|
|
|
select PL310_ERRATA_727915 if CACHE_L2X0
|
|
|
|
|
select PL310_ERRATA_769419 if CACHE_L2X0
|
ARM: config: sort select statements alphanumerically
As suggested by Andrew Morton:
This is a pet peeve of mine. Any time there's a long list of items
(header file inclusions, kconfig entries, array initalisers, etc) and
someone wants to add a new item, they *always* go and stick it at the
end of the list.
Guys, don't do this. Either put the new item into a randomly-chosen
position or, probably better, alphanumerically sort the list.
lets sort all our select statements alphanumerically. This commit was
created by the following perl:
while (<>) {
while (/\\\s*$/) {
$_ .= <>;
}
undef %selects if /^\s*config\s+/;
if (/^\s+select\s+(\w+).*/) {
if (defined($selects{$1})) {
if ($selects{$1} eq $_) {
print STDERR "Warning: removing duplicated $1 entry\n";
} else {
print STDERR "Error: $1 differently selected\n".
"\tOld: $selects{$1}\n".
"\tNew: $_\n";
exit 1;
}
}
$selects{$1} = $_;
next;
}
if (%selects and (/^\s*$/ or /^\s+help/ or /^\s+---help---/ or
/^endif/ or /^endchoice/)) {
foreach $k (sort (keys %selects)) {
print "$selects{$k}";
}
undef %selects;
}
print;
}
if (%selects) {
foreach $k (sort (keys %selects)) {
print "$selects{$k}";
}
}
It found two duplicates:
Warning: removing duplicated S5P_SETUP_MIPIPHY entry
Warning: removing duplicated HARDIRQS_SW_RESEND entry
and they are identical duplicates, hence the shrinkage in the diffstat
of two lines.
We have four testers reporting success of this change (Tony, Stephen,
Linus and Sekhar.)
Acked-by: Jason Cooper <jason@lakedaemon.net>
Acked-by: Tony Lindgren <tony@atomide.com>
Acked-by: Stephen Warren <swarren@nvidia.com>
Acked-by: Linus Walleij <linus.walleij@linaro.org>
Acked-by: Sekhar Nori <nsekhar@ti.com>
Signed-off-by: Russell King <rmk+kernel@arm.linux.org.uk>
2012-10-07 00:12:25 +08:00
|
|
|
select USB_ARCH_HAS_EHCI if USB_SUPPORT
|
|
|
|
|
select USB_ULPI if USB
|
|
|
|
|
select USB_ULPI_VIEWPORT if USB_SUPPORT
|
2010-01-22 08:53:02 +08:00
|
|
|
help
|
|
|
|
|
Support for NVIDIA Tegra AP20 and T20 processors, based on the
|
|
|
|
|
ARM CortexA9MP CPU and the ARM PL310 L2 cache controller
|
|
|
|
|
|
2011-12-14 23:03:25 +08:00
|
|
|
config ARCH_TEGRA_3x_SOC
|
|
|
|
|
bool "Enable support for Tegra30 family"
|
|
|
|
|
select ARCH_REQUIRE_GPIOLIB
|
2012-02-15 04:39:39 +08:00
|
|
|
select ARM_ERRATA_743622
|
|
|
|
|
select ARM_ERRATA_751472
|
|
|
|
|
select ARM_ERRATA_754322
|
2012-08-16 17:36:04 +08:00
|
|
|
select ARM_ERRATA_764369 if SMP
|
ARM: config: sort select statements alphanumerically
As suggested by Andrew Morton:
This is a pet peeve of mine. Any time there's a long list of items
(header file inclusions, kconfig entries, array initalisers, etc) and
someone wants to add a new item, they *always* go and stick it at the
end of the list.
Guys, don't do this. Either put the new item into a randomly-chosen
position or, probably better, alphanumerically sort the list.
lets sort all our select statements alphanumerically. This commit was
created by the following perl:
while (<>) {
while (/\\\s*$/) {
$_ .= <>;
}
undef %selects if /^\s*config\s+/;
if (/^\s+select\s+(\w+).*/) {
if (defined($selects{$1})) {
if ($selects{$1} eq $_) {
print STDERR "Warning: removing duplicated $1 entry\n";
} else {
print STDERR "Error: $1 differently selected\n".
"\tOld: $selects{$1}\n".
"\tNew: $_\n";
exit 1;
}
}
$selects{$1} = $_;
next;
}
if (%selects and (/^\s*$/ or /^\s+help/ or /^\s+---help---/ or
/^endif/ or /^endchoice/)) {
foreach $k (sort (keys %selects)) {
print "$selects{$k}";
}
undef %selects;
}
print;
}
if (%selects) {
foreach $k (sort (keys %selects)) {
print "$selects{$k}";
}
}
It found two duplicates:
Warning: removing duplicated S5P_SETUP_MIPIPHY entry
Warning: removing duplicated HARDIRQS_SW_RESEND entry
and they are identical duplicates, hence the shrinkage in the diffstat
of two lines.
We have four testers reporting success of this change (Tony, Stephen,
Linus and Sekhar.)
Acked-by: Jason Cooper <jason@lakedaemon.net>
Acked-by: Tony Lindgren <tony@atomide.com>
Acked-by: Stephen Warren <swarren@nvidia.com>
Acked-by: Linus Walleij <linus.walleij@linaro.org>
Acked-by: Sekhar Nori <nsekhar@ti.com>
Signed-off-by: Russell King <rmk+kernel@arm.linux.org.uk>
2012-10-07 00:12:25 +08:00
|
|
|
select ARM_GIC
|
2012-03-03 04:58:28 +08:00
|
|
|
select CPU_FREQ_TABLE if CPU_FREQ
|
ARM: config: sort select statements alphanumerically
As suggested by Andrew Morton:
This is a pet peeve of mine. Any time there's a long list of items
(header file inclusions, kconfig entries, array initalisers, etc) and
someone wants to add a new item, they *always* go and stick it at the
end of the list.
Guys, don't do this. Either put the new item into a randomly-chosen
position or, probably better, alphanumerically sort the list.
lets sort all our select statements alphanumerically. This commit was
created by the following perl:
while (<>) {
while (/\\\s*$/) {
$_ .= <>;
}
undef %selects if /^\s*config\s+/;
if (/^\s+select\s+(\w+).*/) {
if (defined($selects{$1})) {
if ($selects{$1} eq $_) {
print STDERR "Warning: removing duplicated $1 entry\n";
} else {
print STDERR "Error: $1 differently selected\n".
"\tOld: $selects{$1}\n".
"\tNew: $_\n";
exit 1;
}
}
$selects{$1} = $_;
next;
}
if (%selects and (/^\s*$/ or /^\s+help/ or /^\s+---help---/ or
/^endif/ or /^endchoice/)) {
foreach $k (sort (keys %selects)) {
print "$selects{$k}";
}
undef %selects;
}
print;
}
if (%selects) {
foreach $k (sort (keys %selects)) {
print "$selects{$k}";
}
}
It found two duplicates:
Warning: removing duplicated S5P_SETUP_MIPIPHY entry
Warning: removing duplicated HARDIRQS_SW_RESEND entry
and they are identical duplicates, hence the shrinkage in the diffstat
of two lines.
We have four testers reporting success of this change (Tony, Stephen,
Linus and Sekhar.)
Acked-by: Jason Cooper <jason@lakedaemon.net>
Acked-by: Tony Lindgren <tony@atomide.com>
Acked-by: Stephen Warren <swarren@nvidia.com>
Acked-by: Linus Walleij <linus.walleij@linaro.org>
Acked-by: Sekhar Nori <nsekhar@ti.com>
Signed-off-by: Russell King <rmk+kernel@arm.linux.org.uk>
2012-10-07 00:12:25 +08:00
|
|
|
select CPU_V7
|
|
|
|
|
select PINCTRL
|
|
|
|
|
select PINCTRL_TEGRA30
|
|
|
|
|
select PL310_ERRATA_769419 if CACHE_L2X0
|
|
|
|
|
select USB_ARCH_HAS_EHCI if USB_SUPPORT
|
|
|
|
|
select USB_ULPI if USB
|
|
|
|
|
select USB_ULPI_VIEWPORT if USB_SUPPORT
|
2011-12-14 23:03:25 +08:00
|
|
|
help
|
|
|
|
|
Support for NVIDIA Tegra T30 processor family, based on the
|
|
|
|
|
ARM CortexA9MP CPU and the ARM PL310 L2 cache controller
|
2010-01-22 08:53:02 +08:00
|
|
|
|
2010-09-27 17:26:33 +08:00
|
|
|
config TEGRA_PCI
|
|
|
|
|
bool "PCI Express support"
|
2011-12-14 23:03:14 +08:00
|
|
|
depends on ARCH_TEGRA_2x_SOC
|
2010-09-27 17:26:33 +08:00
|
|
|
select PCI
|
|
|
|
|
|
2012-05-07 18:24:48 +08:00
|
|
|
config TEGRA_AHB
|
|
|
|
|
bool "Enable AHB driver for NVIDIA Tegra SoCs"
|
|
|
|
|
default y
|
|
|
|
|
help
|
|
|
|
|
Adds AHB configuration functionality for NVIDIA Tegra SoCs,
|
|
|
|
|
which controls AHB bus master arbitration and some
|
|
|
|
|
perfomance parameters(priority, prefech size).
|
|
|
|
|
|
2010-01-22 08:53:02 +08:00
|
|
|
choice
|
2012-03-27 02:49:57 +08:00
|
|
|
prompt "Default low-level debug console UART"
|
2010-01-22 08:53:02 +08:00
|
|
|
default TEGRA_DEBUG_UART_NONE
|
|
|
|
|
|
|
|
|
|
config TEGRA_DEBUG_UART_NONE
|
|
|
|
|
bool "None"
|
|
|
|
|
|
|
|
|
|
config TEGRA_DEBUG_UARTA
|
|
|
|
|
bool "UART-A"
|
|
|
|
|
|
|
|
|
|
config TEGRA_DEBUG_UARTB
|
|
|
|
|
bool "UART-B"
|
|
|
|
|
|
|
|
|
|
config TEGRA_DEBUG_UARTC
|
|
|
|
|
bool "UART-C"
|
|
|
|
|
|
|
|
|
|
config TEGRA_DEBUG_UARTD
|
|
|
|
|
bool "UART-D"
|
|
|
|
|
|
|
|
|
|
config TEGRA_DEBUG_UARTE
|
|
|
|
|
bool "UART-E"
|
|
|
|
|
|
|
|
|
|
endchoice
|
|
|
|
|
|
2012-03-27 02:49:57 +08:00
|
|
|
choice
|
|
|
|
|
prompt "Automatic low-level debug console UART"
|
|
|
|
|
default TEGRA_DEBUG_UART_AUTO_NONE
|
|
|
|
|
|
|
|
|
|
config TEGRA_DEBUG_UART_AUTO_NONE
|
|
|
|
|
bool "None"
|
|
|
|
|
|
|
|
|
|
config TEGRA_DEBUG_UART_AUTO_ODMDATA
|
|
|
|
|
bool "Via ODMDATA"
|
|
|
|
|
help
|
|
|
|
|
Automatically determines which UART to use for low-level debug based
|
|
|
|
|
on the ODMDATA value. This value is part of the BCT, and is written
|
|
|
|
|
to the boot memory device using nvflash, or other flashing tool.
|
|
|
|
|
When bits 19:18 are 3, then bits 17:15 indicate which UART to use;
|
|
|
|
|
0/1/2/3/4 are UART A/B/C/D/E.
|
|
|
|
|
|
|
|
|
|
config TEGRA_DEBUG_UART_AUTO_SCRATCH
|
|
|
|
|
bool "Via UART scratch register"
|
|
|
|
|
help
|
|
|
|
|
Automatically determines which UART to use for low-level debug based
|
|
|
|
|
on the UART scratch register value. Some bootloaders put ASCII 'D'
|
|
|
|
|
in this register when they initialize their own console UART output.
|
|
|
|
|
Using this option allows the kernel to automatically pick the same
|
|
|
|
|
UART.
|
|
|
|
|
|
|
|
|
|
endchoice
|
|
|
|
|
|
2011-02-13 10:22:49 +08:00
|
|
|
config TEGRA_EMC_SCALING_ENABLE
|
|
|
|
|
bool "Enable scaling the memory frequency"
|
2011-02-23 04:35:24 +08:00
|
|
|
|
|
|
|
|
endif
|