| Commit message (Collapse) | Author | Age | |
|---|---|---|---|
| * | devicetree: bindings: Use linux-event-codes.h for evdev codes | Hans de Goede | 2015-10-16 |
| | | | | | | | | | | | | Add a symlink to uapi/linux/linux-event-codes.h, and include that instead of (re)defining all the evdev type and code values in dt-bindings/input/input.h. This way we do not need to keep all the event codes synced manually. Signed-off-by: Hans de Goede <hdegoede@redhat.com> Acked-by: Rob Herring <robh@kernel.org> Signed-off-by: Dmitry Torokhov <dmitry.torokhov@gmail.com> | ||
| * | include: dt-binding: input: create a DT header defining key codes. | Laxman Dewangan | 2013-08-19 |
| Many of Key device tree bindings uses the constant number as key code which matches with kernel header key code and then comment as follows for reference/better readability: linux,code = <102>; /* KEY_HOME */ Create a DT header which defines all the key code so that DT key bindings can use it as follows: linux,code = <KEY_HOME>; Signed-off-by: Laxman Dewangan <ldewangan@nvidia.com> Reviewed-by: Stephen Warren <swarren@nvidia.com> Signed-off-by: Rob Herring <rob.herring@calxeda.com> | |||
 |
index : litmus-rt-edfsc.git | |
| LITMUS^RT with the EDF-SC plugin for Real-Time Systems journal paper | Zelin Tong |
| aboutsummaryrefslogtreecommitdiffstats |