Received: by 2002:a05:6a10:c7c6:0:0:0:0 with SMTP id h6csp2160755pxy; Mon, 2 Aug 2021 22:06:43 -0700 (PDT) X-Google-Smtp-Source: ABdhPJz5Qdk2MQu5SJ2ZJBjm2U984jQm9Afh2EgL4HBV0jeJUiAaAcQtM8YK4Vt1lpQEnUZ+eDVP X-Received: by 2002:a05:6638:1251:: with SMTP id o17mr6485933jas.15.1627967203443; Mon, 02 Aug 2021 22:06:43 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; t=1627967203; cv=none; d=google.com; s=arc-20160816; b=Pw3nFd/MO8dHzS8rNS89N064BSOYaGuX1mfu23UrW/auH19P//OIpGXCmlwSIlOe4Z rVMFS1kSk+qjzKTcGcV2nhAFJJBokEb45uToCkJMqcrFePZT0hMHTZvYRTQZZIUcB9p5 347CKGW1EvcN9Te+6ZpmfuitKtZ7vw3EZQg/eu5vbe8NK/ypIM+mcbGA8BqRYzKUBS// JjCqxYFG/PXmmh4norEvAJEmjAUFc8LldDLddObqLUjyQ5cNVmKm6NB8RA9PQFp//28V +SqTkjtYhQ4zfEIoJi71F2Ct1JSMnUJBLBNDFezqS7Njwp9tUNh7B+e9s0gzjqpxJeOi s+fg== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:user-agent:in-reply-to:content-disposition :mime-version:references:message-id:subject:cc:to:from:date :dkim-signature; bh=t1x2eb6ArQwcke53LEN8sEzOMirAau5sq1TSi3sUCsY=; b=jhaINzfFV6IMIoQTM9vB4cdLRlzDycp/EbTKF41EtchpC9Ii1weXz97YwVfM9+65FN 007ivRheDyVCuq7Ro63vs5jG1HwLlUlGQWpQvafLxosS2dPwZOmJjDUXWTrFwn/B69TH PH4Thl/I1qZr/2YEnLcM5qt8KRnX97pfsVM5TIOREpJ3AOlkYNSY2AGna0f9PuYOFh8/ oorNq++Rg9qsphDvkmgGFmFr2wMmigQMJ2MtirFrk6XIQrtJixQQTRXV1GUsypxEPEdc GCgDy1V/A2qIXgZl80Jz8MrySEYLZrgOMb5PGpEIEbRsdQ//Nk53FG80/3h442YMsKOp 09aA== ARC-Authentication-Results: i=1; mx.google.com; dkim=pass header.i=@linaro.org header.s=google header.b=DAD9hD6c; spf=pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 23.128.96.18 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org; dmarc=pass (p=NONE sp=NONE dis=NONE) header.from=linaro.org Return-Path: Received: from vger.kernel.org (vger.kernel.org. [23.128.96.18]) by mx.google.com with ESMTP id j17si13562081jaj.70.2021.08.02.22.06.31; Mon, 02 Aug 2021 22:06:43 -0700 (PDT) Received-SPF: pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 23.128.96.18 as permitted sender) client-ip=23.128.96.18; Authentication-Results: mx.google.com; dkim=pass header.i=@linaro.org header.s=google header.b=DAD9hD6c; spf=pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 23.128.96.18 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org; dmarc=pass (p=NONE sp=NONE dis=NONE) header.from=linaro.org Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S234097AbhHCFFy (ORCPT + 99 others); Tue, 3 Aug 2021 01:05:54 -0400 Received: from lindbergh.monkeyblade.net ([23.128.96.19]:34018 "EHLO lindbergh.monkeyblade.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S233710AbhHCFFv (ORCPT ); Tue, 3 Aug 2021 01:05:51 -0400 Received: from mail-pj1-x1029.google.com (mail-pj1-x1029.google.com [IPv6:2607:f8b0:4864:20::1029]) by lindbergh.monkeyblade.net (Postfix) with ESMTPS id 4EB64C06175F for ; Mon, 2 Aug 2021 22:05:41 -0700 (PDT) Received: by mail-pj1-x1029.google.com with SMTP id pj14-20020a17090b4f4eb029017786cf98f9so3121294pjb.2 for ; Mon, 02 Aug 2021 22:05:41 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=linaro.org; s=google; h=date:from:to:cc:subject:message-id:references:mime-version :content-disposition:in-reply-to:user-agent; bh=t1x2eb6ArQwcke53LEN8sEzOMirAau5sq1TSi3sUCsY=; b=DAD9hD6clhuKpwr6lD/ftBB86FlJPFcaeGWcqGpbezF8x11hUauwJjYBYtgWpTkUE4 ekMiL6uSzYSub/Fm2bcYDjHl2R96wJQ2EN4ZFJPtPf5Bb/DdW4nwnjfFRc7nn+kMpju0 d/Q8MMNpte5V74V+nn5H0Oj4SHmd27ARSMfgTUnlaPiD8ajWiZUMGz0v6ffTqHd3CPns OjmeWF/RnGRxCUn813IkiM8u1HBMYfrHjm7ry0GLMPLUM56vKjYKFdi9z+XP/2Uwg7JQ Tt6ALJD5AZfATEbA86bZEbYTrn67HWfeUviDgNGBD/8Xd76PmQwVQIsG41ozOyQkx5Qf HuRQ== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:date:from:to:cc:subject:message-id:references :mime-version:content-disposition:in-reply-to:user-agent; bh=t1x2eb6ArQwcke53LEN8sEzOMirAau5sq1TSi3sUCsY=; b=tD5h2WTOjUkDv2dtVMX1uEv3IPesnEzsDrozwATLDgxWJ3JkIZi/S73b646Zt/g5Ni XXDp6YtoxCzcJF3k5VEq7rrx4gdxtJFV+9aL57sKa5YPNo7KS1t4YCwm6q4ayePisagt 6AhFDj+NAUpZJFmfHnCtbIEU0pLadM0t+H4+w+TcMdgFwASmuEYlFgCOutqg/xrNZWxK NAxX5St3XI6ye4K5oaF3TFpAWMJAW9Chf/onXSqoVSmCdyVIBqRUIfssOUtTX/0QI5uQ 641Dx/Uk7WtBAW5ITeAYqTQoofkPW0J6+DNsuZ512iBQadQmdGwVwVrRbyoY+2DKEzJz Y4lg== X-Gm-Message-State: AOAM532qUgCk7V7i0Q6TkPLsGz+NnMuiYs3ZVxG/bgpPg4K5x0kwS3Ll ewl7kStNfwpU5/lP1pjzSclRoYHjCTXYOw== X-Received: by 2002:a62:606:0:b029:3b6:7e9a:fd2c with SMTP id 6-20020a6206060000b02903b67e9afd2cmr13151849pfg.24.1627967140745; Mon, 02 Aug 2021 22:05:40 -0700 (PDT) Received: from localhost ([122.172.201.85]) by smtp.gmail.com with ESMTPSA id s7sm9910588pjg.34.2021.08.02.22.05.39 (version=TLS1_3 cipher=TLS_AES_256_GCM_SHA384 bits=256/256); Mon, 02 Aug 2021 22:05:40 -0700 (PDT) Date: Tue, 3 Aug 2021 10:35:38 +0530 From: Viresh Kumar To: Hector Yuan Cc: linux-mediatek@lists.infradead.org, linux-arm-kernel@lists.infradead.org, linux-pm@vger.kernel.org, "Rafael J. Wysocki" , Rob Herring , devicetree@vger.kernel.org, linux-kernel@vger.kernel.org, wsd_upstream@mediatek.com Subject: Re: [PATCH v13 1/2] dt-bindings: cpufreq: add bindings for MediaTek cpufreq HW Message-ID: <20210803050538.g6aj2zsep735ywqv@vireshk-i7> References: <1627574891-26514-1-git-send-email-hector.yuan@mediatek.com> <1627574891-26514-2-git-send-email-hector.yuan@mediatek.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <1627574891-26514-2-git-send-email-hector.yuan@mediatek.com> User-Agent: NeoMutt/20180716-391-311a52 Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On 30-07-21, 00:08, Hector Yuan wrote: > From: "Hector.Yuan" > > Add devicetree bindings for MediaTek HW driver. > > Signed-off-by: Hector.Yuan > --- > .../bindings/cpufreq/cpufreq-mediatek-hw.yaml | 70 ++++++++++++++++++++ > 1 file changed, 70 insertions(+) > create mode 100644 Documentation/devicetree/bindings/cpufreq/cpufreq-mediatek-hw.yaml > > diff --git a/Documentation/devicetree/bindings/cpufreq/cpufreq-mediatek-hw.yaml b/Documentation/devicetree/bindings/cpufreq/cpufreq-mediatek-hw.yaml > new file mode 100644 > index 0000000..6bb2c97 > --- /dev/null > +++ b/Documentation/devicetree/bindings/cpufreq/cpufreq-mediatek-hw.yaml > @@ -0,0 +1,70 @@ > +# SPDX-License-Identifier: (GPL-2.0-only OR BSD-2-Clause) > +%YAML 1.2 > +--- > +$id: http://devicetree.org/schemas/cpufreq/cpufreq-mediatek-hw.yaml# > +$schema: http://devicetree.org/meta-schemas/core.yaml# > + > +title: MediaTek's CPUFREQ Bindings > + > +maintainers: > + - Hector Yuan > + > +description: > + CPUFREQ HW is a hardware engine used by MediaTek > + SoCs to manage frequency in hardware. It is capable of controlling frequency > + for multiple clusters. > + Should this somewhere have a reference to Documentation/devicetree/bindings/dvfs/performance-domain.yaml ? > +properties: > + compatible: > + const: mediatek,cpufreq-hw > + > + reg: > + minItems: 1 > + maxItems: 2 > + description: | > + Addresses and sizes for the memory of the > + HW bases in each frequency domain. > + > + "#performance-domain-cells": > + description: > + Number of cells in a performance domain specifier. Typically 1 for nodes > + providing multiple performance domains (e.g. performance controllers), > + but can be any value as specified by device tree binding documentation > + of particular provider. You say this can have any value, 1 or more, but then ... > + const: 1 You fix it to 1 ? Perhaps you should add a reference to the performance-domain.yaml here as well, and say const 1 here and describe how the parameter is going to be used. You should only explain it in respect to your SoC. But I am not that good with Yaml stuff, I will let Rob correct me here :) -- viresh