From: "Grant Likely" <grant.likely@secretlab.ca>
To: "Stephen Neuendorffer" <stephen.neuendorffer@xilinx.com>
Cc: linuxppc-dev@ozlabs.org, microblaze-uclinux@itee.uq.edu.au,
Wolfgang Reissnegger <wre@xilinx.com>, Leonid <Leonid@a-k-a.net>
Subject: Re: [PATCH v2] Device tree bindings for Xilinx devices
Date: Tue, 16 Oct 2007 20:31:06 -0600 [thread overview]
Message-ID: <fa686aa40710161931u51213111q6f9d54ba205e2d81@mail.gmail.com> (raw)
In-Reply-To: <20071016232404.5F4D51130091@mail133-blu.bigfish.com>
On 10/16/07, Stephen Neuendorffer <stephen.neuendorffer@xilinx.com> wrote:
>
> It occurs to me that the 'compatible' bindings should probably be the
> name of the preferred driver for the device.
>
> > + l) Xilinx ML300 Framebuffer
> > + - compatible : Must include "xilinx,ml300-fb"
> Should probably be 'xilinxfb', and probably shouldn't reference ML300 at
> all.
Actually, I don't think xilinx,ml300-fb is not specific enough (as
opposed to not general enough). Given that the device tree is
supposed to describe the hardware as uniquely as possible, compatible
should probably contain a value like "xilinx,plb-tft-cntlr-ref-1.00.c"
(<vendor>,<ip core>,<version>).
A design with a modified fb core might specify:
compatible = "acme,super-tft-1.3","xilinx,plb-tft-cntlr-ref-1.00.c";
Which indicates that it is a different part, but it provides the same
interface as the preexisting plb-tft-cntrl-ref ip core. Similarly, a
newer reference design which uses a new version of the tft core should
specifiy:
compatible =
"xilinx,plb-tft-cntrl-ref-1.00.d","xilinx,plb-tft-cntlr-ref-1.00.c";
That way the exact type of device is specified; but it is *compatible*
with the older device. If the newer device has a greater feature set,
then a driver that can match against the leftmost compatible value can
make use of the extra features.
>
> > + n) Xilinx EMAC and Xilinx TEMAC
> > +
> > + Xilinx Ethernet devices. Uses common properties from
> > other Ethernet
> > + devices with the following constraints:
> > +
> > + Required properties:
> > + - compatible : Must include one of: "xilinx,plb-temac",
> > + "xilinx,plb-emac", "xilinx-opb-emac"
> Should probably be just 'emac' and 'temac'.
Actually; looking at the available ip cores; it should probably be:
"xilinx,opb-ethernet-1.02.a" for an emac driver
"xilinx,plb-temac-3.00.a" for a temac.
We should probably use the exact names of the ip core. Less ambiguity that way.
Cheers,
g.
--
Grant Likely, B.Sc., P.Eng.
Secret Lab Technologies Ltd.
grant.likely@secretlab.ca
(403) 399-0195
prev parent reply other threads:[~2007-10-17 2:31 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-10-15 15:53 [PATCH v2] Device tree bindings for Xilinx devices Grant Likely
2007-10-15 19:21 ` Arnd Bergmann
2007-10-15 19:54 ` Grant Likely
2007-10-16 18:24 ` Stephen Neuendorffer
2007-10-16 19:36 ` Grant Likely
2007-10-17 0:21 ` Stephen Neuendorffer
2007-10-17 2:35 ` Grant Likely
2007-10-17 3:03 ` Grant Likely
2007-10-16 23:23 ` Stephen Neuendorffer
2007-10-17 1:49 ` Josh Boyer
2007-10-17 2:31 ` Grant Likely [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=fa686aa40710161931u51213111q6f9d54ba205e2d81@mail.gmail.com \
--to=grant.likely@secretlab.ca \
--cc=Leonid@a-k-a.net \
--cc=linuxppc-dev@ozlabs.org \
--cc=microblaze-uclinux@itee.uq.edu.au \
--cc=stephen.neuendorffer@xilinx.com \
--cc=wre@xilinx.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 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).