linux-kernel - Re: [-mm patch 1/4] GPIO framework for AVR32

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <20061108113023.0281c0f6@cad-250-152.norway.atmel.com>
Date:	Wed, 8 Nov 2006 11:30:23 +0100
From:	Haavard Skinnemoen <hskinnemoen@...el.com>
To:	David Brownell <david-b@...bell.net>
Cc:	akpm@...l.org, linux-kernel@...r.kernel.org, andrew@...people.com
Subject: Re: [-mm patch 1/4] GPIO framework for AVR32

On Tue, 07 Nov 2006 13:36:04 -0800
David Brownell <david-b@...bell.net> wrote:

> > +#define EXTERNAL_IRQ_BASE	NR_INTERNAL_IRQS
> > +#define NR_EXTERNAL_IRQS	32
> > +#define GPIO_IRQ_BASE		(EXTERNAL_IRQ_BASE +
> > NR_EXTERNAL_IRQS) +#define NR_GPIO_IRQS		(4 * 32)
> > +
> > +#define NR_IRQS			(GPIO_IRQ_BASE +
> > NR_GPIO_IRQS)
> 
> Did I miss something, or are the IRQs starting at GPIO_IRQ_BASE
> not actually implemented?  There's no irq_chip with name "GPIO"
> or anything.  The AT91 code should be almost a drop-in there...

No, you didn't miss anything, but I do want to implement a "GPIO"
irq_chip like at91 does. I suppose I can reduce NR_IRQS a bit until
it happens, but then again it's perhaps better to just implement the
irq_chip thing...

Haavard
-
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/