From mboxrd@z Thu Jan 1 00:00:00 1970 From: Stephen Warren Date: Mon, 28 Apr 2014 17:23:57 -0600 Subject: [U-Boot] [Ac100] [PATCH v2 4/6] ARM: tegra: nvec: add keyboard support In-Reply-To: <1398561270-25091-5-git-send-email-danindrey@mail.ru> References: <[PATCH 0/3] ARM: tegra: add nvec keyboard support for paz00> <1398561270-25091-1-git-send-email-danindrey@mail.ru> <1398561270-25091-5-git-send-email-danindrey@mail.ru> Message-ID: <535EE30D.7020108@wwwdotorg.org> List-Id: MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit To: u-boot@lists.denx.de On 04/26/2014 07:14 PM, Andrey Danin wrote: > Signed-off-by: Andrey Danin > CC: Stephen Warren > CC: Marc Dietrich > CC: Julian Andres Klode > CC: ac100 at lists.launchpad.net > --- > Changes for v2: > - fixed incorrect keys handling in nvec-keyboard driver No patch description? Something isn't quite right with the device registration here. If U-Boot starts with stdin=serial, and then I "setenv stdin serial,tegra-nvec-kbc", then I can't use the keyboard. However, if I save the environment and reset, then nvec input works. Similarly, it gets confused if I remove and re-add tegra-nvec-kbc to $stdin. I've also observed quite a stuck keys, hangs, and failed requests: ERROR: nvec failed to perform request at .../drivers/i2c/tegra_nvec.c:166/nvec_do_request() But when it works, it's nice:-)