From: John Williams <john.williams@petalogix.com>
To: Linux Kernel list <linux-kernel@vger.kernel.org>
Cc: Grant Likely <grant.likely@secretlab.ca>,
Michal Simek <michal.simek@petalogix.com>,
John Linn <John.Linn@xilinx.com>,
David DeBonis <ddeboni@xilinx.com>,
Stephen Neuendorffer <stephen.neuendorffer@xilinx.com>
Subject: Xilinx SYSACE driver and 8-bit attachment
Date: Wed, 7 Oct 2009 17:13:22 +1000 [thread overview]
Message-ID: <1d3f23370910070013u6307bc42hf7ab243b52d007df@mail.gmail.com> (raw)
Hi Grant (it's your driver :) and David D ( and your DTS generator :)
I've just debugged a failure on a board with an 8-bit sysAce
connection - I had an infinite "kicking stalled FSM" loop on driver
load.
Turns out that the way the driver probes for an 8-bit connection:
if (of_find_property(op->node, "8-bit", NULL))
...
doesn't match the properties generated by Xilinx's device tree generator:
SysACE_CompactFlash: sysace@83600000 {
compatible = "xlnx,xps-sysace-1.01.a",
"xlnx,xps-sysace-1.00.a";
interrupt-parent = <&Interrupt_Cntlr>;
interrupts = < 5 2 >;
reg = < 0x83600000 0x10000 >;
xlnx,family = "spartan6";
xlnx,mem-width = <0x8>;
So, the question is, which should change?
A temporary hard-code to 8-bit width fixes the bug for me, so I'm
certain it's just this OF property binding problem.
Let me know if we should link the DTS list into this as well.
Thanks,
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
next reply other threads:[~2009-10-07 7:14 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-10-07 7:13 John Williams [this message]
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
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=1d3f23370910070013u6307bc42hf7ab243b52d007df@mail.gmail.com \
--to=john.williams@petalogix.com \
--cc=John.Linn@xilinx.com \
--cc=ddeboni@xilinx.com \
--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®