linuxppc-dev.lists.ozlabs.org archive mirror
 help / color / mirror / Atom feed
From: Clemens Koller <clemens.koller@anagramm.de>
To: Kumar Gala <kumar.gala@freescale.com>
Cc: ppcembed Mailing List <linuxppc-embedded@ozlabs.org>
Subject: Re: [PATCH] ppc32: Register definition for MPC85xx
Date: Tue, 19 Jul 2005 15:40:05 +0200	[thread overview]
Message-ID: <42DD02B5.4090604@anagramm.de> (raw)
In-Reply-To: <B6B4D7F0-2E8B-4779-95C5-6F8993C6D6A9@freescale.com>

Hello, Kumar,

> This isn't going to get into the kernel tree.  I'm against putting  full 
> register definitions in like this because they are too difficult  to 
> maintain properly.  We currently have some 14 different 85xx  devices 
> today and the number is only going to grow larger.

Okay, no problem.

I experienced that it is definitely difficult to maintain if there are lot of
changes/patches which can corrupt the whole set if only one register
is misaligned. Once a set it's completed for a device, it could be nailed down
to a specific device by specifying a filename like immap_mpc8540.h

And... it doesn't necessarily stay within the kernel tree... maybe Freescale
can put out those files on their website for reference?

Best greets,

Clemens Koller

Kumar Gala wrote:
> Clemens,
> 
> This isn't going to get into the kernel tree.  I'm against putting  full 
> register definitions in like this because they are too difficult  to 
> maintain properly.  We currently have some 14 different 85xx  devices 
> today and the number is only going to grow larger.
> 
> If and when you need something specific in the immap_85xx please  
> provide it as a patch along with the driver that you want in.  For  
> certain devices like PCI, LBC, etc I've got no issue adding info into  
> immap_85xx.  However, for devices like DUART, I2C, TSEC, etc I'm  
> completely against the idea of having their register definitions in  
> immap_85xx.
> 
> - kumar
> 
> On Jul 19, 2005, at 5:01 AM, Clemens Koller wrote:
> 
>> Hello!
>>
>> I suggest to put the register definitions into the Kernel _before_
>> more driver writers start using their own / different maps.
>>
>> Greets,
>>
>> Clemens Koller
>>
>> ---
>> Almost complete and verified register map for the MPC85xx.
>> Based on sources from Jason McMullan and the MPC8540 Reference Manual.
>>
>> Signed-off-by: Clemens Koller <clemens.koller@anagramm.de>
>>
>>
>> <immap_85xx-register-update.patch>
>> <ATT1082226.txt>
>>
> 
> 

      reply	other threads:[~2005-07-19 13:40 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-07-19 10:01 [PATCH] ppc32: Register definition for MPC85xx Clemens Koller
2005-07-19 12:27 ` Kumar Gala
2005-07-19 13:40   ` Clemens Koller [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=42DD02B5.4090604@anagramm.de \
    --to=clemens.koller@anagramm.de \
    --cc=kumar.gala@freescale.com \
    --cc=linuxppc-embedded@ozlabs.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).