From: Scott Wood <scottwood@freescale.com>
To: Jia Hongtao <B38951@freescale.com>
Cc: linuxppc-dev@lists.ozlabs.org, soniccat.liu@gmail.com
Subject: Re: [PATCH] powerpc/85xx: workaround for chips with MSI hareware errata to support MSI-X
Date: Mon, 16 Jul 2012 18:20:16 -0500 [thread overview]
Message-ID: <5004A1B0.6070004@freescale.com> (raw)
In-Reply-To: <1342409730-28340-1-git-send-email-B38951@freescale.com>
On 07/15/2012 10:35 PM, Jia Hongtao wrote:
> From: Liu Shuo <soniccat.liu@gmail.com>
>
> The MPIC chip with version 2.0 has a MSI errata (errata PIC1 of mpc8544),
> It causes that neither MSI nor MSI-X can work fine. There is a workaround
> to allow MSI-X to function properly.
s/There is/This is/
There is also a workaround for regular MSI to function properly, though
this patch does not implement it.
> +/* MPIC chip with 2.0 version has erratum PIC1 */
> +static int mpic_has_errata(struct platform_device *dev)
> +{
> + struct device_node *mpic_node;
> +
> + mpic_node = of_irq_find_parent(dev->dev.of_node);
> + if (mpic_node) {
> + u32 *reg_base, brr1 = 0;
> + /* Get the PIC reg base */
> + reg_base = of_iomap(mpic_node, 0);
> + of_node_put(mpic_node);
> + if (!reg_base) {
> + dev_err(&dev->dev, "ioremap problem failed.\n");
> + return -EIO;
> + }
> +
> + /* Get the mpic chip version from block revision register 1 */
> + brr1 = in_be32(reg_base + MPIC_FSL_BRR1);
> + iounmap(reg_base);
> + if ((brr1 & MPIC_FSL_BRR1_VER) == 0x0200)
> + return 1;
There's already been a patch posted that includes BRR1 checking:
http://patchwork.ozlabs.org/patch/169713/
Please coordinate with that. Have the MPIC code read the version once,
and expose it to the MSI driver, rather than digging directly into the
non-MSI MPIC registers from here.
> diff --git a/arch/powerpc/sysdev/fsl_msi.h b/arch/powerpc/sysdev/fsl_msi.h
> index 8225f86..354d546 100644
> --- a/arch/powerpc/sysdev/fsl_msi.h
> +++ b/arch/powerpc/sysdev/fsl_msi.h
> @@ -25,6 +25,9 @@
> #define FSL_PIC_IP_IPIC 0x00000002
> #define FSL_PIC_IP_VMPIC 0x00000003
>
> +#define MSI_HW_ERRATA_MASK 0x000000F0
> +#define MSI_HW_ERRATA_ENDIAN 0x00000010
Why do we need a mask for this?
-Scott
next prev parent reply other threads:[~2012-07-16 23:20 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-07-16 3:35 [PATCH] powerpc/85xx: workaround for chips with MSI hareware errata to support MSI-X Jia Hongtao
2012-07-16 23:20 ` Scott Wood [this message]
2012-07-17 2:19 ` Jia Hongtao-B38951
2012-07-17 6:18 ` Jia Hongtao-B38951
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=5004A1B0.6070004@freescale.com \
--to=scottwood@freescale.com \
--cc=B38951@freescale.com \
--cc=linuxppc-dev@lists.ozlabs.org \
--cc=soniccat.liu@gmail.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.