From: Thor Thayer <tthayer-yzvPICuk2ABMcg4IHK0kFoH6Mc4MB0Vx@public.gmane.org>
To: "devicetree-u79uwXL29TY76Z2rM5mHXA@public.gmane.org"
<devicetree-u79uwXL29TY76Z2rM5mHXA@public.gmane.org>
Cc: "grant.likely-QSEj5FYQhm4dnm+yROfE0A@public.gmane.org"
<grant.likely-QSEj5FYQhm4dnm+yROfE0A@public.gmane.org>,
"robh+dt-DgEjT+Ai2ygdnm+yROfE0A@public.gmane.org"
<robh+dt-DgEjT+Ai2ygdnm+yROfE0A@public.gmane.org>
Subject: Device Tree Child Node Parsing Question
Date: Tue, 23 Dec 2014 10:34:47 -0600 [thread overview]
Message-ID: <549999A7.2010608@opensource.altera.com> (raw)
Hi,
What is the best way to queue devicetree child nodes so the node is
passed in the platform_device pointer to the probe() function?
Documentation/devicetree/usage-model.txt has the following:
"For Linux DT support, the generic behaviour is for child devices to be
registered by the parent's device driver at driver .probe() time."
"Actually, it turns out that registering children of some
platform_devices as more platform_devices is a common pattern, and the
device tree support code reflects that and makes the above example
simpler. The second argument to of_platform_populate() is an
of_device_id table, and any node that matches an entry in that table
will also get its child nodes registered."
I tried calling of_platform_populate() in the probe of the a10_sysctl
node but it doesn't appear to setup the platform device data properly
for the sub-child nodes.
The top child node (a10_sysctl) is probed properly and has a valid
of_node passed in. However, the sub-child nodes such as gpio4 have null
passed in for pdev->dev.of_node (gpio4 probe prototype is int
a10sycon_gpio_probe(struct platform_device *pdev).
My current solution is to call of_find_matching_node() in
a10sycon_gpio_probe() to get a valid node pointer but other examples
tend to dereference pdev->dev.of_node.
Thank you in advance for your insight.
Thor
My device tree looks like this:
/ {
soc {
spi0: spi@fff00000 {
compatible = "snps,dw-spi-mmio";
#address-cells = <1>;
#size-cells = <0>;
reg = <0xfff00000 0x1000>;
interrupts = <0 154 4>;
num-chipselect = <4>;
clocks = <&per_base_clk>;
status = "okay";
a10_sysctl: a10_sysctl@0 {
compatible = "altr,a10sycon";
reg = <0>;
interrupt-parent = <&gpio2>;
/* low-level active IRQ at GPIO2_24 */
interrupts = <24 0x8>;
interrupt-controller;
#interrupt-cells = <2>;
spi-max-frequency = <100000>;
gpio4: gpio-controller {
compatible = "altr,a10sycon-gpio";
gpio-controller;
#gpio-cells = <2>;
ngpios = <16>;
};
a10rst: a10rst {
compatible = "altr,a10sycon-reset";
#reset-cells = <1>;
};
};
};
--
To unsubscribe from this list: send the line "unsubscribe devicetree" in
the body of a message to majordomo-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
next reply other threads:[~2014-12-23 16:34 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-12-23 16:34 Thor Thayer [this message]
[not found] ` <549999A7.2010608-yzvPICuk2ABMcg4IHK0kFoH6Mc4MB0Vx@public.gmane.org>
2014-12-26 19:40 ` Device Tree Child Node Parsing Question Rob Herring
[not found] ` <CAL_JsqLzbEuQgNZoBbzr4R=Nj9_Qs=60uLhzENbZzTaaTgxnZg-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2015-01-05 14:48 ` Thor Thayer
2014-12-27 4:15 ` He YunLei
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=549999A7.2010608@opensource.altera.com \
--to=tthayer-yzvpicuk2abmcg4ihk0kfoh6mc4mb0vx@public.gmane.org \
--cc=devicetree-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
--cc=grant.likely-QSEj5FYQhm4dnm+yROfE0A@public.gmane.org \
--cc=robh+dt-DgEjT+Ai2ygdnm+yROfE0A@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;
as well as URLs for NNTP newsgroup(s).