Received: by 2002:ac0:a5a6:0:0:0:0:0 with SMTP id m35-v6csp4061553imm; Tue, 25 Sep 2018 10:39:25 -0700 (PDT) X-Google-Smtp-Source: ACcGV60Zsb1Kux+b8gwTH+F7o9XvGxDqQm55LrHGrJiS+Dq2aSUZneeqp2l4MLIOuwIVWrIyZtQY X-Received: by 2002:a62:198e:: with SMTP id 136-v6mr2173456pfz.103.1537897164983; Tue, 25 Sep 2018 10:39:24 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; t=1537897164; cv=none; d=google.com; s=arc-20160816; b=VoDtA4QVKgHmG04b1IZzRztPbeZ8gn/I0ujcP3c93QmSnE/mOz73R4kHM0qdBaHX78 y2xC9bPT+0NiczkCGZN/pRM0WGJ97QCcUInPs5gg8BO1bTcn/cx+eLqaUGGLnhAmi9cy x2ftGiNIFSw1UWVf/BaYq7JE/AbUQQj0W0w+owCNQbvijQz6puib3LgDQInns6b8jXxM n1QceLVs7YMlRiDwC5i+gbgogNj8to3IqoEAqRLlJ2K2CihRECp57UQJarUCTENJFfdb 48PL3Us2gDiGmwlCLgRlFtW+434Tl61QuKjUmW/wPYDk3dBgbMsAHGn1R9p/CYR6ZTAL 1eDw== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:sender:to:references:in-reply-to:message-id:date :subject:cc:from:dkim-signature; bh=tKC/W6bifrWOQDRQ8NZQ3YbTITA/cPSy615ajYq1W5A=; b=VcxqOnGA+l8eogmP0dgq92JBRWiwD2caCf5f9oi7oUizO59Q1tpALIo2RG3vWJBaAR /EoQWzsbhlkyz7rHrA3b3JN8wT+7U9CK1pTq+DCTnxdT1io2MPjc1oS1jahJPnlomiWz liomg650ZDzG5x/idNI0wVg5YLXUxfVIJYnjBRQMi0puXjPljcs20bD/3m2/TfjMceJy m1Cx0LJBJjuIRFz60K2HnXNmhSacL8OXELMPceof80JS01v3dZpjSn78VRb9C5I+MUup iuIgs/Yn8CR2c3lZGjqPV9YwbQeTUibF+9U4khREh50HLj4GW2K7WjprWUTx8cUGsZOf xTdA== ARC-Authentication-Results: i=1; mx.google.com; dkim=fail header.i=@gmail.com header.s=20161025 header.b=hMD3owZ6; 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 o1-v6si2692063pfe.259.2018.09.25.10.39.09; Tue, 25 Sep 2018 10:39:24 -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=hMD3owZ6; 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 S1727267AbeIYXrG (ORCPT + 99 others); Tue, 25 Sep 2018 19:47:06 -0400 Received: from mail-ed1-f67.google.com ([209.85.208.67]:43896 "EHLO mail-ed1-f67.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1727239AbeIYXrF (ORCPT ); Tue, 25 Sep 2018 19:47:05 -0400 Received: by mail-ed1-f67.google.com with SMTP id u23so10929582edx.10; Tue, 25 Sep 2018 10:38:29 -0700 (PDT) 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; bh=tKC/W6bifrWOQDRQ8NZQ3YbTITA/cPSy615ajYq1W5A=; b=hMD3owZ6JjM/C+d/gvYcK/4/q5k2G75KiX4ff9qojlLMgFK4V1KLfwCExqO47saSbT 0a0JHTVmIfg2YwLynUubJd1DGgzyUpD5UcqdeW0YRB5xMILdTLH9YRJiwJ3N+fU1Eppt 9yVIQfxYMFEltSXpUV7mlZ2omh/xysnN88/h6AuuGYxs5QNc+N+z+LI3B33RIYfRHehI xuWUrWYh2x380T8PR1JTofudt8qhrU3hl6iefz5BiRnoWeIBBiNriT4phHo7KBpzs/73 ABExc/Ld0sMkz5gB/geOHnO+ZeL9y/6CrsRV/rBNuWBVDUgGGL6iTjMnsb8G7ZuxCox9 mAsg== 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; bh=tKC/W6bifrWOQDRQ8NZQ3YbTITA/cPSy615ajYq1W5A=; b=EUUOFYeroqPoeN3h4jJR1zOrsKTugkKs43L5y0cIDj/CqJedMHfaSgkO7DD/s6soZ/ 0PJt+tVvsfQqGZDKJN8Han0c7hvV26aFh9FgVq01Glfkih8RyrbETGAjj/c2W2gDmqqy TAmMQSFqDxRUECY3O6aK7a18yBgQqnVSGmZ2Wnpr9gaQmW+ksJGpuP3TZfew0sen3DFJ zUsnnELBkoCWRMNI09lpBahDmhHWPZHmzCgqvt9RoMRCFxKJIyPoYtO5Ytg0nJ6mIfVD QlNAm4JbQEtBNMoBhjQJRRNVzw/vxJQG9fknD7huF1C0v+Ov3jWPAa2rBhBEbHS+t3hC soUA== X-Gm-Message-State: ABuFfoj+61rt0xn2pRTfn50ie8yZQ9lqIAF7yBBB4zbY5sUyli5N71g9 HxDLkLK41wvtDZfRmo9QzQ== X-Received: by 2002:a50:cdcc:: with SMTP id h12-v6mr3265740edj.159.1537897108655; Tue, 25 Sep 2018 10:38:28 -0700 (PDT) Received: from localhost.localdomain (host86-147-9-252.range86-147.btcentralplus.com. [86.147.9.252]) by smtp.googlemail.com with ESMTPSA id m11-v6sm6456ejs.58.2018.09.25.10.38.27 (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Tue, 25 Sep 2018 10:38:28 -0700 (PDT) From: Craig Tatlor Cc: ctatlor97@gmail.com, linux-arm-msm@vger.kernel.org, Bjorn Andersson , Linus Walleij , Rob Herring , Mark Rutland , linux-gpio@vger.kernel.org, devicetree@vger.kernel.org, linux-kernel@vger.kernel.org Subject: [PATCH v3 2/2] dt-bindings: pinctrl: qcom: Add SDM660 pinctrl binding Date: Tue, 25 Sep 2018 18:38:00 +0100 Message-Id: <20180925173801.3835-2-ctatlor97@gmail.com> X-Mailer: git-send-email 2.18.0 In-Reply-To: <20180925173801.3835-1-ctatlor97@gmail.com> References: <20180812142413.20856-1-ctatlor97@gmail.com> <20180925173801.3835-1-ctatlor97@gmail.com> To: unlisted-recipients:; (no To-header on input) Sender: linux-kernel-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Add the binding for the TLMM pinctrl block found in the SDM660 platform. Signed-off-by: Craig Tatlor --- .../bindings/pinctrl/qcom,sdm660-pinctrl.txt | 181 ++++++++++++++++++ 1 file changed, 181 insertions(+) create mode 100644 Documentation/devicetree/bindings/pinctrl/qcom,sdm660-pinctrl.txt diff --git a/Documentation/devicetree/bindings/pinctrl/qcom,sdm660-pinctrl.txt b/Documentation/devicetree/bindings/pinctrl/qcom,sdm660-pinctrl.txt new file mode 100644 index 000000000000..97e6622c0b85 --- /dev/null +++ b/Documentation/devicetree/bindings/pinctrl/qcom,sdm660-pinctrl.txt @@ -0,0 +1,181 @@ +Qualcomm Technologies, Inc. SDM660 TLMM block + +This binding describes the Top Level Mode Multiplexer block found in the +SDM660 platform. + +- compatible: + Usage: required + Value type: + Definition: must be "qcom,sdm660-pinctrl" or + "qcom,sdm630-pinctrl". + +- reg: + Usage: required + Value type: + Definition: the base address and size of the TLMM register space. + +- interrupts: + Usage: required + Value type: + Definition: should specify the TLMM summary IRQ. + +- interrupt-controller: + Usage: required + Value type: + Definition: identifies this node as an interrupt controller + +- #interrupt-cells: + Usage: required + Value type: + Definition: must be 2. Specifying the pin number and flags, as defined + in + +- gpio-controller: + Usage: required + Value type: + Definition: identifies this node as a gpio controller + +- gpio-ranges: + Usage: required + Value type: + Definition: Specifies the mapping between gpio controller and + pin-controller pins. + +- #gpio-cells: + Usage: required + Value type: + Definition: must be 2. Specifying the pin number and flags, as defined + in + +Please refer to ../gpio/gpio.txt and ../interrupt-controller/interrupts.txt for +a general description of GPIO and interrupt bindings. + +Please refer to pinctrl-bindings.txt in this directory for details of the +common pinctrl bindings used by client devices, including the meaning of the +phrase "pin configuration node". + +The pin configuration nodes act as a container for an arbitrary number of +subnodes. Each of these subnodes represents some desired configuration for a +pin, a group, or a list of pins or groups. This configuration can include the +mux function to select on those pin(s)/group(s), and various pin configuration +parameters, such as pull-up, drive strength, etc. + + +PIN CONFIGURATION NODES: + +The name of each subnode is not important; all subnodes should be enumerated +and processed purely based on their content. + +Each subnode only affects those parameters that are explicitly listed. In +other words, a subnode that lists a mux function but no pin configuration +parameters implies no information about any pin configuration parameters. +Similarly, a pin subnode that describes a pullup parameter implies no +information about e.g. the mux function. + + +The following generic properties as defined in pinctrl-bindings.txt are valid +to specify in a pin configuration subnode: + +- pins: + Usage: required + Value type: + Definition: List of gpio pins affected by the properties specified in + this subnode. Valid pins are: + gpio0-gpio113, + Supports mux, bias and drive-strength + sdc1_clk, sdc1_cmd, sdc1_data sdc2_clk, sdc2_cmd, sdc2_data sdc1_rclk, + Supports bias and drive-strength + +- function: + Usage: required + Value type: + Definition: Specify the alternative function to be configured for the + specified pins. Functions are only valid for gpio pins. + Valid values are: + adsp_ext, agera_pll, atest_char, atest_char0, atest_char1, + atest_char2, atest_char3, atest_gpsadc0, atest_gpsadc1, + atest_tsens, atest_tsens2, atest_usb1, atest_usb10, + atest_usb11, atest_usb12, atest_usb13, atest_usb2, + atest_usb20, atest_usb21, atest_usb22, atest_usb23, + audio_ref, bimc_dte0, bimc_dte1, blsp_i2c1, blsp_i2c2, + blsp_i2c3, blsp_i2c4, blsp_i2c5, blsp_i2c6, blsp_i2c7, + blsp_i2c8_a, blsp_i2c8_b, blsp_spi1, blsp_spi2, blsp_spi3, + blsp_spi3_cs1, blsp_spi3_cs2, blsp_spi4, blsp_spi5, + blsp_spi6, blsp_spi7, blsp_spi8_a, blsp_spi8_b, + blsp_spi8_cs1, blsp_spi8_cs2, blsp_uart1, blsp_uart2, + blsp_uart5, blsp_uart6_a, blsp_uart6_b, blsp_uim1, + blsp_uim2, blsp_uim5, blsp_uim6, cam_mclk, cci_async, + cci_i2c, cri_trng, cri_trng0, cri_trng1, dbg_out, ddr_bist, + gcc_gp1, gcc_gp2, gcc_gp3, gpio, gps_tx_a, gps_tx_b, gps_tx_c, + isense_dbg, jitter_bist, ldo_en, ldo_update, m_voc, mdp_vsync, + mdss_vsync0, mdss_vsync1, mdss_vsync2, mdss_vsync3, mss_lte, + nav_pps_a, nav_pps_b, nav_pps_c, pa_indicator, phase_flag0, + phase_flag1, phase_flag10, phase_flag11, phase_flag12, + phase_flag13, phase_flag14, phase_flag15, phase_flag16, + phase_flag17, phase_flag18, phase_flag19, phase_flag2, + phase_flag20, phase_flag21, phase_flag22, phase_flag23, + phase_flag24, phase_flag25, phase_flag26, phase_flag27, + phase_flag28, phase_flag29, phase_flag3, phase_flag30, + phase_flag31, phase_flag4, phase_flag5, phase_flag6, + phase_flag7, phase_flag8, phase_flag9, pll_bypassnl, + pll_reset, pri_mi2s, pri_mi2s_ws, prng_rosc, pwr_crypto, + pwr_modem, pwr_nav, qdss_cti0_a, qdss_cti0_b, qdss_cti1_a, + qdss_cti1_b, qdss_gpio, qdss_gpio0, qdss_gpio1, qdss_gpio10, + qdss_gpio11, qdss_gpio12, qdss_gpio13, qdss_gpio14, qdss_gpio15, + qdss_gpio2, qdss_gpio3, qdss_gpio4, qdss_gpio5, qdss_gpio6, + qdss_gpio7, qdss_gpio8, qdss_gpio9, qlink_enable, qlink_request, + qspi_clk, qspi_cs, qspi_data0, qspi_data1, qspi_data2, + qspi_data3, qspi_resetn, sec_mi2s, sndwire_clk, sndwire_data, + sp_cmu, ssc_irq, tgu_ch0, tgu_ch1, tsense_pwm1, tsense_pwm2, + uim1_clk, uim1_data, uim1_present, uim1_reset, uim2_clk, + uim2_data, uim2_present, uim2_reset, uim_batt, vfr_1, + vsense_clkout, vsense_data0, vsense_data1, vsense_mode, + wlan1_adc0, wlan1_adc1, wlan2_adc0, wlan2_adc1 + +- bias-disable: + Usage: optional + Value type: + Definition: The specified pins should be configued as no pull. + +- bias-pull-down: + Usage: optional + Value type: + Definition: The specified pins should be configued as pull down. + +- bias-pull-up: + Usage: optional + Value type: + Definition: The specified pins should be configued as pull up. + +- output-high: + Usage: optional + Value type: + Definition: The specified pins are configured in output mode, driven + high. + Not valid for sdc pins. + +- output-low: + Usage: optional + Value type: + Definition: The specified pins are configured in output mode, driven + low. + Not valid for sdc pins. + +- drive-strength: + Usage: optional + Value type: + Definition: Selects the drive strength for the specified pins, in mA. + Valid values are: 2, 4, 6, 8, 10, 12, 14 and 16 + +Example: + + tlmm: pinctrl@1010000 { + compatible = "qcom,sdm660-pinctrl"; + reg = <0x1010000 0x300000>; + interrupts = <0 208 0>; + gpio-controller; + gpio-ranges = <&tlmm 0 0 114>; + #gpio-cells = <2>; + interrupt-controller; + #interrupt-cells = <2>; + }; -- 2.18.0