2006-06-29 15:06:33 +00:00
|
|
|
if ARCH_AT91
|
|
|
|
|
|
2009-10-22 16:50:26 +00:00
|
|
|
config HAVE_AT91_DATAFLASH_CARD
|
|
|
|
|
bool
|
|
|
|
|
|
2011-11-01 17:43:31 +00:00
|
|
|
config HAVE_AT91_DBGU0
|
|
|
|
|
bool
|
|
|
|
|
|
|
|
|
|
config HAVE_AT91_DBGU1
|
|
|
|
|
bool
|
|
|
|
|
|
2011-11-29 14:01:08 +00:00
|
|
|
config AT91_SAM9_ALT_RESET
|
|
|
|
|
bool
|
2012-03-02 19:14:16 +00:00
|
|
|
default !ARCH_AT91X40
|
2011-11-29 14:01:08 +00:00
|
|
|
|
2011-11-17 17:41:28 +00:00
|
|
|
config AT91_SAM9G45_RESET
|
|
|
|
|
bool
|
2012-03-02 19:14:16 +00:00
|
|
|
default !ARCH_AT91X40
|
2011-11-17 17:41:28 +00:00
|
|
|
|
2012-04-06 05:04:04 +00:00
|
|
|
config SOC_AT91SAM9
|
|
|
|
|
bool
|
|
|
|
|
select CPU_ARM926T
|
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-06 16:12:25 +00:00
|
|
|
select GENERIC_CLOCKEVENTS
|
2012-10-17 13:41:31 +00:00
|
|
|
select MULTI_IRQ_HANDLER
|
|
|
|
|
select SPARSE_IRQ
|
2012-04-06 05:04:04 +00:00
|
|
|
|
2006-06-29 15:06:33 +00:00
|
|
|
menu "Atmel AT91 System-on-Chip"
|
|
|
|
|
|
2012-04-06 03:51:50 +00:00
|
|
|
comment "Atmel AT91 Processor"
|
2006-06-29 15:06:33 +00:00
|
|
|
|
2012-04-06 03:51:50 +00:00
|
|
|
config SOC_AT91RM9200
|
2006-06-29 15:06:33 +00:00
|
|
|
bool "AT91RM9200"
|
2008-10-26 10:55:14 +00:00
|
|
|
select CPU_ARM920T
|
2007-07-31 00:41:26 +00:00
|
|
|
select GENERIC_CLOCKEVENTS
|
2011-11-01 17:43:31 +00:00
|
|
|
select HAVE_AT91_DBGU0
|
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-06 16:12:25 +00:00
|
|
|
select MULTI_IRQ_HANDLER
|
|
|
|
|
select SPARSE_IRQ
|
2006-01-09 17:05:41 +00:00
|
|
|
|
2012-04-06 03:51:50 +00:00
|
|
|
config SOC_AT91SAM9260
|
|
|
|
|
bool "AT91SAM9260, AT91SAM9XE or AT91SAM9G20"
|
2011-11-01 17:43:31 +00:00
|
|
|
select HAVE_AT91_DBGU0
|
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-06 16:12:25 +00:00
|
|
|
select SOC_AT91SAM9
|
2012-04-06 03:51:50 +00:00
|
|
|
help
|
|
|
|
|
Select this if you are using one of Atmel's AT91SAM9260, AT91SAM9XE
|
|
|
|
|
or AT91SAM9G20 SoC.
|
2006-06-29 15:06:33 +00:00
|
|
|
|
2012-04-06 03:51:50 +00:00
|
|
|
config SOC_AT91SAM9261
|
|
|
|
|
bool "AT91SAM9261 or AT91SAM9G10"
|
2011-11-01 17:43:31 +00:00
|
|
|
select HAVE_AT91_DBGU0
|
2009-06-23 14:30:56 +00:00
|
|
|
select HAVE_FB_ATMEL
|
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-06 16:12:25 +00:00
|
|
|
select SOC_AT91SAM9
|
2012-04-06 03:51:50 +00:00
|
|
|
help
|
|
|
|
|
Select this if you are using one of Atmel's AT91SAM9261 or AT91SAM9G10 SoC.
|
2009-06-26 14:37:01 +00:00
|
|
|
|
2012-04-06 03:51:50 +00:00
|
|
|
config SOC_AT91SAM9263
|
2007-02-08 08:42:40 +00:00
|
|
|
bool "AT91SAM9263"
|
2012-04-06 03:51:50 +00:00
|
|
|
select HAVE_AT91_DBGU1
|
2009-06-23 14:30:56 +00:00
|
|
|
select HAVE_FB_ATMEL
|
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-06 16:12:25 +00:00
|
|
|
select SOC_AT91SAM9
|
2007-02-08 08:42:40 +00:00
|
|
|
|
2012-04-06 03:51:50 +00:00
|
|
|
config SOC_AT91SAM9RL
|
2007-05-11 19:49:56 +00:00
|
|
|
bool "AT91SAM9RL"
|
2011-11-01 17:43:31 +00:00
|
|
|
select HAVE_AT91_DBGU0
|
2012-04-06 03:51:50 +00:00
|
|
|
select HAVE_FB_ATMEL
|
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-06 16:12:25 +00:00
|
|
|
select SOC_AT91SAM9
|
2007-05-11 19:49:56 +00:00
|
|
|
|
2012-04-06 03:51:50 +00:00
|
|
|
config SOC_AT91SAM9G45
|
2012-03-15 11:26:43 +00:00
|
|
|
bool "AT91SAM9G45 or AT91SAM9M10 families"
|
2012-04-06 03:51:50 +00:00
|
|
|
select HAVE_AT91_DBGU1
|
2009-06-23 14:30:56 +00:00
|
|
|
select HAVE_FB_ATMEL
|
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-06 16:12:25 +00:00
|
|
|
select SOC_AT91SAM9
|
2012-03-15 11:26:43 +00:00
|
|
|
help
|
|
|
|
|
Select this if you are using one of Atmel's AT91SAM9G45 family SoC.
|
|
|
|
|
This support covers AT91SAM9G45, AT91SAM9G46, AT91SAM9M10 and AT91SAM9M11.
|
2009-06-26 14:36:58 +00:00
|
|
|
|
2012-04-06 03:51:50 +00:00
|
|
|
config SOC_AT91SAM9X5
|
2012-01-23 15:16:44 +00:00
|
|
|
bool "AT91SAM9x5 family"
|
2012-04-06 03:51:50 +00:00
|
|
|
select HAVE_AT91_DBGU0
|
2012-01-23 15:16:44 +00:00
|
|
|
select HAVE_FB_ATMEL
|
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-06 16:12:25 +00:00
|
|
|
select SOC_AT91SAM9
|
2012-03-15 11:48:41 +00:00
|
|
|
help
|
|
|
|
|
Select this if you are using one of Atmel's AT91SAM9x5 family SoC.
|
|
|
|
|
This means that your SAM9 name finishes with a '5' (except if it is
|
|
|
|
|
AT91SAM9G45!).
|
|
|
|
|
This support covers AT91SAM9G15, AT91SAM9G25, AT91SAM9X25, AT91SAM9G35
|
|
|
|
|
and AT91SAM9X35.
|
2012-01-23 15:16:44 +00:00
|
|
|
|
2012-04-17 06:26:31 +00:00
|
|
|
config SOC_AT91SAM9N12
|
|
|
|
|
bool "AT91SAM9N12 family"
|
|
|
|
|
select HAVE_AT91_DBGU0
|
|
|
|
|
select HAVE_FB_ATMEL
|
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-06 16:12:25 +00:00
|
|
|
select SOC_AT91SAM9
|
2012-04-17 06:26:31 +00:00
|
|
|
help
|
|
|
|
|
Select this if you are using Atmel's AT91SAM9N12 SoC.
|
|
|
|
|
|
2012-04-06 03:51:50 +00:00
|
|
|
choice
|
|
|
|
|
prompt "Atmel AT91 Processor Devices for non DT boards"
|
|
|
|
|
|
|
|
|
|
config ARCH_AT91_NONE
|
|
|
|
|
bool "None"
|
|
|
|
|
|
|
|
|
|
config ARCH_AT91RM9200
|
|
|
|
|
bool "AT91RM9200"
|
|
|
|
|
select SOC_AT91RM9200
|
|
|
|
|
|
|
|
|
|
config ARCH_AT91SAM9260
|
|
|
|
|
bool "AT91SAM9260 or AT91SAM9XE"
|
|
|
|
|
select SOC_AT91SAM9260
|
|
|
|
|
|
|
|
|
|
config ARCH_AT91SAM9261
|
|
|
|
|
bool "AT91SAM9261"
|
|
|
|
|
select SOC_AT91SAM9261
|
|
|
|
|
|
|
|
|
|
config ARCH_AT91SAM9G10
|
|
|
|
|
bool "AT91SAM9G10"
|
|
|
|
|
select SOC_AT91SAM9261
|
|
|
|
|
|
|
|
|
|
config ARCH_AT91SAM9263
|
|
|
|
|
bool "AT91SAM9263"
|
|
|
|
|
select SOC_AT91SAM9263
|
|
|
|
|
|
|
|
|
|
config ARCH_AT91SAM9RL
|
|
|
|
|
bool "AT91SAM9RL"
|
|
|
|
|
select SOC_AT91SAM9RL
|
|
|
|
|
|
|
|
|
|
config ARCH_AT91SAM9G20
|
|
|
|
|
bool "AT91SAM9G20"
|
|
|
|
|
select SOC_AT91SAM9260
|
|
|
|
|
|
|
|
|
|
config ARCH_AT91SAM9G45
|
|
|
|
|
bool "AT91SAM9G45"
|
|
|
|
|
select SOC_AT91SAM9G45
|
|
|
|
|
|
2007-07-30 01:39:21 +00:00
|
|
|
config ARCH_AT91X40
|
|
|
|
|
bool "AT91x40"
|
2012-04-06 03:51:50 +00:00
|
|
|
depends on !MMU
|
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-06 16:12:25 +00:00
|
|
|
select ARCH_USES_GETTIMEOFFSET
|
2012-07-04 07:45:16 +00:00
|
|
|
select MULTI_IRQ_HANDLER
|
|
|
|
|
select SPARSE_IRQ
|
2007-07-30 01:39:21 +00:00
|
|
|
|
2006-12-01 10:51:19 +00:00
|
|
|
endchoice
|
|
|
|
|
|
2007-07-30 01:39:21 +00:00
|
|
|
config AT91_PMC_UNIT
|
|
|
|
|
bool
|
|
|
|
|
default !ARCH_AT91X40
|
|
|
|
|
|
2006-06-29 15:06:33 +00:00
|
|
|
# ----------------------------------------------------------
|
|
|
|
|
|
|
|
|
|
if ARCH_AT91RM9200
|
2006-01-09 17:05:41 +00:00
|
|
|
|
|
|
|
|
comment "AT91RM9200 Board Type"
|
|
|
|
|
|
2006-06-26 16:48:29 +00:00
|
|
|
config MACH_ONEARM
|
|
|
|
|
bool "Ajeco 1ARM Single Board Computer"
|
|
|
|
|
help
|
2006-06-29 15:06:33 +00:00
|
|
|
Select this if you are using Ajeco's 1ARM Single Board Computer.
|
2010-10-16 17:36:23 +00:00
|
|
|
<http://www.ajeco.fi/>
|
2006-06-26 16:48:29 +00:00
|
|
|
|
2006-01-09 17:05:41 +00:00
|
|
|
config ARCH_AT91RM9200DK
|
|
|
|
|
bool "Atmel AT91RM9200-DK Development board"
|
2009-10-22 16:50:26 +00:00
|
|
|
select HAVE_AT91_DATAFLASH_CARD
|
2006-01-09 17:05:41 +00:00
|
|
|
help
|
2006-06-29 15:06:33 +00:00
|
|
|
Select this if you are using Atmel's AT91RM9200-DK Development board.
|
|
|
|
|
(Discontinued)
|
|
|
|
|
|
2006-01-09 17:05:41 +00:00
|
|
|
config MACH_AT91RM9200EK
|
|
|
|
|
bool "Atmel AT91RM9200-EK Evaluation Kit"
|
2009-10-22 16:50:26 +00:00
|
|
|
select HAVE_AT91_DATAFLASH_CARD
|
2006-01-09 17:05:41 +00:00
|
|
|
help
|
2006-06-29 15:06:33 +00:00
|
|
|
Select this if you are using Atmel's AT91RM9200-EK Evaluation Kit.
|
|
|
|
|
<http://www.atmel.com/dyn/products/tools_card.asp?tool_id=3507>
|
2006-01-09 17:05:41 +00:00
|
|
|
|
|
|
|
|
config MACH_CSB337
|
2006-06-29 15:06:33 +00:00
|
|
|
bool "Cogent CSB337"
|
2006-01-09 17:05:41 +00:00
|
|
|
help
|
2006-06-29 15:06:33 +00:00
|
|
|
Select this if you are using Cogent's CSB337 board.
|
|
|
|
|
<http://www.cogcomp.com/csb_csb337.htm>
|
2006-01-09 17:05:41 +00:00
|
|
|
|
|
|
|
|
config MACH_CSB637
|
2006-06-29 15:06:33 +00:00
|
|
|
bool "Cogent CSB637"
|
2006-01-09 17:05:41 +00:00
|
|
|
help
|
2006-06-29 15:06:33 +00:00
|
|
|
Select this if you are using Cogent's CSB637 board.
|
|
|
|
|
<http://www.cogcomp.com/csb_csb637.htm>
|
2006-01-09 17:05:41 +00:00
|
|
|
|
|
|
|
|
config MACH_CARMEVA
|
2006-06-29 15:06:33 +00:00
|
|
|
bool "Conitec ARM&EVA"
|
2006-01-09 17:05:41 +00:00
|
|
|
help
|
2006-06-29 15:06:33 +00:00
|
|
|
Select this if you are using Conitec's AT91RM9200-MCU-Module.
|
2010-10-16 17:36:23 +00:00
|
|
|
<http://www.conitec.net/english/linuxboard.php>
|
2006-01-09 17:05:41 +00:00
|
|
|
|
2006-06-29 15:06:33 +00:00
|
|
|
config MACH_ATEB9200
|
|
|
|
|
bool "Embest ATEB9200"
|
2006-01-09 17:05:41 +00:00
|
|
|
help
|
2006-06-29 15:06:33 +00:00
|
|
|
Select this if you are using Embest's ATEB9200 board.
|
|
|
|
|
<http://www.embedinfo.com/english/product/ATEB9200.asp>
|
2006-01-09 17:05:41 +00:00
|
|
|
|
2006-06-29 15:06:33 +00:00
|
|
|
config MACH_KB9200
|
|
|
|
|
bool "KwikByte KB920x"
|
2006-06-20 18:30:18 +00:00
|
|
|
help
|
2006-06-29 15:06:33 +00:00
|
|
|
Select this if you are using KwikByte's KB920x board.
|
2010-10-16 17:36:23 +00:00
|
|
|
<http://www.kwikbyte.com/KB9202.html>
|
2006-06-20 18:30:18 +00:00
|
|
|
|
2007-04-02 13:06:29 +00:00
|
|
|
config MACH_PICOTUX2XX
|
|
|
|
|
bool "picotux 200"
|
|
|
|
|
help
|
|
|
|
|
Select this if you are using a picotux 200.
|
|
|
|
|
<http://www.picotux.com/>
|
|
|
|
|
|
2006-06-20 18:30:18 +00:00
|
|
|
config MACH_KAFA
|
|
|
|
|
bool "Sperry-Sun KAFA board"
|
|
|
|
|
help
|
2006-06-29 15:06:33 +00:00
|
|
|
Select this if you are using Sperry-Sun's KAFA board.
|
|
|
|
|
|
2008-04-15 20:10:11 +00:00
|
|
|
config MACH_ECBAT91
|
|
|
|
|
bool "emQbit ECB_AT91 SBC"
|
2009-10-22 16:50:26 +00:00
|
|
|
select HAVE_AT91_DATAFLASH_CARD
|
2008-04-15 20:10:11 +00:00
|
|
|
help
|
|
|
|
|
Select this if you are using emQbit's ECB_AT91 board.
|
|
|
|
|
<http://wiki.emqbit.com/free-ecb-at91>
|
|
|
|
|
|
2008-05-24 16:06:45 +00:00
|
|
|
config MACH_YL9200
|
|
|
|
|
bool "ucDragon YL-9200"
|
|
|
|
|
help
|
|
|
|
|
Select this if you are using the ucDragon YL-9200 board.
|
|
|
|
|
|
2009-07-30 06:23:42 +00:00
|
|
|
config MACH_CPUAT91
|
|
|
|
|
bool "Eukrea CPUAT91"
|
|
|
|
|
help
|
|
|
|
|
Select this if you are using the Eukrea Electromatique's
|
|
|
|
|
CPUAT91 board <http://www.eukrea.com/>.
|
|
|
|
|
|
2009-11-03 19:39:02 +00:00
|
|
|
config MACH_ECO920
|
|
|
|
|
bool "eco920"
|
|
|
|
|
help
|
|
|
|
|
Select this if you are using the eco920 board
|
|
|
|
|
|
2011-08-02 11:28:42 +00:00
|
|
|
config MACH_RSI_EWS
|
|
|
|
|
bool "RSI Embedded Webserver"
|
|
|
|
|
depends on ARCH_AT91RM9200
|
|
|
|
|
help
|
|
|
|
|
Select this if you are using RSIs EWS board.
|
2006-06-29 15:06:33 +00:00
|
|
|
endif
|
|
|
|
|
|
|
|
|
|
# ----------------------------------------------------------
|
|
|
|
|
|
|
|
|
|
if ARCH_AT91SAM9260
|
|
|
|
|
|
2007-02-15 07:17:38 +00:00
|
|
|
comment "AT91SAM9260 Variants"
|
|
|
|
|
|
|
|
|
|
comment "AT91SAM9260 / AT91SAM9XE Board Type"
|
2006-06-29 15:06:33 +00:00
|
|
|
|
2006-12-01 13:51:13 +00:00
|
|
|
config MACH_AT91SAM9260EK
|
2007-02-15 07:17:38 +00:00
|
|
|
bool "Atmel AT91SAM9260-EK / AT91SAM9XE Evaluation Kit"
|
2009-10-22 16:50:26 +00:00
|
|
|
select HAVE_AT91_DATAFLASH_CARD
|
2006-12-01 13:51:13 +00:00
|
|
|
help
|
2007-02-15 07:17:38 +00:00
|
|
|
Select this if you are using Atmel's AT91SAM9260-EK or AT91SAM9XE Evaluation Kit
|
2006-12-01 13:51:13 +00:00
|
|
|
<http://www.atmel.com/dyn/products/tools_card.asp?tool_id=3933>
|
|
|
|
|
|
2008-04-15 20:05:03 +00:00
|
|
|
config MACH_CAM60
|
|
|
|
|
bool "KwikByte KB9260 (CAM60) board"
|
|
|
|
|
help
|
|
|
|
|
Select this if you are using KwikByte's KB9260 (CAM60) board based on the Atmel AT91SAM9260.
|
|
|
|
|
<http://www.kwikbyte.com/KB9260.html>
|
|
|
|
|
|
2008-04-15 20:07:08 +00:00
|
|
|
config MACH_SAM9_L9260
|
|
|
|
|
bool "Olimex SAM9-L9260 board"
|
2009-10-22 16:50:26 +00:00
|
|
|
select HAVE_AT91_DATAFLASH_CARD
|
2008-04-15 20:07:08 +00:00
|
|
|
help
|
|
|
|
|
Select this if you are using Olimex's SAM9-L9260 board based on the Atmel AT91SAM9260.
|
|
|
|
|
<http://www.olimex.com/dev/sam9-L9260.html>
|
|
|
|
|
|
2008-08-03 01:29:48 +00:00
|
|
|
config MACH_AFEB9260
|
|
|
|
|
bool "Custom afeb9260 board v1"
|
|
|
|
|
help
|
|
|
|
|
Select this if you are using custom afeb9260 board based on
|
|
|
|
|
open hardware design. Select this for revision 1 of the board.
|
|
|
|
|
<svn://194.85.238.22/home/users/george/svn/arm9eb>
|
|
|
|
|
<http://groups.google.com/group/arm9fpga-evolution-board>
|
|
|
|
|
|
2008-05-24 16:47:04 +00:00
|
|
|
config MACH_USB_A9260
|
|
|
|
|
bool "CALAO USB-A9260"
|
|
|
|
|
help
|
|
|
|
|
Select this if you are using a Calao Systems USB-A9260.
|
|
|
|
|
<http://www.calao-systems.com>
|
|
|
|
|
|
|
|
|
|
config MACH_QIL_A9260
|
|
|
|
|
bool "CALAO QIL-A9260 board"
|
|
|
|
|
help
|
|
|
|
|
Select this if you are using a Calao Systems QIL-A9260 Board.
|
|
|
|
|
<http://www.calao-systems.com>
|
|
|
|
|
|
2009-07-30 06:20:03 +00:00
|
|
|
config MACH_CPU9260
|
|
|
|
|
bool "Eukrea CPU9260 board"
|
|
|
|
|
help
|
|
|
|
|
Select this if you are using a Eukrea Electromatique's
|
|
|
|
|
CPU9260 Board <http://www.eukrea.com/>
|
|
|
|
|
|
2010-09-15 10:54:49 +00:00
|
|
|
config MACH_FLEXIBITY
|
|
|
|
|
bool "Flexibity Connect board"
|
|
|
|
|
help
|
|
|
|
|
Select this if you are using Flexibity Connect board
|
|
|
|
|
<http://www.flexibity.com>
|
|
|
|
|
|
2006-06-29 15:06:33 +00:00
|
|
|
endif
|
|
|
|
|
|
|
|
|
|
# ----------------------------------------------------------
|
|
|
|
|
|
|
|
|
|
if ARCH_AT91SAM9261
|
|
|
|
|
|
|
|
|
|
comment "AT91SAM9261 Board Type"
|
|
|
|
|
|
2006-12-01 13:51:13 +00:00
|
|
|
config MACH_AT91SAM9261EK
|
|
|
|
|
bool "Atmel AT91SAM9261-EK Evaluation Kit"
|
2009-10-22 16:50:26 +00:00
|
|
|
select HAVE_AT91_DATAFLASH_CARD
|
2006-12-01 13:51:13 +00:00
|
|
|
help
|
|
|
|
|
Select this if you are using Atmel's AT91SAM9261-EK Evaluation Kit.
|
|
|
|
|
<http://www.atmel.com/dyn/products/tools_card.asp?tool_id=3820>
|
|
|
|
|
|
2006-06-29 15:06:33 +00:00
|
|
|
endif
|
|
|
|
|
|
2006-12-01 13:51:13 +00:00
|
|
|
# ----------------------------------------------------------
|
|
|
|
|
|
2009-06-26 14:37:01 +00:00
|
|
|
if ARCH_AT91SAM9G10
|
|
|
|
|
|
|
|
|
|
comment "AT91SAM9G10 Board Type"
|
|
|
|
|
|
|
|
|
|
config MACH_AT91SAM9G10EK
|
|
|
|
|
bool "Atmel AT91SAM9G10-EK Evaluation Kit"
|
2009-10-22 16:50:26 +00:00
|
|
|
select HAVE_AT91_DATAFLASH_CARD
|
2009-06-26 14:37:01 +00:00
|
|
|
help
|
|
|
|
|
Select this if you are using Atmel's AT91SAM9G10-EK Evaluation Kit.
|
|
|
|
|
<http://www.atmel.com/dyn/products/tools_card.asp?tool_id=4588>
|
|
|
|
|
|
|
|
|
|
endif
|
|
|
|
|
|
|
|
|
|
# ----------------------------------------------------------
|
|
|
|
|
|
2007-02-08 09:22:16 +00:00
|
|
|
if ARCH_AT91SAM9263
|
|
|
|
|
|
|
|
|
|
comment "AT91SAM9263 Board Type"
|
|
|
|
|
|
|
|
|
|
config MACH_AT91SAM9263EK
|
|
|
|
|
bool "Atmel AT91SAM9263-EK Evaluation Kit"
|
2009-10-22 16:50:26 +00:00
|
|
|
select HAVE_AT91_DATAFLASH_CARD
|
2007-02-08 09:22:16 +00:00
|
|
|
help
|
|
|
|
|
Select this if you are using Atmel's AT91SAM9263-EK Evaluation Kit.
|
|
|
|
|
<http://www.atmel.com/dyn/products/tools_card.asp?tool_id=4057>
|
|
|
|
|
|
2008-05-24 16:47:04 +00:00
|
|
|
config MACH_USB_A9263
|
|
|
|
|
bool "CALAO USB-A9263"
|
|
|
|
|
help
|
|
|
|
|
Select this if you are using a Calao Systems USB-A9263.
|
|
|
|
|
<http://www.calao-systems.com>
|
|
|
|
|
|
2008-10-06 19:13:53 +00:00
|
|
|
config MACH_NEOCORE926
|
|
|
|
|
bool "Adeneo NEOCORE926"
|
2009-10-22 16:50:26 +00:00
|
|
|
select HAVE_AT91_DATAFLASH_CARD
|
2008-10-06 19:13:53 +00:00
|
|
|
help
|
|
|
|
|
Select this if you are using the Adeneo Neocore 926 board.
|
|
|
|
|
|
2007-02-08 09:22:16 +00:00
|
|
|
endif
|
|
|
|
|
|
|
|
|
|
# ----------------------------------------------------------
|
|
|
|
|
|
2007-05-11 18:24:18 +00:00
|
|
|
if ARCH_AT91SAM9RL
|
|
|
|
|
|
|
|
|
|
comment "AT91SAM9RL Board Type"
|
|
|
|
|
|
|
|
|
|
config MACH_AT91SAM9RLEK
|
|
|
|
|
bool "Atmel AT91SAM9RL-EK Evaluation Kit"
|
|
|
|
|
help
|
|
|
|
|
Select this if you are using Atmel's AT91SAM9RL-EK Evaluation Kit.
|
|
|
|
|
|
|
|
|
|
endif
|
|
|
|
|
|
|
|
|
|
# ----------------------------------------------------------
|
|
|
|
|
|
2008-07-10 09:15:35 +00:00
|
|
|
if ARCH_AT91SAM9G20
|
|
|
|
|
|
|
|
|
|
comment "AT91SAM9G20 Board Type"
|
|
|
|
|
|
|
|
|
|
config MACH_AT91SAM9G20EK
|
|
|
|
|
bool "Atmel AT91SAM9G20-EK Evaluation Kit"
|
2009-10-22 16:50:26 +00:00
|
|
|
select HAVE_AT91_DATAFLASH_CARD
|
2008-07-10 09:15:35 +00:00
|
|
|
help
|
2009-10-20 14:32:53 +00:00
|
|
|
Select this if you are using Atmel's AT91SAM9G20-EK Evaluation Kit
|
|
|
|
|
that embeds only one SD/MMC slot.
|
|
|
|
|
|
|
|
|
|
config MACH_AT91SAM9G20EK_2MMC
|
2010-09-21 16:01:37 +00:00
|
|
|
depends on MACH_AT91SAM9G20EK
|
2009-10-20 14:32:53 +00:00
|
|
|
bool "Atmel AT91SAM9G20-EK Evaluation Kit with 2 SD/MMC Slots"
|
|
|
|
|
help
|
|
|
|
|
Select this if you are using an Atmel AT91SAM9G20-EK Evaluation Kit
|
|
|
|
|
with 2 SD/MMC Slots. This is the case for AT91SAM9G20-EK rev. C and
|
|
|
|
|
onwards.
|
2012-03-15 12:56:44 +00:00
|
|
|
<http://www.atmel.com/tools/SAM9G20-EK.aspx>
|
2008-07-10 09:15:35 +00:00
|
|
|
|
2009-07-30 06:20:03 +00:00
|
|
|
config MACH_CPU9G20
|
|
|
|
|
bool "Eukrea CPU9G20 board"
|
|
|
|
|
help
|
|
|
|
|
Select this if you are using a Eukrea Electromatique's
|
|
|
|
|
CPU9G20 Board <http://www.eukrea.com/>
|
|
|
|
|
|
2010-10-14 00:06:26 +00:00
|
|
|
config MACH_ACMENETUSFOXG20
|
|
|
|
|
bool "Acme Systems srl FOX Board G20"
|
|
|
|
|
help
|
|
|
|
|
Select this if you are using Acme Systems
|
|
|
|
|
FOX Board G20 <http://www.acmesystems.it>
|
|
|
|
|
|
2010-04-13 13:55:10 +00:00
|
|
|
config MACH_PORTUXG20
|
|
|
|
|
bool "taskit PortuxG20"
|
|
|
|
|
help
|
|
|
|
|
Select this if you are using taskit's PortuxG20.
|
|
|
|
|
<http://www.taskit.de/en/>
|
|
|
|
|
|
|
|
|
|
config MACH_STAMP9G20
|
|
|
|
|
bool "taskit Stamp9G20 CPU module"
|
|
|
|
|
help
|
|
|
|
|
Select this if you are using taskit's Stamp9G20 CPU module on its
|
|
|
|
|
evaluation board.
|
|
|
|
|
<http://www.taskit.de/en/>
|
|
|
|
|
|
2010-10-13 14:18:51 +00:00
|
|
|
config MACH_PCONTROL_G20
|
|
|
|
|
bool "PControl G20 CPU module"
|
|
|
|
|
help
|
|
|
|
|
Select this if you are using taskit's Stamp9G20 CPU module on this
|
|
|
|
|
carrier board, beeing the decentralized unit of a building automation
|
|
|
|
|
system; featuring nvram, eth-switch, iso-rs485, display, io
|
2011-01-14 18:01:13 +00:00
|
|
|
|
|
|
|
|
config MACH_GSIA18S
|
|
|
|
|
bool "GS_IA18_S board"
|
|
|
|
|
help
|
|
|
|
|
This enables support for the GS_IA18_S board
|
|
|
|
|
produced by GeoSIG Ltd company. This is an internet accelerograph.
|
|
|
|
|
<http://www.geosig.com>
|
2011-08-30 16:25:53 +00:00
|
|
|
|
|
|
|
|
config MACH_USB_A9G20
|
|
|
|
|
bool "CALAO USB-A9G20"
|
|
|
|
|
depends on ARCH_AT91SAM9G20
|
|
|
|
|
help
|
|
|
|
|
Select this if you are using a Calao Systems USB-A9G20.
|
|
|
|
|
<http://www.calao-systems.com>
|
|
|
|
|
|
2008-07-10 09:15:35 +00:00
|
|
|
endif
|
|
|
|
|
|
2010-07-06 20:48:53 +00:00
|
|
|
if (ARCH_AT91SAM9260 || ARCH_AT91SAM9G20)
|
|
|
|
|
comment "AT91SAM9260/AT91SAM9G20 boards"
|
|
|
|
|
|
|
|
|
|
config MACH_SNAPPER_9260
|
|
|
|
|
bool "Bluewater Systems Snapper 9260/9G20 module"
|
|
|
|
|
help
|
|
|
|
|
Select this if you are using the Bluewater Systems Snapper 9260 or
|
|
|
|
|
Snapper 9G20 modules.
|
|
|
|
|
<http://www.bluewatersys.com/>
|
|
|
|
|
endif
|
|
|
|
|
|
2008-07-10 09:15:35 +00:00
|
|
|
# ----------------------------------------------------------
|
|
|
|
|
|
2009-06-26 14:36:58 +00:00
|
|
|
if ARCH_AT91SAM9G45
|
|
|
|
|
|
|
|
|
|
comment "AT91SAM9G45 Board Type"
|
|
|
|
|
|
2010-09-22 05:55:59 +00:00
|
|
|
config MACH_AT91SAM9M10G45EK
|
|
|
|
|
bool "Atmel AT91SAM9M10G45-EK Evaluation Kits"
|
2009-06-26 14:36:58 +00:00
|
|
|
help
|
2012-03-15 11:57:03 +00:00
|
|
|
Select this if you are using Atmel's AT91SAM9M10G45-EK Evaluation Kit.
|
|
|
|
|
Those boards can be populated with any SoC of AT91SAM9G45 or AT91SAM9M10
|
|
|
|
|
families: AT91SAM9G45, AT91SAM9G46, AT91SAM9M10 and AT91SAM9M11.
|
|
|
|
|
<http://www.atmel.com/tools/SAM9M10-G45-EK.aspx>
|
2009-06-26 14:36:58 +00:00
|
|
|
|
|
|
|
|
endif
|
|
|
|
|
|
|
|
|
|
# ----------------------------------------------------------
|
|
|
|
|
|
2007-07-30 01:39:21 +00:00
|
|
|
if ARCH_AT91X40
|
|
|
|
|
|
|
|
|
|
comment "AT91X40 Board Type"
|
|
|
|
|
|
|
|
|
|
config MACH_AT91EB01
|
|
|
|
|
bool "Atmel AT91EB01 Evaluation Kit"
|
|
|
|
|
help
|
|
|
|
|
Select this if you are using Atmel's AT91EB01 Evaluation Kit.
|
|
|
|
|
It is also a popular target for simulators such as GDB's
|
|
|
|
|
ARM simulator (commonly known as the ARMulator) and the
|
|
|
|
|
Skyeye simulator.
|
|
|
|
|
|
|
|
|
|
endif
|
|
|
|
|
|
|
|
|
|
# ----------------------------------------------------------
|
|
|
|
|
|
2011-10-10 16:29:24 +00:00
|
|
|
comment "Generic Board Type"
|
|
|
|
|
|
2012-10-28 18:31:09 +00:00
|
|
|
config MACH_AT91RM9200_DT
|
|
|
|
|
bool "Atmel AT91RM9200 Evaluation Kits with device-tree support"
|
|
|
|
|
depends on SOC_AT91RM9200
|
|
|
|
|
select USE_OF
|
|
|
|
|
help
|
|
|
|
|
Select this if you want to experiment device-tree with
|
|
|
|
|
an Atmel RM9200 Evaluation Kit.
|
|
|
|
|
|
2011-10-10 16:29:24 +00:00
|
|
|
config MACH_AT91SAM_DT
|
|
|
|
|
bool "Atmel AT91SAM Evaluation Kits with device-tree support"
|
2012-10-28 18:31:06 +00:00
|
|
|
depends on SOC_AT91SAM9
|
2011-10-10 16:29:24 +00:00
|
|
|
select USE_OF
|
|
|
|
|
help
|
|
|
|
|
Select this if you want to experiment device-tree with
|
|
|
|
|
an Atmel Evaluation Kit.
|
|
|
|
|
|
|
|
|
|
# ----------------------------------------------------------
|
|
|
|
|
|
2006-12-01 13:51:13 +00:00
|
|
|
comment "AT91 Board Options"
|
|
|
|
|
|
|
|
|
|
config MTD_AT91_DATAFLASH_CARD
|
|
|
|
|
bool "Enable DataFlash Card support"
|
2009-10-22 16:50:26 +00:00
|
|
|
depends on HAVE_AT91_DATAFLASH_CARD
|
2006-12-01 13:51:13 +00:00
|
|
|
help
|
|
|
|
|
Enable support for the DataFlash card.
|
|
|
|
|
|
2006-06-29 15:06:33 +00:00
|
|
|
# ----------------------------------------------------------
|
2006-01-09 17:05:41 +00:00
|
|
|
|
2006-06-29 15:06:33 +00:00
|
|
|
comment "AT91 Feature Selections"
|
2006-01-09 17:05:41 +00:00
|
|
|
|
|
|
|
|
config AT91_PROGRAMMABLE_CLOCKS
|
|
|
|
|
bool "Programmable Clocks"
|
|
|
|
|
help
|
|
|
|
|
Select this if you need to program one or more of the PCK0..PCK3
|
|
|
|
|
programmable clock outputs.
|
|
|
|
|
|
2008-09-21 20:35:18 +00:00
|
|
|
config AT91_SLOW_CLOCK
|
|
|
|
|
bool "Suspend-to-RAM disables main oscillator"
|
|
|
|
|
depends on SUSPEND
|
|
|
|
|
help
|
|
|
|
|
Select this if you want Suspend-to-RAM to save the most power
|
|
|
|
|
possible (without powering off the CPU) by disabling the PLLs
|
|
|
|
|
and main oscillator so that only the 32 KiHz clock is available.
|
|
|
|
|
|
|
|
|
|
When only that slow-clock is available, some peripherals lose
|
|
|
|
|
functionality. Many can't issue wakeup events unless faster
|
|
|
|
|
clocks are available. Some lose their operating state and
|
|
|
|
|
need to be completely re-initialized.
|
|
|
|
|
|
2007-11-12 16:59:10 +00:00
|
|
|
config AT91_TIMER_HZ
|
|
|
|
|
int "Kernel HZ (jiffies per second)"
|
|
|
|
|
range 32 1024
|
|
|
|
|
depends on ARCH_AT91
|
|
|
|
|
default "128" if ARCH_AT91RM9200
|
|
|
|
|
default "100"
|
|
|
|
|
help
|
|
|
|
|
On AT91rm9200 chips where you're using a system clock derived
|
|
|
|
|
from the 32768 Hz hardware clock, this tick rate should divide
|
|
|
|
|
it exactly: use a power-of-two value, such as 128 or 256, to
|
|
|
|
|
reduce timing errors caused by rounding.
|
|
|
|
|
|
|
|
|
|
On AT91sam926x chips, or otherwise when using a higher precision
|
|
|
|
|
system clock (of at least several MHz), rounding is less of a
|
|
|
|
|
problem so it can be safer to use a decimal values like 100.
|
|
|
|
|
|
2006-01-09 17:05:41 +00:00
|
|
|
endmenu
|
|
|
|
|
|
|
|
|
|
endif
|
