Received: by 2002:a05:6a10:22f:0:0:0:0 with SMTP id 15csp1054311pxk; Thu, 10 Sep 2020 06:04:04 -0700 (PDT) X-Google-Smtp-Source: ABdhPJwu3evlTMkeUXyx+lOwiXh09dLGD9lzrc2YgxSeSKd13b4nA0fM0FXijlV9e1YWsLLFE/Oz X-Received: by 2002:a05:6402:615:: with SMTP id n21mr8728486edv.59.1599743043822; Thu, 10 Sep 2020 06:04:03 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; t=1599743043; cv=none; d=google.com; s=arc-20160816; b=nxM5tke/iJJmC843dCUgyn1OCUzWvj/o9py4NW0tompGng+sjJLf3JW5oDuM7C/ZTO 3TrZZy8BBD2LmHUGgt8w3f3nx+Zfjgw5aRKn6EX+3+xa16qf34UnaVnUrPXKTSUv+XCn bKxEnDeC6PvGpXiA/jrzemmwT9Tl0U/k9yFzcRjLBMkmP75LgcHypO/cGZXBxypuRHw8 oeWenF/rgay7R2UNiZQt+6CHMHofZZVICP00RDA23L0lK3BrGDwZzM+tRnFIvugGDa9f 3FkR7zkIhic18MWFMelMvVju4ykxjOPLlNkEbIMbBSihed1t80DBh+zEgv8RgKs/+XyS 2WSw== 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=b+FNZgFkzB493UXKWW8EW5usMq9laH674flaJq5kIkA=; b=KcC0zsx8SBnMXns/8dNbOFzfanwEy2hyUCblCYtBt7aSRfEcFw7U7ewU6vji6f2RA2 QktYx1Stmf0m8dl7cb7pi0GI5aZopRSR+f2oCGW8krTbOvt0utgX97dy2SIpZN/4nK37 iDShb+xvzs+5VB1OZLKL1Qmuhao4bylPZiVhJ7kLja0AA1Ps6c8sTClBhPf7/DYr14gY l/8IG2z+O3m0ZYsR9RwqBrRXcyNsEhxEgdsrGWje3vxCbnUAQ9lXQlC5mIJgIaj2hybh uhKFcfBpxv43IRm83Kl1ZN5jv7T2DfaXKDNVjnOdcjsNbVBW+pdMVJ02Ykf3sOkaK8lI DjtQ== 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 ay26si3467673edb.269.2020.09.10.06.03.41; Thu, 10 Sep 2020 06:04:03 -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 S1730361AbgIJNCV (ORCPT + 99 others); Thu, 10 Sep 2020 09:02:21 -0400 Received: from alexa-out.qualcomm.com ([129.46.98.28]:15790 "EHLO alexa-out.qualcomm.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1730717AbgIJMzC (ORCPT ); Thu, 10 Sep 2020 08:55:02 -0400 Received: from ironmsg07-lv.qualcomm.com (HELO ironmsg07-lv.qulacomm.com) ([10.47.202.151]) by alexa-out.qualcomm.com with ESMTP; 10 Sep 2020 05:55:01 -0700 Received: from ironmsg01-blr.qualcomm.com ([10.86.208.130]) by ironmsg07-lv.qulacomm.com with ESMTP/TLS/AES256-SHA; 10 Sep 2020 05:55:00 -0700 Received: from c-skakit-linux.ap.qualcomm.com (HELO c-skakit-linux.qualcomm.com) ([10.242.51.242]) by ironmsg01-blr.qualcomm.com with ESMTP; 10 Sep 2020 18:24:31 +0530 Received: by c-skakit-linux.qualcomm.com (Postfix, from userid 2344709) id 4E54ADB1; Thu, 10 Sep 2020 18:24:30 +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, dianders@chromium.org, satya priya Subject: [PATCH V5 1/4] arm64: dts: qcom: sc7180: Improve the pin config settings for CTS and TX Date: Thu, 10 Sep 2020 18:23:55 +0530 Message-Id: <1599742438-16811-2-git-send-email-skakit@codeaurora.org> X-Mailer: git-send-email 2.7.4 In-Reply-To: <1599742438-16811-1-git-send-email-skakit@codeaurora.org> References: <1599742438-16811-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 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 Reviewed-by: Matthias Kaehlcke --- Changes in V4: - This is newly added in V4 to separate the improvements in pin settings and wakeup related changes. Changes in V5: - As per Doug's comment configured pull-down for CTS pin as earlier. arch/arm64/boot/dts/qcom/sc7180-idp.dts | 10 ++++------ 1 file changed, 4 insertions(+), 6 deletions(-) diff --git a/arch/arm64/boot/dts/qcom/sc7180-idp.dts b/arch/arm64/boot/dts/qcom/sc7180-idp.dts index d8b5507..04888df 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 + * Configure a pull-down on CTS to match the pull of * the Bluetooth module. */ pins = "gpio38"; bias-pull-down; - output-high; }; 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