From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1754308Ab3CKSro (ORCPT ); Mon, 11 Mar 2013 14:47:44 -0400 Received: from avon.wwwdotorg.org ([70.85.31.133]:47935 "EHLO avon.wwwdotorg.org" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1752738Ab3CKSrl (ORCPT ); Mon, 11 Mar 2013 14:47:41 -0400 Message-ID: <513E26C9.4080706@wwwdotorg.org> Date: Mon, 11 Mar 2013 12:47:37 -0600 From: Stephen Warren User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:17.0) Gecko/20130106 Thunderbird/17.0.2 MIME-Version: 1.0 To: Laxman Dewangan CC: "linux-arm-kernel@lists.infradead.org" , "linux-tegra@vger.kernel.org" , "linux-kernel@vger.kernel.org" , Peter De Schrijver Subject: Re: [PATCH V2 4/5] ARM: DT: tegra114: add KBC controller DT entry References: <1362852678-13421-1-git-send-email-ldewangan@nvidia.com> <1362852678-13421-5-git-send-email-ldewangan@nvidia.com> <513E17C1.1070305@wwwdotorg.org> <513E1B7E.8090203@nvidia.com> In-Reply-To: <513E1B7E.8090203@nvidia.com> X-Enigmail-Version: 1.4.6 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On 03/11/2013 11:59 AM, Laxman Dewangan wrote: > On Monday 11 March 2013 11:13 PM, Stephen Warren wrote: >> On 03/09/2013 11:11 AM, Laxman Dewangan wrote: >>> NVIDIA's Tegra114 SoCs have the matrix keyboard controller which >>> supports 11x8 type of matrix. The number of rows and columns >>> are configurable. >>> >>> Add DT entry for KBC controller with compatibility as >>> "nvidia,tegra114-kbc", >>> "nvidia,tegra20-kbc". >> I thought the HW really wasn't compatible with Tegra20 due to the >> reduced number of rows/columns/pins supported? > > Hw controller is really compatible. Only thing is that there is no > physical pins on SoC for KBC-ROW11 to KBC-ROW15. > Because, there is no physical pins for ROW11 to ROW15, we asked to > remove programming/reference this rows from TRM of T114 to consistent > with SoCs. I think that makes the HW incompatible. If you only have knowledge of Tegra20/30, you can assume that there are more rows/pins/columns than there actually are. Applying those same validation restrictions on Tegra114 will yield validation that isn't strict enough; invalid values could be accepted.