From: Scott Wood <scottwood@freescale.com>
To: Kumar Gala <galak@kernel.crashing.org>
Cc: linuxppc-dev@lists.ozlabs.org
Subject: Re: [PATCH 1/2] powerpc/mpic: allow coreint to be determined by MPIC version
Date: Wed, 23 Jan 2013 11:28:33 -0600 [thread overview]
Message-ID: <1358962113.9710.2@snotra> (raw)
In-Reply-To: <AAD002DB-C259-4054-A126-950B69BF1B5D@kernel.crashing.org> (from galak@kernel.crashing.org on Wed Jan 23 11:23:51 2013)
On 01/23/2013 11:23:51 AM, Kumar Gala wrote:
>=20
> On Jan 21, 2013, at 7:56 PM, Scott Wood wrote:
>=20
> > This will be used by the qemu-e500 platform, as the MPIC version =20
> (and
> > thus whether we have coreint) depends on how QEMU is configured.
> >
> > Signed-off-by: Scott Wood <scottwood@freescale.com>
> > ---
> > arch/powerpc/sysdev/mpic.c | 26 +++++++++++++++++++++++---
> > 1 file changed, 23 insertions(+), 3 deletions(-)
>=20
> Is the idea that we'd set mpic->flags such that MPIC_ENABLE_COREINT =20
> was set, but based on the controller version we'd ignore the flag?
Yes, at least for platforms like qemu-e500 where both are posssible =20
(see patch 2/2).
-Scott=
next prev parent reply other threads:[~2013-01-23 17:28 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-01-22 1:56 [PATCH 1/2] powerpc/mpic: allow coreint to be determined by MPIC version Scott Wood
2013-01-22 1:56 ` [PATCH 1/2] powerpc/mpic: make distribute_irqs obey MPIC_SINGLE_DEST_CPU Scott Wood
2013-01-22 1:59 ` Scott Wood
2013-01-22 1:56 ` [PATCH 2/2] powerpc/e500/qemu-e500: enable coreint Scott Wood
2013-02-15 20:14 ` Kumar Gala
2013-01-22 1:56 ` [PATCH 2/2] powerpc/fsl: remove CONFIG_IRQ_ALL_CPUS from mpc85xx/mpc86xx defconfig Scott Wood
2013-01-23 17:23 ` [PATCH 1/2] powerpc/mpic: allow coreint to be determined by MPIC version Kumar Gala
2013-01-23 17:28 ` Scott Wood [this message]
2013-02-15 20:14 ` Kumar Gala
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=1358962113.9710.2@snotra \
--to=scottwood@freescale.com \
--cc=galak@kernel.crashing.org \
--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).