From: Timur Tabi <timur@freescale.com>
To: Grant Likely <grant.likely@secretlab.ca>
Cc: Scott Wood <scottwood@freescale.com>,
Dmitry Eremin-Solenikov <dbaryshkov@gmail.com>,
linuxppc-dev list <linuxppc-dev@ozlabs.org>
Subject: Re: [PATCH] powerpc/85xx: don't call of_platform_bus_probe() twice
Date: Tue, 27 Mar 2012 13:18:10 -0500 [thread overview]
Message-ID: <4F720462.5020400@freescale.com> (raw)
In-Reply-To: <4F69F099.4070409@freescale.com>
Grant, do you have a moment to consider my question? Like I said, I'm
anxious to get a fix into 3.3.
Timur Tabi wrote:
> Timur Tabi wrote:
>> They only problem I see with this is that I am thinking about modifying
>> the drivers/dma driver to probe on "fsl,eloplus-dma-channel" channels
>> directly. If I do that, then who should call of_platform_populate()?
>
> Grant, could you tell me if there's anything actually work with my patch?
> All I'm doing is adding a couple more commonly used entries to
> mpc85xx_common_ids[]. After all, they're common IDs, so don't they belong
> into an array called common_ids?
>
> I've been waiting for months for this problem to be fixed, and 3.3 is
> broken without it. We've already established that you cannot actually
> call of_platform_bus_probe() twice on the same level, so it's not like my
> patch description is wrong or anything.
>
--
Timur Tabi
Linux kernel developer at Freescale
next prev parent reply other threads:[~2012-03-27 18:18 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-11-30 16:19 [PATCH] powerpc/85xx: don't call of_platform_bus_probe() twice Timur Tabi
2012-03-07 21:41 ` Timur Tabi
2012-03-16 20:46 ` Kumar Gala
2012-03-16 20:50 ` Timur Tabi
2012-03-19 16:04 ` Grant Likely
2012-03-19 18:43 ` Timur Tabi
2012-03-20 17:09 ` Grant Likely
2012-03-20 17:25 ` Timur Tabi
2012-03-21 15:15 ` Timur Tabi
2012-03-27 18:18 ` Timur Tabi [this message]
2012-03-28 5:01 ` Grant Likely
2012-03-21 15:08 ` Kumar Gala
2012-04-19 20:15 ` Kumar Gala
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=4F720462.5020400@freescale.com \
--to=timur@freescale.com \
--cc=dbaryshkov@gmail.com \
--cc=grant.likely@secretlab.ca \
--cc=linuxppc-dev@ozlabs.org \
--cc=scottwood@freescale.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;
as well as URLs for NNTP newsgroup(s).