From: Greg Ungerer <gregungerer00@gmail.com>
To: Daniel Palmer <danieruru@gmail.com>, linux-m68k@lists.linux-m68k.org
Subject: Re: [PATCH 1/2] Add correct PLL settings for DragonBall VZ.
Date: Thu, 03 Apr 2014 22:41:51 +1000 [thread overview]
Message-ID: <533D570F.8080000@gmail.com> (raw)
In-Reply-To: <1396449792-5121-1-git-send-email-danieruru@gmail.com>
Hi Daniel,
Looks good, nice and small, a single fix.
Can I suggest that you add an arch name to the patch title, so:
[PATCH 1/2] m68k: Add correct PLL settings for DragonBall VZ
Obviously on this email list we know it is for m68k, but when merged
up stream it makes it much easier from the title to know what it
applies to.
On 03/04/14 00:43, Daniel Palmer wrote:
> Signed-off-by: Daniel Palmer <danieruru@gmail.com>
> ---
> arch/m68k/platform/68000/head.S | 8 +++++++-
> 1 file changed, 7 insertions(+), 1 deletion(-)
>
> diff --git a/arch/m68k/platform/68000/head.S b/arch/m68k/platform/68000/head.S
> index 536ef96..0d00489 100644
> --- a/arch/m68k/platform/68000/head.S
> +++ b/arch/m68k/platform/68000/head.S
> @@ -91,12 +91,18 @@ _start:
> movew #0xe100, 0xfffff900 /* enable */
> #endif /* DEBUG_HEAD */
>
> -#ifdef CONFIG_PILOT
> +#if defined(CONFIG_PILOT)
> movew #0x2410, 0xfffff200 /* PLLCR */
> +#elif defined(CONFIG_M68VZ328)
> + movew #0x2493, 0xfffff200 /* PLLCR */
Would it be cleaner to have a defined value here instead?
This moves the #ifdef'ery to just the PLLCR value, and keeps the
code instructions here cleaner. So something like this at the top of
this head.S:
#if defined(CONFIG_PILOT)
#define PLLCR 0x2410
#elif defined(CONFIG_M68VZ328)
#define PLLCR 0x2493
#else
#define PLLCR 0x2400
#endif
and then just
movew #PLLCR, 0xfffff200 /* PLLCR */
Regards
Greg
> #else
> movew #0x2400, 0xfffff200 /* PLLCR */
> #endif
> +#if defined(CONFIG_M68VZ328)
> + movew #0x0347, 0xfffff202 /* PLLFSR */
> +#else
> movew #0x0123, 0xfffff202 /* PLLFSR */
> +#endif
> moveq #0, %d0
> movew #16384, %d0 /* PLL settle wait loop */
> _pll_settle:
>
next prev parent reply other threads:[~2014-04-03 12:41 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-04-02 14:43 [PATCH 1/2] Add correct PLL settings for DragonBall VZ Daniel Palmer
2014-04-02 14:43 ` [PATCH 2/2] Fix mach_sched_init for EZ and VZ DragonBall chips Daniel Palmer
2014-04-03 12:45 ` Greg Ungerer
2014-04-03 12:41 ` Greg Ungerer [this message]
2014-04-03 12:48 ` [PATCH 1/2] Add correct PLL settings for DragonBall VZ Geert Uytterhoeven
2014-04-04 3:18 ` Daniel Palmer
2014-04-04 8:16 ` Finn Thain
2014-04-04 13:42 ` Greg Ungerer
2014-04-04 7:45 ` Finn Thain
2014-04-04 13:35 ` Greg Ungerer
2014-04-05 8:46 ` Finn Thain
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=533D570F.8080000@gmail.com \
--to=gregungerer00@gmail.com \
--cc=danieruru@gmail.com \
--cc=linux-m68k@lists.linux-m68k.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