On Tue, Dec 27, 2011 at 10:19:30PM -0800, Olof Johansson wrote: > This adds a simple way to specify the ChromeOS-specific keyboard map > instead of the "standard" map that is used on other Tegra devices such > as Harmony-with-keyboard and Seaboard. > > I expect the number of different keyboard layouts to be quite limited, > and not many should be added over time. So instead of encoding the layout > in the device tree, with all the can of worms that entails w.r.t. agreeing > on a suitable binding, just add a property to specify that this is the > map to be used, and include it in the driver. > > If, over time, the number of mappings increase, the binding can be > updated to include a custom map as a new property, without having to > worry about backwards compatibility on existing devices. > I'd rather we did not make shortcuts and did the proper DT binding. Samsung folks want the similar thing so making a generic DT keymap parser and using it in the driver would be the best way. Another option is to simply loading proper keymap by the early userspace. Thanks. -- Dmitry -- To unsubscribe from this list: send the line "unsubscribe linux-tegra" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
