From: Scott Wood <scottwood@freescale.com>
To: Dmitry Eremin-Solenikov <dbaryshkov@gmail.com>
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: Thu, 22 Jul 2010 14:25:52 -0500 [thread overview]
Message-ID: <20100722142552.1e01dba8@schlenkerla.am.freescale.net> (raw)
In-Reply-To: <AANLkTikX8An80SMZiypoO63Be8MKyCsmNzviwqR6syQd@mail.gmail.com>
On Thu, 22 Jul 2010 23:03:03 +0400
Dmitry Eremin-Solenikov <dbaryshkov@gmail.com> wrote:
> Hello,
>
> On Thu, Jul 22, 2010 at 10:40 PM, Kumar Gala <galak@kernel.crashing.org> wrote:
> >
> > On Jul 22, 2010, at 1:25 PM, Scott Wood wrote:
> >> How about keeping the error stuff as a separate device from Linux's
> >> perspective, but have the main Freescale PCI code create it as a
> >> platform device instead of putting it in the device tree?
> >
> > I'd be good with that solution.
>
> Then we come back to the question that was raised before (during initial
> review of edac driver): as PCI code is probbed long before other parts
> of the kernel and mpc85xx_edac code can be compiled as module,
> it's not possible to directly call mpc85xx_edac code from fsl_pci.c
Right, that's why I suggested creating a platform device rather than
just a function call.
> Two initial suggestions were:
> 1) creating special platform device
> 2) creating special of_platform device from dts
>
> Which approach should I choose? Did i miss any other opportunities?
#1, as it keeps the split out of the device tree.
Besides the theoretical/aesthetic issues of putting Linux
implementation concerns into the device tree, #2 would mean that the
edac driver wouldn't work when Linux is booted with an old device tree.
-Scott
next prev parent reply other threads:[~2010-07-22 19:26 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 [this message]
2010-07-22 19:10 ` Grant Likely
2010-07-24 0:20 ` Dmitry Eremin-Solenikov
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=20100722142552.1e01dba8@schlenkerla.am.freescale.net \
--to=scottwood@freescale.com \
--cc=bluesmoke-devel@lists.sourceforge.net \
--cc=dbaryshkov@gmail.com \
--cc=dougthompson@xmission.com \
--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).