[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <50E6D4EA.4090307@imgtec.com>
Date: Fri, 4 Jan 2013 13:11:06 +0000
From: James Hogan <james.hogan@...tec.com>
To: Vineet Gupta <Vineet.Gupta1@...opsys.com>
CC: <linux-arch@...r.kernel.org>, <linux-kernel@...r.kernel.org>,
"Arnd Bergmann" <arnd@...db.de>,
Thomas Gleixner <tglx@...utronix.de>
Subject: Re: [PATCH v2 22/44] metag: Time keeping
On 04/01/13 12:48, Vineet Gupta wrote:
> Another question if you don't mind. In our setup we have a UART (non-standard ARC
> specific) which is wired up to the boot CPU (only). Now if the init/rcS happens to
> run on non-boot CPU, the setup/request_irq( ) and hence consequential low level
> cpu irq unmasking will only happen on *that* cpu. Now if user were to type a
> key-stroke, the interrupt will be asserted on boot-cpu, which has interrupt
> masked. How is this handled.
I'm guessing the best way would be to set the affinity of the irq from
the serial driver, and implement the irq_set_affinity callback for the
relevant irq_chip to do the necessary work, but others may have better
ideas.
Meta has something similar for output via jtag debug pod, but it doesn't
use interrupts so it has to poll from an add_timer_on()'d timer and
output from a kthread_bind()'d kthread.
Cheers
James
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists