2013-11-09 20:33:48 +08:00
|
|
|
config ARCH_SHMOBILE
|
|
|
|
|
bool
|
2014-10-23 22:38:31 +08:00
|
|
|
select ZONE_DMA if ARM_LPAE
|
2013-11-09 20:33:48 +08:00
|
|
|
|
2014-08-25 11:03:52 +08:00
|
|
|
config PM_RCAR
|
|
|
|
|
bool
|
|
|
|
|
|
2014-08-25 11:04:01 +08:00
|
|
|
config PM_RMOBILE
|
|
|
|
|
bool
|
2014-12-03 21:41:45 +08:00
|
|
|
select PM_GENERIC_DOMAINS
|
2014-08-25 11:04:01 +08:00
|
|
|
|
2014-08-25 11:03:34 +08:00
|
|
|
config ARCH_RCAR_GEN1
|
|
|
|
|
bool
|
2014-08-25 11:03:52 +08:00
|
|
|
select PM_RCAR if PM || SMP
|
2014-08-25 11:03:34 +08:00
|
|
|
select RENESAS_INTC_IRQPIN
|
|
|
|
|
select SYS_SUPPORTS_SH_TMU
|
|
|
|
|
|
2014-08-25 11:03:43 +08:00
|
|
|
config ARCH_RCAR_GEN2
|
|
|
|
|
bool
|
2014-08-25 11:03:52 +08:00
|
|
|
select PM_RCAR if PM || SMP
|
2014-08-25 11:03:43 +08:00
|
|
|
select RENESAS_IRQC
|
|
|
|
|
select SYS_SUPPORTS_SH_CMT
|
2014-11-05 01:38:28 +08:00
|
|
|
select PCI_DOMAINS if PCI
|
2014-08-25 11:03:43 +08:00
|
|
|
|
2014-08-25 11:03:25 +08:00
|
|
|
config ARCH_RMOBILE
|
|
|
|
|
bool
|
2014-12-03 21:41:45 +08:00
|
|
|
select PM_RMOBILE if PM
|
2014-08-25 11:03:25 +08:00
|
|
|
select SYS_SUPPORTS_SH_CMT
|
|
|
|
|
select SYS_SUPPORTS_SH_TMU
|
|
|
|
|
|
2014-06-10 22:06:10 +08:00
|
|
|
menuconfig ARCH_SHMOBILE_MULTI
|
2013-11-29 00:27:29 +08:00
|
|
|
bool "Renesas ARM SoCs" if ARCH_MULTI_V7
|
2013-07-18 04:31:09 +08:00
|
|
|
depends on MMU
|
2013-11-09 20:33:48 +08:00
|
|
|
select ARCH_SHMOBILE
|
2013-07-18 04:31:09 +08:00
|
|
|
select HAVE_ARM_SCU if SMP
|
2014-02-02 06:35:44 +08:00
|
|
|
select HAVE_ARM_TWD if SMP
|
2013-07-18 04:31:09 +08:00
|
|
|
select ARM_GIC
|
2014-02-05 13:36:28 +08:00
|
|
|
select ARCH_DMA_ADDR_T_64BIT if ARM_LPAE
|
2014-04-08 06:39:19 +08:00
|
|
|
select NO_IOPORT_MAP
|
2013-07-18 04:31:09 +08:00
|
|
|
select PINCTRL
|
|
|
|
|
select ARCH_REQUIRE_GPIOLIB
|
|
|
|
|
|
|
|
|
|
if ARCH_SHMOBILE_MULTI
|
|
|
|
|
|
2014-06-10 22:06:10 +08:00
|
|
|
#comment "Renesas ARM SoCs System Type"
|
2013-07-18 04:31:09 +08:00
|
|
|
|
2013-07-18 04:31:18 +08:00
|
|
|
config ARCH_EMEV2
|
|
|
|
|
bool "Emma Mobile EV2"
|
2014-02-20 19:54:46 +08:00
|
|
|
select SYS_SUPPORTS_EM_STI
|
2013-07-18 04:31:18 +08:00
|
|
|
|
2013-11-07 07:31:25 +08:00
|
|
|
config ARCH_R7S72100
|
|
|
|
|
bool "RZ/A1H (R7S72100)"
|
2014-02-20 19:54:46 +08:00
|
|
|
select SYS_SUPPORTS_SH_MTU2
|
2013-11-07 07:31:25 +08:00
|
|
|
|
2014-12-18 00:18:17 +08:00
|
|
|
config ARCH_R8A73A4
|
|
|
|
|
bool "R-Mobile APE6 (R8A73A40)"
|
|
|
|
|
select ARCH_RMOBILE
|
|
|
|
|
select RENESAS_IRQC
|
|
|
|
|
|
2014-08-25 11:36:53 +08:00
|
|
|
config ARCH_R8A7740
|
|
|
|
|
bool "R-Mobile A1 (R8A77400)"
|
|
|
|
|
select ARCH_RMOBILE
|
|
|
|
|
select RENESAS_INTC_IRQPIN
|
|
|
|
|
|
2015-02-27 00:42:13 +08:00
|
|
|
config ARCH_R8A7778
|
|
|
|
|
bool "R-Car M1A (R8A77781)"
|
|
|
|
|
select ARCH_RCAR_GEN1
|
|
|
|
|
|
2014-05-15 19:32:05 +08:00
|
|
|
config ARCH_R8A7779
|
|
|
|
|
bool "R-Car H1 (R8A77790)"
|
2014-08-25 11:03:34 +08:00
|
|
|
select ARCH_RCAR_GEN1
|
2014-05-15 19:32:05 +08:00
|
|
|
|
2013-12-11 22:13:52 +08:00
|
|
|
config ARCH_R8A7790
|
|
|
|
|
bool "R-Car H2 (R8A77900)"
|
2014-08-25 11:03:43 +08:00
|
|
|
select ARCH_RCAR_GEN2
|
ARM: shmobile: R-Car Gen2: Add da9063/da9210 regulator quirk
The r8a7790/lager and r8a7791/koelsch development boards have da9063 and
da9210 regulators. Both regulators have their interrupt request lines
tied to the same interrupt pin (IRQ2) on the SoC.
After cold boot or da9063-induced restart, both the da9063 and da9210
seem to assert their interrupt request lines. Hence as soon as one
driver requests this irq, it gets stuck in an interrupt storm, as it
only manages to deassert its own interrupt request line, and the other
driver hasn't installed an interrupt handler yet.
To handle this, install a quirk that masks the interrupts in both the
da9063 and da9210. This quirk has to run after the i2c master driver
has been initialized, but before the i2c slave drivers are initialized.
As it depends on i2c, select I2C if one of the affected platforms is
enabled in the kernel config.
On koelsch, the following happens:
- Cold boot or reboot using the da9063 restart handler:
IRQ2 is asserted, installing da9063/da9210 regulator quirk
...
i2c i2c-6: regulator_quirk_notify: 1, IRQC_MONITOR = 0x3fb
i2c 6-0058: regulator_quirk_notify: 1, IRQC_MONITOR = 0x3fb
i2c 6-0058: Detected da9063
i2c 6-0058: Masking da9063 interrupt sources
i2c 6-0068: regulator_quirk_notify: 1, IRQC_MONITOR = 0x3fb
i2c 6-0068: Detected da9210
i2c 6-0068: Masking da9210 interrupt sources
i2c 6-0068: IRQ2 is not asserted, removing quirk
- Warm boot (reset button):
rcar_gen2_regulator_quirk: IRQ2 is not asserted, not installing quirk
Signed-off-by: Geert Uytterhoeven <geert+renesas@glider.be>
Tested-by: Wolfram Sang <wsa+renesas@sang-engineering.com>
Reviewed-by: Mark Brown <broonie@kernel.org>
Signed-off-by: Simon Horman <horms+renesas@verge.net.au>
2015-03-10 03:50:40 +08:00
|
|
|
select I2C
|
2013-12-11 22:13:52 +08:00
|
|
|
|
2013-11-06 18:40:01 +08:00
|
|
|
config ARCH_R8A7791
|
2014-08-28 16:28:09 +08:00
|
|
|
bool "R-Car M2-W (R8A77910)"
|
2014-08-25 11:03:43 +08:00
|
|
|
select ARCH_RCAR_GEN2
|
ARM: shmobile: R-Car Gen2: Add da9063/da9210 regulator quirk
The r8a7790/lager and r8a7791/koelsch development boards have da9063 and
da9210 regulators. Both regulators have their interrupt request lines
tied to the same interrupt pin (IRQ2) on the SoC.
After cold boot or da9063-induced restart, both the da9063 and da9210
seem to assert their interrupt request lines. Hence as soon as one
driver requests this irq, it gets stuck in an interrupt storm, as it
only manages to deassert its own interrupt request line, and the other
driver hasn't installed an interrupt handler yet.
To handle this, install a quirk that masks the interrupts in both the
da9063 and da9210. This quirk has to run after the i2c master driver
has been initialized, but before the i2c slave drivers are initialized.
As it depends on i2c, select I2C if one of the affected platforms is
enabled in the kernel config.
On koelsch, the following happens:
- Cold boot or reboot using the da9063 restart handler:
IRQ2 is asserted, installing da9063/da9210 regulator quirk
...
i2c i2c-6: regulator_quirk_notify: 1, IRQC_MONITOR = 0x3fb
i2c 6-0058: regulator_quirk_notify: 1, IRQC_MONITOR = 0x3fb
i2c 6-0058: Detected da9063
i2c 6-0058: Masking da9063 interrupt sources
i2c 6-0068: regulator_quirk_notify: 1, IRQC_MONITOR = 0x3fb
i2c 6-0068: Detected da9210
i2c 6-0068: Masking da9210 interrupt sources
i2c 6-0068: IRQ2 is not asserted, removing quirk
- Warm boot (reset button):
rcar_gen2_regulator_quirk: IRQ2 is not asserted, not installing quirk
Signed-off-by: Geert Uytterhoeven <geert+renesas@glider.be>
Tested-by: Wolfram Sang <wsa+renesas@sang-engineering.com>
Reviewed-by: Mark Brown <broonie@kernel.org>
Signed-off-by: Simon Horman <horms+renesas@verge.net.au>
2015-03-10 03:50:40 +08:00
|
|
|
select I2C
|
2013-11-06 18:40:01 +08:00
|
|
|
|
2015-06-01 22:22:54 +08:00
|
|
|
config ARCH_R8A7793
|
|
|
|
|
bool "R-Car M2-N (R8A7793)"
|
|
|
|
|
select ARCH_RCAR_GEN2
|
|
|
|
|
|
2014-09-04 22:02:28 +08:00
|
|
|
config ARCH_R8A7794
|
|
|
|
|
bool "R-Car E2 (R8A77940)"
|
|
|
|
|
select ARCH_RCAR_GEN2
|
2013-07-18 04:31:18 +08:00
|
|
|
|
2015-01-09 21:08:50 +08:00
|
|
|
config ARCH_SH73A0
|
|
|
|
|
bool "SH-Mobile AG5 (R8A73A00)"
|
|
|
|
|
select ARCH_RMOBILE
|
|
|
|
|
select RENESAS_INTC_IRQPIN
|
|
|
|
|
|
2013-11-29 00:27:29 +08:00
|
|
|
comment "Renesas ARM SoCs Board Type"
|
2013-11-07 07:31:25 +08:00
|
|
|
|
2014-05-15 19:32:05 +08:00
|
|
|
config MACH_MARZEN
|
|
|
|
|
bool "MARZEN board"
|
|
|
|
|
depends on ARCH_R8A7779
|
|
|
|
|
select REGULATOR_FIXED_VOLTAGE if REGULATOR
|
|
|
|
|
|
2013-11-29 00:27:29 +08:00
|
|
|
comment "Renesas ARM SoCs System Configuration"
|
2013-07-18 04:31:09 +08:00
|
|
|
endif
|
|
|
|
|
|
2013-11-09 20:33:48 +08:00
|
|
|
if ARCH_SHMOBILE_LEGACY
|
2010-02-05 19:14:49 +08:00
|
|
|
|
2013-11-29 00:27:29 +08:00
|
|
|
comment "Renesas ARM SoCs System Type"
|
2010-02-05 19:14:49 +08:00
|
|
|
|
2010-11-17 18:59:31 +08:00
|
|
|
config ARCH_SH73A0
|
|
|
|
|
bool "SH-Mobile AG5 (R8A73A00)"
|
2014-08-25 11:03:25 +08:00
|
|
|
select ARCH_RMOBILE
|
2010-11-19 15:47:16 +08:00
|
|
|
select ARCH_WANT_OPTIONAL_GPIOLIB
|
2010-11-17 18:59:31 +08:00
|
|
|
select ARM_GIC
|
2011-08-31 00:19:13 +08:00
|
|
|
select I2C
|
2014-08-20 21:39:22 +08:00
|
|
|
select SH_INTC
|
2013-02-26 11:01:09 +08:00
|
|
|
select RENESAS_INTC_IRQPIN
|
2010-11-17 18:59:31 +08:00
|
|
|
|
2011-11-11 10:45:52 +08:00
|
|
|
config ARCH_R8A7740
|
|
|
|
|
bool "R-Mobile A1 (R8A77400)"
|
2014-08-25 11:03:25 +08:00
|
|
|
select ARCH_RMOBILE
|
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 ARCH_WANT_OPTIONAL_GPIOLIB
|
2013-03-27 21:54:04 +08:00
|
|
|
select ARM_GIC
|
|
|
|
|
select RENESAS_INTC_IRQPIN
|
2011-11-11 10:45:52 +08:00
|
|
|
|
2013-03-21 18:01:36 +08:00
|
|
|
config ARCH_R8A7778
|
2013-05-09 08:05:40 +08:00
|
|
|
bool "R-Car M1A (R8A77781)"
|
2014-08-25 11:03:34 +08:00
|
|
|
select ARCH_RCAR_GEN1
|
2013-04-12 13:37:50 +08:00
|
|
|
select ARCH_WANT_OPTIONAL_GPIOLIB
|
2013-03-21 18:01:36 +08:00
|
|
|
select ARM_GIC
|
2011-11-11 10:45:52 +08:00
|
|
|
|
2011-12-14 00:36:12 +08:00
|
|
|
config ARCH_R8A7779
|
|
|
|
|
bool "R-Car H1 (R8A77790)"
|
2014-08-25 11:03:34 +08:00
|
|
|
select ARCH_RCAR_GEN1
|
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 ARCH_WANT_OPTIONAL_GPIOLIB
|
|
|
|
|
select ARM_GIC
|
2011-12-14 00:36:12 +08:00
|
|
|
|
2013-11-29 00:27:29 +08:00
|
|
|
comment "Renesas ARM SoCs Board Type"
|
2010-02-05 19:14:49 +08:00
|
|
|
|
2012-04-06 16:28:59 +08:00
|
|
|
config MACH_ARMADILLO800EVA
|
|
|
|
|
bool "Armadillo-800 EVA board"
|
|
|
|
|
depends on ARCH_R8A7740
|
|
|
|
|
select ARCH_REQUIRE_GPIOLIB
|
2012-07-05 21:17:42 +08:00
|
|
|
select REGULATOR_FIXED_VOLTAGE if REGULATOR
|
2014-01-07 14:55:49 +08:00
|
|
|
select SMSC_PHY if SH_ETH
|
2015-05-19 21:40:37 +08:00
|
|
|
select SND_SOC_WM8978 if SND_SIMPLE_CARD && I2C
|
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 USE_OF
|
2012-04-06 16:28:59 +08:00
|
|
|
|
2013-03-21 18:03:38 +08:00
|
|
|
config MACH_BOCKW
|
|
|
|
|
bool "BOCK-W platform"
|
|
|
|
|
depends on ARCH_R8A7778
|
|
|
|
|
select ARCH_REQUIRE_GPIOLIB
|
2013-07-09 17:07:13 +08:00
|
|
|
select REGULATOR_FIXED_VOLTAGE if REGULATOR
|
2013-08-26 16:52:35 +08:00
|
|
|
select SND_SOC_AK4554 if SND_SIMPLE_CARD
|
2015-05-19 21:40:37 +08:00
|
|
|
select SND_SOC_AK4642 if SND_SIMPLE_CARD && I2C
|
2014-01-07 15:40:32 +08:00
|
|
|
select USE_OF
|
2013-03-21 18:03:38 +08:00
|
|
|
|
2013-07-24 15:36:51 +08:00
|
|
|
config MACH_BOCKW_REFERENCE
|
|
|
|
|
bool "BOCK-W - Reference Device Tree Implementation"
|
|
|
|
|
depends on ARCH_R8A7778
|
|
|
|
|
select ARCH_REQUIRE_GPIOLIB
|
|
|
|
|
select REGULATOR_FIXED_VOLTAGE if REGULATOR
|
|
|
|
|
select USE_OF
|
|
|
|
|
---help---
|
|
|
|
|
Use reference implementation of BockW board support
|
|
|
|
|
which makes use of device tree at the expense
|
|
|
|
|
of not supporting a number of devices.
|
|
|
|
|
|
|
|
|
|
This is intended to aid developers
|
|
|
|
|
|
2011-12-14 00:36:12 +08:00
|
|
|
config MACH_MARZEN
|
|
|
|
|
bool "MARZEN board"
|
|
|
|
|
depends on ARCH_R8A7779
|
2011-12-14 00:36:22 +08:00
|
|
|
select ARCH_REQUIRE_GPIOLIB
|
2012-07-05 21:17:42 +08:00
|
|
|
select REGULATOR_FIXED_VOLTAGE if REGULATOR
|
2013-07-24 15:30:42 +08:00
|
|
|
select USE_OF
|
2011-12-14 00:36:12 +08:00
|
|
|
|
2012-04-11 11:57:31 +08:00
|
|
|
config MACH_KZM9G
|
|
|
|
|
bool "KZM-A9-GT board"
|
|
|
|
|
depends on ARCH_SH73A0
|
|
|
|
|
select ARCH_REQUIRE_GPIOLIB
|
2012-07-05 21:17:42 +08:00
|
|
|
select REGULATOR_FIXED_VOLTAGE if REGULATOR
|
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 SND_SOC_AK4642 if SND_SIMPLE_CARD
|
|
|
|
|
select USE_OF
|
2012-04-11 11:57:31 +08:00
|
|
|
|
2013-11-29 00:27:29 +08:00
|
|
|
comment "Renesas ARM SoCs System Configuration"
|
2010-02-05 19:14:49 +08:00
|
|
|
|
2012-01-18 01:20:23 +08:00
|
|
|
config CPU_HAS_INTEVT
|
|
|
|
|
bool
|
|
|
|
|
default y
|
|
|
|
|
|
2013-07-18 04:31:27 +08:00
|
|
|
config SH_CLK_CPG
|
|
|
|
|
bool
|
|
|
|
|
|
|
|
|
|
source "drivers/sh/Kconfig"
|
|
|
|
|
|
|
|
|
|
endif
|
|
|
|
|
|
2013-11-09 20:33:48 +08:00
|
|
|
if ARCH_SHMOBILE
|
2013-07-18 04:31:27 +08:00
|
|
|
|
2010-02-05 19:14:49 +08:00
|
|
|
menu "Timer and clock configuration"
|
|
|
|
|
|
2010-07-29 21:03:04 +08:00
|
|
|
config SHMOBILE_TIMER_HZ
|
|
|
|
|
int "Kernel HZ (jiffies per second)"
|
|
|
|
|
range 32 1024
|
|
|
|
|
default "128"
|
|
|
|
|
help
|
|
|
|
|
Allows the configuration of the timer frequency. It is customary
|
|
|
|
|
to have the timer interrupt run at 1000 Hz or 100 Hz, but in the
|
|
|
|
|
case of low timer frequencies other values may be more suitable.
|
2013-11-29 00:27:29 +08:00
|
|
|
Renesas ARM SoC systems using a 32768 Hz RCLK for clock events may
|
|
|
|
|
want to select a HZ value such as 128 that can evenly divide RCLK.
|
2010-07-29 21:03:04 +08:00
|
|
|
A HZ value that does not divide evenly may cause timer drift.
|
|
|
|
|
|
2010-02-05 19:14:49 +08:00
|
|
|
endmenu
|
|
|
|
|
|
|
|
|
|
endif
|