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 EF1D3C433FE for ; Wed, 23 Nov 2022 09:37:25 +0000 (UTC) Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S237927AbiKWJhY (ORCPT ); Wed, 23 Nov 2022 04:37:24 -0500 Received: from lindbergh.monkeyblade.net ([23.128.96.19]:57392 "EHLO lindbergh.monkeyblade.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S237998AbiKWJhD (ORCPT ); Wed, 23 Nov 2022 04:37:03 -0500 Received: from mail-lf1-x12d.google.com (mail-lf1-x12d.google.com [IPv6:2a00:1450:4864:20::12d]) by lindbergh.monkeyblade.net (Postfix) with ESMTPS id 87359B9BB3 for ; Wed, 23 Nov 2022 01:34:19 -0800 (PST) Received: by mail-lf1-x12d.google.com with SMTP id g12so27346257lfh.3 for ; Wed, 23 Nov 2022 01:34:19 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=linaro.org; s=google; h=content-transfer-encoding:in-reply-to:from:references:cc:to :content-language:subject:user-agent:mime-version:date:message-id :from:to:cc:subject:date:message-id:reply-to; bh=u8s2q4f5w/4IPeNoebI+nh7g4r0oLg4pQUjqS5WFRYk=; b=FLRmBljcZFVd3iH3NW/n9fV3NPM5BxVX81sqR6LZ5RbeAjwAUUACbw7bpAZTUCkHbg UbLObKsVx6nYalwPse7wmcQC25HSwU38xJ//YSSuY3Vksu8EV5v5XbGXI6+cbOvQDyYx my4KGi161b0Pitcm7UZF0+yxoQ5eKEEisxE1HLR3Q47rHpGxWxJChp7fnH49Ey6Zrdyc Bh5td7XP54jj5mPNPbrbsqYpl0XmY5dugMm9p2q31pwT4wIbIGUCTMIvqfz7l4WUTJ8v ptI8vjj1FYlKgmvDZYPmWU+2/54FuurMfxTrl/VXOSfvxMVdeWLqu5m/SzeDXPJ+uy/R jQKQ== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20210112; h=content-transfer-encoding:in-reply-to:from:references:cc:to :content-language:subject:user-agent:mime-version:date:message-id :x-gm-message-state:from:to:cc:subject:date:message-id:reply-to; bh=u8s2q4f5w/4IPeNoebI+nh7g4r0oLg4pQUjqS5WFRYk=; b=UvJPnK4LIl6jwguIgRG+8JEwbZE4lhO39kOUivw7tTcywKguM+dmrqyi9/zDmt+aAd zknIGJzeAnz/DztMsat7QdO6Fpm3xNh7cSVgO6mIRPoLtUkWOkcsyEIDVppGEpOlvPo6 bjWJcGUW8TqDuWZaKTIxCLZG5nb2IkXq5xly4ZbFWxNY+YL1Q2rUYNW8kFWzTpT6rSpz 30Vc/lDLmisvSMsQ0+/9xj/i9TmWN7GV3Cly3E8ryNX9tRbKs4UpUfD/RAc/uyy23Ky9 CPkEM9EPtRhxzS1LvUuxGBwsuN/6/xwym6sjhFPaGtq3oXzMhlcRknTTVdXypIzwAvRX wDkw== X-Gm-Message-State: ANoB5plbiJSERYaOqEExcnzAkEIHielfKBxkEB364oAH7qyL6of8qUxx LImWfkGsxEiGl92AVZj1vwcVDgFVkuZzH3+5 X-Google-Smtp-Source: AA0mqf7D378yEUBmE+4xmSMMT7l3z+IL8SiWvdALDT0ayiY7awFjMZCumei8TeFsYJZZ0ZLkVaiH9g== X-Received: by 2002:a05:6512:258a:b0:4a2:27f0:46a5 with SMTP id bf10-20020a056512258a00b004a227f046a5mr4360007lfb.611.1669196057899; Wed, 23 Nov 2022 01:34:17 -0800 (PST) Received: from [192.168.0.20] (088156142067.dynamic-2-waw-k-3-2-0.vectranet.pl. [88.156.142.67]) by smtp.gmail.com with ESMTPSA id s5-20020a056512314500b004a1e7216131sm2806605lfi.116.2022.11.23.01.34.16 (version=TLS1_3 cipher=TLS_AES_128_GCM_SHA256 bits=128/128); Wed, 23 Nov 2022 01:34:17 -0800 (PST) Message-ID: Date: Wed, 23 Nov 2022 10:34:16 +0100 MIME-Version: 1.0 User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:102.0) Gecko/20100101 Thunderbird/102.5.0 Subject: Re: [PATCH v2 07/14] dt-bindings: clock: Add StarFive JH7110 system and always-on clock definitions Content-Language: en-US To: Hal Feng , linux-riscv@lists.infradead.org, devicetree@vger.kernel.org, linux-clk@vger.kernel.org Cc: Conor Dooley , Palmer Dabbelt , Rob Herring , Krzysztof Kozlowski , Stephen Boyd , Michael Turquette , Philipp Zabel , Emil Renner Berthing , linux-kernel@vger.kernel.org References: <20221118010627.70576-1-hal.feng@starfivetech.com> <20221118010627.70576-8-hal.feng@starfivetech.com> <4d1fbddc-ee8b-1ab3-d1a9-8496bda3f668@linaro.org> <1db979d5-1fb6-f3c9-8ce0-e3e2e23e5d14@starfivetech.com> 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 22/11/2022 09:04, Hal Feng wrote: >>>> Filename based / the same as compatible (or bindings filename). >>> >>> Should I split this file into two files for "SYSCRG" and "AONCRG", which >>> maybe named as "starfive-jh7110-sys.h" and "starfive-jh7110-aon.h". Ditto >>> for the patch 8. >> >> Does not have to be, but anyway naming must follow compatible naming, so >> vendor,soc-device. > > Can I name it "starfive,jh7110-crg.h"? This file is included in > starfive,jh7110-syscrg.yaml and starfive,jh7110-aoncrg.yaml. Sounds ok. Best regards, Krzysztof