1<html><head><meta http-equiv="Content-Type" content="text/html; charset=ANSI_X3.4-1968"><title>struct key_entry</title><meta name="generator" content="DocBook XSL Stylesheets V1.78.1"><link rel="home" href="index.html" title="Linux Device Drivers"><link rel="up" href="ch08s05.html" title="Sparse keymap support"><link rel="prev" href="ch08s05.html" title="Sparse keymap support"><link rel="next" href="API-sparse-keymap-entry-from-scancode.html" title="sparse_keymap_entry_from_scancode"></head><body bgcolor="white" text="black" link="#0000FF" vlink="#840084" alink="#0000FF"><div class="navheader"><table width="100%" summary="Navigation header"><tr><th colspan="3" align="center"><span class="phrase">struct key_entry</span></th></tr><tr><td width="20%" align="left"><a accesskey="p" href="ch08s05.html">Prev</a> </td><th width="60%" align="center">Sparse keymap support</th><td width="20%" align="right"> <a accesskey="n" href="API-sparse-keymap-entry-from-scancode.html">Next</a></td></tr></table><hr></div><div class="refentry"><a name="API-struct-key-entry"></a><div class="titlepage"></div><div class="refnamediv"><h2>Name</h2><p>struct key_entry — 2 keymap entry for use in sparse keymap 3 </p></div><div class="refsynopsisdiv"><h2>Synopsis</h2><pre class="programlisting"> 4struct key_entry { 5 int type; 6 u32 code; 7 union {unnamed_union}; 8}; </pre></div><div class="refsect1"><a name="idp1114741412"></a><h2>Members</h2><div class="variablelist"><dl class="variablelist"><dt><span class="term">type</span></dt><dd><p> 9Type of the key entry (KE_KEY, KE_SW, KE_VSW, KE_END); 10drivers are allowed to extend the list with their own 11private definitions. 12 </p></dd><dt><span class="term">code</span></dt><dd><p> 13Device-specific data identifying the button/switch 14 </p></dd><dt><span class="term">{unnamed_union}</span></dt><dd><p> 15anonymous 16 </p></dd></dl></div></div><div class="refsect1"><a name="idp1114744212"></a><h2>Description</h2><p> 17 This structure defines an entry in a sparse keymap used by some 18 input devices for which traditional table-based approach is not 19 suitable. 20</p></div></div><div class="navfooter"><hr><table width="100%" summary="Navigation footer"><tr><td width="40%" align="left"><a accesskey="p" href="ch08s05.html">Prev</a> </td><td width="20%" align="center"><a accesskey="u" href="ch08s05.html">Up</a></td><td width="40%" align="right"> <a accesskey="n" href="API-sparse-keymap-entry-from-scancode.html">Next</a></td></tr><tr><td width="40%" align="left" valign="top">Sparse keymap support </td><td width="20%" align="center"><a accesskey="h" href="index.html">Home</a></td><td width="40%" align="right" valign="top"> <span class="phrase">sparse_keymap_entry_from_scancode</span></td></tr></table></div></body></html> 21