From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: X-Spam-Checker-Version: SpamAssassin 3.4.0 (2014-02-07) on aws-us-west-2-korg-lkml-1.web.codeaurora.org Received: from bombadil.infradead.org (bombadil.infradead.org [198.137.202.133]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by smtp.lore.kernel.org (Postfix) with ESMTPS id 46743C3DA63 for ; Tue, 23 Jul 2024 20:57:58 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/relaxed; d=lists.infradead.org; s=bombadil.20210309; h=Sender:List-Subscribe:List-Help :List-Post:List-Archive:List-Unsubscribe:List-Id:In-Reply-To:Content-Type: MIME-Version:References:Message-ID:Subject:Cc:To:From:Date:Reply-To: Content-Transfer-Encoding:Content-ID:Content-Description:Resent-Date: Resent-From:Resent-Sender:Resent-To:Resent-Cc:Resent-Message-ID:List-Owner; bh=CcmgMimpEjWgpJsb9QHE9/rSAczTRUIfKxWJN6PQ+5M=; b=WIe+l4txkX4KBfpxvFtnz5kiZw NhwKcJi+aVfhTNgzTilMs5fwR2UynRl/pnIpLS6VQ2wbDtOKI0D8k09ZleiYrhnnJ8jNH9LvTo0g2 qftHirFJ6dgV06aCpICbC0gnx76OaagvC8bs63HPKFJymZdf0+WbiILT02qmbs0tXWwATAAzi8JcR AmlLxiUvf593hvoH04CR5nSBz56L3oOx5mJ9AM4ObUACCNR9CVgpOABe2kDWU8xq+8Ww+pBvJNAMq jPQoHfwfpy4vEFroXC3fYZgy9G/nTlrxRl4sW+Ut2HVvn2M2QfuIXFh8ypAWTpIw4mzA7A+1Qz7SE OXWGOwLw==; Received: from localhost ([::1] helo=bombadil.infradead.org) by bombadil.infradead.org with esmtp (Exim 4.97.1 #2 (Red Hat Linux)) id 1sWMZq-0000000DVeF-3Wc3; Tue, 23 Jul 2024 20:57:42 +0000 Received: from sin.source.kernel.org ([145.40.73.55]) by bombadil.infradead.org with esmtps (Exim 4.97.1 #2 (Red Hat Linux)) id 1sWMZS-0000000DVYb-3gpu for linux-arm-kernel@lists.infradead.org; Tue, 23 Jul 2024 20:57:20 +0000 Received: from smtp.kernel.org (transwarp.subspace.kernel.org [100.75.92.58]) by sin.source.kernel.org (Postfix) with ESMTP id DF103CE0EEE; Tue, 23 Jul 2024 20:57:15 +0000 (UTC) Received: by smtp.kernel.org (Postfix) with ESMTPSA id 08EC0C4AF09; Tue, 23 Jul 2024 20:57:14 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=kernel.org; s=k20201202; t=1721768235; bh=bUppBWqZH2uLys4TfLAbBxHCtv32OZjdBJVR4LSQNHM=; h=Date:From:To:Cc:Subject:References:In-Reply-To:From; b=rInKOLlYARp2bm42ZHYHmmhJMT2LQ0QLzVRmo/rTy+vCUxHU4zLDx3y9Z9JzyNhuu jMQjAPU0VUltwAsf9tkxAfGY6mcM+LxG2AFtR7L+MNKk8bgnIdpOSDmxv/X5h7ZC3W TUja5feINGe5X1EN1oC+s2uZshIJhKO5/eu5CSUiMWToMDDIutDuBhtIN3HK+6HH5M 9IMXoA8PcVIFA5cvOt/i5mgHzYHBIzMPoc2mYSisiuGoKx+iipYIMRAvIxIjuqJ7HY +dSwtsnpQxJptJi11yAZ2BmbZSEnY+q9RlRjxaf/wj/84EUhhjRzgS1JcfFS9BFO+a bVo+2i/TLilwA== Date: Tue, 23 Jul 2024 15:57:14 -0500 From: Rob Herring To: Sunyeal Hong Cc: Krzysztof Kozlowski , Sylwester Nawrocki , Chanwoo Choi , Alim Akhtar , Michael Turquette , Stephen Boyd , Conor Dooley , linux-samsung-soc@vger.kernel.org, linux-clk@vger.kernel.org, devicetree@vger.kernel.org, linux-arm-kernel@lists.infradead.org, linux-kernel@vger.kernel.org Subject: Re: [PATCH v4 1/4] dt-bindings: clock: add ExynosAuto v920 SoC CMU bindings Message-ID: <20240723205714.GA1093352-robh@kernel.org> References: <20240722223333.1137947-1-sunyeal.hong@samsung.com> <20240722223333.1137947-2-sunyeal.hong@samsung.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20240722223333.1137947-2-sunyeal.hong@samsung.com> X-CRM114-Version: 20100106-BlameMichelson ( TRE 0.8.0 (BSD) ) MR-646709E3 X-CRM114-CacheID: sfid-20240723_135719_410842_A83987FF X-CRM114-Status: GOOD ( 20.11 ) X-BeenThere: linux-arm-kernel@lists.infradead.org X-Mailman-Version: 2.1.34 Precedence: list List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Sender: "linux-arm-kernel" Errors-To: linux-arm-kernel-bounces+linux-arm-kernel=archiver.kernel.org@lists.infradead.org On Tue, Jul 23, 2024 at 07:33:30AM +0900, Sunyeal Hong wrote: > Add dt-schema for ExynosAuto v920 SoC clock controller. > Add device tree clock binding definitions for below CMU blocks. > > - CMU_TOP > - CMU_PERIC0 > > Signed-off-by: Sunyeal Hong > --- > .../clock/samsung,exynosautov920-clock.yaml | 115 +++++++++++ > .../clock/samsung,exynosautov920.h | 191 ++++++++++++++++++ > 2 files changed, 306 insertions(+) > create mode 100644 Documentation/devicetree/bindings/clock/samsung,exynosautov920-clock.yaml > create mode 100644 include/dt-bindings/clock/samsung,exynosautov920.h > > diff --git a/Documentation/devicetree/bindings/clock/samsung,exynosautov920-clock.yaml b/Documentation/devicetree/bindings/clock/samsung,exynosautov920-clock.yaml > new file mode 100644 > index 000000000000..90f9f17da959 > --- /dev/null > +++ b/Documentation/devicetree/bindings/clock/samsung,exynosautov920-clock.yaml > @@ -0,0 +1,115 @@ > +# SPDX-License-Identifier: (GPL-2.0-only OR BSD-2-Clause) > +%YAML 1.2 > +--- > +$id: http://devicetree.org/schemas/clock/samsung,exynosautov920-clock.yaml# > +$schema: http://devicetree.org/meta-schemas/core.yaml# > + > +title: Samsung ExynosAuto v920 SoC clock controller > + > +maintainers: > + - Sunyeal Hong > + - Chanwoo Choi > + - Krzysztof Kozlowski > + - Sylwester Nawrocki > + > +description: | > + ExynosAuto v920 clock controller is comprised of several CMU units, generating > + clocks for different domains. Those CMU units are modeled as separate device > + tree nodes, and might depend on each other. Root clocks in that clock tree are > + two external clocks:: OSCCLK/XTCXO (38.4 MHz) and RTCCLK/XrtcXTI (32768 Hz). > + The external OSCCLK must be defined as fixed-rate clock in dts. > + > + CMU_TOP is a top-level CMU, where all base clocks are prepared using PLLs and > + dividers; all other clocks of function blocks (other CMUs) are usually > + derived from CMU_TOP. > + > + Each clock is assigned an identifier and client nodes can use this identifier > + to specify the clock which they consume. All clocks available for usage > + in clock consumer nodes are defined as preprocessor macros in > + 'include/dt-bindings/clock/samsung,exynosautov920.h' header. > + > +properties: > + compatible: > + enum: > + - samsung,exynosautov920-cmu-top > + - samsung,exynosautov920-cmu-peric0 > + > + clocks: > + minItems: 1 > + maxItems: 3 > + > + clock-names: > + minItems: 1 > + maxItems: 3 Move the descriptions and names here. Then in the if/then schemas just set the number of items to 1 or 3 as appropriate. Rob