From patchwork Mon Jul 25 15:20:54 2016 Content-Type: text/plain; charset="utf-8" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit X-Patchwork-Submitter: Steve Twiss X-Patchwork-Id: 652330 Return-Path: X-Original-To: incoming-dt@patchwork.ozlabs.org Delivered-To: patchwork-incoming-dt@bilbo.ozlabs.org Received: from vger.kernel.org (vger.kernel.org [209.132.180.67]) by ozlabs.org (Postfix) with ESMTP id 3rylQl3Djqz9ssP for ; Tue, 26 Jul 2016 01:23:59 +1000 (AEST) Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1752930AbcGYPX5 (ORCPT ); Mon, 25 Jul 2016 11:23:57 -0400 Received: from mail1.bemta14.messagelabs.com ([193.109.254.111]:61405 "EHLO mail1.bemta14.messagelabs.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1752814AbcGYPX5 (ORCPT ); Mon, 25 Jul 2016 11:23:57 -0400 Received: from [85.158.140.211] by server-7.bemta-14.messagelabs.com id E5/DC-06589-70F26975; Mon, 25 Jul 2016 15:23:51 +0000 X-Brightmail-Tracker: H4sIAAAAAAAAA+NgFrrCIsWRWlGSWpSXmKPExsUSt3OpsS6b/rR wg2X/dS3mHznHavG839vi8q45bBZLr19kslg2dwu7xeWJnewObB5r5q1h9Ng56y67x6ZVnWwe d67tYfP4vEkugDWKNTMvKb8igTWjb+cn9oIrshXPj09gamDcLN7FyMUhJLCeUaJ39UH2LkZOI KdC4tKZwywgNpuAocS8N+8ZQWwWAVWJ5XOmsIHYwgL5Etc27mMHaRYRmMEo0f70O1gRs0CsxK lXn5lAbF4BB4lnf0+yQtiCEidnPmGBqJGQOPjiBXMXIwfQMi2J5cciQcISAvYS099fBQtLCOh LNB6LhQgbSnyf9Y0FwjaXeDr9AdsERv5ZSIbOQjJ0ASPTKkaN4tSistQiXUMjvaSizPSMktzE zBxdQ0MTvdzU4uLE9NScxKRiveT83E2MwBBmAIIdjGenOR9ilORgUhLldWCcFi7El5SfUpmRW JwRX1Sak1p8iFGGg0NJgneyLlBOsCg1PbUiLTMHGE0waQkOHiURXjWQNG9xQWJucWY6ROoUoy 7HlgU31jIJseTl56VKifPOBykSACnKKM2DGwGL7EuMslLCvIxARwnxFKQW5WaWoMq/YhTnYFQ S5s0GmcKTmVcCt+kV0BFMQEcs4JkMckRJIkJKqoFx7SnOKIlbd2uNWreq/a2JLnood+6y4QLe C4uYv1sqaAb4pOcGcemu3/T2isGkz6K/ztnYTvu01szUr+/cGTs5J7Wllwp5l1eujt41dX+L6 bejjKxnQv9zzWdOYL3/v/b/TpVI7ohXc14/PO7j/OGwW+N9zVnHnLq2vpLaq5ghEJbzSnnB6+ uiSizFGYmGWsxFxYkA8rmej+cCAAA= X-Env-Sender: stwiss.opensource@diasemi.com X-Msg-Ref: server-15.tower-194.messagelabs.com!1469460230!47427801!1 X-Originating-IP: [94.185.165.51] X-StarScan-Received: X-StarScan-Version: 8.77; banners=-,-,- X-VirusChecked: Checked Received: (qmail 2595 invoked from network); 25 Jul 2016 15:23:50 -0000 Received: from mailrelay2.diasemi.com (HELO sw-ex-cashub01.diasemi.com) (94.185.165.51) by server-15.tower-194.messagelabs.com with AES128-SHA encrypted SMTP; 25 Jul 2016 15:23:50 -0000 Received: from swsrvapps-01.diasemi.com (10.20.28.141) by SW-EX-CASHUB01.diasemi.com (10.20.16.140) with Microsoft SMTP Server id 14.3.248.2; Mon, 25 Jul 2016 16:23:49 +0100 Received: by swsrvapps-01.diasemi.com (Postfix, from userid 22547) id A692D3FACB; Mon, 25 Jul 2016 16:23:49 +0100 (BST) From: Steve Twiss Date: Mon, 25 Jul 2016 16:20:54 +0100 Subject: [PATCH V1] documentation: da9052: Update regulator bindings names to match DA9052/53 DTS expectations To: DEVICETREE , DTKERNEL , LINUXKERNEL , Mark Rutland CC: Support Opensource , Ying-Chun Liu Message-ID: <20160725152349.A692D3FACB@swsrvapps-01.diasemi.com> MIME-Version: 1.0 X-KSE-AttachmentFiltering-Interceptor-Info: protection disabled X-KSE-ServerInfo: sw-ex-cashub01.diasemi.com, 9 X-KSE-Antivirus-Interceptor-Info: scan successful X-KSE-Antivirus-Info: Clean, bases: 25/07/2016 11:45:00 Sender: devicetree-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: devicetree@vger.kernel.org From: Steve Twiss Hi Mark, Buck and LDO binding name changes. The binding names for the regulators have been changed to match the current expectation from existing device tree source files. This fix rectifies the disparity between what currently exists in some .dts[i] board files and what is listed in this binding document. This change re-aligns those differences and also brings the binding document in-line with the expectations of the product datasheet from Dialog Semiconductor. Bucks and LDOs now follow the expected notation: { buck1, buck2, buck3, buck4 } { ldo1, ldo2, ldo3, ldo4, ldo5, ldo6, ldo7, ldo8, ldo9, ldo10 } Signed-off-by: Steve Twiss Acked-by: Rob Herring --- This patch applies against linux-next and v4.7 Hi, Several device tree source files use a regulator naming scheme different to that found in the binding text document. Since those have been used already, I would like ensure to the binding document follows those existing DT file naming conventions. Please refer to the files containing da9052/53 references: - ./arch/arm/boot/dts/imx53-voipac-dmm-668.dtsi - ./arch/arm/boot/dts/imx53-qsb.dts Those board files use the naming convention: { buck1, buck2, buck3, buck4 } { ldo1, ldo2, ldo3, ldo4, ldo5, ldo6, ldo7, ldo8, ldo9, ldo10 } Instead of the existing suggestion in the device tree binding file: { buck0, buck1, buck2, buck3 } { ldo4, ldo5, ldo6, ldo7, ldo8, ldo9, ldo10, ldo11, ldo12, ldo13 } The binding file regulator names (as it stands) does not reflect any real-world uses I can find. This change would bring it in-line with currect expectations from existing DTS files and make it similar enough to the product datasheets to be "less confusing" than it currently is. Regards, Steve See reference: https://lkml.org/lkml/2016/7/25/197 .../devicetree/bindings/mfd/da9052-i2c.txt | 22 +++++++++++----------- 1 file changed, 11 insertions(+), 11 deletions(-) diff --git a/Documentation/devicetree/bindings/mfd/da9052-i2c.txt b/Documentation/devicetree/bindings/mfd/da9052-i2c.txt index 1857f4a..9554292 100644 --- a/Documentation/devicetree/bindings/mfd/da9052-i2c.txt +++ b/Documentation/devicetree/bindings/mfd/da9052-i2c.txt @@ -8,10 +8,13 @@ Sub-nodes: - regulators : Contain the regulator nodes. The DA9052/53 regulators are bound using their names as listed below: - buck0 : regulator BUCK0 - buck1 : regulator BUCK1 - buck2 : regulator BUCK2 - buck3 : regulator BUCK3 + buck1 : regulator BUCK CORE + buck2 : regulator BUCK PRO + buck3 : regulator BUCK MEM + buck4 : regulator BUCK PERI + ldo1 : regulator LDO1 + ldo2 : regulator LDO2 + ldo3 : regulator LDO3 ldo4 : regulator LDO4 ldo5 : regulator LDO5 ldo6 : regulator LDO6 @@ -19,9 +22,6 @@ Sub-nodes: ldo8 : regulator LDO8 ldo9 : regulator LDO9 ldo10 : regulator LDO10 - ldo11 : regulator LDO11 - ldo12 : regulator LDO12 - ldo13 : regulator LDO13 The bindings details of individual regulator device can be found in: Documentation/devicetree/bindings/regulator/regulator.txt @@ -36,22 +36,22 @@ i2c@63fc8000 { /* I2C1 */ reg = <0x48>; regulators { - buck0 { + buck1 { regulator-min-microvolt = <500000>; regulator-max-microvolt = <2075000>; }; - buck1 { + buck2 { regulator-min-microvolt = <500000>; regulator-max-microvolt = <2075000>; }; - buck2 { + buck3 { regulator-min-microvolt = <925000>; regulator-max-microvolt = <2500000>; }; - buck3 { + buck4 { regulator-min-microvolt = <925000>; regulator-max-microvolt = <2500000>; };