Received: by 2002:ac0:a5a6:0:0:0:0:0 with SMTP id m35-v6csp2990681imm; Mon, 24 Sep 2018 13:38:08 -0700 (PDT) X-Google-Smtp-Source: ACcGV62844lNsNTcG3HtLMafyNIqNgmQrqqXXiGrEtZncyLYbm2nq9b6EqMrcZKBEO+WDr8F31w4 X-Received: by 2002:a17:902:c85:: with SMTP id 5-v6mr401914plt.141.1537821488020; Mon, 24 Sep 2018 13:38:08 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; t=1537821487; cv=none; d=google.com; s=arc-20160816; b=BBshUngqjbK/ZJp3gmfDLks4A77hL7r9ykGTvV4jwyf5KSj+9YADIOnb937Af1u8Bg ZHHvXLJhFyk4AzocN0fMEDdwaez+wOoMdXE7fRO6kukKnZ9PL8MJ1E0eFakPDqu5GQe+ VS3Pr1pTg05BlaX0goGKurR6NsvBbOxGdFy1mWDwiE+slfbf5NZzwuu9w0zSuOBmFm// obpIWHoOZhWOzA/IaVVYUl6rIEsQEGwEhy7ygapfFUu7wzN+/V6T0zsfCe0ZUvGYptPQ QYCAXTwa/6+X/TmjRhc2pmevLhdBEQ2hmmW1ftEG3x7k6NTjWzAcjjfXpqe2ceSuso9+ wgqg== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:sender:message-id:from:cc:to:subject :content-transfer-encoding:mime-version:references:in-reply-to :user-agent:date:dkim-signature; bh=nnqqUrXYArlVoT3RtJCvHHD2Y6DiO/ed09vGXHTBKkg=; b=covIGvz6nuAeFvjjDnDlVva9HBXf0Zfwn0wMpAWm1WOeWdbGdC5tQx7nrMTw7QO7jE 2YfEPsWuZxw9PrAF+NsUvvkisrFPZoxsPqc+ZwZa4fhTW3kn4/TFjs9JSCn8twp67af4 rJrdBnVOv99PC4CA3d3PI/Ht0c7o2kOJYCF69tRWiUdemeDYBZxunNMo6EI3nv9B9UUb jNF42agM/+1kfZ9IZwFQ/rq1r2NWfwWti2PcKDMbh0Rn+uAkqBkS2ya3cwbEfsrZiilF 92VPEZITnODhHym4u9blO1kN037+7rRlD+L94ZSUsSmDzFY4o0NGHQWkWnaokGwdeZGq 09Xg== ARC-Authentication-Results: i=1; mx.google.com; dkim=fail header.i=@gmail.com header.s=20161025 header.b=KjjYSX2S; 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=fail (p=NONE sp=QUARANTINE 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 d12-v6si255080plo.210.2018.09.24.13.37.52; Mon, 24 Sep 2018 13:38:07 -0700 (PDT) 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=fail header.i=@gmail.com header.s=20161025 header.b=KjjYSX2S; 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=fail (p=NONE sp=QUARANTINE dis=NONE) header.from=gmail.com Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1727555AbeIYCl3 (ORCPT + 99 others); Mon, 24 Sep 2018 22:41:29 -0400 Received: from mail-wm1-f66.google.com ([209.85.128.66]:34027 "EHLO mail-wm1-f66.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1727408AbeIYCl3 (ORCPT ); Mon, 24 Sep 2018 22:41:29 -0400 Received: by mail-wm1-f66.google.com with SMTP id j25-v6so10868738wmc.1; Mon, 24 Sep 2018 13:37:26 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=date:user-agent:in-reply-to:references:mime-version :content-transfer-encoding:subject:to:cc:from:message-id; bh=nnqqUrXYArlVoT3RtJCvHHD2Y6DiO/ed09vGXHTBKkg=; b=KjjYSX2SLoLrokm2QqdQ7XxXsV5RVQ9VZ8BAWOP3YQLQA08x2JookIQmEBZ8nbh6h7 AvE40yRzdKTTeuV4HITVVHp6YpFXzWY17JTZF7DVv6xTwYAQgsHZJa2rOgwrMsxwEgVu h0/+e0jGosKiXwtr7xFdn2asMwaUFhJGbuoXutua05BYBkFHYsRIlRr/M8xOzwTgVUkb WOA1UE22ohG4bzM7ZTLqUAWLyo58cX0QHSgEJlpbGBY5BxPkoKsdqkyqH4mv/X7Ov1cU xuKDrGoP9N0OIHN6BA+KNDq3w5DPuSc/oy8bVuIsz2kjGy68CQTX7ysQdj7l6Q63TJTg OOSg== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:date:user-agent:in-reply-to:references :mime-version:content-transfer-encoding:subject:to:cc:from :message-id; bh=nnqqUrXYArlVoT3RtJCvHHD2Y6DiO/ed09vGXHTBKkg=; b=oV97mSi9Q0MQ+QlOZ5MAlDKmH4NUlqHlc5utQ5EdYhdI/JWPqMMWujnwLbkkT+1gSp XJKXxejV5LmmD/OiXMBXtb3+d/PIB2fIdSHbhXOIpmN6sYeoM5EnVK+oClBbleNipTet YjYYLs2pvRtjyGfqC2vVF3hfxqLUA478UV8e6lQtisPX7M/50btIn9elNnC3A9Pis1Os pTAZPEmTtUBYLjypwGyDDmvzosaOph7Ey61FK1u5MA3BaDWh3n2Ol2x0KHc8ah0e98r2 qJQAgm2MP5d20O3ets89dbA4r2JhmEIBMkldn5xyXWQLHfjFa0sRHsCdVNN63ZrBAnz4 8JfA== X-Gm-Message-State: ABuFfojIuGNT4fC3v111Yvr7EjaWaebgPjiuaNCyvv3ejPdcGmyEtveV LCLlUOifBrLfga2qaSvI0g== X-Received: by 2002:a1c:1f87:: with SMTP id f129-v6mr58422wmf.153.1537821445399; Mon, 24 Sep 2018 13:37:25 -0700 (PDT) Received: from android-dhcp-8-1-0-d4-38-9c-a2-1f-05.home (host86-147-9-252.range86-147.btcentralplus.com. [86.147.9.252]) by smtp.gmail.com with ESMTPSA id v2-v6sm220798wrs.54.2018.09.24.13.37.24 (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Mon, 24 Sep 2018 13:37:24 -0700 (PDT) Date: Mon, 24 Sep 2018 21:37:22 +0100 User-Agent: K-9 Mail for Android In-Reply-To: <20180924185306.GO1367@tuxbook-pro> References: <20180812142413.20856-1-ctatlor97@gmail.com> <20180924185306.GO1367@tuxbook-pro> MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable Subject: Re: [PATCH v2] pinctrl: qcom: Add sdm660 pinctrl driver To: Bjorn Andersson CC: linux-arm-msm@vger.kernel.org, Linus Walleij , Rob Herring , Mark Rutland , linux-gpio@vger.kernel.org, devicetree@vger.kernel.org, linux-kernel@vger.kernel.org From: Craig Message-ID: Sender: linux-kernel-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On 24 September 2018 19:53:06 BST, Bjorn Andersson wrote: >On Sun 12 Aug 07:24 PDT 2018, Craig Tatlor wrote: > >> Add initial pinctrl driver to support pin configuration with >> pinctrl framework for sdm660=2E >> Based off CAF implementation=2E >>=20 >> Signed-off-by: Craig Tatlor >> --- >>=20 >> Changes from v1: >> Adds gpio-ranges property to bindings >>=20 >>=20 >> =2E=2E=2E/bindings/pinctrl/qcom,sdm660-pinctrl=2Etxt | 202 +++ > >As the DT binding part of the patch is significant, please split it >into >its own patch=2E > Right >> drivers/pinctrl/qcom/Kconfig | 10 + >> drivers/pinctrl/qcom/Makefile | 1 + >> drivers/pinctrl/qcom/pinctrl-sdm660=2Ec | 1451 >+++++++++++++++++ >> 4 files changed, 1663 insertions(+) >> create mode 100644 >Documentation/devicetree/bindings/pinctrl/qcom,sdm660-pinctrl=2Etxt >> create mode 100644 drivers/pinctrl/qcom/pinctrl-sdm660=2Ec >>=20 >> diff --git >a/Documentation/devicetree/bindings/pinctrl/qcom,sdm660-pinctrl=2Etxt >b/Documentation/devicetree/bindings/pinctrl/qcom,sdm660-pinctrl=2Etxt >[=2E=2E] >> +- function: >> + Usage: required >> + Value type: >> + Definition: Specify the alternative function to be configured for >the >> + specified pins=2E Functions are only valid for gpio pins=2E >> + Valid values are: >> + >> + blsp_uart1, blsp_spi1, blsp_i2c1, blsp_uim1, atest_tsens, >> + bimc_dte1, dac_calib0, blsp_spi8, blsp_uart8, blsp_uim8, >> + qdss_cti_trig_out_b, bimc_dte0, dac_calib1, >qdss_cti_trig_in_b, >> + dac_calib2, atest_tsens2, atest_usb1, blsp_spi10, blsp_uart10, >> + blsp_uim10, atest_bbrx1, atest_usb13, atest_bbrx0, >atest_usb12, >> + mdp_vsync, edp_lcd, blsp_i2c10, atest_gpsadc1, atest_usb11, >> + atest_gpsadc0, edp_hot, atest_usb10, m_voc, dac_gpio, >atest_char, >> + cam_mclk, pll_bypassnl, qdss_stm7, blsp_i2c8, >qdss_tracedata_b, >> + pll_reset, qdss_stm6, qdss_stm5, qdss_stm4, atest_usb2, >cci_i2c, >> + qdss_stm3, dac_calib3, atest_usb23, atest_char3, dac_calib4, >> + qdss_stm2, atest_usb22, atest_char2, qdss_stm1, dac_calib5, >> + atest_usb21, atest_char1, dbg_out, qdss_stm0, dac_calib6, >> + atest_usb20, atest_char0, dac_calib10, qdss_stm10, >> + qdss_cti_trig_in_a, cci_timer4, blsp_spi6, blsp_uart6, >blsp_uim6, >> + blsp2_spi, qdss_stm9, qdss_cti_trig_out_a, dac_calib11, >> + qdss_stm8, cci_timer0, qdss_stm13, dac_calib7, cci_timer1, >> + qdss_stm12, dac_calib8, cci_timer2, blsp1_spi, qdss_stm11, >> + dac_calib9, cci_timer3, cci_async, dac_calib12, blsp_i2c6, >> + qdss_tracectl_a, dac_calib13, qdss_traceclk_a, dac_calib14, >> + dac_calib15, hdmi_rcv, dac_calib16, hdmi_cec, pwr_modem, >> + dac_calib17, hdmi_ddc, pwr_nav, dac_calib18, pwr_crypto, >> + dac_calib19, hdmi_hot, dac_calib20, dac_calib21, pci_e0, >> + dac_calib22, dac_calib23, dac_calib24, tsif1_sync, >dac_calib25, >> + sd_write, tsif1_error, blsp_spi2, blsp_uart2, blsp_uim2, >> + qdss_cti, blsp_i2c2, blsp_spi3, blsp_uart3, blsp_uim3, >blsp_i2c3, >> + uim3, blsp_spi9, blsp_uart9, blsp_uim9, blsp10_spi, blsp_i2c9, >> + blsp_spi7, blsp_uart7, blsp_uim7, qdss_tracedata_a, blsp_i2c7, >> + qua_mi2s, gcc_gp1_clk_a, ssc_irq, uim4, blsp_spi11, >blsp_uart11, >> + blsp_uim11, gcc_gp2_clk_a, gcc_gp3_clk_a, blsp_i2c11, >cri_trng0, >> + cri_trng1, cri_trng, qdss_stm18, pri_mi2s, qdss_stm17, >blsp_spi4, >> + blsp_uart4, blsp_uim4, qdss_stm16, qdss_stm15, blsp_i2c4, >> + qdss_stm14, dac_calib26, spkr_i2s, audio_ref, lpass_slimbus, >> + isense_dbg, tsense_pwm1, tsense_pwm2, btfm_slimbus, ter_mi2s, >> + qdss_stm22, qdss_stm21, qdss_stm20, qdss_stm19, gcc_gp1_clk_b, >> + sec_mi2s, blsp_spi5, blsp_uart5, blsp_uim5, gcc_gp2_clk_b, >> + gcc_gp3_clk_b, blsp_i2c5, blsp_spi12, blsp_uart12, blsp_uim12, >> + qdss_stm25, qdss_stm31, blsp_i2c12, qdss_stm30, qdss_stm29, >> + tsif1_clk, qdss_stm28, tsif1_en, tsif1_data, sdc4_cmd, >qdss_stm27, >> + qdss_traceclk_b, tsif2_error, sdc43, vfr_1, qdss_stm26, >tsif2_clk, >> + sdc4_clk, qdss_stm24, tsif2_en, sdc42, qdss_stm23, >qdss_tracectl_b, >> + sd_card, tsif2_data, sdc41, tsif2_sync, sdc40, mdp_vsync_p_b, >> + ldo_en, mdp_vsync_s_b, ldo_update, blsp11_uart_tx_b, >blsp11_uart_rx_b, >> + blsp11_i2c_sda_b, prng_rosc, blsp11_i2c_scl_b, uim2, uim1, >uim_batt, >> + pci_e2, pa_indicator, adsp_ext, ddr_bist, qdss_tracedata_11, >> + qdss_tracedata_12, modem_tsync, nav_dr, nav_pps, pci_e1, >gsm_tx, >> + qspi_cs, ssbi2, ssbi1, mss_lte, qspi_clk, qspi0, qspi1, qspi2, >qspi3, >> + gpio > >Please review this list, there are a few items in here that are not >valid functions in your driver=2E > Okay, will do >[=2E=2E] >> + >> +Example: >> + >> + tlmm: pinctrl@1010000 { >> + compatible =3D "qcom,sdm660-pinctrl"; >> + reg =3D <0x1010000 0x300000>; >> + interrupts =3D <0 208 0>; > >Replace the 0s in the interrupts specifier=2E Okay > >> + gpio-controller; >> + gpio-ranges =3D <&tlmm 0 0 114>; >> + #gpio-cells =3D <2>; >> + interrupt-controller; >> + #interrupt-cells =3D <2>; >> + >> + uart_console_active: uart_console_active { >> + mux { >> + pins =3D "gpio4", "gpio5"; >> + function =3D "blsp_uart8"; >> + }; >> + >> + config { >> + pins =3D "gpio4", "gpio5"; >> + drive-strength =3D <2>; >> + bias-disable; >> + }; >> + }; > >This example isn't valid=2E Please update it, or just drop the pinctrl >state from the example=2E > Right, will drop it >> + }; >> diff --git a/drivers/pinctrl/qcom/Kconfig >b/drivers/pinctrl/qcom/Kconfig >> index 195492033075=2E=2E091beadb8a1c 100644 >> --- a/drivers/pinctrl/qcom/Kconfig >> +++ b/drivers/pinctrl/qcom/Kconfig >> @@ -147,6 +147,16 @@ config PINCTRL_QCOM_SSBI_PMIC >> which are using SSBI for communication with SoC=2E Example >PMIC's >> devices are pm8058 and pm8921=2E >> =20 >> +config PINCTRL_SDM660 >> + tristate "Qualcomm Technologies Inc SDM660 pin controller >driver" >> + depends on GPIOLIB && OF >> + select PINCTRL_MSM >> + help >> + This is the pinctrl, pinmux, pinconf and gpiolib driver for >the >> + Qualcomm Technologies Inc TLMM block found on the Qualcomm >> + Technologies Inc SDM660 platform=2E >> + >> + > >Extra empty line Yeah > >> config PINCTRL_SDM845 >> tristate "Qualcomm Technologies Inc SDM845 pin controller >driver" >> depends on GPIOLIB && OF >> diff --git a/drivers/pinctrl/qcom/Makefile >b/drivers/pinctrl/qcom/Makefile >> index 0c6f3ddc296d=2E=2E9b08808a2f1c 100644 >> --- a/drivers/pinctrl/qcom/Makefile >> +++ b/drivers/pinctrl/qcom/Makefile >> @@ -19,4 +19,5 @@ obj-$(CONFIG_PINCTRL_QCOM_SPMI_PMIC) +=3D >pinctrl-spmi-gpio=2Eo >> obj-$(CONFIG_PINCTRL_QCOM_SPMI_PMIC) +=3D pinctrl-spmi-mpp=2Eo >> obj-$(CONFIG_PINCTRL_QCOM_SSBI_PMIC) +=3D pinctrl-ssbi-gpio=2Eo >> obj-$(CONFIG_PINCTRL_QCOM_SSBI_PMIC) +=3D pinctrl-ssbi-mpp=2Eo >> +obj-$(CONFIG_PINCTRL_SDM660) +=3D pinctrl-sdm660=2Eo >> obj-$(CONFIG_PINCTRL_SDM845) +=3D pinctrl-sdm845=2Eo >> diff --git a/drivers/pinctrl/qcom/pinctrl-sdm660=2Ec >b/drivers/pinctrl/qcom/pinctrl-sdm660=2Ec >> new file mode 100644 >> index 000000000000=2E=2Eded56111f168 >> --- /dev/null >> +++ b/drivers/pinctrl/qcom/pinctrl-sdm660=2Ec >> @@ -0,0 +1,1451 @@ >> +// SPDX-License-Identifier: GPL-2=2E0 >> +/* >> + * Copyright (c) 2016, The Linux Foundation=2E All rights reserved=2E >> + * Copyright (c) 2018, Craig Tatlor=2E >> + */ >> + >> +#include >> +#include >> +#include >> +#include >> + >> +#include "pinctrl-msm=2Eh" >> + >> +#define NORTH 0x00900000 >> +#define CENTER 0x00500000 >> +#define SOUTH 0x00100000 > >Please respin this on top of the QCS404 series, where we describe each >tile explicitly in DT=2E > >The three regions are: > >South: 0x03100000 size 0x300000 >Center: 0x03500000 size 0x300000 >North: 0x03900000 size 0x300000 Right, will do > >[=2E=2E] >> +static const unsigned int sdc1_clk_pins[] =3D { 114 }; >> +static const unsigned int sdc1_cmd_pins[] =3D { 115 }; >> +static const unsigned int sdc1_data_pins[] =3D { 116 }; >> +static const unsigned int sdc2_clk_pins[] =3D { 117 }; >> +static const unsigned int sdc2_cmd_pins[] =3D { 118 }; >> +static const unsigned int sdc2_data_pins[] =3D { 119 }; >> +static const unsigned int sdc1_rclk_pins[] =3D { 120 }; > >The numbering of these "fake" pins isn't significant, so please reorder >sdc1_rclk to follow the other sdc1 pins=2E Yup > >> + >> +enum sdm660_functions { >> + msm_mux_blsp_spi1, > >There's no harm in sorting this list, but it makes it easier to read=2E >> + Okay, will do, alphabetically I guess? >> +static const struct msm_function sdm660_functions[] =3D { >> + FUNCTION(blsp_spi1), > >Ditto=2E > >[=2E=2E] >> +static const struct msm_pingroup sdm660_groups[] =3D { >[=2E=2E] >> + SDC_QDSD_PINGROUP(sdc1_clk, 0x99a000, 13, 6), >> + SDC_QDSD_PINGROUP(sdc1_cmd, 0x99a000, 11, 3), >> + SDC_QDSD_PINGROUP(sdc1_data, 0x99a000, 9, 0), >> + SDC_QDSD_PINGROUP(sdc2_clk, 0x99b000, 14, 6), >> + SDC_QDSD_PINGROUP(sdc2_cmd, 0x99b000, 11, 3), >> + SDC_QDSD_PINGROUP(sdc2_data, 0x99b000, 9, 0), >> + SDC_QDSD_PINGROUP(sdc1_rclk, 0x99a000, 15, 0), > >Move the sdc1_rclk up to the other sdc1 groups=2E Right > >> +}; > >Regards, >Bjorn