From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S932778AbcKVKWY (ORCPT ); Tue, 22 Nov 2016 05:22:24 -0500 Received: from fllnx209.ext.ti.com ([198.47.19.16]:46205 "EHLO fllnx209.ext.ti.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S932701AbcKVKWW (ORCPT ); Tue, 22 Nov 2016 05:22:22 -0500 Subject: Re: [PATCH 1/3] ARM: davinci: hawk: fix mmc card detect gpio To: Axel Haslam References: <20161121161541.27048-1-ahaslam@baylibre.com> <20161121161541.27048-2-ahaslam@baylibre.com> <8ced1194-4c68-7385-1594-0983855e7c89@ti.com> CC: Kevin Hilman , , From: Sekhar Nori Message-ID: <8d75e58f-8b2f-fac8-81e1-d02b0b392423@ti.com> Date: Tue, 22 Nov 2016 15:51:51 +0530 User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:45.0) Gecko/20100101 Thunderbird/45.4.0 MIME-Version: 1.0 In-Reply-To: Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: 7bit Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Tuesday 22 November 2016 03:40 PM, Axel Haslam wrote: > On Tue, Nov 22, 2016 at 10:53 AM, Sekhar Nori wrote: >> On Monday 21 November 2016 09:45 PM, Axel Haslam wrote: >>> The card detect gpio on the hawk board is gpio4_0 and not gpio3_12 >>> >>> Signed-off-by: Axel Haslam >> >> The LCDK and HawkBoard are different boards. The HawkBoard schematic >> from eLinux.org page is broken, but looking for it on the net, I found >> one and the MMC/SD CD pin in that schematic is indeed connected to GPIO3_12. >> >> So I believe the original code is correct. > > mmm, ok, the lcdk is booted using the hawk board file, I think this is just a coincidence. The LCDK came after the hawkboard as its replacement, and I guess there was some effort to derive out of hawkboard design. But they are not 100% software compatible, like you are discovering now. > so we should differentiate the two boards? Yes. > or should we just live with inconsistencies on the lcdk? Not sure what you mean by "live with inconsistencies on the lcdk". The two boards need to be treated as close cousins, but independent boards. Thanks, Sekhar