From patchwork Sat Nov 25 18:44:22 2023 Content-Type: text/plain; charset="utf-8" MIME-Version: 1.0 Content-Transfer-Encoding: 8bit X-Patchwork-Submitter: Krzysztof Kozlowski X-Patchwork-Id: 13468611 Return-Path: X-Spam-Checker-Version: SpamAssassin 3.4.0 (2014-02-07) on aws-us-west-2-korg-lkml-1.web.codeaurora.org Received: from bombadil.infradead.org (bombadil.infradead.org [198.137.202.133]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by smtp.lore.kernel.org (Postfix) with ESMTPS id 3F164C4167B for ; Sat, 25 Nov 2023 18:44:50 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/relaxed; d=lists.infradead.org; s=bombadil.20210309; h=Sender: Content-Transfer-Encoding:Content-Type:List-Subscribe:List-Help:List-Post: List-Archive:List-Unsubscribe:List-Id:MIME-Version:Message-Id:Date:Subject:Cc :To:From:Reply-To:Content-ID:Content-Description:Resent-Date:Resent-From: Resent-Sender:Resent-To:Resent-Cc:Resent-Message-ID:In-Reply-To:References: List-Owner; bh=H2DnG9L7M92P2RC5fdMlT0SVhKIvcqs5iyU1HMCimuw=; b=cewew9ZZR+0xPr NYU44BY6v3trHYEv8yMi6U8SlIe0jlI1yLsd5707p2YN8ZMIyY33vDeOjq8XAKUQ94gLq2qNDPizI Rk95XG56xaGmoGxdQUcWijUjvru1A2E52CTFj7cmo+ATLepMZNIK6eL0KL/bQ7u5IXU6XLNl8J56x X7xgaWHsGYi9SEZ7vNasMY1K+ntOQTmciTVqjhh8c0anDU40bjikiFT7lBceU1yV2V6Po+L+4Fghp V3dip9WuRXqj9HBl+49Rva+qfgZv042gIAHha9M2LEuDCxhk5FRi3gL0ZoxYMRAKbS8ZNDn1fn02H ZCkaUN38ZQMcjWyIVF2w==; Received: from localhost ([::1] helo=bombadil.infradead.org) by bombadil.infradead.org with esmtp (Exim 4.96 #2 (Red Hat Linux)) id 1r6xdt-009dtN-1e; Sat, 25 Nov 2023 18:44:37 +0000 Received: from mail-ej1-x632.google.com ([2a00:1450:4864:20::632]) by bombadil.infradead.org with esmtps (Exim 4.96 #2 (Red Hat Linux)) id 1r6xdp-009dss-38 for linux-rockchip@lists.infradead.org; Sat, 25 Nov 2023 18:44:35 +0000 Received: by mail-ej1-x632.google.com with SMTP id a640c23a62f3a-a049d19b63bso408427666b.2 for ; Sat, 25 Nov 2023 10:44:33 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=linaro.org; s=google; t=1700937872; x=1701542672; darn=lists.infradead.org; h=content-transfer-encoding:mime-version:message-id:date:subject:cc :to:from:from:to:cc:subject:date:message-id:reply-to; bh=MXUstR7Xy9tnBrtksEQd/hbu5+ugdxqEwGT2RmAkAxQ=; b=FXrGFBlcmHtauH3dXC3KU+YLljk/o2Lnmx6JdB0aezwaKji1bFwHhPxpvbcts1bbxd Mf/UlMqXFHLn4B0OMswKLnkQp34peX8c2CwoJkyhFZnW8A4o/o77xWnldhDhZ893rMn7 ZLAyEKYu8AGH1s4i1ZnS4aMpVFGBnfpE807mFKeo29yZKy7H3l1s70nNWoJAhbPFN2WU inL4rQ0E5G/gQJs0ngqWPoj1jjWynlN2wL+KxcdxZCqfe3OzR/An/+hmdL7HdKPg0f/Z /GBQPYc75/b1oLYuJMXvu6WqqQGNCwiqNeg3ssRFi9fSt0MxF9JE9ywxB2xU91sNoGcO fhRg== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20230601; t=1700937872; x=1701542672; h=content-transfer-encoding:mime-version:message-id:date:subject:cc :to:from:x-gm-message-state:from:to:cc:subject:date:message-id :reply-to; bh=MXUstR7Xy9tnBrtksEQd/hbu5+ugdxqEwGT2RmAkAxQ=; b=HyU2L2avpTnKB9sRammXij1I/OXFGWcrEx4BdsaNGIEuAnxO8LPhTQNA8RC8buzMf7 rI5kuUW/ahcqPBlYrmBx399ug4vSXNcZXmo/A0bjcb+3aub5E4K2AFHu/EAQWLUHSLIp 9ofxKE7qW2TcKpJxhKqyock205xFWL6xS4H3tV7s2QuFnrCZPcqikRLBufg/iFKyc2PR bKw/ZtWlFv58FCgv0jJKOo5Rr3tPf7TsbC/V79u+MrpYI2vWGLL1lFng0stbrNgJRsD4 s9L7G879/cdN6yLzjl4/17VoM/gz2Op2D2FE/WSKPhqdDxOypj/ttMkVTbzErtUEPAHh Qi5w== X-Gm-Message-State: AOJu0Yzu+5FPtxzI2D650vwEAGyUfvlV5E7TellWHrcKj54Oj5hEQg4/ XUeQSGcPAUDcwxTjlNfdA1XfDw== X-Google-Smtp-Source: AGHT+IG0p1cN7S1e73FovrjNTWznxSs1Y/JTDOV400UkrX1ND/mMHN/cl9JI2N6LHUlMmRph94th7Q== X-Received: by 2002:a17:907:9250:b0:9ae:420e:739b with SMTP id kb16-20020a170907925000b009ae420e739bmr4008521ejb.46.1700937872326; Sat, 25 Nov 2023 10:44:32 -0800 (PST) Received: from krzk-bin.. ([178.197.223.109]) by smtp.gmail.com with ESMTPSA id k13-20020a17090632cd00b009ca522853ecsm3776610ejk.58.2023.11.25.10.44.28 (version=TLS1_3 cipher=TLS_AES_256_GCM_SHA384 bits=256/256); Sat, 25 Nov 2023 10:44:31 -0800 (PST) From: Krzysztof Kozlowski To: Rob Herring , Krzysztof Kozlowski , Conor Dooley , Matthias Brugger , AngeloGioacchino Del Regno , devicetree@vger.kernel.org, linux-kernel@vger.kernel.org, linux-arm-kernel@lists.infradead.org, linux-mediatek@lists.infradead.org Cc: Krzysztof Kozlowski , Andrew Davis , Andrew Lunn , Arnd Bergmann , Bjorn Andersson , Chen-Yu Tsai , Dmitry Baryshkov , Geert Uytterhoeven , Heiko Stuebner , Jonathan Corbet , Konrad Dybcio , Michal Simek , Neil Armstrong , Nishanth Menon , Olof Johansson , =?utf-8?b?UmFmYcWCIE1pxYJlY2tp?= , linux-rockchip@lists.infradead.org, linux-samsung-soc@vger.kernel.org, linux-amlogic@lists.infradead.org, linux-arm-msm@vger.kernel.org, workflows@vger.kernel.org, linux-doc@vger.kernel.org Subject: [PATCH v3] docs: dt-bindings: add DTS Coding Style document Date: Sat, 25 Nov 2023 19:44:22 +0100 Message-Id: <20231125184422.12315-1-krzysztof.kozlowski@linaro.org> X-Mailer: git-send-email 2.34.1 MIME-Version: 1.0 X-CRM114-Version: 20100106-BlameMichelson ( TRE 0.8.0 (BSD) ) MR-646709E3 X-CRM114-CacheID: sfid-20231125_104434_064577_3425EBDC X-CRM114-Status: GOOD ( 26.00 ) X-BeenThere: linux-rockchip@lists.infradead.org X-Mailman-Version: 2.1.34 Precedence: list List-Id: Upstream kernel work for Rockchip platforms List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Sender: "Linux-rockchip" Errors-To: linux-rockchip-bounces+linux-rockchip=archiver.kernel.org@lists.infradead.org Document preferred coding style for Devicetree sources (DTS and DTSI), to bring consistency among all (sub)architectures and ease in reviews. Cc: Andrew Davis cc: Andrew Lunn Cc: AngeloGioacchino Del Regno Cc: Arnd Bergmann Cc: Bjorn Andersson Cc: Chen-Yu Tsai Cc: Dmitry Baryshkov Cc: Geert Uytterhoeven Cc: Heiko Stuebner Cc: Jonathan Corbet Cc: Konrad Dybcio Cc: Matthias Brugger Cc: Michal Simek Cc: Neil Armstrong Cc: Nishanth Menon Cc: Olof Johansson Cc: Rafał Miłecki Acked-by: Neil Armstrong Acked-by: Heiko Stuebner Signed-off-by: Krzysztof Kozlowski Reviewed-by: Laurent Pinchart Acked-by: Konrad Dybcio Reviewed-by: Geert Uytterhoeven --- Merging idea: Rob/DT bindings Changes in v3 ============= 1. should->shall (Angelo) 2. Comments // -> /* (Angelo, Michal) 3. Use imaginary example in "Order of Properties in Device Node" (Angelo) 4. Added paragraphs for three sections with justifications of chosen style. 5. Allow two style of ordering overrides in board DTS: alphabetically or by order of DTSI (Rob). 6. I did not incorporate feedback about, due to lack of consensus and my disagreement: a. SoM being DTS without DTSI in "Organizing DTSI and DTS" Changes in v2 ============= 1. Hopefully incorporate entire feedback from comments: a. Fix \ { => / { (Rob) b. Name: dts-coding-style (Rob) c. Exceptions for ordering nodes by name for Renesas and pinctrl (Geert, Konrad) d. Ordering properties by common/vendor (Rob) e. Array entries in <> (Rob) 2. New chapter: Organizing DTSI and DTS 3. Several grammar fixes (missing articles) Cc: linux-rockchip@lists.infradead.org Cc: linux-mediatek@lists.infradead.org Cc: linux-samsung-soc@vger.kernel.org Cc: linux-amlogic@lists.infradead.org Cc: linux-arm-kernel@lists.infradead.org Cc: linux-arm-msm@vger.kernel.org Cc: workflows@vger.kernel.org Cc: linux-doc@vger.kernel.org --- .../devicetree/bindings/dts-coding-style.rst | 194 ++++++++++++++++++ Documentation/devicetree/bindings/index.rst | 1 + 2 files changed, 195 insertions(+) create mode 100644 Documentation/devicetree/bindings/dts-coding-style.rst diff --git a/Documentation/devicetree/bindings/dts-coding-style.rst b/Documentation/devicetree/bindings/dts-coding-style.rst new file mode 100644 index 000000000000..e374bec0f555 --- /dev/null +++ b/Documentation/devicetree/bindings/dts-coding-style.rst @@ -0,0 +1,194 @@ +.. SPDX-License-Identifier: GPL-2.0 +.. _dtscodingstyle: + +===================================== +Devicetree Sources (DTS) Coding Style +===================================== + +When writing Devicetree Sources (DTS) please observe below guidelines. They +should be considered complementary to any rules expressed already in Devicetree +Specification and dtc compiler (including W=1 and W=2 builds). + +Individual architectures and sub-architectures can add additional rules, making +the style stricter. + +Naming and Valid Characters +--------------------------- + +Devicetree specification allows broader range of characters in node and +property names, but for code readability the choice shall be narrowed. + +1. Node and property names are allowed to use only: + + * lowercase characters: [a-z] + * digits: [0-9] + * dash: - + +2. Labels are allowed to use only: + + * lowercase characters: [a-z] + * digits: [0-9] + * underscore: _ + +3. Unit addresses shall use lowercase hex, without leading zeros (padding). + +4. Hex values in properties, e.g. "reg", shall use lowercase hex. The address + part can be padded with leading zeros. + +Example:: + + gpi_dma2: dma-controller@800000 { + compatible = "qcom,sm8550-gpi-dma", "qcom,sm6350-gpi-dma"; + reg = <0x0 0x00800000 0x0 0x60000>; + } + +Order of Nodes +-------------- + +1. Nodes within any bus, thus using unit addresses for children, shall be + ordered incrementally by unit address. + Alternatively for some sub-architectures, nodes of the same type can be + grouped together (e.g. all I2C controllers one after another even if this + breaks unit address ordering). + +2. Nodes without unit addresses shall be ordered alpha-numerically by the node + name. For a few types of nodes, they can be ordered by the main property + (e.g. pin configuration states ordered by value of "pins" property). + +3. When extending nodes in the board DTS via &label, the entries shall be + ordered either alpha-numerically or by keeping the order from DTSI (choice + depending on sub-architecture). + +Above ordering rules are easy to enforce during review, reduce chances of +conflicts for simultaneous additions (new nodes) to a file and help in +navigating through the DTS source. + +Example:: + + /* SoC DTSI */ + + / { + cpus { + /* ... */ + }; + + psci { + /* ... */ + }; + + soc@ { + dma: dma-controller@10000 { + /* ... */ + }; + + clk: clock-controller@80000 { + /* ... */ + }; + }; + }; + + /* Board DTS - alphabetical order */ + + &clk { + /* ... */ + }; + + &dma { + /* ... */ + }; + + /* Board DTS - alternative order, keep as DTSI */ + + &dma { + /* ... */ + }; + + &clk { + /* ... */ + }; + +Order of Properties in Device Node +---------------------------------- + +Following order of properties in device nodes is preferred: + +1. compatible +2. reg +3. ranges +4. Standard/common properties (defined by common bindings, e.g. without + vendor-prefixes) +5. Vendor-specific properties +6. status (if applicable) +7. Child nodes, where each node is preceded with a blank line + +The "status" property is by default "okay", thus it can be omitted. + +Above order follows approach: + +1. Most important properties start the node: compatible then bus addressing to + match unit address. +2. Each node will have common properties in similar place. +3. Status is the last information to annotate that device node is or is not + finished (board resources are needed). + +Example:: + + /* SoC DTSI */ + + device_node: device-class@6789abc { + compatible = "vendor,device"; + reg = <0x0 0x06789abc 0x0 0xa123>; + ranges = <0x0 0x0 0x06789abc 0x1000>; + #dma-cells = <1>; + clocks = <&clock_controller 0>, <&clock_controller 1>; + clock-names = "bus", "host"; + vendor,custom-property = <2>; + status = "disabled"; + + child_node: child-class@100 { + reg = <0x100 0x200>; + /* ... */ + }; + }; + + /* Board DTS */ + + &device_node { + vdd-supply = <&board_vreg1>; + status = "okay"; + } + +Indentation +----------- + +1. Use indentation according to :ref:`codingstyle`. +2. For arrays spanning across lines, it is preferred to align the continued + entries with opening < from the first line. +3. Each entry in arrays with multiple cells (e.g. "reg" with two IO addresses) + shall be enclosed in <>. + +Example:: + + thermal-sensor@c271000 { + compatible = "qcom,sm8550-tsens", "qcom,tsens-v2"; + reg = <0x0 0x0c271000 0x0 0x1000>, + <0x0 0x0c222000 0x0 0x1000>; + }; + +Organizing DTSI and DTS +----------------------- + +The DTSI and DTS files shall be organized in a way representing the common +(and re-usable) parts of the hardware. Typically this means organizing DTSI +and DTS files into several files: + +1. DTSI with contents of the entire SoC (without nodes for hardware not present + on the SoC). +2. If applicable: DTSI with common or re-usable parts of the hardware (e.g. + entire System-on-Module). +3. DTS representing the board. + +Hardware components which are present on the board shall be placed in the +board DTS, not in the SoC or SoM DTSI. A partial exception is a common +external reference SoC-input clock, which could be coded as a fixed-clock in +the SoC DTSI with its frequency provided by each board DTS. diff --git a/Documentation/devicetree/bindings/index.rst b/Documentation/devicetree/bindings/index.rst index d9002a3a0abb..cc1fbdc05657 100644 --- a/Documentation/devicetree/bindings/index.rst +++ b/Documentation/devicetree/bindings/index.rst @@ -4,6 +4,7 @@ :maxdepth: 1 ABI + dts-coding-style writing-bindings writing-schema submitting-patches