From: Gala Kumar-B11780 <B11780@freescale.com>
To: Wood Scott-B07421 <B07421@freescale.com>
Cc: Lan Chunhe-B25806 <B25806@freescale.com>,
"linuxppc-dev@lists.ozlabs.org" <linuxppc-dev@lists.ozlabs.org>
Subject: Re: [PATCH 3/3] edac/85xx: Enable the EDAC PCI err driver by device_initcall
Date: Thu, 27 Sep 2012 21:45:08 +0000 [thread overview]
Message-ID: <CF1EE7AED478CD48A05574C8E2DA142D5E2C18@039-SN1MPN1-006.039d.mgd.msft.net> (raw)
In-Reply-To: <1348762151.18375.6@snotra>
On Sep 27, 2012, at 11:09 AM, Scott Wood wrote:
> On 09/27/2012 02:02:03 PM, Chunhe Lan wrote:
>> Original process of call:
>> The mpc85xx_pci_err_probe function completes to been registered
>> and enabled of EDAC PCI err driver at the latter time stage of
>> kernel boot in the mpc85xx_edac.c.
>> Current process of call:
>> The mpc85xx_pci_err_probe function completes to been registered
>> and enabled of EDAC PCI err driver at the first time stage of
>> kernel boot in the fsl_pci.c.
>> So in this case the following error messages appear in the boot log:
>> PCI: Probing PCI hardware
>> pci 0000:00:00.0: ignoring class b20 (doesn't match header type 01)
>> PCIE error(s) detected
>> PCIE ERR_DR register: 0x00020000
>> PCIE ERR_CAP_STAT register: 0x80000001
>> PCIE ERR_CAP_R0 register: 0x00000800
>> PCIE ERR_CAP_R1 register: 0x00000000
>> PCIE ERR_CAP_R2 register: 0x00000000
>> PCIE ERR_CAP_R3 register: 0x00000000
>> Because the EDAC PCI err driver is registered and enabled earlier than
>> original point of call. But at this point of time, PCI hardware is not
>> probed and initialized, and it is in unknowable state.
>> So, move enable function into mpc85xx_pci_err_en which is called at the
>> middle time stage of kernel boot and after PCI hardware is probed and
>> initialized by device_initcall in the fsl_pci.c.
>> Signed-off-by: Chunhe Lan <Chunhe.Lan@freescale.com>
>> ---
>> arch/powerpc/sysdev/fsl_pci.c | 12 ++++++++++
>> arch/powerpc/sysdev/fsl_pci.h | 5 ++++
>> drivers/edac/mpc85xx_edac.c | 47 ++++++++++++++++++++++++++++-------=
-----
>> 3 files changed, 50 insertions(+), 14 deletions(-)
>> diff --git a/arch/powerpc/sysdev/fsl_pci.c b/arch/powerpc/sysdev/fsl_pci=
.c
>> index 3d6f4d8..a591965 100644
>> --- a/arch/powerpc/sysdev/fsl_pci.c
>> +++ b/arch/powerpc/sysdev/fsl_pci.c
>> @@ -904,4 +904,16 @@ static int __init fsl_pci_init(void)
>> return platform_driver_register(&fsl_pci_driver);
>> }
>> arch_initcall(fsl_pci_init);
>> +
>> +static int __init fsl_pci_err_en(void)
>> +{
>> + struct device_node *np;
>> +
>> + for_each_node_by_type(np, "pci")
>> + if (of_match_node(pci_ids, np))
>> + mpc85xx_pci_err_en(np);
>> +
>> + return 0;
>> +}
>> +device_initcall(fsl_pci_err_en);
>=20
> Why can't you call this from the normal PCIe controller init, instead of =
searching for the node independently?
Don't we have this now with mpc85xx_pci_err_probe() ??
- k=
next prev parent reply other threads:[~2012-09-27 21:45 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-09-27 19:02 [PATCH 1/3] edac: Use ccsr_pci structure instead of hardcoded define Chunhe Lan
2012-09-27 19:02 ` [PATCH 2/3] edac/85xx: PCI/PCIe error interrupt edac support Chunhe Lan
2012-09-27 19:02 ` [PATCH 3/3] edac/85xx: Enable the EDAC PCI err driver by device_initcall Chunhe Lan
2012-09-27 16:09 ` Scott Wood
2012-09-27 21:45 ` Gala Kumar-B11780 [this message]
2012-09-27 21:51 ` Scott Wood
2012-09-27 22:33 ` Kumar Gala
2012-09-28 17:35 ` Scott Wood
2012-09-29 14:42 ` Chunhe Lan
2012-10-01 19:11 ` Scott Wood
2012-09-28 14:29 ` Chunhe Lan
2012-10-03 13:22 ` [PATCH 1/3] edac: Use ccsr_pci structure instead of hardcoded define Gala Kumar-B11780
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=CF1EE7AED478CD48A05574C8E2DA142D5E2C18@039-SN1MPN1-006.039d.mgd.msft.net \
--to=b11780@freescale.com \
--cc=B07421@freescale.com \
--cc=B25806@freescale.com \
--cc=linuxppc-dev@lists.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).