From: kristoffer.ericson@gmail.com (Kristoffer Ericson)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH 2/2] SA1100: add processor check to sa1110-cpufreq driver
Date: Thu, 22 Apr 2010 11:26:29 +0200 [thread overview]
Message-ID: <20100422112629.c42e69af.kristoffer.ericson@gmail.com> (raw)
In-Reply-To: <1271875749-2891-3-git-send-email-mad_soft@inbox.ru>
Acked-by: Kristoffer Ericson <kristoffer.ericson@gmail.com>
On Wed, 21 Apr 2010 22:49:09 +0400
Dmitry Artamonow <mad_soft@inbox.ru> wrote:
> Just to make sure that this driver won't run on StrongArm SA1100
> when both SA1100 and SA1110 cpufreq drivers are built in (usually
> in multimachine config). SA1100 driver already has similar check.
>
> Signed-off-by: Dmitry Artamonow <mad_soft@inbox.ru>
> ---
> arch/arm/mach-sa1100/cpu-sa1110.c | 3 +++
> 1 files changed, 3 insertions(+), 0 deletions(-)
>
> diff --git a/arch/arm/mach-sa1100/cpu-sa1110.c b/arch/arm/mach-sa1100/cpu-sa1110.c
> index 63b32b6..7252874 100644
> --- a/arch/arm/mach-sa1100/cpu-sa1110.c
> +++ b/arch/arm/mach-sa1100/cpu-sa1110.c
> @@ -363,6 +363,9 @@ static int __init sa1110_clk_init(void)
> struct sdram_params *sdram;
> const char *name = sdram_name;
>
> + if (!cpu_is_sa1110())
> + return -ENODEV;
> +
> if (!name[0]) {
> if (machine_is_assabet())
> name = "TC59SM716-CL3";
> --
> 1.7.0.4
>
--
Kristoffer Ericson <kristoffer.ericson@gmail.com>
prev parent reply other threads:[~2010-04-22 9:26 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-04-21 18:49 [PATCH 0/2] Couple of SA11x0 cpufreq fixes Dmitry Artamonow
2010-04-21 18:49 ` [PATCH 1/2] SA1100: fix wrong CPU type for h3100 and h3600 Dmitry Artamonow
2010-04-21 22:10 ` Eric Miao
2010-04-22 9:27 ` Kristoffer Ericson
2010-04-21 18:49 ` [PATCH 2/2] SA1100: add processor check to sa1110-cpufreq driver Dmitry Artamonow
2010-04-21 22:11 ` Eric Miao
2010-04-22 9:26 ` Kristoffer Ericson [this message]
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=20100422112629.c42e69af.kristoffer.ericson@gmail.com \
--to=kristoffer.ericson@gmail.com \
--cc=linux-arm-kernel@lists.infradead.org \
/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).