public inbox for linux-arm-kernel@lists.infradead.org
 help / color / mirror / Atom feed
From: ryan@bluewatersys.com (Ryan Mallon)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH] ep93xx: define magic numbers for pll1 and pll2
Date: Tue, 12 Jan 2010 08:43:42 +1300	[thread overview]
Message-ID: <4B4B7F6E.5010304@bluewatersys.com> (raw)
In-Reply-To: <BD79186B4FD85F4B8E60E381CAEE190902089912@mi8nycmail19.Mi8.com>

H Hartley Sweeten wrote:
> On Sunday, January 10, 2010 6:06 PM, Ryan Mallon wrote:
>> H Hartley Sweeten wrote:
>>> Add defines for the pll register magic numbers that determine if
>>> the pll's are bypassed and if pll2 is enabled.  Rename the clock
>>> set registers to more closely match the datasheet.  Also, remove
>>> the unnecessary braces since each conditional statement is a single
>>> statement.
>>>
>>> Signed-off-by: H Hartley Sweeten <hsweeten@visionengravers.com>
>>> Cc: Ryan Mallon <ryan@bluewatersys.com>
>>>
>>> ---
>>>
> 
> [snip]
>  
>>> diff --git a/arch/arm/mach-ep93xx/include/mach/ep93xx-regs.h b/arch/arm/mach-ep93xx/include/mach/ep93xx-regs.h
>>> index d55194a..cd35912 100644
>>> --- a/arch/arm/mach-ep93xx/include/mach/ep93xx-regs.h
>>> +++ b/arch/arm/mach-ep93xx/include/mach/ep93xx-regs.h
>>> @@ -167,8 +167,11 @@
>>>  #define EP93XX_SYSCON_PWRCNT_DMA_M2P1	(1<<16)
>>>  #define EP93XX_SYSCON_HALT		EP93XX_SYSCON_REG(0x08)
>>>  #define EP93XX_SYSCON_STANDBY		EP93XX_SYSCON_REG(0x0c)
>>> -#define EP93XX_SYSCON_CLOCK_SET1	EP93XX_SYSCON_REG(0x20)
>>> -#define EP93XX_SYSCON_CLOCK_SET2	EP93XX_SYSCON_REG(0x24)
>>> +#define EP93XX_SYSCON_CLKSET1		EP93XX_SYSCON_REG(0x20)
>>> +#define EP93XX_SYSCON_CLKSET1_NBYP1	(1<<23)
>>> +#define EP93XX_SYSCON_CLKSET2		EP93XX_SYSCON_REG(0x24)
>>> +#define EP93XX_SYSCON_CLKSET2_NBYP2	(1<<19)
>>> +#define EP93XX_SYSCON_CLKSET2_PLL2_EN	(1<<18)
>>>  #define EP93XX_SYSCON_DEVCFG		EP93XX_SYSCON_REG(0x80)
>>>  #define EP93XX_SYSCON_DEVCFG_SWRST	(1<<31)
>>>  #define EP93XX_SYSCON_DEVCFG_D1ONG	(1<<30) 
>> Looks okay. If the clock registers are only ever used inside clock.c
>> should we move them there to cut down the size of ep93xx-regs.h?
> 
> For right now I would like to keep all the 'SYSCON' defines in the header.
> All of the other peripherals have a specific driver that it makes sense to
> move the register defines into and then access them using the offset from
> the base address.  The SysCon registers are a bit unique in that many
> subsystems need access for various reasons.
> 
> Eventually a lot of them can be moved into clock.c but for right now
> lets just leave them in the header.

Fair enough. We can look at this at some point in the future.

> Is that an Acked-by?

Yup.

Acked-by: Ryan Mallon <ryan@bluewatersys.com>

-- 
Bluewater Systems Ltd - ARM Technology Solution Centre

Ryan Mallon         		5 Amuri Park, 404 Barbadoes St
ryan at bluewatersys.com         	PO Box 13 889, Christchurch 8013
http://www.bluewatersys.com	New Zealand
Phone: +64 3 3779127		Freecall: Australia 1800 148 751
Fax:   +64 3 3779135			  USA 1800 261 2934

  reply	other threads:[~2010-01-11 19:43 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-12-30 16:56 [PATCH] ep93xx: define magic numbers for pll1 and pll2 H Hartley Sweeten
2010-01-11  1:05 ` Ryan Mallon
2010-01-11 18:31   ` H Hartley Sweeten
2010-01-11 19:43     ` Ryan Mallon [this message]
2010-01-11 20:43       ` H Hartley Sweeten

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=4B4B7F6E.5010304@bluewatersys.com \
    --to=ryan@bluewatersys.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