From: Dmitry Eremin-Solenikov <dbaryshkov@gmail.com>
To: Grant Likely <grant.likely@secretlab.ca>
Cc: linuxppc-dev@ozlabs.org,
Doug Thompson <dougthompson@xmission.com>,
bluesmoke-devel@lists.sourceforge.net
Subject: Re: [PATCH 2/2] mpc85xx_edac: change to use new definitions for PCI EDAC regspace
Date: Sat, 24 Jul 2010 04:20:41 +0400 [thread overview]
Message-ID: <AANLkTik-3cujkh774H6WQB8sHD+gkKLT2FQp=8HYaWBt@mail.gmail.com> (raw)
In-Reply-To: <AANLkTimsKcn3n90cyqQTQ4Ycy2dlsHdi7afeiNX4M0v5@mail.gmail.com>
Hello,
On 7/22/10, Grant Likely <grant.likely@secretlab.ca> wrote:
> On Thu, Jul 22, 2010 at 10:48 AM, Dmitry Eremin-Solenikov
> <dbaryshkov@gmail.com> wrote:
>> Hello,
>>
>> On Thu, Jul 22, 2010 at 7:38 PM, Kumar Gala <galak@kernel.crashing.org>
>> wrote:
>>>
>>> On Jul 21, 2010, at 7:03 PM, Dmitry Eremin-Solenikov wrote:
>>>
>>>> Currently (as mpc8540-pci) devices are not created on of_platform bus,
>>>> mpc85xx_edac can't probe to them. Follow the change to dts trees to bind
>>>> not to the main mpc8540-pci node but to special mpc85xx-pci-error nodes,
>>>> present on soc bus.
>>>>
>>>> Signed-off-by: Dmitry Eremin-Solenikov <dbaryshkov@gmail.com>
>>>> ---
>>>> drivers/edac/mpc85xx_edac.c | 18 +++++++++---------
>>>> 1 files changed, 9 insertions(+), 9 deletions(-)
>>>
>>> Nak.
>>>
>>> We already have a node in the dts for the PCI controller. Lets update
>>> the platform code to add the pci controller to the of_platform_bus_probe
>>> list.
>>
>> I've had that idea. However it's really look strange to me to call
>> of_platform_bus_probe() on the bus node, for which we (IMO) explicitly
>> won't like for
>> child devices (PCI devices) to be added to of_platform bus. Would it
>> be suitable to just call of_platform_device_create for it (Or do i
>> miss someth<ing)?
>
> Try the attached patch (lightly tested). If it works for you then
> I'll post it for wider review.
Yes, this patch worked for me. However it looks a bit like a hack for me.
--
With best wishes
Dmitry
------------------------------------------------------------------------------
This SF.net email is sponsored by Sprint
What will you do first with EVO, the first 4G phone?
Visit sprint.com/first -- http://p.sf.net/sfu/sprint-com-first
next prev parent reply other threads:[~2010-07-24 0:20 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-07-22 0:03 [PATCH 1/2] MPC85xx: add definitions for PCI error detection soc part Dmitry Eremin-Solenikov
2010-07-22 0:03 ` [PATCH 2/2] mpc85xx_edac: change to use new definitions for PCI EDAC regspace Dmitry Eremin-Solenikov
2010-07-22 15:38 ` Kumar Gala
2010-07-22 16:48 ` Dmitry Eremin-Solenikov
2010-07-22 18:25 ` Scott Wood
2010-07-22 18:40 ` Kumar Gala
2010-07-22 19:03 ` Dmitry Eremin-Solenikov
2010-07-22 19:15 ` Grant Likely
2010-07-22 19:25 ` Scott Wood
2010-07-22 19:10 ` Grant Likely
2010-07-24 0:20 ` Dmitry Eremin-Solenikov [this message]
[not found] ` <AANLkTik-3cujkh774H6WQB8sHD+gkKLT2FQp=8HYaWBt-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2010-07-24 0:56 ` Grant Likely
2010-07-24 10:09 ` Dmitry Eremin-Solenikov
2010-07-22 15:19 ` [PATCH 1/2] MPC85xx: add definitions for PCI error detection soc part Peter Tyser
2010-07-22 16:56 ` Dmitry Eremin-Solenikov
2010-07-22 17:09 ` Peter Tyser
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='AANLkTik-3cujkh774H6WQB8sHD+gkKLT2FQp=8HYaWBt@mail.gmail.com' \
--to=dbaryshkov@gmail.com \
--cc=bluesmoke-devel@lists.sourceforge.net \
--cc=dougthompson@xmission.com \
--cc=grant.likely@secretlab.ca \
--cc=linuxppc-dev@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).