From: "Andrew Jeffery" <andrew@aj.id.au>
To: "Joel Stanley" <joel@jms.id.au>,
"Rob Herring" <robh+dt@kernel.org>,
"Arnd Bergmann" <arnd@arndb.de>,
"Olof Johansson" <olof@lixom.net>
Cc: "Mark Rutland" <mark.rutland@arm.com>,
devicetree@vger.kernel.org,
"Ryan Chen" <ryan_chen@aspeedtech.com>,
linux-aspeed@lists.ozlabs.org, "Cédric Le Goater" <clg@kaod.org>,
linux-arm-kernel@lists.infradead.org
Subject: Re: [PATCH 2/7] ARM: aspeed: Select timer in each SoC
Date: Thu, 22 Aug 2019 10:57:22 +0930 [thread overview]
Message-ID: <0e9c483f-4f12-45a4-8d2c-1aa3ae34fa7a@www.fastmail.com> (raw)
In-Reply-To: <20190821055530.8720-3-joel@jms.id.au>
On Wed, 21 Aug 2019, at 15:26, Joel Stanley wrote:
> In preparation for adding the ast2600 which does not use this timer.
>
> Signed-off-by: Joel Stanley <joel@jms.id.au>
Reviewed-by: Andrew Jeffery <andrew@aj.id.au>
> ---
> arch/arm/mach-aspeed/Kconfig | 3 ++-
> 1 file changed, 2 insertions(+), 1 deletion(-)
>
> diff --git a/arch/arm/mach-aspeed/Kconfig b/arch/arm/mach-aspeed/Kconfig
> index a15c3a291386..2979aa4daeea 100644
> --- a/arch/arm/mach-aspeed/Kconfig
> +++ b/arch/arm/mach-aspeed/Kconfig
> @@ -5,7 +5,6 @@ menuconfig ARCH_ASPEED
> select SRAM
> select WATCHDOG
> select ASPEED_WATCHDOG
> - select FTTMR010_TIMER
> select MFD_SYSCON
> select PINCTRL
> help
> @@ -18,6 +17,7 @@ config MACH_ASPEED_G4
> depends on ARCH_MULTI_V5
> select CPU_ARM926T
> select PINCTRL_ASPEED_G4
> + select FTTMR010_TIMER
> help
> Say yes if you intend to run on an Aspeed ast2400 or similar
> fourth generation BMCs, such as those used by OpenPower Power8
> @@ -28,6 +28,7 @@ config MACH_ASPEED_G5
> depends on ARCH_MULTI_V6
> select CPU_V6
> select PINCTRL_ASPEED_G5
> + select FTTMR010_TIMER
> help
> Say yes if you intend to run on an Aspeed ast2500 or similar
> fifth generation Aspeed BMCs.
> --
> 2.23.0.rc1
>
>
_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel
next prev parent reply other threads:[~2019-08-22 1:27 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-08-21 5:55 [PATCH 0/7] ARM: Add ASPEED AST2600 support Joel Stanley
2019-08-21 5:55 ` [PATCH 1/7] dt-bindings: arm: cpus: Add ASPEED SMP Joel Stanley
2019-08-21 16:23 ` Rob Herring
2019-08-22 2:08 ` Andrew Jeffery
2019-08-21 5:55 ` [PATCH 2/7] ARM: aspeed: Select timer in each SoC Joel Stanley
2019-08-22 1:27 ` Andrew Jeffery [this message]
2019-08-21 5:55 ` [PATCH 3/7] ARM: aspeed: Add ASPEED AST2600 architecture Joel Stanley
2019-08-22 1:28 ` Andrew Jeffery
2019-08-21 5:55 ` [PATCH 4/7] ARM: aspeed: Enable SMP boot Joel Stanley
2019-08-21 5:55 ` [PATCH 5/7] ARM: dts: aspeed: Add AST2600 and EVB Joel Stanley
2019-08-22 1:58 ` Andrew Jeffery
2019-08-21 5:55 ` [PATCH 6/7] ARM: configs: multi_v7: Add ASPEED G6 Joel Stanley
2019-08-22 2:04 ` Andrew Jeffery
2019-08-21 5:55 ` [PATCH 7/7] ARM: configs: aspeed_g5: Enable AST2600 Joel Stanley
2019-08-22 2:07 ` Andrew Jeffery
2019-08-22 4:43 ` Joel Stanley
2019-08-27 20:12 ` Arnd Bergmann
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=0e9c483f-4f12-45a4-8d2c-1aa3ae34fa7a@www.fastmail.com \
--to=andrew@aj.id.au \
--cc=arnd@arndb.de \
--cc=clg@kaod.org \
--cc=devicetree@vger.kernel.org \
--cc=joel@jms.id.au \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-aspeed@lists.ozlabs.org \
--cc=mark.rutland@arm.com \
--cc=olof@lixom.net \
--cc=robh+dt@kernel.org \
--cc=ryan_chen@aspeedtech.com \
/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;
as well as URLs for NNTP newsgroup(s).