2008-09-09 22:13:33 +08:00
|
|
|
if ARCH_MSM
|
2007-11-26 20:12:13 +08:00
|
|
|
|
2012-09-11 01:33:09 +08:00
|
|
|
comment "Qualcomm MSM SoC Type"
|
2013-09-10 07:24:54 +08:00
|
|
|
depends on ARCH_MSM_DT
|
2012-09-11 01:33:09 +08:00
|
|
|
|
2010-03-17 07:29:44 +08:00
|
|
|
choice
|
|
|
|
|
prompt "Qualcomm MSM SoC Type"
|
|
|
|
|
default ARCH_MSM7X00A
|
2013-09-10 07:24:54 +08:00
|
|
|
depends on !ARCH_MSM_DT
|
2010-03-17 07:29:44 +08:00
|
|
|
|
|
|
|
|
config ARCH_MSM7X00A
|
|
|
|
|
bool "MSM7x00A / MSM7x01A"
|
|
|
|
|
select ARCH_MSM_ARM11
|
|
|
|
|
select CPU_V6
|
2011-05-17 04:57:39 +08:00
|
|
|
select GPIO_MSM_V1
|
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 MACH_TROUT if !MACH_HALIBUT
|
2010-04-22 07:20:27 +08:00
|
|
|
select MSM_PROC_COMM
|
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 MSM_SMD
|
|
|
|
|
select MSM_SMD_PKG3
|
2010-03-17 07:29:44 +08:00
|
|
|
|
2010-05-07 03:44:57 +08:00
|
|
|
config ARCH_MSM7X30
|
|
|
|
|
bool "MSM7x30"
|
|
|
|
|
select ARCH_MSM_SCORPION
|
|
|
|
|
select CPU_V7
|
2011-05-17 04:57:39 +08:00
|
|
|
select GPIO_MSM_V1
|
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 MACH_MSM7X30_SURF # if !
|
|
|
|
|
select MSM_GPIOMUX
|
2010-04-22 07:20:27 +08:00
|
|
|
select MSM_PROC_COMM
|
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 MSM_SMD
|
|
|
|
|
select MSM_VIC
|
2010-05-07 03:44:57 +08:00
|
|
|
|
2010-05-07 04:54:17 +08:00
|
|
|
config ARCH_QSD8X50
|
|
|
|
|
bool "QSD8X50"
|
|
|
|
|
select ARCH_MSM_SCORPION
|
|
|
|
|
select CPU_V7
|
2011-05-17 04:57:39 +08:00
|
|
|
select GPIO_MSM_V1
|
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 MACH_QSD8X50_SURF if !MACH_QSD8X50A_ST1_5
|
|
|
|
|
select MSM_GPIOMUX
|
2010-04-22 07:20:27 +08:00
|
|
|
select MSM_PROC_COMM
|
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 MSM_SMD
|
|
|
|
|
select MSM_VIC
|
2010-08-19 02:00:25 +08:00
|
|
|
|
2012-09-11 01:33:09 +08:00
|
|
|
endchoice
|
|
|
|
|
|
2010-08-13 04:02:56 +08:00
|
|
|
config ARCH_MSM8X60
|
|
|
|
|
bool "MSM8X60"
|
|
|
|
|
select ARM_GIC
|
|
|
|
|
select CPU_V7
|
2011-05-17 06:53:38 +08:00
|
|
|
select GPIO_MSM_V2
|
2013-02-28 07:28:14 +08:00
|
|
|
select HAVE_SMP
|
2010-08-28 01:01:23 +08:00
|
|
|
select MSM_SCM if SMP
|
2010-08-13 04:02:56 +08:00
|
|
|
|
2010-12-02 11:31:16 +08:00
|
|
|
config ARCH_MSM8960
|
|
|
|
|
bool "MSM8960"
|
|
|
|
|
select ARM_GIC
|
|
|
|
|
select CPU_V7
|
2013-02-28 07:28:14 +08:00
|
|
|
select HAVE_SMP
|
2013-06-11 06:50:19 +08:00
|
|
|
select GPIO_MSM_V2
|
2010-12-02 11:31:16 +08:00
|
|
|
select MSM_SCM if SMP
|
2013-09-10 07:24:54 +08:00
|
|
|
|
2013-12-21 03:09:15 +08:00
|
|
|
config ARCH_MSM8974
|
|
|
|
|
bool "MSM8974"
|
|
|
|
|
select ARM_GIC
|
|
|
|
|
select CPU_V7
|
|
|
|
|
select HAVE_ARM_ARCH_TIMER
|
|
|
|
|
select HAVE_SMP
|
|
|
|
|
select MSM_SCM if SMP
|
|
|
|
|
select USE_OF
|
|
|
|
|
|
2013-09-10 07:24:54 +08:00
|
|
|
config ARCH_MSM_DT
|
|
|
|
|
def_bool y
|
2013-12-21 03:09:15 +08:00
|
|
|
depends on (ARCH_MSM8X60 || ARCH_MSM8960 || ARCH_MSM8974)
|
2013-09-10 07:24:53 +08:00
|
|
|
select SPARSE_IRQ
|
2012-09-06 03:28:58 +08:00
|
|
|
select USE_OF
|
2010-12-02 11:31:16 +08:00
|
|
|
|
2011-11-09 02:33:04 +08:00
|
|
|
config MSM_HAS_DEBUG_UART_HS
|
|
|
|
|
bool
|
|
|
|
|
|
2010-05-07 04:54:17 +08:00
|
|
|
config MSM_SOC_REV_A
|
|
|
|
|
bool
|
|
|
|
|
|
|
|
|
|
config ARCH_MSM_ARM11
|
|
|
|
|
bool
|
2013-09-10 07:24:54 +08:00
|
|
|
|
2010-05-07 04:54:17 +08:00
|
|
|
config ARCH_MSM_SCORPION
|
2010-03-17 07:29:44 +08:00
|
|
|
bool
|
|
|
|
|
|
2010-05-01 13:06:50 +08:00
|
|
|
config MSM_VIC
|
|
|
|
|
bool
|
2010-03-17 07:29:44 +08:00
|
|
|
|
2010-05-07 04:54:17 +08:00
|
|
|
menu "Qualcomm MSM Board Type"
|
2013-09-10 07:24:54 +08:00
|
|
|
depends on !ARCH_MSM_DT
|
2010-05-07 04:54:17 +08:00
|
|
|
|
|
|
|
|
config MACH_HALIBUT
|
2008-09-09 22:13:33 +08:00
|
|
|
depends on ARCH_MSM
|
2010-05-07 04:54:17 +08:00
|
|
|
depends on ARCH_MSM7X00A
|
|
|
|
|
bool "Halibut Board (QCT SURF7201A)"
|
|
|
|
|
help
|
|
|
|
|
Support for the Qualcomm SURF7201A eval board.
|
|
|
|
|
|
|
|
|
|
config MACH_TROUT
|
|
|
|
|
depends on ARCH_MSM
|
|
|
|
|
depends on ARCH_MSM7X00A
|
|
|
|
|
bool "HTC Dream (aka trout)"
|
|
|
|
|
help
|
|
|
|
|
Support for the HTC Dream, T-Mobile G1, Android ADP1 devices.
|
|
|
|
|
|
2010-05-07 03:44:57 +08:00
|
|
|
config MACH_MSM7X30_SURF
|
|
|
|
|
depends on ARCH_MSM7X30
|
|
|
|
|
bool "MSM7x30 SURF"
|
|
|
|
|
help
|
|
|
|
|
Support for the Qualcomm MSM7x30 SURF eval board.
|
|
|
|
|
|
2010-05-07 04:54:17 +08:00
|
|
|
config MACH_QSD8X50_SURF
|
|
|
|
|
depends on ARCH_QSD8X50
|
|
|
|
|
bool "QSD8x50 SURF"
|
|
|
|
|
help
|
|
|
|
|
Support for the Qualcomm QSD8x50 SURF eval board.
|
|
|
|
|
|
|
|
|
|
config MACH_QSD8X50A_ST1_5
|
|
|
|
|
depends on ARCH_QSD8X50
|
|
|
|
|
bool "QSD8x50A ST1.5"
|
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 MSM_SOC_REV_A
|
2010-05-07 04:54:17 +08:00
|
|
|
help
|
|
|
|
|
Support for the Qualcomm ST1.5.
|
|
|
|
|
|
|
|
|
|
endmenu
|
2007-11-26 20:12:13 +08:00
|
|
|
|
2010-03-17 07:29:44 +08:00
|
|
|
config MSM_SMD_PKG3
|
|
|
|
|
bool
|
|
|
|
|
|
2010-04-22 07:20:27 +08:00
|
|
|
config MSM_PROC_COMM
|
|
|
|
|
bool
|
|
|
|
|
|
2008-09-30 07:00:48 +08:00
|
|
|
config MSM_SMD
|
2010-04-23 05:16:46 +08:00
|
|
|
bool
|
2008-09-30 07:00:48 +08:00
|
|
|
|
2010-09-02 07:26:12 +08:00
|
|
|
config MSM_GPIOMUX
|
2013-06-19 09:53:33 +08:00
|
|
|
bool
|
2013-09-10 07:24:54 +08:00
|
|
|
depends on !ARCH_MSM_DT
|
2013-06-11 06:50:19 +08:00
|
|
|
help
|
|
|
|
|
Support for MSM V1 TLMM GPIOMUX architecture.
|
2010-11-13 11:29:57 +08:00
|
|
|
|
2010-08-28 01:01:23 +08:00
|
|
|
config MSM_SCM
|
|
|
|
|
bool
|
2007-11-26 20:12:13 +08:00
|
|
|
endif
|