From: Scott Wood <scottwood@freescale.com>
To: Sethi Varun-B16395 <B16395@freescale.com>
Cc: Wood Scott-B07421 <B07421@freescale.com>,
"Linuxppc-dev@lists.ozlabs.org" <Linuxppc-dev@lists.ozlabs.org>
Subject: Re: [PATCH 4/4] powerpc/mpic: FSL MPIC error interrupt support.
Date: Mon, 18 Jun 2012 14:23:29 -0500 [thread overview]
Message-ID: <4FDF8031.3090705@freescale.com> (raw)
In-Reply-To: <C5ECD7A89D1DC44195F34B25E172658D11E224@039-SN2MPN1-012.039d.mgd.msft.net>
On 06/18/2012 02:19 PM, Sethi Varun-B16395 wrote:
>
>
>> -----Original Message-----
>> From: Wood Scott-B07421
>> Sent: Tuesday, June 19, 2012 12:47 AM
>> To: Sethi Varun-B16395
>> Cc: Kumar Gala; Wood Scott-B07421; Linuxppc-dev@lists.ozlabs.org
>> Subject: Re: [PATCH 4/4] powerpc/mpic: FSL MPIC error interrupt support.
>>
>> On 06/18/2012 02:12 PM, Sethi Varun-B16395 wrote:
>>>
>>>
>>>>>> +/*
>>>>>>> + * Error interrupt registers
>>>>>>> + */
>>>>>>> +
>>>>>>> +#define MPIC_ERR_INT_BASE 0x3900
>>>>>>> +#define MPIC_ERR_INT_EISR 0x0000
>>>>>>> +#define MPIC_ERR_INT_EIMR 0x0010
>>>>>>> +
>>>>>>> #define MPIC_MAX_IRQ_SOURCES 2048
>>>>>>> #define MPIC_MAX_CPUS 32
>>>>>>> #define MPIC_MAX_ISU 32
>>>>>>>
>>>>>>> #define MPIC_MAX_TIMER 8
>>>>>>> #define MPIC_MAX_IPI 4
>>>>>>> +#define MPIC_MAX_ERR 32
>>>>>>
>>>>>> Should probably be 64
>>>>>
>>>>> This patch supports MPIC 4.1 and EISR0. When support is added for
>>>>> EISR1 (didn't realize this was coming until your comment prompted me
>>>>> to check...), this should be updated, but this change alone would
>>>>> not make it work.
>>>>
>>>> Would prefer we handle this now rather than later (T4240 is going to
>>>> need
>>>> EISR1 support).
>>> Hi Kumar,
>>> As of now I don't have a proper mechanism to test this functionality.
>>> I will submit a follow up patch for EISR1/EIMR1 support once I have a
>>> mechanism to test this functionality.
>>
>> You could still write the code in a way that scales to multiple EISRs,
>> and test that it works with EISR0.
>>
> Yes, but I would like to submit the patch once I have tested it.
So test it the way I described, and submit. :-P
-Scott
next prev parent reply other threads:[~2012-06-18 19:23 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-03-27 12:17 [PATCH 4/4] powerpc/mpic: FSL MPIC error interrupt support Varun Sethi
2012-03-27 13:59 ` Kumar Gala
2012-03-27 19:07 ` Scott Wood
2012-03-28 14:35 ` Kumar Gala
2012-06-18 19:12 ` Sethi Varun-B16395
2012-06-18 19:17 ` Scott Wood
2012-06-18 19:19 ` Sethi Varun-B16395
2012-06-18 19:23 ` Scott Wood [this message]
2012-07-06 4:02 ` Sethi Varun-B16395
2012-07-06 14:26 ` 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=4FDF8031.3090705@freescale.com \
--to=scottwood@freescale.com \
--cc=B07421@freescale.com \
--cc=B16395@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).