From mboxrd@z Thu Jan 1 00:00:00 1970 From: Stephen Warren Date: Mon, 12 Dec 2011 11:31:36 -0700 Subject: [U-Boot] [PATCH 4/6] tegra: Add tegra keyboard support In-Reply-To: References: <1322881071-11148-1-git-send-email-sjg@chromium.org> <1322881071-11148-5-git-send-email-sjg@chromium.org> <4EDFE259.9080201@nvidia.com> <4EE64135.5070300@nvidia.com> Message-ID: <4EE64888.9030703@nvidia.com> List-Id: MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit To: u-boot@lists.denx.de On 12/12/2011 11:10 AM, Simon Glass wrote: > On Mon, Dec 12, 2011 at 10:00 AM, Stephen Warren wrote: >> On 12/08/2011 02:56 PM, Simon Glass wrote: ... >> I'd like to ask for comments in linux-input in case they have any other >> ideas, e.g. whether a set of separately documented modifier mapping >> properties makes sense. If not, I suppose the following set of >> properties would suffice: >> >> nvidia,keycode-plain >> nvidia,keycode-fn >> u-boot,keycode-shift >> u-boot,keycode-ctrl >> >> (although the last two seem to want both nvidia, and u-boot, prefixes) > > OK. Since this seems to be a kernel issue and Nvidia-specific can I > ask if you can please send this email? I will wait for confirmation > that this is OK before going further. OK, I'll send the email. I would like to point out though that this is neither a kernel issue nor NVIDIA-specific: It's a device tree issue dealing with how to best represent certain HW features, and it will apply equally to any HW that has a keyboard with modifier keys; essentially all of them. -- nvpublic