Received: by 2002:a25:8b91:0:0:0:0:0 with SMTP id j17csp18423787ybl; Fri, 3 Jan 2020 02:01:24 -0800 (PST) X-Google-Smtp-Source: APXvYqyWjdK0UgoEzkfMSI19FY8HosJEFOb0Xmc04q9uaRCEizAzclfEKbsAj35iLqnIs0AqZR6K X-Received: by 2002:a9d:470a:: with SMTP id a10mr42250668otf.370.1578045684362; Fri, 03 Jan 2020 02:01:24 -0800 (PST) ARC-Seal: i=1; a=rsa-sha256; t=1578045684; cv=none; d=google.com; s=arc-20160816; b=FUxOjil8x6qomHEuk32MMkMpuZ5+rUOxuGS49n3BWo5eFWON8nuZ/+3Vw9N8XyAFRP sRYB4s+xvO5hnO5pM68+zsfvesUPW3l3P0+87L08w0twKP2kG6OUzRW1YJJA+4H93hoj a6X/QPYDV5Urr3qhuIKsmOiLGC9KJ+scYMQJHLIF1RhN5LbLa7abm58WvYpcEiuLaE5u h+9jnLlNiS+HbF5YZbxvsk7IegEn7HwV7Kxq/XaQ8S4QP8GF5/zI+6peKvuz4MV9Cqhu MyKBW437siyGlqYmk+aZGzV8Td3A6H3g1Se8mHKfEvqlQG+9MFAMdkQniXVDNTcXSVNv tdVg== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:sender:message-id:date:subject:cc:to:from; bh=1PTTEzm7wWuC/pylNMXkVG0kOJS7dOV/zk2ug35AqEA=; b=wI7mfCMSvua7SBvO0hwdwcVmZAJgcPuGVRausoeCqiCSZWEdPzoO0cEJhhmwSMrz60 4wmd9MnOwcps1rlLdN8WVZHyQuT5r7+RB6P8ctbk/DPV8CBSOqyRHqVWjPT1pni2+wub X4DKjPlHhVj4tfMGMY6SdqP32LdcqFGJR55SEvAq8y6ot4aGUmz6tFyQlTKfo71RZ7EY yP4vl5V42AcvCRtURoRuibfa+E4JWG2JTjj/BsVU/XAWUKmk8LKSJtyUfKzefwfWEeND Wg0mODNhVSh43+M5FpcrrxMkWuw10jEzxXjelih43VLP1Hqgd2b/qWscKhi8e7t3FFiW dKYA== ARC-Authentication-Results: i=1; mx.google.com; spf=pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org; dmarc=fail (p=NONE sp=NONE dis=NONE) header.from=intel.com Return-Path: Received: from vger.kernel.org (vger.kernel.org. [209.132.180.67]) by mx.google.com with ESMTP id 185si27370717oie.52.2020.01.03.02.01.09; Fri, 03 Jan 2020 02:01:24 -0800 (PST) Received-SPF: pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) client-ip=209.132.180.67; Authentication-Results: mx.google.com; spf=pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org; dmarc=fail (p=NONE sp=NONE dis=NONE) header.from=intel.com Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1727484AbgACKAZ (ORCPT + 99 others); Fri, 3 Jan 2020 05:00:25 -0500 Received: from mga01.intel.com ([192.55.52.88]:2331 "EHLO mga01.intel.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1725972AbgACKAZ (ORCPT ); Fri, 3 Jan 2020 05:00:25 -0500 X-Amp-Result: SKIPPED(no attachment in message) X-Amp-File-Uploaded: False Received: from orsmga005.jf.intel.com ([10.7.209.41]) by fmsmga101.fm.intel.com with ESMTP/TLS/DHE-RSA-AES256-GCM-SHA384; 03 Jan 2020 02:00:25 -0800 X-ExtLoop1: 1 X-IronPort-AV: E=Sophos;i="5.69,390,1571727600"; d="scan'208";a="394288544" Received: from sgsxdev004.isng.intel.com (HELO localhost) ([10.226.88.13]) by orsmga005.jf.intel.com with ESMTP; 03 Jan 2020 02:00:22 -0800 From: Dilip Kota To: devicetree@vger.kernel.org, linux-kernel@vger.kernel.org Cc: p.zabel@pengutronix.de, robh@kernel.org, martin.blumenstingl@googlemail.com, cheol.yong.kim@intel.com, chuanhua.lei@linux.intel.com, qi-ming.wu@intel.com, Dilip Kota Subject: [PATCH v6 1/2] dt-bindings: reset: Add YAML schemas for the Intel Reset controller Date: Fri, 3 Jan 2020 18:00:17 +0800 Message-Id: X-Mailer: git-send-email 2.11.0 Sender: linux-kernel-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Add YAML schemas for the reset controller on Intel Gateway SoC. Signed-off-by: Dilip Kota Reviewed-by: Rob Herring --- Changes on v6: No changes Changes on v5: Add Reviewed-by: Rob Herring Rebase patches on v5.5-rc1 kernel Changes on v4: Address Rob review comments Drop oneOf and items for 'compatible' Add maxItems for 'reg' and 'intel,global-reset' Changes on v3: Fix DTC warnings Add support to legacy xrx200 SoC Change file name to intel,rcu-gw.yaml .../devicetree/bindings/reset/intel,rcu-gw.yaml | 63 ++++++++++++++++++++++ 1 file changed, 63 insertions(+) create mode 100644 Documentation/devicetree/bindings/reset/intel,rcu-gw.yaml diff --git a/Documentation/devicetree/bindings/reset/intel,rcu-gw.yaml b/Documentation/devicetree/bindings/reset/intel,rcu-gw.yaml new file mode 100644 index 000000000000..246dea8a2ec9 --- /dev/null +++ b/Documentation/devicetree/bindings/reset/intel,rcu-gw.yaml @@ -0,0 +1,63 @@ +# SPDX-License-Identifier: (GPL-2.0 OR BSD-2-Clause) +%YAML 1.2 +--- +$id: http://devicetree.org/schemas/reset/intel,rcu-gw.yaml# +$schema: http://devicetree.org/meta-schemas/core.yaml# + +title: System Reset Controller on Intel Gateway SoCs + +maintainers: + - Dilip Kota + +properties: + compatible: + enum: + - intel,rcu-lgm + - intel,rcu-xrx200 + + reg: + description: Reset controller registers. + maxItems: 1 + + intel,global-reset: + description: Global reset register offset and bit offset. + allOf: + - $ref: /schemas/types.yaml#/definitions/uint32-array + - maxItems: 2 + + "#reset-cells": + minimum: 2 + maximum: 3 + description: | + First cell is reset request register offset. + Second cell is bit offset in reset request register. + Third cell is bit offset in reset status register. + For LGM SoC, reset cell count is 2 as bit offset in + reset request and reset status registers is same. Whereas + 3 for legacy SoCs as bit offset differs. + +required: + - compatible + - reg + - intel,global-reset + - "#reset-cells" + +additionalProperties: false + +examples: + - | + rcu0: reset-controller@e0000000 { + compatible = "intel,rcu-lgm"; + reg = <0xe0000000 0x20000>; + intel,global-reset = <0x10 30>; + #reset-cells = <2>; + }; + + pwm: pwm@e0d00000 { + status = "disabled"; + compatible = "intel,lgm-pwm"; + reg = <0xe0d00000 0x30>; + clocks = <&cgu0 1>; + #pwm-cells = <2>; + resets = <&rcu0 0x30 21>; + }; -- 2.11.0