public inbox for linuxppc-dev@ozlabs.org 
 help / color / mirror / Atom feed
From: Segher Boessenkool <segher@kernel•crashing.org>
To: David Gibson <david@gibson•dropbear.id.au>
Cc: linuxppc-dev@ozlabs•org, Stefan Roese <sr@denx•de>,
	Paul Mackerras <paulus@samba•org>
Subject: Re: Small fixes for the Ebony device tree
Date: Tue, 15 May 2007 08:47:00 +0200	[thread overview]
Message-ID: <5c785f662c13fdd938d48e40d3107050@kernel.crashing.org> (raw)
In-Reply-To: <20070515063408.GE6998@localhost.localdomain>

>>> finally "ibm,sdram-4xx".
>>
>> Is that last entry ever useful?  Do all those controllers
>> have something in common?
>
> A quick glance over the descriptions in the 440GP and 405GP user
> manuals suggests that they have most of the registers in common,
> though I haven't checked to see if the semantics of those registers
> are actually all the same.

Let me rephrase: can a kernel driver ever do anything
useful with the device if it _only_ knows it is some
4xx memory controller?

If that isn't the case, but for example, the 440GP's
controller can be driven by the 405GP driver, you
can express exactly that in the "compatible" property.
It is a bad plan in general to say "4xx", it suggests
compatibility both ways, which almost never is true;
so what _does_ it mean?  Lowest common denominator?
Say exactly that, then.  "compatible" is meant for
drivers to figure if they can drive the device (or,
equivalently, for the kernel to figure out which driver
can drive a given device).


Segher

  reply	other threads:[~2007-05-15  6:47 UTC|newest]

Thread overview: 24+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-05-15  2:00 Small fixes for the Ebony device tree David Gibson
2007-05-15  5:11 ` Segher Boessenkool
2007-05-15  5:47   ` David Gibson
2007-05-15  6:11     ` Stefan Roese
2007-05-15  6:18       ` David Gibson
2007-05-15  6:28         ` Segher Boessenkool
2007-05-15  6:34           ` David Gibson
2007-05-15  6:47             ` Segher Boessenkool [this message]
2007-05-15  6:58               ` David Gibson
2007-05-15  7:07                 ` Segher Boessenkool
2007-05-16  3:47                   ` David Gibson
2007-05-15  6:46         ` Stefan Roese
2007-05-15  7:02           ` Segher Boessenkool
  -- strict thread matches above, loose matches on Subject: below --
2007-05-16  3:48 David Gibson
2007-05-16 13:35 ` Segher Boessenkool
2007-05-14  4:54 David Gibson
2007-05-14 12:22 ` Josh Boyer
2007-05-14 12:59 ` Segher Boessenkool
2007-05-14 15:09   ` Josh Boyer
2007-05-15  1:17   ` David Gibson
2007-05-15  4:59     ` Segher Boessenkool
2007-05-15  5:46       ` David Gibson
2007-05-16  3:47         ` David Gibson
2007-05-15 18:15 ` Mark A. Greer

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=5c785f662c13fdd938d48e40d3107050@kernel.crashing.org \
    --to=segher@kernel$(echo .)crashing.org \
    --cc=david@gibson$(echo .)dropbear.id.au \
    --cc=linuxppc-dev@ozlabs$(echo .)org \
    --cc=paulus@samba$(echo .)org \
    --cc=sr@denx$(echo .)de \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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