Received: by 2002:a05:6a10:22f:0:0:0:0 with SMTP id 15csp608457pxk; Thu, 3 Sep 2020 08:09:28 -0700 (PDT) X-Google-Smtp-Source: ABdhPJxWH9a4mEsC7d++nS0gocUy7qVXUP2HnTQI01r7gy8bpZ13MyqrxyANRpAammt9xNRHbQeb X-Received: by 2002:a17:907:206a:: with SMTP id qp10mr2692404ejb.497.1599145768774; Thu, 03 Sep 2020 08:09:28 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; t=1599145768; cv=none; d=google.com; s=arc-20160816; b=wDk8Dmot4RQ9meHBOa92TzMSmSwjPXGqROz9YvwZ7pnAP8BCvhoy3wWb6k4/ezYE3w rm2t7JCzZkbLShip+B/xIDL0yJgwkYlI6J+GjOVVf7N7JTOTaSBKfBLAjVdO2xYZsZr2 Nlo0FPFxTx5/BxbgIjBwIzRE6PIBol9C/SsfliSyE+rHQcRZy7Pv5d3XZVrN8FfvXe8R tqjVp/FeLK4MWDZAn0PKeHIgpFkQ0CkdtZIiM/Vjpi4xheobHr1beGmYyIs/KP8t99Ws 7MUHvNSspLo14hmYmzOSPG35KudXmcSDNBUiGoBWcyKCBExkpFB3YBAKWxiJlQdPj9zl TMxw== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:sender:references:in-reply-to:message-id:date :subject:cc:to:from; bh=oxoJxoV8XtLtB4Bd6KEf2HfyX8qczv4bjI1KW/6ciNE=; b=dj3dKpOQyzcvARsxv74kdSrAm/UanO+jsr/RbGIAMTzKOl2V7Lxont3sSAFRZq+AYt ub6UQH2/5aY6aXlYwbBPgVSNi+pFfrO14n3vxem1T6gioUr1xE54cczk38KEDvChGVC6 5fuMb62BO3vVVyK+Y1GNiscBjRg0HvMzFlgpK81srzjnW8ce8B0GF/Ewo2DbfODKoQr0 07wWjPlMiZ1AfrsQmS+6e9FfV9OHAy03AHguzVyl4uVJ8d04jv5ltYBVALPlmM7+ci2X oqH34ch3PXDcOS+Ik8gLSzM0oYnI4otFcNLLOJjJCdzaeTB3ZA5hQVxyucQtkGgIt7oC 3w+g== ARC-Authentication-Results: i=1; mx.google.com; spf=pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 23.128.96.18 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org Return-Path: Received: from vger.kernel.org (vger.kernel.org. [23.128.96.18]) by mx.google.com with ESMTP id qt8si2051306ejb.159.2020.09.03.08.09.04; Thu, 03 Sep 2020 08:09:28 -0700 (PDT) Received-SPF: pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 23.128.96.18 as permitted sender) client-ip=23.128.96.18; Authentication-Results: mx.google.com; spf=pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 23.128.96.18 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1729161AbgICPHl (ORCPT + 99 others); Thu, 3 Sep 2020 11:07:41 -0400 Received: from alexa-out.qualcomm.com ([129.46.98.28]:22454 "EHLO alexa-out.qualcomm.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1729495AbgICPFi (ORCPT ); Thu, 3 Sep 2020 11:05:38 -0400 Received: from ironmsg07-lv.qualcomm.com (HELO ironmsg07-lv.qulacomm.com) ([10.47.202.151]) by alexa-out.qualcomm.com with ESMTP; 03 Sep 2020 08:05:32 -0700 Received: from ironmsg02-blr.qualcomm.com ([10.86.208.131]) by ironmsg07-lv.qulacomm.com with ESMTP/TLS/AES256-SHA; 03 Sep 2020 08:05:31 -0700 Received: from c-skakit-linux.ap.qualcomm.com (HELO c-skakit-linux.qualcomm.com) ([10.242.51.242]) by ironmsg02-blr.qualcomm.com with ESMTP; 03 Sep 2020 20:35:05 +0530 Received: by c-skakit-linux.qualcomm.com (Postfix, from userid 2344709) id B0B154435; Thu, 3 Sep 2020 20:35:04 +0530 (IST) From: satya priya To: Bjorn Andersson Cc: Matthias Kaehlcke , gregkh@linuxfoundation.org, Andy Gross , Rob Herring , linux-arm-msm@vger.kernel.org, devicetree@vger.kernel.org, linux-kernel@vger.kernel.org, akashast@codeaurora.org, rojay@codeaurora.org, msavaliy@qti.qualcomm.com, satya priya Subject: [PATCH V4 2/4] arm64: dts: qcom: sc7180: Improve the pin config settings for CTS and TX Date: Thu, 3 Sep 2020 20:34:56 +0530 Message-Id: <1599145498-20707-3-git-send-email-skakit@codeaurora.org> X-Mailer: git-send-email 2.7.4 In-Reply-To: <1599145498-20707-1-git-send-email-skakit@codeaurora.org> References: <1599145498-20707-1-git-send-email-skakit@codeaurora.org> Sender: linux-kernel-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Configure no-pull for CTS, as this is driven by BT do not specify any pull in order to not conflict with BT pulls. Remove output-high from CTS and TX as this is not really required. During bringup to fix transfer failures this was added to match with console uart settings. Probably some boot loader config was missing then. As it is working fine now, remove it. Signed-off-by: satya priya Reviewed-by: Akash Asthana --- Changes in V4: - This is newly added in V4 to separate the improvements in pin settings and wakeup related changes. arch/arm64/boot/dts/qcom/sc7180-idp.dts | 14 ++++++-------- 1 file changed, 6 insertions(+), 8 deletions(-) diff --git a/arch/arm64/boot/dts/qcom/sc7180-idp.dts b/arch/arm64/boot/dts/qcom/sc7180-idp.dts index d8b5507..cecac3e 100644 --- a/arch/arm64/boot/dts/qcom/sc7180-idp.dts +++ b/arch/arm64/boot/dts/qcom/sc7180-idp.dts @@ -474,32 +474,30 @@ &qup_uart3_default { pinconf-cts { /* - * Configure a pull-down on 38 (CTS) to match the pull of - * the Bluetooth module. + * Configure no-pull on CTS. As this is driven by BT, do not + * specify any pull in order to not conflict with BT pulls. */ pins = "gpio38"; - bias-pull-down; - output-high; + bias-disable; }; pinconf-rts { - /* We'll drive 39 (RTS), so no pull */ + /* We'll drive RTS, so no pull */ pins = "gpio39"; drive-strength = <2>; bias-disable; }; pinconf-tx { - /* We'll drive 40 (TX), so no pull */ + /* We'll drive TX, so no pull */ pins = "gpio40"; drive-strength = <2>; bias-disable; - output-high; }; pinconf-rx { /* - * Configure a pull-up on 41 (RX). This is needed to avoid + * Configure a pull-up on RX. This is needed to avoid * garbage data when the TX pin of the Bluetooth module is * in tri-state (module powered off or not driving the * signal yet). -- QUALCOMM INDIA, on behalf of Qualcomm Innovation Center, Inc. is a member of Code Aurora Forum, hosted by The Linux Foundation