From: Grant Likely <grant.likely-s3s/WqlpOiPyB63q8FvJNQ@public.gmane.org>
To: John Williams <john.williams-g5w7nrANp4BDPfheJLI6IQ@public.gmane.org>
Cc: David DeBonis <ddeboni-gjFFaj9aHVfQT0dZR+AlfA@public.gmane.org>,
Linux Kernel list
<linux-kernel-u79uwXL29TY76Z2rM5mHXA@public.gmane.org>,
Michal Simek
<michal.simek-g5w7nrANp4BDPfheJLI6IQ@public.gmane.org>,
devicetree-discuss
<devicetree-discuss-uLR06cmDAlY/bJ5BZ2RsiQ@public.gmane.org>
Subject: Re: Xilinx SYSACE driver and 8-bit attachment
Date: Wed, 7 Oct 2009 07:34:45 -0600 [thread overview]
Message-ID: <fa686aa40910070634r4a8dcf74qdcbfb3bde3413109@mail.gmail.com> (raw)
In-Reply-To: <1d3f23370910070013u6307bc42hf7ab243b52d007df-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
[Added devicetree-discuss to cc: list]
On Wed, Oct 7, 2009 at 1:13 AM, John Williams
<john.williams-g5w7nrANp4BDPfheJLI6IQ@public.gmane.org> wrote:
> Hi Grant (it's your driver :) and David D ( and your DTS generator :)
[...]
> if (of_find_property(op->node, "8-bit", NULL))
[...]
> doesn't match the properties generated by Xilinx's device tree generator:
[...]
> xlnx,mem-width = <0x8>;
>
> So, the question is, which should change?
Well, obviously its a device tree generator bug, the driver code is
perfect. :-P
In all seriousness though, the '8-bit' property has been present for a
while now and needs to be retained to not break existing users. It
would be okay for the driver to be modified to *also* check for the
xlnx,mem-width property, but the better solution is to modify the
device tree generator. Plus, the '8-bit' property is the documented
binding in Documentation/powerpc/dts-bindings/xilinx.txt
Cheers,
g.
--
Grant Likely, B.Sc., P.Eng.
Secret Lab Technologies Ltd.
next parent reply other threads:[~2009-10-07 13:34 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <1d3f23370910070013u6307bc42hf7ab243b52d007df@mail.gmail.com>
[not found] ` <1d3f23370910070013u6307bc42hf7ab243b52d007df-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2009-10-07 13:34 ` Grant Likely [this message]
2009-10-07 14:24 ` Xilinx SYSACE driver and 8-bit attachment John Linn
[not found] ` <838c3c32-27d9-4a0a-a197-c7227b911942-+Ck8Kgl/v0/UuUXyfqFqSbjjLBE8jN/0@public.gmane.org>
2009-10-07 23:41 ` John Williams
[not found] ` <1d3f23370910071641s75b2d217h71a839b1a0b4013c-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2009-10-07 23:44 ` John Linn
[not found] ` <7a2a686d-ddf4-4a42-8c73-c933cebf22a4-+Ck8Kgl/v09Eus+KprP3J7jjLBE8jN/0@public.gmane.org>
2009-10-07 23:46 ` John Williams
2009-10-07 14:42 ` John Linn
[not found] ` <192797ad-5dd4-4ebe-8db3-d381bb949e1e-+Ck8Kgl/v09YkiQOvaGFS7jjLBE8jN/0@public.gmane.org>
2009-10-07 14:52 ` Grant Likely
2009-10-07 16:18 ` Stephen Neuendorffer
[not found] ` <fa686aa40910070634r4a8dcf74qdcbfb3bde3413109-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2009-10-07 23:44 ` John Williams
[not found] ` <1d3f23370910071644y5877cf9v879967340a463f19-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2009-10-07 23:47 ` John Linn
2009-10-07 23:48 ` Stephen Neuendorffer
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=fa686aa40910070634r4a8dcf74qdcbfb3bde3413109@mail.gmail.com \
--to=grant.likely-s3s/wqlpoipyb63q8fvjnq@public.gmane.org \
--cc=ddeboni-gjFFaj9aHVfQT0dZR+AlfA@public.gmane.org \
--cc=devicetree-discuss-uLR06cmDAlY/bJ5BZ2RsiQ@public.gmane.org \
--cc=john.williams-g5w7nrANp4BDPfheJLI6IQ@public.gmane.org \
--cc=linux-kernel-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
--cc=michal.simek-g5w7nrANp4BDPfheJLI6IQ@public.gmane.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