Received: by 2002:a25:7ec1:0:0:0:0:0 with SMTP id z184csp3926702ybc; Tue, 26 Nov 2019 00:40:20 -0800 (PST) X-Google-Smtp-Source: APXvYqyyxeD7qky9MlHCE79KfLcqUZWckbiqBV+ApSFUK71xETXLA6c997IMal9vxY1diWev6Rkp X-Received: by 2002:a17:906:3602:: with SMTP id q2mr5676220ejb.167.1574757620434; Tue, 26 Nov 2019 00:40:20 -0800 (PST) ARC-Seal: i=1; a=rsa-sha256; t=1574757620; cv=none; d=google.com; s=arc-20160816; b=O8lv6uljmS63f0BkODGEMwU7+mxEOIFu+b8crCMJZHQxC48FD4GaB0Pbyb0uG0Rito vVrzJgJgWgyE0Uaht0vRWbyagGRuVRKg/whC9CFpId987YBPmHQbIKs3Sjk+w3klgLJj XND1gq0Y/z7DV47cTBiZbfv5qqaSs4blAITnP9cwVLe7QoM8sZ/ongrjq4a/pv0JYp2R khIeRJBNYM0fWt2yUJOXaWEdAXXx2cfwu8PO5A9Gl73MagpxcQ/ZrwvzMAX8/ngnRmnD 5Okg8LZ4c37jV32HE1BTNflHe/j7ElczyxS75dn9FqWijn4W7dF2RvyMH7CHmCRvUtMi xCDw== 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=ghr7jBLVPFv5KXin/jCgW73I7qoGCQF1JWOf5hUItPQ=; b=GFoUoOAv+RtJMxR22A8ybMFTRwxT1w1bc9RBTqmfD+fEshhDNSoZG79qwq2OA35oTx 5hTKNJG1ZqMAWrWdb2ZwtlSTGagsVYhyNXCrHKse/GExz9qeY9WnA4uHoLrZWBlagwfN oH6SVwQOcu3GrE4oD6Sk35je6mbXl5NSz7UgpchjW1jdECneMZ2GdeOhtTgYP2J4Ikbt Ti9U1KuB7+3XHqtGZNci2gbThkkEhFJIdm7NAg6Qi7FrDp4myRBlZfYU7aZNQVPg8OIw HdV1gseepNSxjf7csX/YaI/JVvsTJ+AqBa3/WPYVIzCtdswzAPjRT3E2Mp9TefiKaZ50 7Huw== 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 f12si6364336eje.253.2019.11.26.00.39.56; Tue, 26 Nov 2019 00:40:20 -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 S1727543AbfKZIfg (ORCPT + 99 others); Tue, 26 Nov 2019 03:35:36 -0500 Received: from mga05.intel.com ([192.55.52.43]:18783 "EHLO mga05.intel.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1726192AbfKZIff (ORCPT ); Tue, 26 Nov 2019 03:35:35 -0500 X-Amp-Result: SKIPPED(no attachment in message) X-Amp-File-Uploaded: False Received: from fmsmga005.fm.intel.com ([10.253.24.32]) by fmsmga105.fm.intel.com with ESMTP/TLS/DHE-RSA-AES256-GCM-SHA384; 26 Nov 2019 00:35:35 -0800 X-ExtLoop1: 1 X-IronPort-AV: E=Sophos;i="5.69,245,1571727600"; d="scan'208";a="408588394" Received: from sgsxdev004.isng.intel.com (HELO localhost) ([10.226.88.13]) by fmsmga005.fm.intel.com with ESMTP; 26 Nov 2019 00:35:32 -0800 From: Dilip Kota To: robh@kernel.org, p.zabel@pengutronix.de, martin.blumenstingl@googlemail.com, devicetree@vger.kernel.org, linux-kernel@vger.kernel.org Cc: cheol.yong.kim@intel.com, chuanhua.lei@linux.intel.com, qi-ming.wu@intel.com, Dilip Kota Subject: [PATCH v4 1/2] dt-bindings: reset: Add YAML schemas for the Intel Reset controller Date: Tue, 26 Nov 2019 16:35:17 +0800 Message-Id: <4193fef447c220406ab39225eb3eb66025734cd3.1574755533.git.eswara.kota@linux.intel.com> 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 --- 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. + Reset cell count is 2 in the case of bit offset in + reset request and reset status registers is same. + Whereas 3 if 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