From: Scott Wood <scottwood@freescale.com>
To: Jia Hongtao-B38951 <B38951@freescale.com>
Cc: Wood Scott-B07421 <B07421@freescale.com>,
"linuxppc-dev@lists.ozlabs.org" <linuxppc-dev@lists.ozlabs.org>,
Li Yang-R58472 <r58472@freescale.com>
Subject: Re: [PATCH V4] powerpc/MPIC: Add get_version API both for internal and external use
Date: Tue, 9 Apr 2013 22:07:35 -0500 [thread overview]
Message-ID: <1365563255.29365.1@snotra> (raw)
In-Reply-To: <412C8208B4A0464FA894C5F0C278CD5D01C3557B@039-SN1MPN1-003.039d.mgd.msft.net> (from B38951@freescale.com on Tue Apr 9 22:04:44 2013)
On 04/09/2013 10:04:44 PM, Jia Hongtao-B38951 wrote:
>=20
>=20
> > -----Original Message-----
> > From: Wood Scott-B07421
> > Sent: Wednesday, April 10, 2013 10:32 AM
> > To: Jia Hongtao-B38951
> > Cc: linuxppc-dev@lists.ozlabs.org; galak@kernel.crashing.org; Wood =20
> Scott-
> > B07421; Li Yang-R58472; Jia Hongtao-B38951
> > Subject: Re: [PATCH V4] powerpc/MPIC: Add get_version API both for
> > internal and external use
> >
> > On 04/07/2013 09:01:54 PM, Jia Hongtao wrote:
> > > diff --git a/arch/powerpc/sysdev/mpic.c =20
> 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 =20
> mpic_host_ops =3D {
> > > .xlate =3D mpic_host_xlate,
> > > };
> > >
> > > +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 =20
> check
> > mpic->flags for MPIC_FSL.
> >
> > > +
> > > /*
> > > * Exported functions
> > > */
> > >
> > > +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 =20
> either.
> >
> > Otherwise, this and the MSI-X patch look OK to me.
> >
> > -Scott
>=20
>=20
> Since all the functions including mpic_alloc() and mpic_init() do the
> check for MPIC_FSL before using fsl_mpic_get_version() I'd like to add
> check just for fsl_mpic_primary_get_version().
>=20
> It will be like this:
> u32 fsl_mpic_primary_get_version(void)
> {
> struct mpic *mpic =3D mpic_primary;
>=20
> if (mpic && (mpic->flags & MPIC_FSL))
> return fsl_mpic_get_version(mpic);
>=20
> return 0;
> }
>=20
> Could we reach an agreement here?
Is there any particular reason? It would be more robust and more =20
consistent if the check were done in fsl_mpic_get_version().
-Scott=
next prev parent reply other threads:[~2013-04-10 3:07 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
2013-04-10 2:35 ` Jia Hongtao-B38951
2013-04-10 3:04 ` Jia Hongtao-B38951
2013-04-10 3:07 ` Scott Wood [this message]
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=1365563255.29365.1@snotra \
--to=scottwood@freescale.com \
--cc=B07421@freescale.com \
--cc=B38951@freescale.com \
--cc=linuxppc-dev@lists.ozlabs.org \
--cc=r58472@freescale.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 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).