linux-kernel - Re: [RFC 2/5] gpio: add support for Technologic Systems TS-5500 GPIOs

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: <1305322106-sup-3383@v0nbox>
Date:	Fri, 13 May 2011 17:33:52 -0400
From:	Vivien Didelot <vivien.didelot@...oirfairelinux.com>
To:	Alan Cox <alan@...rguk.ukuu.org.uk>
Cc:	linux-kernel <linux-kernel@...r.kernel.org>,
	Jerome Oufella <jerome.oufella@...oirfairelinux.com>,
	platform-driver-x86 <platform-driver-x86@...r.kernel.org>,
	linux-serial <linux-serial@...r.kernel.org>,
	lm-sensors <lm-sensors@...sensors.org>
Subject: Re: [RFC 2/5] gpio: add support for Technologic Systems TS-5500 GPIOs

Excerpts from Alan Cox's message of sam avr 30 06:15:36 -0400 2011:
> > +    /* Enable IRQ generation */
> > +    mutex_lock(&drvdata->gpio_lock);
> > +    PORT_BIT_SET(0x7A, 7); /* DIO1_13 on IRQ7 */
> > +    PORT_BIT_SET(0x7D, 7); /* DIO2_13 on IRQ6 */
> > +    if (use_lcdio) {
> > +        PORT_BIT_CLEAR(0x7D, 4); /* Enable LCD header usage as DIO */
> > +        PORT_BIT_SET(0x7D, 6);   /* LCD_RS on IRQ1 */
> > +    }
> 
> What happens if an IRQ occurs at this point, you have no handler for it ?

The IRQ is just not handled. What would be the proper way to handle
that? Would it be possible to write those registers when the IRQ is
requested?

Thanks,
Vivien.
--
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/