All of lore.kernel.org
 help / color / mirror / Atom feed
From: ludovic.desroches@atmel.com (ludovic.desroches)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH v2] ARM: at91: aic can use fast eoi handler type
Date: Fri, 1 Jun 2012 09:45:56 +0200	[thread overview]
Message-ID: <4FC87334.90303@atmel.com> (raw)
In-Reply-To: <20120601032442.GA11721@mudshark.cambridge.arm.com>

Hi Will,

Le 06/01/2012 05:24 AM, Will Deacon a ?crit :
> Hi Ludovic,
>
> Thanks for the update. Few comments inline.
>
> On Thu, May 31, 2012 at 03:31:44PM +0100, ludovic.desroches at atmel.com wrote:
>> diff --git a/arch/arm/mach-at91/gpio.c b/arch/arm/mach-at91/gpio.c
>> index 325837a..a8bd715 100644
>> --- a/arch/arm/mach-at91/gpio.c
>> +++ b/arch/arm/mach-at91/gpio.c
>> @@ -593,7 +593,7 @@ static void gpio_irq_handler(unsigned irq, struct irq_desc *desc)
>>   	int		n;
>>
>>   	/* temporarily mask (level sensitive) parent IRQ */
>> -	chip->irq_ack(idata);
>> +	chip->irq_mask(idata);
>
> You don't need to mask the IRQ for fasteoi. However, you shouldn't be coding
> the flow control like this -- use chained_irq_enter instead.
>
>>   	for (;;) {
>>   		/* Reading ISR acks pending (edge triggered) GPIO interrupts.
>>   		 * When there none are pending, we're finished unless we need
>> @@ -614,6 +614,7 @@ static void gpio_irq_handler(unsigned irq, struct irq_desc *desc)
>>   			n = find_next_bit(&isr, BITS_PER_LONG, n + 1);
>>   		}
>>   	}
>> +	chip->irq_eoi(idata);
>
> chained_irq_exit.

Thanks I was not aware about this two functions.

>
>> diff --git a/arch/arm/mach-at91/irq.c b/arch/arm/mach-at91/irq.c
>> index 601b4ee..3aa18a6 100644
>> --- a/arch/arm/mach-at91/irq.c
>> +++ b/arch/arm/mach-at91/irq.c
>> @@ -55,6 +55,15 @@ static void at91_aic_unmask_irq(struct irq_data *d)
>>   	at91_aic_write(AT91_AIC_IECR, 1<<  d->hwirq);
>>   }
>>
>> +static void at91_aic_eoi(struct irq_data *d)
>> +{
>> +	/*
>> +	 * Mark end-of-interrupt on AIC, the controller doesn't care about
>> +	 * the value written in this register.
>> +	 */
>> +	at91_aic_write(AT91_AIC_EOICR, 0);
>> +}
>
> Does the EOICR read as zero, or can you read back the value which you wrote?
> In the latter case, writing the interrupt number can be a useful debugging
> aid when you have to debug IRQ issues with JTAG. Your call.

It is a write only register so value read back is 0. Moreover there is a 
new version of AIC where writing '1 << d->hwirq' as no more sense since 
we have an interrupt select register.

Regards

Ludovic

      reply	other threads:[~2012-06-01  7:45 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-05-31 14:31 [PATCH v2] ARM: at91: aic can use fast eoi handler type ludovic.desroches at atmel.com
2012-06-01  3:24 ` Will Deacon
2012-06-01  7:45   ` ludovic.desroches [this message]

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=4FC87334.90303@atmel.com \
    --to=ludovic.desroches@atmel.com \
    --cc=linux-arm-kernel@lists.infradead.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 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.