From: Scott Wood <scottwood@freescale.com>
To: Jia Hongtao <hongtao.jia@freescale.com>
Cc: hongtao.jia@freescale.com, B07421@freescale.com,
linuxppc-dev@lists.ozlabs.org
Subject: Re: [PATCH V4] powerpc/MPIC: Add get_version API both for internal and external use
Date: Tue, 9 Apr 2013 21:32:28 -0500 [thread overview]
Message-ID: <1365561148.29365.0@snotra> (raw)
In-Reply-To: <1365386514-14647-1-git-send-email-hongtao.jia@freescale.com> (from hongtao.jia@freescale.com on Sun Apr 7 21:01:54 2013)
On 04/07/2013 09:01:54 PM, Jia Hongtao wrote:
> diff --git a/arch/powerpc/sysdev/mpic.c b/arch/powerpc/sysdev/mpic.c
> index d30e6a6..48c8fae 100644
> --- a/arch/powerpc/sysdev/mpic.c
> +++ b/arch/powerpc/sysdev/mpic.c
> @@ -1165,10 +1165,30 @@ static struct irq_domain_ops mpic_host_ops =3D {
> .xlate =3D mpic_host_xlate,
> };
>=20
> +static u32 fsl_mpic_get_version(struct mpic *mpic)
> +{
> + u32 brr1;
> +
> + brr1 =3D _mpic_read(mpic->reg_type, &mpic->thiscpuregs,
> + MPIC_FSL_BRR1);
> +
> + return brr1 & MPIC_FSL_BRR1_VER;
> +}
If it's not an FSL mpic, thiscpuregs->base will be NULL. Please check =20
mpic->flags for MPIC_FSL.
> +
> /*
> * Exported functions
> */
>=20
> +u32 fsl_mpic_primary_get_version(void)
> +{
> + struct mpic *mpic =3D mpic_primary;
> +
> + if (mpic)
> + return fsl_mpic_get_version(mpic);
> +
> + return 0;
> +}
...especially since the external version doesn't check for it either.
Otherwise, this and the MSI-X patch look OK to me.
-Scott=
next prev parent reply other threads:[~2013-04-10 2:32 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-04-08 2:01 [PATCH V4] powerpc/MPIC: Add get_version API both for internal and external use Jia Hongtao
2013-04-10 2:22 ` Jia Hongtao-B38951
2013-04-10 2:32 ` Scott Wood [this message]
2013-04-10 2:35 ` Jia Hongtao-B38951
2013-04-10 3:04 ` Jia Hongtao-B38951
2013-04-10 3:07 ` Scott Wood
2013-04-10 3:10 ` Jia Hongtao-B38951
2013-04-10 3:12 ` Scott Wood
2013-04-10 3:14 ` Jia Hongtao-B38951
2013-04-10 3:20 ` Scott Wood
2013-04-10 3:26 ` 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=1365561148.29365.0@snotra \
--to=scottwood@freescale.com \
--cc=B07421@freescale.com \
--cc=hongtao.jia@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).