Return-Path: X-Spam-Checker-Version: SpamAssassin 3.4.0 (2014-02-07) on aws-us-west-2-korg-lkml-1.web.codeaurora.org X-Spam-Level: X-Spam-Status: No, score=-4.0 required=3.0 tests=BAYES_00, HEADER_FROM_DIFFERENT_DOMAINS,MAILING_LIST_MULTI,SPF_HELO_NONE,SPF_PASS autolearn=no autolearn_force=no version=3.4.0 Received: from mail.kernel.org (mail.kernel.org [198.145.29.99]) by smtp.lore.kernel.org (Postfix) with ESMTP id 99B80C07E96 for ; Thu, 8 Jul 2021 08:28:05 +0000 (UTC) Received: from vger.kernel.org (vger.kernel.org [23.128.96.18]) by mail.kernel.org (Postfix) with ESMTP id 77E4C61CCA for ; Thu, 8 Jul 2021 08:28:05 +0000 (UTC) Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S230526AbhGHIaq convert rfc822-to-8bit (ORCPT ); Thu, 8 Jul 2021 04:30:46 -0400 Received: from mx-relay89-hz1.antispameurope.com ([94.100.132.89]:38669 "EHLO mx-relay89-hz1.antispameurope.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S230414AbhGHIap (ORCPT ); Thu, 8 Jul 2021 04:30:45 -0400 X-Greylist: delayed 416 seconds by postgrey-1.27 at vger.kernel.org; Thu, 08 Jul 2021 04:30:45 EDT Received: from unknown ([185.80.187.2]) by mx-relay89-hz1.antispameurope.com; Thu, 08 Jul 2021 10:20:58 +0200 Received: from grp-ex01.Vivavis.int (192.168.17.53) by grp-ex01.Vivavis.int (192.168.17.53) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id 15.2.858.12; Thu, 8 Jul 2021 10:20:42 +0200 Received: from grp-ex01.Vivavis.int ([fe80::b524:e95:f072:33b7]) by grp-ex01.Vivavis.int ([fe80::b524:e95:f072:33b7%9]) with mapi id 15.02.0858.012; Thu, 8 Jul 2021 10:20:42 +0200 From: "embedded (VIVAVIS AG)" To: "devicetree@vger.kernel.org" Subject: Voltage and current regulator: usage of 'regulators' parent node in device tree Thread-Topic: Voltage and current regulator: usage of 'regulators' parent node in device tree Thread-Index: Addz0fY74DQKBToLRVyPKgu6Ziqk0A== Date: Thu, 8 Jul 2021 08:20:42 +0000 Message-ID: Accept-Language: de-DE, en-US Content-Language: de-DE X-MS-Has-Attach: X-MS-TNEF-Correlator: x-originating-ip: [172.16.7.31] x-g-data-mailsecurity-for-exchange-state: 0 x-g-data-mailsecurity-for-exchange-error: 0 x-g-data-mailsecurity-for-exchange-sender: 23 x-g-data-mailsecurity-for-exchange-server: 61419075-592b-4c8d-b7a0-bf1d145a8b8e x-c2processedorg: 2f045ba3-9b34-4118-a5bd-6c10d5957477 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 8BIT MIME-Version: 1.0 X-cloud-security-sender: embedded@vivavis.com X-cloud-security-recipient: devicetree@vger.kernel.org X-cloud-security-crypt: load encryption module X-cloud-security-Virusscan: CLEAN X-cloud-security-disclaimer: This E-Mail was scanned by E-Mailservice on mx-relay89-hz1.antispameurope.com with BC67A1246334 X-cloud-security-connect: unknown[185.80.187.2], TLS=1, IP=185.80.187.2 X-cloud-security-Digest: 326b0c2de32243424679839d02f247e3 X-cloud-security: scantime:5.750 Precedence: bulk List-ID: X-Mailing-List: devicetree@vger.kernel.org I see a lot of Device trees wrapping the regulator nodes within a parent node like this regulators { compatible = "simple-bus"; #address-cells = <1>; #size-cells = <0>; reg_p3v3: regulator@0 { compatible = "regulator-fixed"; [...] regulator-always-on; }; [...] Contrary to that, patches exist removing the 'regulators' node, because the 'simple-bus' doesn't really exist in hardware. Unfortunately, the documentation is unclear about wrapping regulator nodes like shown above. Should I avoid the parent 'regulators' node and why? Is the given naming schema in fixed-regulator.yaml best practice to follow? reg_xyz: regulator-xyz { compatible = "regulator-fixed"; regulator-name = "xyz"; Thank you for clarification. Carsten Stelling