Received: by 2002:a05:6a10:9848:0:0:0:0 with SMTP id x8csp726315pxf; Wed, 24 Mar 2021 14:33:51 -0700 (PDT) X-Google-Smtp-Source: ABdhPJzcORHP0eygxADARxqC5H2JaQAW9km75o1LfbdyWkbRZMkld2F0CTn1Pq/yvIe3d+Yw9sU/ X-Received: by 2002:a17:906:3d62:: with SMTP id r2mr5776371ejf.488.1616621631581; Wed, 24 Mar 2021 14:33:51 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; t=1616621631; cv=none; d=google.com; s=arc-20160816; b=MZgUd0tP/QFG5dUXiyT49id0Wz9hLBFWwqs4HcexIRYvP54FqLNmDQy28z4POYizmq FnEs5KDMCCIzGIc2mibNp2/tPQw33GIn+iNBfVLJv9KazX5nu17cmQOGi/yCD5sBe7KV 3KyNFjTjhVgByag0dbfoaWhkkud2cPEBLJIldEEPpaeVqCk2mi9p0dcB01j0Hi2xEljq R/OzGyVYCBCRe2duvqebnUmppKtlLDTzfF+Pi6MXNbU6Pz+hUHP/Ap/sTD1U73rzm1ZG 64qUzEorvZrn30OP0k7AUcUpedR0FAoXH5dON21zzNYzyy5HHd5q9mndHfRqETgwvfVk lJfw== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:content-transfer-encoding:content-language :in-reply-to:mime-version:user-agent:date:message-id:from:references :cc:to:subject:dkim-signature; bh=84HXR80VeHqLZESZc4iMlUDSruLJkHK/M+dHGF0r0qw=; b=0LMFeZWejednmyUKgBSFsWVbfat5QKxSDUxc+7hkrcQEoWOLSzpezoN9JCKqyRXDLp 6MC5O9R088u5P/lCSlREj0oTr4I4banlvwR9KWTB8eTtGvtWTKQpPv4SgnK/svZZUMYa fcq6XYo5wWB565Ov466/b8/ORia/6aLALga1yPrfQzGsTBCwGFM7QsKTU6Lj5UH58MpV 6iz+8CSaDXFmEXB2kzmtXyduPi5p7HgjybdnfeCl/WF+kl4dJTnZzFj0T9kbjWcMZh6Z vcDDhL+M1rLwiDUr9IdynaRsNF+XHqVOV5E4xqeiRDMJoTOjZiNm1KJ4NOGnOc9hsGLG 0mQQ== ARC-Authentication-Results: i=1; mx.google.com; dkim=pass header.i=@gmail.com header.s=20161025 header.b=Oz0KBish; 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=QUARANTINE dis=NONE) header.from=gmail.com Return-Path: Received: from vger.kernel.org (vger.kernel.org. [23.128.96.18]) by mx.google.com with ESMTP id r15si2660727edq.306.2021.03.24.14.33.15; Wed, 24 Mar 2021 14:33:51 -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=@gmail.com header.s=20161025 header.b=Oz0KBish; 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=QUARANTINE dis=NONE) header.from=gmail.com Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S233977AbhCWXCA (ORCPT + 99 others); Tue, 23 Mar 2021 19:02:00 -0400 Received: from lindbergh.monkeyblade.net ([23.128.96.19]:47250 "EHLO lindbergh.monkeyblade.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S233782AbhCWXBd (ORCPT ); Tue, 23 Mar 2021 19:01:33 -0400 Received: from mail-lj1-x22c.google.com (mail-lj1-x22c.google.com [IPv6:2a00:1450:4864:20::22c]) by lindbergh.monkeyblade.net (Postfix) with ESMTPS id E7FF3C061574; Tue, 23 Mar 2021 16:01:32 -0700 (PDT) Received: by mail-lj1-x22c.google.com with SMTP id f26so27813805ljp.8; Tue, 23 Mar 2021 16:01:32 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=subject:to:cc:references:from:message-id:date:user-agent :mime-version:in-reply-to:content-language:content-transfer-encoding; bh=84HXR80VeHqLZESZc4iMlUDSruLJkHK/M+dHGF0r0qw=; b=Oz0KBishfAMWO1yb3BpbgXhz7TWlRcehMQEHkJwal80qEUOQUATrfcXELGBvDnJG7A pQydMuERCrpZLnZ8vLvJMkPPcIbRYJSxvUK8LZ1MGfRuhyb9aheNjSEMjq/dvwB4LpcV 2GGTDvDhVMWjzoqypG+Kl2XhsK2dun22t6VmcbdyfuUnG4e9MWbEKh14Mg8WoZCHPJu/ g1JCpUSJ65LrsVBftTHkXiljFCBUQF+RDwUS2JRKfKYWybis5CvDe3SaKI6RByO4utA4 CbSZWPmabvcoO52k4I0KZa9ey/RJxea+24Kh2LayAB4KgVSIU1Ws87nQ3gcBadNGBSDf pjig== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:subject:to:cc:references:from:message-id:date :user-agent:mime-version:in-reply-to:content-language :content-transfer-encoding; bh=84HXR80VeHqLZESZc4iMlUDSruLJkHK/M+dHGF0r0qw=; b=HAafdFRUPa06lxaqSKIX07s+J0Xk1JHgS9crRw9xdrZg/AJ7dH6HKoEw+reahB2ZbP hmuRGBrWDldATv3zAl9s7LBZ8VF7c938wutyIEENzg/1wyjhkDw/lfjU8ECz99DNIiAF zjA+MFaPj8J9udnr0JpB4Up7g/6hFvaGiK+EBDYSZyKk4UXo2KAGrHfmN9AuqBF5KR8H VV6DzZ1McVuvvfq71Bdwd+kv9DgBEdIkaBS/4Vf2yzAz2INwiR7rfv36vxy2rmrwWmKy 7GbPGyzu6tPSSbaRVbVfnBOk56z8h1dhIGjKSTk3MvSwgVT0R4S9NqPkUOSt5VEDuaE8 if4Q== X-Gm-Message-State: AOAM530J4U104LHlDynYGoiuc0UZdKfyY5FQPxZQtfHeEAfF+njIdlxc hDeEvyeNT2ankndwFXuzmJZ68nSbQCM= X-Received: by 2002:a2e:8e36:: with SMTP id r22mr131297ljk.427.1616540491159; Tue, 23 Mar 2021 16:01:31 -0700 (PDT) Received: from [192.168.2.145] (109-252-193-60.dynamic.spd-mgts.ru. [109.252.193.60]) by smtp.googlemail.com with ESMTPSA id j19sm41718lfg.225.2021.03.23.16.01.30 (version=TLS1_3 cipher=TLS_AES_128_GCM_SHA256 bits=128/128); Tue, 23 Mar 2021 16:01:30 -0700 (PDT) Subject: Re: [PATCH v4 3/6] dt-bindings: power: tegra: Add binding for core power domain To: Rob Herring Cc: Thierry Reding , Jonathan Hunter , Mark Brown , Paul Fertser , Matt Merhar , Peter Geis , Nicolas Chauvet , Viresh Kumar , Stephen Boyd , =?UTF-8?B?TWljaGHFgiBNaXJvc8WCYXc=?= , Krzysztof Kozlowski , devicetree@vger.kernel.org, linux-tegra@vger.kernel.org, linux-pm@vger.kernel.org, linux-kernel@vger.kernel.org References: <20210314164810.26317-1-digetx@gmail.com> <20210314164810.26317-4-digetx@gmail.com> <20210323224826.GA1490612@robh.at.kernel.org> From: Dmitry Osipenko Message-ID: Date: Wed, 24 Mar 2021 02:01:29 +0300 User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:78.0) Gecko/20100101 Thunderbird/78.8.1 MIME-Version: 1.0 In-Reply-To: <20210323224826.GA1490612@robh.at.kernel.org> Content-Type: text/plain; charset=utf-8 Content-Language: en-US Content-Transfer-Encoding: 8bit Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org 24.03.2021 01:48, Rob Herring пишет: > On Sun, Mar 14, 2021 at 07:48:07PM +0300, Dmitry Osipenko wrote: >> All NVIDIA Tegra SoCs have a core power domain where majority of hardware >> blocks reside. Add binding for the core power domain. >> >> Signed-off-by: Dmitry Osipenko >> --- >> .../power/nvidia,tegra20-core-domain.yaml | 51 +++++++++++++++++++ >> 1 file changed, 51 insertions(+) >> create mode 100644 Documentation/devicetree/bindings/power/nvidia,tegra20-core-domain.yaml >> >> diff --git a/Documentation/devicetree/bindings/power/nvidia,tegra20-core-domain.yaml b/Documentation/devicetree/bindings/power/nvidia,tegra20-core-domain.yaml >> new file mode 100644 >> index 000000000000..4692489d780a >> --- /dev/null >> +++ b/Documentation/devicetree/bindings/power/nvidia,tegra20-core-domain.yaml >> @@ -0,0 +1,51 @@ >> +# SPDX-License-Identifier: GPL-2.0-only OR BSD-2-Clause >> +%YAML 1.2 >> +--- >> +$id: http://devicetree.org/schemas/power/nvidia,tegra20-core-domain.yaml# >> +$schema: http://devicetree.org/meta-schemas/core.yaml# >> + >> +title: NVIDIA Tegra Core Power Domain >> + >> +maintainers: >> + - Dmitry Osipenko >> + - Jon Hunter >> + - Thierry Reding >> + >> +allOf: >> + - $ref: power-domain.yaml# >> + >> +properties: >> + compatible: >> + enum: >> + - nvidia,tegra20-core-domain >> + - nvidia,tegra30-core-domain >> + >> + operating-points-v2: >> + description: >> + Should contain level, voltages and opp-supported-hw property. >> + The supported-hw is a bitfield indicating SoC speedo or process >> + ID mask. >> + >> + "#power-domain-cells": >> + const: 0 >> + >> + power-supply: >> + description: >> + Phandle to voltage regulator connected to the SoC Core power rail. >> + >> +required: >> + - compatible >> + - operating-points-v2 >> + - "#power-domain-cells" >> + - power-supply >> + >> +additionalProperties: false >> + >> +examples: >> + - | >> + power-domain { >> + compatible = "nvidia,tegra20-core-domain"; >> + operating-points-v2 = <&opp_table>; >> + power-supply = <®ulator>; >> + #power-domain-cells = <0>; > > AFAICT, there's no way to access this 'hardware'? correct