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 X-Spam-Level: X-Spam-Status: No, score=-14.7 required=3.0 tests=BAYES_00,DKIMWL_WL_HIGH, DKIM_SIGNED,DKIM_VALID,INCLUDES_CR_TRAILER,INCLUDES_PATCH,MAILING_LIST_MULTI, SPF_HELO_NONE,SPF_PASS,URIBL_BLOCKED autolearn=unavailable autolearn_force=no version=3.4.0 Received: from mail.kernel.org (mail.kernel.org [198.145.29.99]) by smtp.lore.kernel.org (Postfix) with ESMTP id 0480DC4338F for ; Tue, 17 Aug 2021 20:27:22 +0000 (UTC) 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 mail.kernel.org (Postfix) with ESMTPS id AEF1560FD9 for ; Tue, 17 Aug 2021 20:27:21 +0000 (UTC) DMARC-Filter: OpenDMARC Filter v1.4.1 mail.kernel.org AEF1560FD9 Authentication-Results: mail.kernel.org; dmarc=fail (p=none dis=none) header.from=kernel.org Authentication-Results: mail.kernel.org; spf=none smtp.mailfrom=lists.infradead.org DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/relaxed; d=lists.infradead.org; s=bombadil.20210309; h=Sender: Content-Transfer-Encoding:Content-Type:List-Subscribe:List-Help:List-Post: List-Archive:List-Unsubscribe:List-Id:In-Reply-To:MIME-Version:References: Message-ID:Subject:Cc:To:From:Date:Reply-To:Content-ID:Content-Description: Resent-Date:Resent-From:Resent-Sender:Resent-To:Resent-Cc:Resent-Message-ID: List-Owner; bh=sifu3ieH/qG+kOuu5cG/kybmTZ9DiAjdQ1cwvqu/G8I=; b=lcWkuf3nSdzRvW x+ady7uzVbE3cUqHDh+tnpOmiV69hmi5SqYJ/ZB+QDTwR4gcdjEHHMfyBOmrPTxexs8zvFJ69Ma52 f2+u+o4pWJ+WNQve/QJYUSh7mCe0YVK4fEXtGdU8MmRlGcOBkKrJcK/3ay30sjLvUq3OE2aiMM+kA dYuEooBnEZjQ83uXX8NChtHiZSUNuLw6c6UujxOWSHqlt8w1dyfvjWP3tuNon4ChC+4EoNpHPKByz WNcf9y4u2zYIiPGarmhxrJUj30U7KU18h+QvsIcwzgKu7F8jUtd/C7jcIRtE5Glb83TeewiJOkQ5J DHA20YWyLGxa92Wwm5dQ==; Received: from localhost ([::1] helo=bombadil.infradead.org) by bombadil.infradead.org with esmtp (Exim 4.94.2 #2 (Red Hat Linux)) id 1mG5eL-003QPF-8Z; Tue, 17 Aug 2021 20:25:29 +0000 Received: from mail-oi1-f180.google.com ([209.85.167.180]) by bombadil.infradead.org with esmtps (Exim 4.94.2 #2 (Red Hat Linux)) id 1mG5eG-003QOE-VG for linux-arm-kernel@lists.infradead.org; Tue, 17 Aug 2021 20:25:26 +0000 Received: by mail-oi1-f180.google.com with SMTP id o185so910186oih.13 for ; Tue, 17 Aug 2021 13:25:24 -0700 (PDT) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:date:from:to:cc:subject:message-id:references :mime-version:content-disposition:in-reply-to; bh=gqCWS94qFMQo89WcKVKUOC7+B5Uopx/LB045sFLOWjc=; b=JzuzTNeIN8UNkV929YvemNiBwsMClikMDrDMoNDwf4XwxgHGOvm1s4RESITrh6Vkg1 nYUKCfd0WCI+7H4d3ebpKyIvjdeH1eBwHyY1n76fzM5MjglMLgQsV0Lcxs2m9uCwXszb 5zF5tKFXjagTCzJWIXZRsZtGRgkKS7hIUSJilf2NnUfwBpPyix0jUSh0EBiCPEI7QKwb q/JucWyW1JVR+GQHWXw499Y+X5yajWJ4+oYtD8bZtYO+TiLrEguHKRNlYLNFmVnYjNzI X+46XTgIeKe9av1OWksigswvssh44RvIkvMu8ANMRS2tQm/BQ3tMota7/5ZHYOE9wwdG jqEw== X-Gm-Message-State: AOAM530mlKVX4WPf7WJ3iRtKQ+8uf/rTZQqAcm5pv893gQmx5/c0QbeF 5MSPZmwWmioDwFUct/VOPw== X-Google-Smtp-Source: ABdhPJw3WAOdSl9AOXFA1Bcnzo80QQ5HItahZY+gRyqMfrEbwR40R5tG0kH8KnJkxKYMvusGnp+OUA== X-Received: by 2002:a05:6808:1290:: with SMTP id a16mr4013369oiw.115.1629231923724; Tue, 17 Aug 2021 13:25:23 -0700 (PDT) Received: from robh.at.kernel.org (24-155-109-49.dyn.grandenetworks.net. [24.155.109.49]) by smtp.gmail.com with ESMTPSA id w14sm585525otl.58.2021.08.17.13.25.22 (version=TLS1_3 cipher=TLS_AES_256_GCM_SHA384 bits=256/256); Tue, 17 Aug 2021 13:25:23 -0700 (PDT) Received: (nullmailer pid 780338 invoked by uid 1000); Tue, 17 Aug 2021 20:25:22 -0000 Date: Tue, 17 Aug 2021 15:25:22 -0500 From: Rob Herring To: Krzysztof Kozlowski Cc: Sam Protsenko , Michael Turquette , Stephen Boyd , Sylwester Nawrocki , Tomasz Figa , Chanwoo Choi , linux-clk , devicetree , linux-arm Mailing List , Linux Samsung SOC , Linux Kernel Mailing List Subject: Re: [PATCH v2 6/8] dt-bindings: clock: samsung: convert Exynos AudSS to dtschema Message-ID: References: <20210810093145.26153-1-krzysztof.kozlowski@canonical.com> <20210810093145.26153-7-krzysztof.kozlowski@canonical.com> <2f8ff138-4d34-619c-e137-099dc9251e25@canonical.com> MIME-Version: 1.0 Content-Disposition: inline In-Reply-To: <2f8ff138-4d34-619c-e137-099dc9251e25@canonical.com> X-CRM114-Version: 20100106-BlameMichelson ( TRE 0.8.0 (BSD) ) MR-646709E3 X-CRM114-CacheID: sfid-20210817_132525_069107_2BE58613 X-CRM114-Status: GOOD ( 31.60 ) 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: , Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Sender: "linux-arm-kernel" Errors-To: linux-arm-kernel-bounces+linux-arm-kernel=archiver.kernel.org@lists.infradead.org On Wed, Aug 11, 2021 at 08:46:46AM +0200, Krzysztof Kozlowski wrote: > On 10/08/2021 19:46, Sam Protsenko wrote: > > On Tue, 10 Aug 2021 at 12:32, Krzysztof Kozlowski > > wrote: > >> > >> Convert Samsung Exynos Audio SubSystem clock controller bindings to DT > >> schema format using json-schema. > >> > >> Signed-off-by: Krzysztof Kozlowski > >> --- > >> .../bindings/clock/clk-exynos-audss.txt | 103 ------------------ > >> .../clock/samsung,exynos-audss-clock.yaml | 79 ++++++++++++++ > >> 2 files changed, 79 insertions(+), 103 deletions(-) > >> delete mode 100644 Documentation/devicetree/bindings/clock/clk-exynos-audss.txt > >> create mode 100644 Documentation/devicetree/bindings/clock/samsung,exynos-audss-clock.yaml > >> > >> diff --git a/Documentation/devicetree/bindings/clock/clk-exynos-audss.txt b/Documentation/devicetree/bindings/clock/clk-exynos-audss.txt > >> deleted file mode 100644 > >> index 6030afb10b5c..000000000000 > >> --- a/Documentation/devicetree/bindings/clock/clk-exynos-audss.txt > >> +++ /dev/null > >> @@ -1,103 +0,0 @@ > >> -* Samsung Audio Subsystem Clock Controller > >> - > >> -The Samsung Audio Subsystem clock controller generates and supplies clocks > >> -to Audio Subsystem block available in the S5PV210 and Exynos SoCs. The clock > >> -binding described here is applicable to all SoCs in Exynos family. > >> - > >> -Required Properties: > >> - > >> -- compatible: should be one of the following: > >> - - "samsung,exynos4210-audss-clock" - controller compatible with all Exynos4 SoCs. > >> - - "samsung,exynos5250-audss-clock" - controller compatible with Exynos5250 > >> - SoCs. > >> - - "samsung,exynos5410-audss-clock" - controller compatible with Exynos5410 > >> - SoCs. > >> - - "samsung,exynos5420-audss-clock" - controller compatible with Exynos5420 > >> - SoCs. > >> -- reg: physical base address and length of the controller's register set. > >> - > >> -- #clock-cells: should be 1. > >> - > >> -- clocks: > >> - - pll_ref: Fixed rate PLL reference clock, parent of mout_audss. "fin_pll" > >> - is used if not specified. > >> - - pll_in: Input PLL to the AudioSS block, parent of mout_audss. "fout_epll" > >> - is used if not specified. > >> - - cdclk: External i2s clock, parent of mout_i2s. "cdclk0" is used if not > >> - specified. > >> - - sclk_audio: Audio bus clock, parent of mout_i2s. "sclk_audio0" is used if > >> - not specified. > >> - - sclk_pcm_in: PCM clock, parent of sclk_pcm. "sclk_pcm0" is used if not > >> - specified. > >> - > >> -- clock-names: Aliases for the above clocks. They should be "pll_ref", > >> - "pll_in", "cdclk", "sclk_audio", and "sclk_pcm_in" respectively. > >> - > >> -Optional Properties: > >> - > >> - - power-domains: a phandle to respective power domain node as described by > >> - generic PM domain bindings (see power/power_domain.txt for more > >> - information). > >> - > >> -The following is the list of clocks generated by the controller. Each clock is > >> -assigned an identifier and client nodes use this identifier to specify the > >> -clock which they consume. Some of the clocks are available only on a particular > >> -Exynos4 SoC and this is specified where applicable. > >> - > >> -Provided clocks: > >> - > >> -Clock ID SoC (if specific) > >> ------------------------------------------------ > >> - > >> -mout_audss 0 > >> -mout_i2s 1 > >> -dout_srp 2 > >> -dout_aud_bus 3 > >> -dout_i2s 4 > >> -srp_clk 5 > >> -i2s_bus 6 > >> -sclk_i2s 7 > >> -pcm_bus 8 > >> -sclk_pcm 9 > >> -adma 10 Exynos5420 > >> - > >> -Example 1: An example of a clock controller node using the default input > >> - clock names is listed below. > >> - > >> -clock_audss: audss-clock-controller@3810000 { > >> - compatible = "samsung,exynos5250-audss-clock"; > >> - reg = <0x03810000 0x0C>; > >> - #clock-cells = <1>; > >> -}; > >> - > >> -Example 2: An example of a clock controller node with the input clocks > >> - specified. > >> - > >> -clock_audss: audss-clock-controller@3810000 { > >> - compatible = "samsung,exynos5250-audss-clock"; > >> - reg = <0x03810000 0x0C>; > >> - #clock-cells = <1>; > >> - clocks = <&clock 1>, <&clock 7>, <&clock 138>, <&clock 160>, > >> - <&ext_i2s_clk>; > >> - clock-names = "pll_ref", "pll_in", "sclk_audio", "sclk_pcm_in", "cdclk"; > >> -}; > >> - > >> -Example 3: I2S controller node that consumes the clock generated by the clock > >> - controller. Refer to the standard clock bindings for information > >> - about 'clocks' and 'clock-names' property. > >> - > >> -i2s0: i2s@3830000 { > >> - compatible = "samsung,i2s-v5"; > >> - reg = <0x03830000 0x100>; > >> - dmas = <&pdma0 10 > >> - &pdma0 9 > >> - &pdma0 8>; > >> - dma-names = "tx", "rx", "tx-sec"; > >> - clocks = <&clock_audss EXYNOS_I2S_BUS>, > >> - <&clock_audss EXYNOS_I2S_BUS>, > >> - <&clock_audss EXYNOS_SCLK_I2S>, > >> - <&clock_audss EXYNOS_MOUT_AUDSS>, > >> - <&clock_audss EXYNOS_MOUT_I2S>; > >> - clock-names = "iis", "i2s_opclk0", "i2s_opclk1", > >> - "mout_audss", "mout_i2s"; > >> -}; > > > > Seems like some examples and "Provided clocks" table were dropped in > > in yaml binding. Also there is no description for example present in > > yaml file. Is that some redundant info and was dropped intentionally? > > I'm just worrying about losing some useful info during the conversion. > > I don't see any point of having a clock consumer example in a clock > provider binding. +1 Just another one to get wrong... _______________________________________________ linux-arm-kernel mailing list linux-arm-kernel@lists.infradead.org http://lists.infradead.org/mailman/listinfo/linux-arm-kernel