All of lore.kernel.org
 help / color / mirror / Atom feed
From: Koen Martens <linuxarm@metro.cx>
To: Ben Dooks <ben-linux-arm@fluff.org>
Cc: linux-arm-kernel@lists.arm.linux.org.uk, ben@simtec.co.uk,
	linux-kernel@vger.kernel.org
Subject: Re: [patch] s3c2412 support
Date: Fri, 03 Mar 2006 11:34:53 +0100	[thread overview]
Message-ID: <44081BCD.3040502@metro.cx> (raw)
In-Reply-To: <20060301091035.GB26072@trinity.fluff.org>

Ben Dooks wrote:

>It would help to split these emails into smaller chunks than all the files
>so that comments could be with the chunks that it goes with.
>  
>
All right, i'll repost in a minute..

>Makefile.diff	- going to have to remove those #s at somepoint
>  
>
True, but i can't submit those as long as i use tomtom specific cpu-type 
registers (see reply to other post later today).

>regs-clock.diff - didn't need to add s3c2412_get_pll, same as s3c2410_get_pll 
>  
>
Hmm, i disagree.. The term (mdiv+8) is multiplied by 2 for s3c2412, this 
is not the case for s3c2410..
I changed it to use the 64 bit arithmetic like s3c2410_get_pll and 
you'll notice the difference is this line:

+       fvco = (uint64_t)baseclk * ((mdiv + 8)<<1);

Maybe it is better to use one get_pll and add an extra parameter to 
indicate the multiplication of (mdiv+8) ?

>regs-gpio.diff	- group the s3c2412 changes together into larger #ifdefs
>  
>
Done.

>regs-rtc.diff	- two sets of changes here? 2410 and 2412 additions
>  
>
Ok, cleaned that up..

>cpu.diff:
>
>the 2412 is an ARM926EJS, so I'd expect the core-ID accessed
>via the co-processor registers to be diffeernt, so this could give
>the indication of what sort of CPU to try.
>
>this also seems to have the S3C2442 ID patch from the patch-q in it,
>please be careful about merging patches like that.
>  
>
Ok, cleaned that up a bit too.. As for the core-ID remark, i will try 
and have a look at it today, but as it is my last day at this firm today 
i can't make any guarantees. Maybe Dimitry Andric will pick this up when 
i'm gone..

Best,

Koen

-- 
K.F.J. Martens, Sonologic, http://www.sonologic.nl/
Networking, hosting, embedded systems, unix, artificial intelligence.
Public PGP key: http://www.metro.cx/pubkey-gmc.asc
Wondering about the funny attachment your mail program
can't read? Visit http://www.openpgp.org/


  reply	other threads:[~2006-03-03 10:36 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-02-28 14:18 [patch] s3c2412 support Koen Martens
2006-03-01  9:10 ` Ben Dooks
2006-03-03 10:34   ` Koen Martens [this message]
  -- strict thread matches above, loose matches on Subject: below --
2006-02-28 14:16 Koen Martens

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=44081BCD.3040502@metro.cx \
    --to=linuxarm@metro.cx \
    --cc=ben-linux-arm@fluff.org \
    --cc=ben@simtec.co.uk \
    --cc=linux-arm-kernel@lists.arm.linux.org.uk \
    --cc=linux-kernel@vger.kernel.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.