All of lore.kernel.org
 help / color / mirror / Atom feed
* Preferred userspace IPC mechanism for new drivers?
@ 2015-05-06 21:07 Larrew, Jesse
  2015-05-07  7:10 ` Greg KH
  0 siblings, 1 reply; 2+ messages in thread
From: Larrew, Jesse @ 2015-05-06 21:07 UTC (permalink / raw)
  To: kernelnewbies

Hello,
 
I?m writing a driver that needs to communicate with userspace applications. Userspace needs to be able to send commands and associated data to the driver, so the ioctl interface seems pretty straightforward. However, LDD3 states that new ioctls in the kernel are a no-no. If that?s the case, then what is the preferred interface to userspace for new drivers?
 
ProcFS seems to be discouraged. Sysfs seems to be more for exporting device model information rather than passing binary blobs back and forth. DebugFS seems to be intended only for debug. Generic Netlink seems like the most viable candidate that I?ve investigated so far. Is that what most people are using these days?
 
Any advice would be greatly appreciated. Thanks!

Sincerely,

Jesse Larrew
Senior Software Engineer
AMD Security Architecture R&D
jesse.larrew at amd.com
O: +(1) 512-602-0092 (x50092)
M: +(1) 512-791-4852

^ permalink raw reply	[flat|nested] 2+ messages in thread

end of thread, other threads:[~2015-05-07  7:10 UTC | newest]

Thread overview: 2+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2015-05-06 21:07 Preferred userspace IPC mechanism for new drivers? Larrew, Jesse
2015-05-07  7:10 ` Greg KH

This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.