Received: by 2002:a05:6a10:d5a5:0:0:0:0 with SMTP id gn37csp727354pxb; Wed, 6 Oct 2021 14:09:19 -0700 (PDT) X-Google-Smtp-Source: ABdhPJwjaLhSn5NvbJrczGjOp1bVKZ3Qi9te45uoyDMOl6fqV4u5SAEY55lz2wKpK1aElMfdgCdP X-Received: by 2002:a17:907:9602:: with SMTP id gb2mr605359ejc.354.1633554558943; Wed, 06 Oct 2021 14:09:18 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; t=1633554558; cv=none; d=google.com; s=arc-20160816; b=vf1GF5XG6Sf8YHvUePsQInoYvaM5th9OLW3aiXZ7zwkFbQHNoWRkJdopD5AZZNBgom 4YHeFCaCxPW88mbelTCkMCXbUA6SybMDrc3y5uW+8N3YRhYdtMt7NDobUshdUTWIDzGZ /L+Mz/cKTOHu9yDROsROGK5QYWy635GaZ/QfBeRg4QuS0Yxat0bIGY5jBaP4gLaQjgJt e7W1jfZlfyvEFxwK7FZVoFugacqHirvPRmYxTRWsUkWdVv8ivGSILUDUb28nafaZ2iWX layIbjV+bcfYGCqmw6Mwu3+mPzmXV02Ilyamc252rUHFqddHy4r2eFraC3q6faOVAOlW 7sMQ== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:in-reply-to:content-disposition:mime-version :references:message-id:subject:cc:to:from:date; bh=gmYMkMgyNF+M0/XN9qtQib3Updmh2p5yOstnRWqGc6E=; b=PcnuNuP1igLNh9t9PYZkVtsBNkQ14uFBU+V6df9tbTAJ4Ymh+LkG6TRmRnepvTZRrZ nKoQ0zzpAoyvRXRUAqKwUGoG8ExwjnPlz6WeCayCF/Pn4BLAQBm45yEdQb3NPVl9RAVn qUjxpNm367OGbhVzFwvLZHr+vBN5nLyibwoW3xisWK4qCEnuILzkHrYHxx1Wu0vMDilj qMJ2rWZG5+d1elgrpIWoVwBCzwBsL3bya/P+NwswNTYe7cKqaQ4u2v3Ecpkbw9a9Ie1x MKMu5cdKdsCCsvQbNiXV3+rDL/izuVNYDyNvoFWMT+ZEFT5S0Jwmh606VJ4ltkyjTT27 KYFg== 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; dmarc=pass (p=NONE sp=NONE dis=NONE) header.from=kernel.org Return-Path: Received: from vger.kernel.org (vger.kernel.org. [23.128.96.18]) by mx.google.com with ESMTP id r8si28782816ejy.37.2021.10.06.14.08.54; Wed, 06 Oct 2021 14:09:18 -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; dmarc=pass (p=NONE sp=NONE dis=NONE) header.from=kernel.org Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S239548AbhJFVJS (ORCPT + 99 others); Wed, 6 Oct 2021 17:09:18 -0400 Received: from mail-ot1-f44.google.com ([209.85.210.44]:44825 "EHLO mail-ot1-f44.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S239530AbhJFVJQ (ORCPT ); Wed, 6 Oct 2021 17:09:16 -0400 Received: by mail-ot1-f44.google.com with SMTP id o27-20020a9d411b000000b005453f95356cso3904581ote.11; Wed, 06 Oct 2021 14:07:23 -0700 (PDT) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20210112; h=x-gm-message-state:date:from:to:cc:subject:message-id:references :mime-version:content-disposition:in-reply-to; bh=gmYMkMgyNF+M0/XN9qtQib3Updmh2p5yOstnRWqGc6E=; b=Hkh0/0yaeBEkYVSdQyR49uhLFOWQ+fEAALDis0H98egZOLVm/ef1LqKiPbqX7qoNm8 QVViWmKziiarVfLAO6LeGPRHOV2miC/SxDz2y6BwC3KsUES2x0r/3CkzIJWQHali53HG 6DwLwT3SVr9Naf7vzu2KnAakkY7QOFjSZbaULVTgwD2waAvJyLgGVugTFxPz1m+KZQK7 BJ4EXvz2kEOVIvn3Mno7T5lxEpQJ2dmO2Ivy4QlsqciKd0anc0gHRnusxDmsDwHwdgFK qu/es5xeQ0FDjS0kAvQ9gbawSO8CroOgzRjSlUSNHwUhP9B269Am8HM1H/YP6wCubEeo 4KTQ== X-Gm-Message-State: AOAM530aGpydpZXYWoqLNjCjbMvgHcAMCy5LiaL3QSQEm352ZmZ0kt6Z fadICwwZbZN7mPO+q5tx/Q== X-Received: by 2002:a05:6830:2706:: with SMTP id j6mr441090otu.82.1633554443383; Wed, 06 Oct 2021 14:07:23 -0700 (PDT) Received: from robh.at.kernel.org (66-90-148-213.dyn.grandenetworks.net. [66.90.148.213]) by smtp.gmail.com with ESMTPSA id k3sm3496369otn.16.2021.10.06.14.07.22 (version=TLS1_3 cipher=TLS_AES_256_GCM_SHA384 bits=256/256); Wed, 06 Oct 2021 14:07:22 -0700 (PDT) Received: (nullmailer pid 2875966 invoked by uid 1000); Wed, 06 Oct 2021 21:07:21 -0000 Date: Wed, 6 Oct 2021 16:07:21 -0500 From: Rob Herring To: Johan Jonker Cc: heiko@sntech.de, linus.walleij@linaro.org, linux-gpio@vger.kernel.org, devicetree@vger.kernel.org, linux-arm-kernel@lists.infradead.org, linux-rockchip@lists.infradead.org, linux-kernel@vger.kernel.org Subject: Re: [PATCH v2 1/3] dt-bindings: pinctrl: convert rockchip,pinctrl.txt to YAML Message-ID: References: <20210930095225.9718-1-jbx6244@gmail.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20210930095225.9718-1-jbx6244@gmail.com> Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Thu, Sep 30, 2021 at 11:52:23AM +0200, Johan Jonker wrote: > Convert rockchip,pinctrl.txt to YAML > > Signed-off-by: Johan Jonker > --- > > Changed V2: > Add '|' to maintain the paragraphs. > Change gpio patternProperties. > Move description to items. > Remove type array. > Restyle > --- > .../bindings/pinctrl/rockchip,pinctrl.txt | 114 ------------ > .../bindings/pinctrl/rockchip,pinctrl.yaml | 176 ++++++++++++++++++ > 2 files changed, 176 insertions(+), 114 deletions(-) > delete mode 100644 Documentation/devicetree/bindings/pinctrl/rockchip,pinctrl.txt > create mode 100644 Documentation/devicetree/bindings/pinctrl/rockchip,pinctrl.yaml > > diff --git a/Documentation/devicetree/bindings/pinctrl/rockchip,pinctrl.txt b/Documentation/devicetree/bindings/pinctrl/rockchip,pinctrl.txt > deleted file mode 100644 > index 84c411129..000000000 > --- a/Documentation/devicetree/bindings/pinctrl/rockchip,pinctrl.txt > +++ /dev/null > @@ -1,114 +0,0 @@ > -* Rockchip Pinmux Controller > - > -The Rockchip Pinmux Controller, enables the IC > -to share one PAD to several functional blocks. The sharing is done by > -multiplexing the PAD input/output signals. For each PAD there are several > -muxing options with option 0 being the use as a GPIO. > - > -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 Rockchip pin configuration node is a node of a group of pins which can be > -used for a specific device or function. This node represents both mux and > -config of the pins in that group. The 'pins' selects the function mode(also > -named pin mode) this pin can work on and the 'config' configures various pad > -settings such as pull-up, etc. > - > -The pins are grouped into up to 5 individual pin banks which need to be > -defined as gpio sub-nodes of the pinmux controller. > - > -Required properties for iomux controller: > - - compatible: should be > - "rockchip,px30-pinctrl": for Rockchip PX30 > - "rockchip,rv1108-pinctrl": for Rockchip RV1108 > - "rockchip,rk2928-pinctrl": for Rockchip RK2928 > - "rockchip,rk3066a-pinctrl": for Rockchip RK3066a > - "rockchip,rk3066b-pinctrl": for Rockchip RK3066b > - "rockchip,rk3128-pinctrl": for Rockchip RK3128 > - "rockchip,rk3188-pinctrl": for Rockchip RK3188 > - "rockchip,rk3228-pinctrl": for Rockchip RK3228 > - "rockchip,rk3288-pinctrl": for Rockchip RK3288 > - "rockchip,rk3308-pinctrl": for Rockchip RK3308 > - "rockchip,rk3328-pinctrl": for Rockchip RK3328 > - "rockchip,rk3368-pinctrl": for Rockchip RK3368 > - "rockchip,rk3399-pinctrl": for Rockchip RK3399 > - "rockchip,rk3568-pinctrl": for Rockchip RK3568 > - > - - rockchip,grf: phandle referencing a syscon providing the > - "general register files" > - > -Optional properties for iomux controller: > - - rockchip,pmu: phandle referencing a syscon providing the pmu registers > - as some SoCs carry parts of the iomux controller registers there. > - Required for at least rk3188 and rk3288. On the rk3368 this should > - point to the PMUGRF syscon. > - > -Deprecated properties for iomux controller: > - - reg: first element is the general register space of the iomux controller > - It should be large enough to contain also separate pull registers. > - second element is the separate pull register space of the rk3188. > - Use rockchip,grf and rockchip,pmu described above instead. > - > -Required properties for gpio sub nodes: > -See rockchip,gpio-bank.yaml > - > -Required properties for pin configuration node: > - - rockchip,pins: 3 integers array, represents a group of pins mux and config > - setting. The format is rockchip,pins = . > - The MUX 0 means gpio and MUX 1 to N mean the specific device function. > - The phandle of a node containing the generic pinconfig options > - to use, as described in pinctrl-bindings.txt in this directory. > - > -Examples: > - > -#include > - > -... > - > -pinctrl@20008000 { > - compatible = "rockchip,rk3066a-pinctrl"; > - rockchip,grf = <&grf>; > - > - #address-cells = <1>; > - #size-cells = <1>; > - ranges; > - > - gpio0: gpio0@20034000 { > - compatible = "rockchip,gpio-bank"; > - reg = <0x20034000 0x100>; > - interrupts = ; > - clocks = <&clk_gates8 9>; > - > - gpio-controller; > - #gpio-cells = <2>; > - > - interrupt-controller; > - #interrupt-cells = <2>; > - }; > - > - ... > - > - pcfg_pull_default: pcfg_pull_default { > - bias-pull-pin-default > - }; > - > - uart2 { > - uart2_xfer: uart2-xfer { > - rockchip,pins = <1 RK_PB0 1 &pcfg_pull_default>, > - <1 RK_PB1 1 &pcfg_pull_default>; > - }; > - }; > -}; > - > -uart2: serial@20064000 { > - compatible = "snps,dw-apb-uart"; > - reg = <0x20064000 0x400>; > - interrupts = ; > - reg-shift = <2>; > - reg-io-width = <1>; > - clocks = <&mux_uart2>; > - > - pinctrl-names = "default"; > - pinctrl-0 = <&uart2_xfer>; > -}; > diff --git a/Documentation/devicetree/bindings/pinctrl/rockchip,pinctrl.yaml b/Documentation/devicetree/bindings/pinctrl/rockchip,pinctrl.yaml > new file mode 100644 > index 000000000..01a62245b > --- /dev/null > +++ b/Documentation/devicetree/bindings/pinctrl/rockchip,pinctrl.yaml > @@ -0,0 +1,176 @@ > +# SPDX-License-Identifier: GPL-2.0 > +%YAML 1.2 > +--- > +$id: http://devicetree.org/schemas/pinctrl/rockchip,pinctrl.yaml# > +$schema: http://devicetree.org/meta-schemas/core.yaml# > + > +title: Rockchip Pinmux Controller > + > +maintainers: > + - Heiko Stuebner > + > +description: | > + The Rockchip Pinmux Controller enables the IC to share one PAD > + to several functional blocks. The sharing is done by multiplexing > + the PAD input/output signals. For each PAD there are several muxing > + options with option 0 being used as a GPIO. > + > + 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 Rockchip pin configuration node is a node of a group of pins which can be > + used for a specific device or function. This node represents both mux and > + config of the pins in that group. The 'pins' selects the function mode > + (also named pin mode) this pin can work on and the 'config' configures > + various pad settings such as pull-up, etc. > + > + The pins are grouped into up to 9 individual pin banks which need to be > + defined as gpio sub-nodes of the pinmux controller. > + > +properties: > + compatible: > + enum: > + - rockchip,px30-pinctrl > + - rockchip,rk2928-pinctrl > + - rockchip,rk3066a-pinctrl > + - rockchip,rk3066b-pinctrl > + - rockchip,rk3128-pinctrl > + - rockchip,rk3188-pinctrl > + - rockchip,rk3228-pinctrl > + - rockchip,rk3288-pinctrl > + - rockchip,rk3308-pinctrl > + - rockchip,rk3328-pinctrl > + - rockchip,rk3368-pinctrl > + - rockchip,rk3399-pinctrl > + - rockchip,rk3568-pinctrl > + - rockchip,rv1108-pinctrl > + > + rockchip,grf: > + $ref: /schemas/types.yaml#/definitions/phandle > + description: > + The phandle of the syscon node for the GRF registers. > + > + rockchip,pmu: > + $ref: /schemas/types.yaml#/definitions/phandle > + description: > + The phandle of the syscon node for the PMU registers, > + as some SoCs carry parts of the iomux controller registers there. > + Required for at least rk3188 and rk3288. On the rk3368 this should > + point to the PMUGRF syscon. > + > + "#address-cells": > + enum: [1, 2] > + > + "#size-cells": > + enum: [1, 2] > + > + ranges: true > + > +patternProperties: > + "gpio@[0-9a-f]+$": > + type: object > + > + $ref: "/schemas/gpio/rockchip,gpio-bank.yaml#" > + > + unevaluatedProperties: false > + > + "pcfg-[a-z0-9-]+$": > + type: object > + properties: > + bias-disable: true > + > + bias-pull-down: true > + > + bias-pull-pin-default: true > + > + bias-pull-up: true > + > + drive-strength: > + minimum: 0 > + maximum: 20 > + > + input-enable: true > + > + input-schmitt-enable: true > + > + output-high: true > + > + output-low: true > + > + additionalProperties: false > + > +additionalProperties: > + type: object > + additionalProperties: > + type: object > + properties: > + rockchip,pins: Needs a type reference (uint32-matrix). > + minItems: 1 > + items: > + items: > + - minimum: 0 > + maximum: 8 > + description: > + Pin bank. > + - minimum: 0 > + maximum: 31 > + description: > + Pin bank index. > + - minimum: 0 > + maximum: 6 > + description: > + Mux 0 means gpio and mux 1 to N means > + the specific device function. > + - description: > + The phandle of a node contains the generic pinconfig options > + to use as described in pinctrl-bindings.txt. > + > +examples: > + - | > + #include > + #include > + > + pinctrl: pinctrl { > + compatible = "rockchip,rk3066a-pinctrl"; > + rockchip,grf = <&grf>; > + > + #address-cells = <1>; > + #size-cells = <1>; > + ranges; > + > + gpio0: gpio@20034000 { > + compatible = "rockchip,gpio-bank"; > + reg = <0x20034000 0x100>; > + interrupts = ; > + clocks = <&clk_gates8 9>; > + > + gpio-controller; > + #gpio-cells = <2>; > + > + interrupt-controller; > + #interrupt-cells = <2>; > + }; > + > + pcfg_pull_default: pcfg-pull-default { > + bias-pull-pin-default; > + }; > + > + uart2 { > + uart2_xfer: uart2-xfer { > + rockchip,pins = <1 RK_PB0 1 &pcfg_pull_default>, > + <1 RK_PB1 1 &pcfg_pull_default>; > + }; > + }; > + }; > + > + uart2: serial@20064000 { > + compatible = "snps,dw-apb-uart"; > + reg = <0x20064000 0x400>; > + interrupts = ; > + clocks = <&mux_uart2>; > + pinctrl-0 = <&uart2_xfer>; > + pinctrl-names = "default"; > + reg-io-width = <1>; > + reg-shift = <2>; > + }; > -- > 2.20.1 > >