mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: John Williams <john.williams@petalogix.com>
To: Grant Likely <grant.likely@secretlab.ca>
Cc: Linux Kernel list <linux-kernel@vger.kernel.org>,
	Michal Simek <michal.simek@petalogix.com>,
	John Linn <John.Linn@xilinx.com>,
	David DeBonis <ddeboni@xilinx.com>,
	Stephen Neuendorffer <stephen.neuendorffer@xilinx.com>,
	devicetree-discuss <devicetree-discuss@lists.ozlabs.org>
Subject: Re: Xilinx SYSACE driver and 8-bit attachment
Date: Thu, 8 Oct 2009 09:44:43 +1000	[thread overview]
Message-ID: <1d3f23370910071644y5877cf9v879967340a463f19@mail.gmail.com> (raw)
In-Reply-To: <fa686aa40910070634r4a8dcf74qdcbfb3bde3413109@mail.gmail.com>

On Wed, Oct 7, 2009 at 11:34 PM, Grant Likely <grant.likely@secretlab.ca> wrote:
> [Added devicetree-discuss to cc: list]
>
> On Wed, Oct 7, 2009 at 1:13 AM, John Williams
> <john.williams@petalogix.com> 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

How did I know you'd say that? :)

> 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

I tend to agree - but I also tend think that putting funky, arbitrary
output strings in the DTS generator is also a bad idea.

In this case, my vote is leaning towards adding a test for
"xlnx,mem-width = <..>" to the driver, in addition to the existing
"8-bit" tag to keep back compatability.

How would you feel about that?

In future, for new Xilinx drivers I think the default binding should
be inspired by what comes from the DTS generator automatically, with
out any special per-device hacks.  This has a natural tendency towards
minimum pain I think.

John
-- 
John Williams, PhD, B.Eng, B.IT
PetaLogix - Linux Solutions for a Reconfigurable World
w: www.petalogix.com  p: +61-7-30090663  f: +61-7-30090663

  parent reply	other threads:[~2009-10-07 23:45 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-10-07  7:13 John Williams
2009-10-07 13:34 ` Grant Likely
2009-10-07 14:24   ` John Linn
2009-10-07 23:41     ` John Williams
2009-10-07 23:44       ` John Linn
2009-10-07 23:46         ` John Williams
2009-10-07 14:42   ` John Linn
2009-10-07 14:52     ` Grant Likely
2009-10-07 16:18       ` Stephen Neuendorffer
2009-10-07 23:44   ` John Williams [this message]
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=1d3f23370910071644y5877cf9v879967340a463f19@mail.gmail.com \
    --to=john.williams@petalogix.com \
    --cc=John.Linn@xilinx.com \
    --cc=ddeboni@xilinx.com \
    --cc=devicetree-discuss@lists.ozlabs.org \
    --cc=grant.likely@secretlab.ca \
    --cc=linux-kernel@vger.kernel.org \
    --cc=michal.simek@petalogix.com \
    --cc=stephen.neuendorffer@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

all inboxes | Powered by JetHome®