Linux MIPS Architecture development
 help / color / mirror / Atom feed
From: Sergei Shtylyov <sshtylyov@ru.mvista.com>
To: Ralf Baechle <ralf@linux-mips.org>
Cc: Rodolfo Giometti <giometti@linux.it>,
	linux-mips@linux-mips.org, rmk@arm.linux.org.uk
Subject: Re: [PATCH] au1x00 serial real interrupt
Date: Sat, 09 Sep 2006 20:34:28 +0400	[thread overview]
Message-ID: <4502ED14.6080506@ru.mvista.com> (raw)
In-Reply-To: <44FD9587.3030708@ru.mvista.com>

Hello.

Sergei Shtylyov wrote:

>> ------------------------------------------------------------------------
>>
>> diff --git a/include/asm-mips/serial.h b/include/asm-mips/serial.h
>> index 7b23664..0197062 100644
>> --- a/include/asm-mips/serial.h
>> +++ b/include/asm-mips/serial.h
>> @@ -11,6 +11,14 @@
>>  
>>  #include <linux/config.h>
>>  
>> +#ifdef CONFIG_SOC_AU1X00
>> +/*
>> + * We have to redefine "is_real_interrupt()" for Au1x00 CPUs...
>> + */
>> +#undef is_real_interrupt
>> +#define is_real_interrupt(irq)    ((irq) != ~0)
>> +#endif
>> +
>>  /*
>>   * This assumes you have a 1.8432 MHz clock for your UART.
>>   *

>    Ralf, how about this patch? Can it be applied, at least 3 months 
> after posting? Alchemy UART0 uses IRQ0 and 0 is treated as "no IRQ" by 
> drivers/serial/8250.c which says the macro should be redefined in 
> <asm/serial.h> if needed.

    If the values other than 0 need to be filtered out, to be precise...

    Well, after looking at drivers/serial/8250.c a bit more, I think this may 
be even more simlified since that driver seems to treat the negative values as 
completely invalid anyway. IOW, we can just:

#define is_real_interrupt(irq)	1

    Russel, what do you think?

WBR, Sergei

  reply	other threads:[~2006-09-09 16:32 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-05-22 16:52 [PATCH] au1x00 serial real interrupt Rodolfo Giometti
2006-09-05 15:19 ` Sergei Shtylyov
2006-09-09 16:34   ` Sergei Shtylyov [this message]
2006-09-09 16:39     ` Russell King
2006-09-09 16:58       ` Sergei Shtylyov
2006-09-14 18:10       ` Ralf Baechle
2006-09-18 20:13     ` Sergei Shtylyov

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=4502ED14.6080506@ru.mvista.com \
    --to=sshtylyov@ru.mvista.com \
    --cc=giometti@linux.it \
    --cc=linux-mips@linux-mips.org \
    --cc=ralf@linux-mips.org \
    --cc=rmk@arm.linux.org.uk \
    /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