Received: by 2002:a05:6a10:8c0a:0:0:0:0 with SMTP id go10csp851551pxb; Fri, 22 Jan 2021 00:18:31 -0800 (PST) X-Google-Smtp-Source: ABdhPJy/vacQraf4T5xKuxDM1wi8i7qTXFx4XGvjRqN7rxSa+PZQ++uaZXKAHdkO2BCTdDTnaGiL X-Received: by 2002:a50:ee94:: with SMTP id f20mr2343701edr.222.1611303511624; Fri, 22 Jan 2021 00:18:31 -0800 (PST) ARC-Seal: i=1; a=rsa-sha256; t=1611303511; cv=none; d=google.com; s=arc-20160816; b=cyC1gWoUYSt5NJUHkvNUH3fBKKFEZEGcC9MHS7HGax5inCl5dQ4+NJ8zudBXGDDK7n t8uTOaPdQ1CP6Dgp8EcgXZAVNXc16lelST7kzzdJpHGjSCZ9DphpPE6wwPjvRDpoWFcA r5K/zlf+Lg0Tkok+4mHmgq5QYd97zrZD2KzbL5c1kXue/tdr0/8p3muAVqTuCVkoQt+T Uum+fMsi6KHbvltIjdhqiAYORfIMvAq7DdKsLTZN8WK1VLFu8/Lq0FhquDnWkmmCs2I3 P829vufuB8myWjCR+C3PxJGCU0YxY9b0l+aiPCWC7iUy3aoTnwDwidk+s0lmprKgROKB Bdlw== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:cc:to:subject:message-id:date:from:in-reply-to :references:mime-version:dkim-signature; bh=gC7rk0hC8Zt8EImbc+l8NzK6TAlu0aggpClSObCpidU=; b=Dq6+cjSsIVFD4f161hnA/XzbjBR/zvjV5kFlGAycPJsvLDBps8hvX8mMeJkCUpzpob bJtnGip0eNL78iVT1sIPJR91IwbKbU71jkxCgs8hMOBo0/UWxIbt1iaadepgmJdUuN9j V05T63O5cebNqwIpUF9seinDxKz2sfk2ERE6ZNkTVb8vGc9F/+HaQEV3X/RUhCQeINZ3 52cCa4sv/6cN22i0iy/VnWi0s1X1RpBahzKM5UJ+m/bImP7vN9+X2iEVvqCwkdwRI2h2 +9hhRPJe+CM7rJTooP5ZQIKQ1cC5SaJsK0OBIOBHhtY22rWoi9Hf8We9NCbrr8+bKsCT sjTg== ARC-Authentication-Results: i=1; mx.google.com; dkim=pass header.i=@chromium.org header.s=google header.b=P3JxhjaI; 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=chromium.org Return-Path: Received: from vger.kernel.org (vger.kernel.org. [23.128.96.18]) by mx.google.com with ESMTP id z27si3597675edi.351.2021.01.22.00.18.07; Fri, 22 Jan 2021 00:18:31 -0800 (PST) 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=@chromium.org header.s=google header.b=P3JxhjaI; 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=chromium.org Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1726954AbhAVIOa (ORCPT + 99 others); Fri, 22 Jan 2021 03:14:30 -0500 Received: from lindbergh.monkeyblade.net ([23.128.96.19]:55772 "EHLO lindbergh.monkeyblade.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1726736AbhAVIO2 (ORCPT ); Fri, 22 Jan 2021 03:14:28 -0500 Received: from mail-pf1-x433.google.com (mail-pf1-x433.google.com [IPv6:2607:f8b0:4864:20::433]) by lindbergh.monkeyblade.net (Postfix) with ESMTPS id ECB69C0613D6 for ; Fri, 22 Jan 2021 00:13:43 -0800 (PST) Received: by mail-pf1-x433.google.com with SMTP id o20so3235687pfu.0 for ; Fri, 22 Jan 2021 00:13:43 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=chromium.org; s=google; h=mime-version:references:in-reply-to:from:date:message-id:subject:to :cc; bh=gC7rk0hC8Zt8EImbc+l8NzK6TAlu0aggpClSObCpidU=; b=P3JxhjaIvdObM6aJYWr90L23Dzb8CMOC0rk24BlBQjbWg/a16XWIpqlZWm2eUo8MLW hAs74iu2Wt4jV6QJsRLQAVEpMGT5NJZFEcij38O9sWPaYQK5UdpoJAXoPHotHG61HZZo 1q26pUDgt46Qtt/6ZhJ9VvrCNSaGD2get1xX4= X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to:cc; bh=gC7rk0hC8Zt8EImbc+l8NzK6TAlu0aggpClSObCpidU=; b=nlExkvn3MkN4gqhi4pASLJVlxmUbIS/On6jf6i/ANXcsAPuHq33vsM3zwDmpGZX2eE kbyDKPbHcQB/zZ4d8eABkl3UjaeW43W9CDa+JU4+0BffCtWAoyVnfRhWfIj4bgD+E3ne qXG2ofs9LWlBvQgtdxaSiiF8TyQzNxAvdq/bJP0EbWXLCMQh4Y43vKvO+Cw1JpI7X4t8 45v5juHf9bpeEFk9I0W0OOEDIa3vJGpctpOXb0oqZdvsgPQOCzxxnjW/zMX7pEcwN8/A oeFUkZVuKG8YaKYgwp7o5LznLLoHZDSI3ImbQ8SZ0GXIv6sk0G3OxdFYee6Zr9M9dvpz 9VeA== X-Gm-Message-State: AOAM5311CAoiYAWq4Lp8LWBDsLMHsGMn4cjYrWcIK3TSMdv79mmbo1Vh Si6fIzR2lJjOC7vhpKEb6gr3qJ7rTAtnpJZkRlB75w== X-Received: by 2002:a62:8895:0:b029:19e:92ec:6886 with SMTP id l143-20020a6288950000b029019e92ec6886mr3625801pfd.12.1611303223430; Fri, 22 Jan 2021 00:13:43 -0800 (PST) MIME-Version: 1.0 References: <20210115112331.27434-1-crystal.guo@mediatek.com> <20210115112331.27434-2-crystal.guo@mediatek.com> In-Reply-To: <20210115112331.27434-2-crystal.guo@mediatek.com> From: Ikjoon Jang Date: Fri, 22 Jan 2021 16:13:32 +0800 Message-ID: Subject: Re: [v7,1/2] dt-binding: reset-controller: mediatek: add YAML schemas To: Crystal Guo Cc: p.zabel@pengutronix.de, Rob Herring , Matthias Brugger , open list , "open list:OPEN FIRMWARE AND FLATTENED DEVICE TREE BINDINGS" , =?UTF-8?B?U3RhbmxleSBDaHUgKOacseWOn+mZnik=?= , srv_heupstream , =?UTF-8?B?U2VpeWEgV2FuZyAo546L6L+65ZCbKQ==?= , =?UTF-8?B?RmFuIENoZW4gKOmZs+WHoSk=?= , "moderated list:ARM/Mediatek SoC support" , Yingjoe Chen , s-anna@ti.com, "moderated list:ARM/Mediatek SoC support" , Yidi.Lin@mediatek.com Content-Type: text/plain; charset="UTF-8" Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Fri, Jan 15, 2021 at 7:23 PM Crystal Guo wrote: > > Add a YAML documentation for Mediatek, which uses ti reset-controller > driver directly. The TI reset controller provides a common reset > management, and is suitable for Mediatek SoCs. > > Signed-off-by: Crystal Guo > --- > .../bindings/reset/mediatek-syscon-reset.yaml | 51 +++++++++++++++++++ > 1 file changed, 51 insertions(+) > create mode 100644 Documentation/devicetree/bindings/reset/mediatek-syscon-reset.yaml > > diff --git a/Documentation/devicetree/bindings/reset/mediatek-syscon-reset.yaml b/Documentation/devicetree/bindings/reset/mediatek-syscon-reset.yaml > new file mode 100644 > index 000000000000..85d241cdb0ea > --- /dev/null > +++ b/Documentation/devicetree/bindings/reset/mediatek-syscon-reset.yaml > @@ -0,0 +1,51 @@ > +# SPDX-License-Identifier: (GPL-2.0-only OR BSD-2-Clause) > +%YAML 1.2 > +--- > +$id: http://devicetree.org/schemas/reset/mediatek-syscon-reset.yaml# > +$schema: http://devicetree.org/meta-schemas/core.yaml# > + > +title: Mediatek Reset Controller > + > +maintainers: > + - Crystal Guo > + > +description: > + The bindings describe the reset-controller for Mediatek SoCs, > + which is based on TI reset controller. For more detail, please > + visit Documentation/devicetree/bindings/reset/ti-syscon-reset.txt. > + > +properties: > + compatible: > + const: mediatek,syscon-reset > + > + '#reset-cells': > + const: 1 > + > + ti,reset-bits: > + description: > > + Contains the reset control register information, please refer to > + Documentation/devicetree/bindings/reset/ti-syscon-reset.txt. > + I remember that Rob didn't like adding new users of this property, How about removing this from here and using a hardcoded version of register layouts into driver code (and match it with compatible) ? e.g. struct ti_syscon_reset_data mt8192_reset_data { ... } > +required: > + - compatible > + - '#reset-cells' > + - ti,reset-bits > + > +additionalProperties: false > + > +examples: > + - | > + #include > + infracfg: infracfg@10001000 { > + compatible = "mediatek,mt8192-infracfg", "syscon", "simple-mfd"; > + reg = <0 0x10001000>; > + #clock-cells = <1>; > + > + infracfg_rst: reset-controller { > + compatible = "mediatek,syscon-reset"; > + #reset-cells = <1>; > + ti,reset-bits = < > + 0x140 15 0x144 15 0 0 (ASSERT_SET | DEASSERT_SET | STATUS_NONE) > + >; > + }; > + }; > -- > 2.18.0 >