From: Tabi Timur-B04825 <B04825-KZfg59tc24xl57MIdRCFDg@public.gmane.org>
To: Grant Likely <grant.likely-s3s/WqlpOiPyB63q8FvJNQ@public.gmane.org>
Cc: "dbaryshkov-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org"
<dbaryshkov-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>,
"devicetree-discuss-uLR06cmDAlY/bJ5BZ2RsiQ@public.gmane.org
Discuss"
<devicetree-discuss-uLR06cmDAlY/bJ5BZ2RsiQ@public.gmane.org>,
"linuxppc-dev-uLR06cmDAlY/bJ5BZ2RsiQ@public.gmane.org list"
<linuxppc-dev-uLR06cmDAlY/bJ5BZ2RsiQ@public.gmane.org>
Subject: Re: issues calling of_platform_bus_probe() twice
Date: Sun, 18 Mar 2012 16:14:23 +0000 [thread overview]
Message-ID: <4F6609DE.2050001@freescale.com> (raw)
In-Reply-To: <20120318090804.C70493E060A@localhost>
Grant Likely wrote:
> That's because you're using it wrong. of_platform_bus_probe() creates
> platform devices at the starting level and every level below it as
> described by the bus ids. It is illegal to call of_platform_bus_probe()
> twice at the same level in the DT.
Well, *I* am not using it wrong. Notice that my patch fixes (or works
around) the commit that *did* do it wrong:
http://patchwork.ozlabs.org/patch/126289/
--
Timur Tabi
Linux kernel developer at Freescale
next prev parent reply other threads:[~2012-03-18 16:14 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-03-16 21:21 issues calling of_platform_bus_probe() twice Kumar Gala
[not found] ` <31B4E554-FA95-431D-B353-92680CD14A0A-XVmvHMARGAS8U2dJNN8I7kB+6BGkLq7r@public.gmane.org>
2012-03-16 21:23 ` Benjamin Herrenschmidt
2012-03-17 7:27 ` Grant Likely
2012-03-17 13:35 ` Tabi Timur-B04825
[not found] ` <4F649304.9010001-KZfg59tc24xl57MIdRCFDg@public.gmane.org>
2012-03-17 23:29 ` Benjamin Herrenschmidt
2012-03-17 23:33 ` Tabi Timur-B04825
2012-03-18 9:08 ` Grant Likely
2012-03-18 16:14 ` Tabi Timur-B04825 [this message]
2012-03-18 18:22 ` Grant Likely
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=4F6609DE.2050001@freescale.com \
--to=b04825-kzfg59tc24xl57midrcfdg@public.gmane.org \
--cc=dbaryshkov-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org \
--cc=devicetree-discuss-uLR06cmDAlY/bJ5BZ2RsiQ@public.gmane.org \
--cc=grant.likely-s3s/WqlpOiPyB63q8FvJNQ@public.gmane.org \
--cc=linuxppc-dev-uLR06cmDAlY/bJ5BZ2RsiQ@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).