Received: by 2002:a05:6359:c8b:b0:c7:702f:21d4 with SMTP id go11csp3488811rwb; Fri, 30 Sep 2022 04:28:56 -0700 (PDT) X-Google-Smtp-Source: AMsMyM781Kz1LR2hPu0CD3VwGlHI0QwNxYSNXRwTknTcn3PdOIzMINdfkhqPRCjiL3YmEiWqTLtf X-Received: by 2002:a17:907:a0e:b0:780:72bb:5ce4 with SMTP id bb14-20020a1709070a0e00b0078072bb5ce4mr6220446ejc.234.1664537335851; Fri, 30 Sep 2022 04:28:55 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; t=1664537335; cv=none; d=google.com; s=arc-20160816; b=O13my1lRE11/DhyaBUaeUqxMdvv/rhjRt7NLugxJqucpDynrGqtT8V22RC+x3SYEhM 2eU5bcYbevQ9wMZVrPby9v30Q+WHdemox6A2ttXeSjaGbN/DPsJdE/dEosJLuHUJFMcO THq/rveZ2WQ9APsZIfCxcmvJSUNgGUAEXd6HmhM1rTcZg/SwzTAjPpd/MixC+GyK984P CN/K6apPUnPglWclgY6JkRN55c05aM1TnsCgdryktjUuE2BHfF9m58ddGs3dSH7Dd7Fi JmGDK3N8z5EGYS083PKQmDd6KJsLSk87mDFDeDuwdK2BhXM1Wm7Sh9jnh7LlRM9Gqqhu Jd5w== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:cc:to:subject:message-id:date:from:in-reply-to :references:mime-version:dkim-signature; bh=sLfdwfGAGdIy8Vpz4sY75ob+Mqn+9Fq+UGKJ4awK39k=; b=wOCe/tX46qAIUBCpzd+OQyHJJdrGtkuIAC2MrRQEY8m/i1V2lJmRSAmav9bURf7Gzg 5PHK/S1wAIThKGd/7B5Z89lghGK5pSasf0C4CnikSqH0wNJchKppp+HS2w9OJfne3FRJ NQPbaMwNNAAH87Yz3UxVxYuvBQG0zOL4vHTgUZCwW/8+mORWKwHTDmqWvKAnyewkT08U lhbGp2PVMfWgCy3DYvEPHL3TmzAej1Fn4E3KCRJLju7eLYdlV8KBF34JCT/ht9Hx0rJe +hngqnNfBDE+bI/3tic26G7DG33NntDbbrA8uOrDn52+yIHFHGMJTTf9o1NPg8x3FN1s P7Lw== ARC-Authentication-Results: i=1; mx.google.com; dkim=pass header.i=@gmail.com header.s=20210112 header.b=ZgK9Ndov; spf=pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 2620:137:e000::1:20 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org; dmarc=pass (p=NONE sp=QUARANTINE dis=NONE) header.from=gmail.com Return-Path: Received: from out1.vger.email (out1.vger.email. [2620:137:e000::1:20]) by mx.google.com with ESMTP id y16-20020a056402441000b00450fd95d41esi1983452eda.341.2022.09.30.04.28.30; Fri, 30 Sep 2022 04:28:55 -0700 (PDT) Received-SPF: pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 2620:137:e000::1:20 as permitted sender) client-ip=2620:137:e000::1:20; Authentication-Results: mx.google.com; dkim=pass header.i=@gmail.com header.s=20210112 header.b=ZgK9Ndov; spf=pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 2620:137:e000::1:20 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org; dmarc=pass (p=NONE sp=QUARANTINE dis=NONE) header.from=gmail.com Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S231543AbiI3LM7 (ORCPT + 99 others); Fri, 30 Sep 2022 07:12:59 -0400 Received: from lindbergh.monkeyblade.net ([23.128.96.19]:46454 "EHLO lindbergh.monkeyblade.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S229869AbiI3LMZ (ORCPT ); Fri, 30 Sep 2022 07:12:25 -0400 Received: from mail-ed1-x529.google.com (mail-ed1-x529.google.com [IPv6:2a00:1450:4864:20::529]) by lindbergh.monkeyblade.net (Postfix) with ESMTPS id 5A08A1D0C3; Fri, 30 Sep 2022 03:49:51 -0700 (PDT) Received: by mail-ed1-x529.google.com with SMTP id c30so5466622edn.2; Fri, 30 Sep 2022 03:49:51 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20210112; h=cc:to:subject:message-id:date:from:in-reply-to:references :mime-version:from:to:cc:subject:date; bh=sLfdwfGAGdIy8Vpz4sY75ob+Mqn+9Fq+UGKJ4awK39k=; b=ZgK9Ndov9go63KjVYLBZCO1oyIL+Rmq/LOi916CpZgVR1EqHENZGRBHqBHaXvYm2ql 9y1hCravDhx9MtMoOEXw0qcjwaG8Sm62TaZjrEijWi8reLJiWJvAeXwc4A+Mew8V3kzO Mlcvxx6wrjyr8uw+yiJ/i1h8Dnscd46dwzx9q010CfituYy8ku5W+rCQ0z0Xs9evM+2w 17A0QwIfyZOSigujAwqyEklg+2PcrL5hbOrp2s0BRPBVDvQ0fThyDTemK3du7sQiXAHn ltdnnqGEEaAp3rlS/H8NO3Q3kaf+t6dYmDWE6R1OyY/zINKueOybyJln71jcD+JOoOC5 fNOw== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20210112; h=cc:to:subject:message-id:date:from:in-reply-to:references :mime-version:x-gm-message-state:from:to:cc:subject:date; bh=sLfdwfGAGdIy8Vpz4sY75ob+Mqn+9Fq+UGKJ4awK39k=; b=qyKlDV/tXtEfVRKv1T0n3wHZl+9l4A6Oq6nwgq1CcmAzImv54zGVwK9DEjw/LSBxIN mqE38i4rwp1blLS3iFsRookzWUnugHZaJUxKx26aR9p5/NfYAAuqtXqDtVNpJp0rU3UD piDb0SwFPqqKj+wqBC3xlw63BFzG9o5Alr/SRZv3PpjxmKO/5YbmoNqM5M5alMrY2AxO DhaBssjC0rmBdIVB2gFiq/idCe8hgEBne3Zg5+BkNkBle1KxnIX1Lv7hAe6WAm0vy6Q2 8AS5/GfX7n2ZhKKwTjncw84KEs8pHjOENW8B+ASjzCL9LLbsxE/54wZQxnmn4gPQDtlM cEXA== X-Gm-Message-State: ACrzQf1teb4coIH9gXos54OXZZe8wQzBDatiIJiwslz/AoXz8znCvuxc KcrWiz7c4drjEGJ5zUVSTfIUAbBjvs5mW3ozf1E= X-Received: by 2002:a05:6402:40c2:b0:44f:963d:1ab4 with SMTP id z2-20020a05640240c200b0044f963d1ab4mr7425439edb.319.1664534989283; Fri, 30 Sep 2022 03:49:49 -0700 (PDT) MIME-Version: 1.0 References: <20220905230406.30801-1-prabhakar.mahadev-lad.rj@bp.renesas.com> <20220905230406.30801-3-prabhakar.mahadev-lad.rj@bp.renesas.com> <29d456ed-620c-8dc9-01f0-54f96b670b94@linaro.org> In-Reply-To: From: "Lad, Prabhakar" Date: Fri, 30 Sep 2022 11:49:22 +0100 Message-ID: Subject: Re: [PATCH v2 2/4] media: dt-bindings: Document Renesas RZ/G2L CRU block To: Laurent Pinchart , Krzysztof Kozlowski Cc: Lad Prabhakar , Mauro Carvalho Chehab , Rob Herring , Krzysztof Kozlowski , Philipp Zabel , Jacopo Mondi , =?UTF-8?Q?Niklas_S=C3=B6derlund?= , Sakari Ailus , Hans Verkuil , Geert Uytterhoeven , linux-media@vger.kernel.org, devicetree@vger.kernel.org, linux-kernel@vger.kernel.org, linux-renesas-soc@vger.kernel.org, Biju Das Content-Type: text/plain; charset="UTF-8" X-Spam-Status: No, score=-2.1 required=5.0 tests=BAYES_00,DKIM_SIGNED, DKIM_VALID,DKIM_VALID_AU,DKIM_VALID_EF,FREEMAIL_FROM, RCVD_IN_DNSWL_NONE,SPF_HELO_NONE,SPF_PASS autolearn=ham autolearn_force=no version=3.4.6 X-Spam-Checker-Version: SpamAssassin 3.4.6 (2021-04-09) on lindbergh.monkeyblade.net Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Hi Laurent and Krzysztof, On Thu, Sep 22, 2022 at 2:46 PM Laurent Pinchart wrote: > > On Wed, Sep 21, 2022 at 08:58:26PM +0200, Krzysztof Kozlowski wrote: > > On 21/09/2022 19:29, Laurent Pinchart wrote: > > >>>>> + clock-names: > > >>>>> + items: > > >>>>> + - const: vclk > > >>>>> + - const: pclk > > >>>>> + - const: aclk > > >>>> > > >>>> Drop the "clk" suffixes. Remaining names could be made a bit more readable. > > >>> > > >>> These names come from the documentation, isn't it better to match the > > >>> datasheet ? > > >> > > >> If datasheet calls it "vclk_really_clk_it_is_clk_clk", it's not the > > >> reason to use it. :) > > >> > > >> The "clk" is redundant even if the hardware engineer thought different. > > >> > > >> The same for IRQs ("tx" not "txirq"), for dmas ("tx" not "txdma"). > > > > > > I'd argue that naming clocks "v", "p" and "a" would be less readable and > > > more confusing. Is this a new rule ? > > > > Not really, but also it's only a style issue. > > > > Indeed "v" and "p" are not much better... but still "vclk" does not > > bring any additional information over "v". It's redundant. > > > > You can also drop entire entry - unless it helps in particular > > implementation. > > There are multiple clocks, so I think names are better than indices. If > you really insist we could name them "v", "p" and "a", but I think the > clk suffix here improves readability. If those clocks were named > "videoclk", "pixelclk" and "axiclk" I'd be fine dropping the suffix, but > that's not the case here. > I have got the below details from the HW team: CRU_SYSCLK -> System clock for CSI-2 DPHY CRU_VCLK -> video clock CRU_PCLK -> APB clock CRU_ACLK -> AXI clock So I'll rename the clocks to below respectively: + clock-names: + items: + - const: system + - const: video + - const: apb + - const: axi Does the above sound good? Cheers, Prabhakar