From mboxrd@z Thu Jan 1 00:00:00 1970 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=-3.8 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 DBCF5C07E95 for ; Wed, 7 Jul 2021 13:15:09 +0000 (UTC) Received: from vger.kernel.org (vger.kernel.org [23.128.96.18]) by mail.kernel.org (Postfix) with ESMTP id B2C1361361 for ; Wed, 7 Jul 2021 13:15:09 +0000 (UTC) Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S231682AbhGGNRs convert rfc822-to-8bit (ORCPT ); Wed, 7 Jul 2021 09:17:48 -0400 Received: from mx-relay36-hz1.antispameurope.com ([94.100.133.212]:36463 "EHLO mx-relay36-hz1.antispameurope.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S229829AbhGGNRr (ORCPT ); Wed, 7 Jul 2021 09:17:47 -0400 X-Greylist: delayed 332 seconds by postgrey-1.27 at vger.kernel.org; Wed, 07 Jul 2021 09:17:46 EDT Received: from unknown ([185.80.187.2]) by mx-relay36-hz1.antispameurope.com; Wed, 07 Jul 2021 15:09:33 +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; Wed, 7 Jul 2021 15:09:25 +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; Wed, 7 Jul 2021 15:09:25 +0200 From: "embedded (VIVAVIS AG)" To: "linux-kernel@vger.kernel.org" CC: "broonie@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: AddzLeJh24+ag2vTQDK05eDkXARutw== Date: Wed, 7 Jul 2021 13:09:25 +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: linux-kernel@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-relay36-hz1.antispameurope.com with 9E5E28AAEBC X-cloud-security-connect: unknown[185.80.187.2], TLS=1, IP=185.80.187.2 X-cloud-security-Digest: 966d240c89d870d849cb0391ebe0f129 X-cloud-security: scantime:2.299 Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org I see a lot of Devicetrees 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? 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