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 vger.kernel.org (vger.kernel.org [23.128.96.18]) by smtp.lore.kernel.org (Postfix) with ESMTP id 7DA9FC4332F for ; Mon, 25 Apr 2022 16:30:11 +0000 (UTC) Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S242886AbiDYQdM (ORCPT ); Mon, 25 Apr 2022 12:33:12 -0400 Received: from lindbergh.monkeyblade.net ([23.128.96.19]:60172 "EHLO lindbergh.monkeyblade.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S235867AbiDYQdM (ORCPT ); Mon, 25 Apr 2022 12:33:12 -0400 Received: from mail-ej1-x62c.google.com (mail-ej1-x62c.google.com [IPv6:2a00:1450:4864:20::62c]) by lindbergh.monkeyblade.net (Postfix) with ESMTPS id 33DBB63C4 for ; Mon, 25 Apr 2022 09:30:07 -0700 (PDT) Received: by mail-ej1-x62c.google.com with SMTP id dk23so7359099ejb.8 for ; Mon, 25 Apr 2022 09:30:07 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=linaro.org; s=google; h=message-id:date:mime-version:user-agent:subject:content-language:to :cc:references:from:in-reply-to:content-transfer-encoding; bh=EU4QiPP93gBlWOe2hApZIvBdZh/GzN6+GSAbqnd1hoQ=; b=k5UcG9yzd5C+t8pNBeRZNZogRTEGnCU1O8cr+kn04NtswKGSVst089clW2lDdh3uv5 GvcwBnd4xXtZF8qs7sMp+8fI7hYbSZLvrtqd1zSajKS1Iw9rYRbCFrl9kRJNyZqS80Ff BvElCMS8mnpGNoXYmURPCLc3ZuD2ZGZ0Qpmf1YHkr0m/316f1QrUnETqHSDbrzlYY4Sj PncIvjdhTbqZ8ZrIngf8ZXLXQl4jJobTLzG57bpwuy22JVp50H0g1NBzHacHcfqBDErc CWMsGuQp1TwyskeXq/j29vtBgEbX+/Mnsgu9+zGWb4X9dRqfAMXp48Oj0rPPwxtKpYJz gA6A== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20210112; h=x-gm-message-state:message-id:date:mime-version:user-agent:subject :content-language:to:cc:references:from:in-reply-to :content-transfer-encoding; bh=EU4QiPP93gBlWOe2hApZIvBdZh/GzN6+GSAbqnd1hoQ=; b=GlsF25honvyQm7ZYCqU1906o6uXkgoEnuFmM3cKDOdaVRpf+bG66PlZA5vSjzYriYB SUjpJ6Y6gA4sWqUHACyf1N66za99/rNC8veRHT+t7HQKmIilHg+aD8DXldVqrk2eopNT YMc3Nhvk9e4eH4tdo9wbfQTeDmjL3cXmgI0zTzAtu5anXonFpwu1GU2TQokmwaM45uVi qFTyMWulo1t6cTuj2HgEy4V4VL7AoqzDNDcn0sv3dkB6laeK2LQL2SfBbF5H/z6eFLet Q/s6elOiW6NsfdiduuhAx8SmpZ7dGhn9dDD0poRAzIohPISqIiKrfp9xI3v2WSXHgN6/ 2GHQ== X-Gm-Message-State: AOAM5328sNS9QMa8/9QHq5P9bYe+U4raYEcr7GsGry0g7cxxXYXxZ+Cv JS66di1SVSZJLgWz5jffz+buYg== X-Google-Smtp-Source: ABdhPJyb7RSeWvgIu/XMZI6hViaDXKdRVhUABAMdlPkExjnMZkDVSCxU0agCcrztfH45qOGSOqpnBg== X-Received: by 2002:a17:906:730c:b0:6f0:f69:b2e with SMTP id di12-20020a170906730c00b006f00f690b2emr16867495ejc.276.1650904205504; Mon, 25 Apr 2022 09:30:05 -0700 (PDT) Received: from [192.168.0.244] (xdsl-188-155-176-92.adslplus.ch. [188.155.176.92]) by smtp.gmail.com with ESMTPSA id s27-20020a50ab1b000000b00425e8a3a7a0sm1589979edc.10.2022.04.25.09.30.04 (version=TLS1_3 cipher=TLS_AES_128_GCM_SHA256 bits=128/128); Mon, 25 Apr 2022 09:30:05 -0700 (PDT) Message-ID: Date: Mon, 25 Apr 2022 18:30:04 +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 1/2] arm64: dts: renesas: r9a07g044: Fix external clk node names Content-Language: en-US To: Biju Das , Rob Herring , Krzysztof Kozlowski Cc: Geert Uytterhoeven , Magnus Damm , "linux-renesas-soc@vger.kernel.org" , "devicetree@vger.kernel.org" , Chris Paterson , Biju Das , Prabhakar Mahadev Lad References: <20220423140658.145000-1-biju.das.jz@bp.renesas.com> <7bd2ae6d-c55f-4ab7-0c98-72da0d5d4050@linaro.org> <886fda10-fad9-83c4-10f1-1ae36cf0a6b0@linaro.org> From: Krzysztof Kozlowski In-Reply-To: Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit Precedence: bulk List-ID: X-Mailing-List: devicetree@vger.kernel.org On 25/04/2022 18:26, Biju Das wrote: >> >> What do you mean "ok"? I said "clk-[0-9]", so "clk-0", "clk-1", "clk-2" >> and so on. No specific prefix. > > Ah ok. > > As you mentioned above "generic part is "clk". You add specific audio/audio-X prefix > or suffix" > > So based on that, I thought "clk" is generic part and "-1-audio" as suffix, "clk-1-audio" > should be acceptable. > > For eg:- If I plan to match the label name with the hardware manual(audio_clk1), Labels are not restricted (except using [a-z0-9_], no dashes), so it is perfectly fine. > > then, as per the discussion we have, the node names should be > > either > > "audio_clk1: clk-0" > > or > > "audio_clk1: clk-1" > > Or > > "audio_clk1: audio1-clk" > > Correct? Yes, correct. Best regards, Krzysztof