From: Segher Boessenkool <segher@kernel.crashing.org>
To: Matt Sealey <matt@genesi-usa.com>
Cc: linuxppc-dev list <linuxppc-dev@ozlabs.org>
Subject: Re: New fsl device bindings file
Date: Sat, 5 Jul 2008 01:12:31 +0200 [thread overview]
Message-ID: <e88aa775e8f6dcc85f1e4b9c3ca28fdd@kernel.crashing.org> (raw)
In-Reply-To: <486E26C0.9060604@genesi-usa.com>
>> /* deprecated; */
>> device_type =3D "i2c";
>
> How about "deprecated but kept for compatibility with true Open=20
> Firmware
> implementations"?
Well, except a flat tree isn't compatible with OF at all here.
A "device_type" promises a certain interface; a flat tree doesn't
even have the "open" method. =46rom the OF base spec:
=93device_type=94 S
Standard property name to specify the implemented interface.
prop-encoded-array: Text string encoded with encode-string.
Specifies the =93device type=94 of this package, thus implying a
specific set of package class methods implemented by this
package.
> Seriously, you can't have a binding for "OF" and then cut out that=20
> part of the
> standard at a whim.
Nothing is cut out. There never was a device binding for device_type
i2c; creating one would be a considerable effort, and since flat tree
users wouldn't use it anyway, you can't be seriously suggesting they
should do this.
> It should be there (at least for those parts which are
> governed by a client interface API, like display, serial etc.
Huh? Nothing in the client interface mentions display or serial
as far as I know.
> but cutting it off takes away all it's meaning,
So what? There _is_ no "real" device interface, when a flat tree is
used.
> plus Linux implementations STILL keep searching
> that property along with "compatible",
That's a bug.
Segher
next prev parent reply other threads:[~2008-07-04 23:12 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-07-03 18:20 New fsl device bindings file Kumar Gala
2008-07-03 18:28 ` Scott Wood
2008-07-03 18:34 ` Grant Likely
2008-07-03 18:38 ` Kumar Gala
2008-07-04 4:26 ` Grant Likely
2008-07-05 5:24 ` Olof Johansson
2008-07-07 1:39 ` David Gibson
2008-07-07 1:45 ` Olof Johansson
2008-07-07 15:28 ` Kumar Gala
2008-07-03 18:36 ` Kumar Gala
2008-07-05 11:34 ` Jochen Friedrich
2008-07-03 18:53 ` Anton Vorontsov
2008-07-03 23:36 ` Paul Mackerras
2008-07-04 13:33 ` Matt Sealey
2008-07-04 23:12 ` Segher Boessenkool [this message]
2008-07-05 1:26 ` David Gibson
2008-07-05 6:53 ` Grant Likely
2008-07-04 22:59 ` Segher Boessenkool
2008-07-04 23:14 ` Segher Boessenkool
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=e88aa775e8f6dcc85f1e4b9c3ca28fdd@kernel.crashing.org \
--to=segher@kernel.crashing.org \
--cc=linuxppc-dev@ozlabs.org \
--cc=matt@genesi-usa.com \
/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.