Received: by 10.223.176.5 with SMTP id f5csp637412wra; Tue, 30 Jan 2018 17:00:08 -0800 (PST) X-Google-Smtp-Source: AH8x226S9wQ7zm+Y5UnnMdHDjOlgdTjF3O0g96jilTQIiLpW3+CRQSVFU3mHzeH2LEl6IW10jNl3 X-Received: by 2002:a17:902:e81:: with SMTP id 1-v6mr26291770plx.235.1517360407910; Tue, 30 Jan 2018 17:00:07 -0800 (PST) ARC-Seal: i=1; a=rsa-sha256; t=1517360407; cv=none; d=google.com; s=arc-20160816; b=MiUIKUXxhP9MkwGt0vZ+Xb4FYrODZSGofPmNqamh/m79zXuyUghFa/WW+nu2Ff85n0 BO+pt7OgcMcm3/ac7iBu6pVX4WtLZJYjED7sb8tdgavElBnPEzvPbAq8J2C5hjSjh9hi Csi5Njos7dIZt3WFXKa+jmTT6HPr4z2hFSZC3kwkw4/yQXhCreCcyWlAvTEi/ie6raTn Xeg0URMwWsgACz9y31D8BHTgZcRGaZ16u/BgbhXR3zR9MdekheG1dUa6Ns/XxaX4Q2cd U/aK3M45iPjdwSgmnn4CESYA/kViXv+OsRCv1L942294KUh49AlNCs3Fclu56j86Er4P XkeA== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:sender:content-transfer-encoding:mime-version :references:in-reply-to:message-id:date:subject:cc:to:from :dkim-signature:arc-authentication-results; bh=vDdzboCXGLr73ddvxQPznL4/7FOFWTcU0WdJ+03IS64=; b=y+88APdlUR4RKfIqzE/ZIxorVwMKXUIC76LOz+1DSRld9Kbc/3AuOw6OFyNE6rnYf4 AwTPELIkkENg1rTKkNaLji91r/aoeNcFOQUJiykaOkdLo/uaHNOwemRpEVks64qbE4F9 D3tG2NuDHsxF3ojaA/OVO0WAKZQmiiq6GvBF0XvsjLOdvEQTpk+5hkWgiWNC/tTaNTlt Z70VB7e0ortiN/3GYiE4eMAaiDfxy+X0lOVbRT6gmazPMTMBRxdC5E0MPa6G+mx8SqTh fsv9GDehUkuGcN+HwFA9RgVEUI2VUJ/8a7sHIiyIpYCl/DHs0q4OxJnf0fKPnFBIqA3M f18g== ARC-Authentication-Results: i=1; mx.google.com; dkim=pass header.i=@gmail.com header.s=20161025 header.b=GhSQSBB1; spf=pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org; dmarc=pass (p=NONE sp=NONE dis=NONE) header.from=gmail.com Return-Path: Received: from vger.kernel.org (vger.kernel.org. [209.132.180.67]) by mx.google.com with ESMTP id z3-v6si11643777plo.815.2018.01.30.16.59.53; Tue, 30 Jan 2018 17:00:07 -0800 (PST) Received-SPF: pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) client-ip=209.132.180.67; Authentication-Results: mx.google.com; dkim=pass header.i=@gmail.com header.s=20161025 header.b=GhSQSBB1; spf=pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org; dmarc=pass (p=NONE sp=NONE dis=NONE) header.from=gmail.com Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S932248AbeAaAFu (ORCPT + 99 others); Tue, 30 Jan 2018 19:05:50 -0500 Received: from mail-wm0-f66.google.com ([74.125.82.66]:33416 "EHLO mail-wm0-f66.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1752824AbeAaAFg (ORCPT ); Tue, 30 Jan 2018 19:05:36 -0500 Received: by mail-wm0-f66.google.com with SMTP id x4so5922605wmc.0; Tue, 30 Jan 2018 16:05:35 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=from:to:cc:subject:date:message-id:in-reply-to:references :mime-version:content-transfer-encoding; bh=vDdzboCXGLr73ddvxQPznL4/7FOFWTcU0WdJ+03IS64=; b=GhSQSBB1FhksJ77gH0HcIGfS/+o27fTz9+OL9AUxWMEYxsnN/neRk4xa3RBLXah89M CU/ljPSthHO8lOkJPjJQItZ0CLSSZO4YehoXuYYPRGVEHF2rXh1vmsufdZzT/uOziCGj Ow/sgvtpHmvowFKYx8zMcFa+UMFmqO0NxsvUtTtrgnnWkxBEt6Hjh66AXcBi1TnN4Xmm D++FhqnEvMqcMOXv2AJhke+ouWt2W8DcDZl3ue0v7dTYYz0uWpNzlU5M4GoMYvAiX7fm 2L4/2Vrvf/VU3OuyRGjjHNOwQKROrhnne+5IZZ2xMdZeiK+BSZogqFvvLQD6h53qpTEs x8dg== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:from:to:cc:subject:date:message-id:in-reply-to :references:mime-version:content-transfer-encoding; bh=vDdzboCXGLr73ddvxQPznL4/7FOFWTcU0WdJ+03IS64=; b=HCyJTSG/wiHLy9hSbM/1kAO3eBl0nKswrZ6yf+uIkBVkZzE2En54ARrU89Us6fNele W/kdFf3XSNSplUCnYt9Sp6LMakLiWDZ6VTiNVJKli1XBUDNHZFHNISqd1gOjjLCjLapc R7zAtFAt1kN0htIH/4XA7TBzAfu8E7mkUjWfaq8ZzKgZOeKt9piAIJdNohqldj2mcrlZ P+m0djF9vQuzAG6T/PejWo8LuAXrAlZ3Gny6uRpzNOChrksfkX7rCc/J+AW2S6oTg3MI kqA8lBw7Cybp4nhvUeUELtXxJne58dhGZn8ep+Je6XeKql7eHNqssCf5bUxpPrznLNFv n4xw== X-Gm-Message-State: AKwxytexYYzcguXPjxfaFgNZqLzFQFla6SUqoQfMRmnGRaBFklhjVsUo 8g1BLJEQruq2cPtk3i064DzJxECR X-Received: by 10.28.109.154 with SMTP id b26mr3028157wmi.0.1517357134560; Tue, 30 Jan 2018 16:05:34 -0800 (PST) Received: from localhost.localdomain (vno44-1-88-172-188-148.fbx.proxad.net. [88.172.188.148]) by smtp.gmail.com with ESMTPSA id 204sm16652610wmx.0.2018.01.30.16.05.32 (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Tue, 30 Jan 2018 16:05:33 -0800 (PST) From: =?UTF-8?q?Beno=C3=AEt=20Th=C3=A9baudeau?= To: linux-kernel@vger.kernel.org, devicetree@vger.kernel.org, linux-arm-kernel@lists.infradead.org, Russell King , Mark Rutland , Rob Herring , Fabio Estevam , Sascha Hauer , Shawn Guo Cc: =?UTF-8?q?Uwe=20Kleine-K=C3=B6nig?= , Michael Nazzareno Trimarchi , =?UTF-8?q?Beno=C3=AEt=20Th=C3=A9baudeau?= Subject: [PATCH v2 2/2] ARM: dts: imx25-pinfunc: Always set SION for eSDHC CMD Date: Wed, 31 Jan 2018 01:05:14 +0100 Message-Id: <20180131000514.5286-2-benoit.thebaudeau.dev@gmail.com> X-Mailer: git-send-email 2.14.1 In-Reply-To: <20180131000514.5286-1-benoit.thebaudeau.dev@gmail.com> References: <20180131000514.5286-1-benoit.thebaudeau.dev@gmail.com> MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit Sender: linux-kernel-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org The eSDHC does not work properly if the SION bit is not set for the bidirectional CMD signal, whatever the eSDHC instance and the selected pad. Therefore, setting SION is mandatory for all eSDHC CMD ports. Do this for MX25_PAD_*__ESDHCn_CMD in imx25-pinfunc.h in order to enforce this behavior for all boards. This had already been done for eSDHC1, but not for eSDHC2. Also, define MX25_PAD_FEC_MDC__ESDHC2_CMD so that all the possible cases are covered from now on. Cc: Uwe Kleine-König Signed-off-by: Benoît Thébaudeau Reviewed-by: Fabio Estevam --- Changes v1 -> v2: - Update eSDHC instance and port naming following the addition of "ARM: dts: imx25-pinfunc: Use consistent naming for eSDHC". - Reference the more verbose comment for MX25_PAD_SD1_CMD__ESDHC1_CMD instead of copying the same less detailed comment everywhere (suggested by Uwe). --- arch/arm/boot/dts/imx25-pinfunc.h | 18 +++++++++++------- 1 file changed, 11 insertions(+), 7 deletions(-) diff --git a/arch/arm/boot/dts/imx25-pinfunc.h b/arch/arm/boot/dts/imx25-pinfunc.h index 2915c65a13c9..71a61c4c984f 100644 --- a/arch/arm/boot/dts/imx25-pinfunc.h +++ b/arch/arm/boot/dts/imx25-pinfunc.h @@ -236,7 +236,8 @@ #define MX25_PAD_LD8__LD8 0x0e8 0x2e0 0x000 0x00 0x000 #define MX25_PAD_LD8__UART4_RXD 0x0e8 0x2e0 0x570 0x02 0x000 #define MX25_PAD_LD8__FEC_TX_ERR 0x0e8 0x2e0 0x000 0x05 0x000 -#define MX25_PAD_LD8__ESDHC2_CMD 0x0e8 0x2e0 0x4e0 0x06 0x000 +/* See the comment for MX25_PAD_SD1_CMD__ESDHC1_CMD. */ +#define MX25_PAD_LD8__ESDHC2_CMD 0x0e8 0x2e0 0x4e0 0x16 0x000 #define MX25_PAD_LD9__LD9 0x0ec 0x2e4 0x000 0x00 0x000 #define MX25_PAD_LD9__UART4_TXD 0x0ec 0x2e4 0x000 0x02 0x000 @@ -316,7 +317,8 @@ #define MX25_PAD_CSI_D5__CSPI3_RDY 0x12c 0x324 0x000 0x07 0x000 #define MX25_PAD_CSI_D6__CSI_D6 0x130 0x328 0x000 0x00 0x000 -#define MX25_PAD_CSI_D6__ESDHC2_CMD 0x130 0x328 0x4e0 0x02 0x001 +/* See the comment for MX25_PAD_SD1_CMD__ESDHC1_CMD. */ +#define MX25_PAD_CSI_D6__ESDHC2_CMD 0x130 0x328 0x4e0 0x12 0x001 #define MX25_PAD_CSI_D6__SIM1_PD0 0x130 0x328 0x000 0x04 0x000 #define MX25_PAD_CSI_D6__GPIO_1_31 0x130 0x328 0x000 0x05 0x000 @@ -419,11 +421,11 @@ #define MX25_PAD_UART2_CTS__GPIO_4_29 0x18c 0x384 0x000 0x05 0x000 /* - * Removing the SION bit from MX25_PAD_SD1_CMD__ESDHC1_CMD breaks detecting an - * SD card. According to the i.MX25 reference manual (e.g. Figure 23-2 in - * IMX25RM Rev. 2 from 01/2011) this pin is bidirectional. So it seems to be a - * silicon bug that configuring the ESDHC1_CMD function doesn't enable the input - * path for this pin. + * Removing the SION bit from MX25_PAD_*__ESDHCn_CMD breaks detecting an SD + * card. According to the i.MX25 reference manual (e.g. Figure 23-2 in IMX25RM + * Rev. 2 from 01/2011) this pin is bidirectional. So it seems to be a silicon + * bug that configuring the ESDHCn_CMD function doesn't enable the input path + * for this pin. * This might have side effects for other hardware units that are connected to * that pin and use the respective function as input. */ @@ -496,6 +498,8 @@ #define MX25_PAD_KPP_COL3__GPIO_3_4 0x1c4 0x3bc 0x000 0x05 0x000 #define MX25_PAD_FEC_MDC__FEC_MDC 0x1c8 0x3c0 0x000 0x00 0x000 +/* See the comment for MX25_PAD_SD1_CMD__ESDHC1_CMD. */ +#define MX25_PAD_FEC_MDC__ESDHC2_CMD 0x1c8 0x3c0 0x4e0 0x11 0x002 #define MX25_PAD_FEC_MDC__AUD4_TXD 0x1c8 0x3c0 0x464 0x02 0x001 #define MX25_PAD_FEC_MDC__GPIO_3_5 0x1c8 0x3c0 0x000 0x05 0x000 -- 2.14.1