linux-kernel - Re: RESEND: Generating interrupts from a USB device driver? (USB to SPI/GPIO bridge)

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] [day] [month] [year] [list]

Message-ID: <52263FF3.6080409@att.net>
Date:	Tue, 03 Sep 2013 15:00:51 -0500
From:	Daniel Santos <danielfsantos@....net>
To:	Greg KH <gregkh@...uxfoundation.org>
CC:	LKML <linux-kernel@...r.kernel.org>,
	linux-gpio <linux-gpio@...r.kernel.org>,
	linux-usb <linux-usb@...r.kernel.org>,
	linux-spi <linux-spi@...r.kernel.org>
Subject: Re: RESEND: Generating interrupts from a USB device driver? (USB
 to SPI/GPIO bridge)

On 09/02/2013 06:07 PM, Greg KH wrote:
> On Mon, Sep 02, 2013 at 05:46:58PM -0500, Daniel Santos wrote:
>> Hello guys.  I didn't get a response the last time so hopefully with
>> 3.11 out I'll get one this time.
>>
>> I need to be able to generate interrupts from a USB device driver while
>> servicing the complete() function of an interrupt URB.
> No you don't :)

Hmm, am I wrong that if I want my gpios to be poll()-able from userspace 
(via /sys/class/gpio/gpio<num>/value), that I must generate an IRQ and 
populate my .to_irq function of gpio_chip? Or is it cleaner to find the 
dirent and directly call sysfs_notify_dirent() to facilitate this 
behavior to userspace?

Of course, this will wont enable drivers that want an irq in the kernel, 
but aside from this ADNS-9800, I don't need that functionality.

Thanks,
Daniel
--
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/