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 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 432BBC433F5 for ; Mon, 18 Apr 2022 11:22:33 +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:In-Reply-To:From:References:Cc:To: Subject:MIME-Version:Date:Message-ID:Reply-To:Content-ID:Content-Description: Resent-Date:Resent-From:Resent-Sender:Resent-To:Resent-Cc:Resent-Message-ID: List-Owner; bh=NNqx5136lB2CtnVs2KCc4Rlz4bRHTgQ6E6CFiuz0wW4=; b=YaCHm46wDaF8ik 5RfcthAgwJTmDrT93v2Ot3FGLuHNdflJb8BgKCP6IHPl3BLZYYOeKIQFunu014gvAWlEdGGAJ59VN uUArB8CFr3KkvNdQFbPHwxAv8EsmI1z0z1S01QyE4eWN3033EmhFycHqxToEXtCNc0jxF9X6B/Puq L41imlPyA4lH+niWGVvjVXJobzXCDLQlbeHAZ3uI23UOPJgFTsaVhpjxek2XtJU9bmLLWNSUXfwcJ cMvGCeo/lm5HU2PmYdKR4nPgMnEN/khJoAJ+TXbpR8QG/0L7bmA3hGGGVceS5+8EDfHbabQu5IyjO tyEa/W5nwmrFMjkKzkPg==; Received: from localhost ([::1] helo=bombadil.infradead.org) by bombadil.infradead.org with esmtp (Exim 4.94.2 #2 (Red Hat Linux)) id 1ngPRb-00GRfZ-Pn; Mon, 18 Apr 2022 11:21:23 +0000 Received: from dfw.source.kernel.org ([2604:1380:4641:c500::1]) by bombadil.infradead.org with esmtps (Exim 4.94.2 #2 (Red Hat Linux)) id 1ngPRY-00GRet-9L; Mon, 18 Apr 2022 11:21:21 +0000 Received: from smtp.kernel.org (relay.kernel.org [52.25.139.140]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by dfw.source.kernel.org (Postfix) with ESMTPS id 9835E60ACE; Mon, 18 Apr 2022 11:21:19 +0000 (UTC) Received: by smtp.kernel.org (Postfix) with ESMTPSA id 0EC65C385A1; Mon, 18 Apr 2022 11:21:16 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=kernel.org; s=k20201202; t=1650280879; bh=JtbuCbrZbi3dPFYVVkBHNhS7wJ87kP5Yh2cP76lFqDg=; h=Date:Subject:To:Cc:References:From:In-Reply-To:From; b=iRreG9ldmKxo4O/bDI2DATJ5fXcEBD5AcronFDUmy399cld5aXrndE3vasr4q+FTL XjAMdMr3q+Y2sd8xcERorbyBAWSNFLiLrHvaDLry2x3h2XeJm/bHyH4uwGSOwgqIqB /93jK4SXYdiTHQDn+Ijj2KOJv2pUtfbVIiKbk5z2fA+uTdbQ7ujExUaSPr/S+So1Pa Uv/amKFBMb7UMKynsLQx+enwEEu2YMKlfyyEsJV4bnmWNzRA8PDzMoEAKd1B6angot Wj1SUQS0villydBBCU/5YWd5fUQk5uFkpvZiRFUpJaL8WPaVfNr6KqO6LhPAdFem1Y 6tzkJByFsapGA== Message-ID: Date: Mon, 18 Apr 2022 13:21:14 +0200 MIME-Version: 1.0 User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:91.0) Gecko/20100101 Thunderbird/91.7.0 Subject: Re: [PATCH 2/2] arm64: dts: rockchip: Add Hardkernel ODROID-M1 board Content-Language: en-US To: Heiko Stuebner , Peter Geis Cc: Dongjin Kim , devicetree , arm-mail-list , "open list:ARM/Rockchip SoC..." , Linux Kernel Mailing List References: <20220329094446.415219-1-tobetter@gmail.com> <12089439.O9o76ZdvQC@phil> From: Krzysztof Kozlowski In-Reply-To: <12089439.O9o76ZdvQC@phil> X-CRM114-Version: 20100106-BlameMichelson ( TRE 0.8.0 (BSD) ) MR-646709E3 X-CRM114-CacheID: sfid-20220418_042120_412878_32F63B2B X-CRM114-Status: GOOD ( 18.27 ) X-BeenThere: linux-arm-kernel@lists.infradead.org X-Mailman-Version: 2.1.34 Precedence: list List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Sender: "linux-arm-kernel" Errors-To: linux-arm-kernel-bounces+linux-arm-kernel=archiver.kernel.org@lists.infradead.org On 17/04/2022 22:55, Heiko Stuebner wrote: >> Usually adding - in subsequent DTS files - means increasing the numbers >> so if you have regulator-[012] then just use regulator-[345] in other >> files. I see potential mess when you combine several DTSI files, each >> defining regulators, so in such case "some-name-regulator" (or reversed) >> is also popular approach. > > so going with > > dc_12v: dc-12v-regulator { > }; > > i.e. doing a some-name-regulator would be an in-spec way to go? > > In this case I would definitely prefer this over doing a numbered thing. > > I.e. regulator-0 can create really hard to debug issues, when you have > another accidential regulator-0 for a different regulator in there, which > then would create some sort of merged node. I don't think such case happens frequently, because all regulators are usually used by something (as a phandle) thus they should have a label. This label should be descriptive, so if one can assign same label to entirely different regulators, then the same chances are that same descriptive node will be used. IOW, if you think such mistake with regulator names can happen, then the same can happen with the label... Anyway, answering the question - "dc-12v-regulator" is still not matching exactly the Devicetree spec recommendation, but it's okay for me. :) Best regards, Krzysztof _______________________________________________ linux-arm-kernel mailing list linux-arm-kernel@lists.infradead.org http://lists.infradead.org/mailman/listinfo/linux-arm-kernel