From: Timur Tabi <timur@freescale.com>
To: Bruce_Leonard@selinc.com
Cc: linuxppc-embedded@ozlabs.org
Subject: Re: Using DMA
Date: Tue, 11 Nov 2008 15:54:49 -0600 [thread overview]
Message-ID: <4919FF29.1080203@freescale.com> (raw)
In-Reply-To: <OFA4A29B19.15508F00-ON882574FE.0075F65A-882574FE.00779C47@selinc.com>
Bruce_Leonard@selinc.com wrote:
> Yea, that works! I hit the probe function. Thanks very much Timur. I
> would never have found that.
I'm glad to help.
> Experimentally, I've found that I don't need the "simple-bus"
> compatibility in the of_device_id array in the Elo DMA driver. Any idea
> why?
Not off-hand.
> Thanks again for all the help. If you've got some time, could you explain
> why adding the "simple-bus" compatibility to the SOC node of the device
> tree was needed. I _still_ (after fighting with them for over a year)
> don't get device trees.
The 'compatible' field is usually the field used to find a node. Also, I
believe the OF code only probes nodes one level deep from a node it already
knows about. So if you don't have a compatible=simple-bus where it belongs,
then the kernel won't automatically probe all nodes under it.
However, certain standard nodes, like I2C and serial ports, are probed
independently of where they are located. This happens in fsl_soc.c. I could
have updated fsl_soc.c to automatically probe the DMA nodes as well, but
fsl_soc.c is reserved for devices that have architecture-independent drivers, so
something needs to extract the data from the device tree and put it into
arch-independent platform data structures for the drivers. Since the DMA driver
is powerpc-only, it doesn't qualify for this service. The driver has to extract
all the information it needs directly from the device tree.
--
Timur Tabi
Linux kernel developer at Freescale
prev parent reply other threads:[~2008-11-11 21:54 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-11-06 2:07 Using DMA Bruce_Leonard
2008-11-06 18:29 ` Scott Wood
2008-11-06 18:36 ` Bill Gatliff
2008-11-06 20:58 ` Bruce_Leonard
2008-11-06 21:42 ` Bill Gatliff
2008-11-07 15:43 ` Timur Tabi
2008-11-07 21:31 ` Bruce_Leonard
2008-11-07 21:46 ` Timur Tabi
2008-11-07 22:12 ` Bruce_Leonard
2008-11-07 22:28 ` Timur Tabi
2008-11-07 22:37 ` Bruce_Leonard
2008-11-09 3:26 ` Bill Gatliff
2008-11-09 3:25 ` Bill Gatliff
2008-11-10 0:09 ` Bruce_Leonard
2008-11-10 14:35 ` Timur Tabi
2008-11-10 17:58 ` Bruce_Leonard
2008-11-11 9:09 ` Rajasekaran Kaliyaperumal, Chennai
2008-11-11 10:22 ` Porting Linux to 8051 [ was:Re: Using DMA ] Martyn Welch
2008-11-10 22:06 ` Using DMA Bruce_Leonard
2008-11-11 14:51 ` Timur Tabi
2008-11-11 18:19 ` Bruce_Leonard
2008-11-11 19:22 ` Timur Tabi
2008-11-11 21:46 ` Bruce_Leonard
2008-11-11 21:54 ` Timur Tabi [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=4919FF29.1080203@freescale.com \
--to=timur@freescale.com \
--cc=Bruce_Leonard@selinc.com \
--cc=linuxppc-embedded@ozlabs.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;
as well as URLs for NNTP newsgroup(s).