Received: by 2002:a05:6a10:c604:0:0:0:0 with SMTP id y4csp4202357pxt; Tue, 10 Aug 2021 23:46:29 -0700 (PDT) X-Google-Smtp-Source: ABdhPJy7sZy+7kPStmePBSbSYzs++CokL0XZucO90LkImZynbJW8nVspEvDSNWxzPOj8p+/1t1eD X-Received: by 2002:a05:6402:4d1:: with SMTP id n17mr9551861edw.337.1628664389561; Tue, 10 Aug 2021 23:46:29 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; t=1628664389; cv=none; d=google.com; s=arc-20160816; b=uXshBln1n9bL0nYqfYZJ/fyhI/kNOZoBIBPvP4r2Zs2x7ONSvcbSWZhedg0ogDm0s4 rLfejnrWD3xMMLPhJhVG3+lP+Sa7CkwGRcnbXi7MNU9LLYuWSzpTgSHY7bgKPhMskUMH EglVpN+Fve5ox8Jzeq2LmDfFZO7j8Ocj/7moBMIrNdvYdp7F+P//lMSjEZwnbvqzcexq PSEc3+tSwguwuNeBlBY/VkB7tiesMoFCpoT2xu/2SeMyqCl+vw1HH6QLdUvqnbyzxDl2 vDufslUbdeBiA2B6E7L1AAqj3JQOE7x/KohXK2/5LWtCPM3TlaO81kbkArR/lXDjEFSE Qtaw== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:content-transfer-encoding:content-language :in-reply-to:mime-version:user-agent:date:message-id:from:references :cc:to:subject:dkim-signature; bh=yI4F0TrXeF6j0uWlAGd8JOKtXjZO1rjsb+fsK6ntWNc=; b=hFaM7F1Vx0G/KIbIfn2AH/DT+cn9UucAkeNzNMxm227w2wnwGAs4WA4ePExLTmyxbb ecAIx1RI/3S0SHtfy13x/TteU2xzwMppR4lMl3eJgEgL2E5tB9zOo5Fza6xkR2veuGLh nOq4tVkuizAXlWXL7tE7qlgy1H5E+KB6EIj+sHTQ7Y8o1v40cAnUheNCTat0XR9LYC9f 6Rs4AmRt0XIgO1kttG/+DVW12xBbK8TRuq8IRC5LmViRQbOtArLHwCZ4wp0vwp/I9JRC Uhk184n+/WTvxeBB3AS9RrNaqHAPFQShFIwvTmjOBIn1cmWH4q7uQjuaVoksU7nTNLos UT3g== ARC-Authentication-Results: i=1; mx.google.com; dkim=pass header.i=@canonical.com header.s=20210705 header.b=QCrL0IH+; 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=canonical.com Return-Path: Received: from vger.kernel.org (vger.kernel.org. [23.128.96.18]) by mx.google.com with ESMTP id gw9si12782442ejb.227.2021.08.10.23.46.03; Tue, 10 Aug 2021 23:46:29 -0700 (PDT) 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=@canonical.com header.s=20210705 header.b=QCrL0IH+; 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=canonical.com Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S234760AbhHKGoq (ORCPT + 99 others); Wed, 11 Aug 2021 02:44:46 -0400 Received: from smtp-relay-canonical-1.canonical.com ([185.125.188.121]:60988 "EHLO smtp-relay-canonical-1.canonical.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S234779AbhHKGop (ORCPT ); Wed, 11 Aug 2021 02:44:45 -0400 Received: from mail-ej1-f70.google.com (mail-ej1-f70.google.com [209.85.218.70]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (2048 bits) server-digest SHA256) (No client certificate requested) by smtp-relay-canonical-1.canonical.com (Postfix) with ESMTPS id CE4C840658 for ; Wed, 11 Aug 2021 06:44:15 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=canonical.com; s=20210705; t=1628664255; bh=yI4F0TrXeF6j0uWlAGd8JOKtXjZO1rjsb+fsK6ntWNc=; h=Subject:To:Cc:References:From:Message-ID:Date:MIME-Version: In-Reply-To:Content-Type; b=QCrL0IH+NlioFBUPojDPQNjzXAW1OEc8lRhhkTAfkV/v6OYo1c9fxEuQ3p3z3kaI3 ksU+1ZWG/y09CdLfH0FCh7AfI5ePFtiePiDbYwxGpCt8Bnx1q5xj7PMY7dFZixoX0R cksG9BIKsMRAr0N/xqg+zff7nh73AIUp/FqHTEgssqc6clKwR+lZS1W0NBY/jRETyx JPx0mOl5ECPsKNNWzvtc5tuS4JAQ4r1rLuTtQ0oANkcKYhK5UyYR/efsVprlcg/bkg rirD9G+mNTS87LBxa3J+uzs1seecMUc2mwGDNis+MO5Ihd1HM3SmmbCdoMj8dqfIj8 lGZRSAhMZJIgg== Received: by mail-ej1-f70.google.com with SMTP id e1-20020a170906c001b02905b53c2f6542so284542ejz.7 for ; Tue, 10 Aug 2021 23:44:15 -0700 (PDT) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:subject:to:cc:references:from:message-id:date :user-agent:mime-version:in-reply-to:content-language :content-transfer-encoding; bh=yI4F0TrXeF6j0uWlAGd8JOKtXjZO1rjsb+fsK6ntWNc=; b=oU+BHnCwqL2rTa1POq9xQCGv3F+35l8vMmF07r36u5a2I9XUdYwBDcMLZzJeF2yIz4 VHn/SeGyQxlkoTDMyhDCFB/svV7CDfJzk0Ax4p7FKvC3eC7mNcZs7IvfbQQz9ghiOQ81 JKgb2vKwNdksphQKYQHyK/l/aR3UbMXUIBNF2cN5p+zYu+8HG5ZUT7jLtrPJxTpKg5bb JMsSIw0oj405o3LTabs9roFxK/gL0fKG9LnbNZc+pibASJrpL+Uslb1ULo0CQpW9jg/N yqXiFEPhdSUxQ1NipbpbWcEsiDj4qbMJghKcbiVKI0395aAhf7CMCebFCOrsFC2c9s+X +Ijg== X-Gm-Message-State: AOAM531K258XEEeVIALTTQHwFB7eP5f5J6RlyMm5z8cUWAYI30sQgifn cUHyd1XmB4DGf/j9iBjXJn4LOBhjwWJY+3sLDA1wG4pF5YJB3D66Y4bUp1CrII8cigOqp2Sx3vZ hYgWTN8OhS/n0QxSX6mJjZxDpdD3C2uV071infTRkmA== X-Received: by 2002:a05:6402:60b:: with SMTP id n11mr9969670edv.235.1628664255151; Tue, 10 Aug 2021 23:44:15 -0700 (PDT) X-Received: by 2002:a05:6402:60b:: with SMTP id n11mr9969663edv.235.1628664255049; Tue, 10 Aug 2021 23:44:15 -0700 (PDT) Received: from [192.168.8.102] ([86.32.42.198]) by smtp.gmail.com with ESMTPSA id f16sm2712974edw.79.2021.08.10.23.44.13 (version=TLS1_3 cipher=TLS_AES_128_GCM_SHA256 bits=128/128); Tue, 10 Aug 2021 23:44:14 -0700 (PDT) Subject: Re: [PATCH v2 1/8] dt-bindings: clock: samsung: convert Exynos5250 to dtschema To: Sam Protsenko Cc: Michael Turquette , Stephen Boyd , Rob Herring , Sylwester Nawrocki , Tomasz Figa , Chanwoo Choi , linux-clk , devicetree , linux-arm Mailing List , Linux Samsung SOC , Linux Kernel Mailing List References: <20210810093145.26153-1-krzysztof.kozlowski@canonical.com> <20210810093145.26153-2-krzysztof.kozlowski@canonical.com> From: Krzysztof Kozlowski Message-ID: <48a205be-6a37-5acc-e2ee-fa18643711a9@canonical.com> Date: Wed, 11 Aug 2021 08:44:13 +0200 User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:78.0) Gecko/20100101 Thunderbird/78.11.0 MIME-Version: 1.0 In-Reply-To: Content-Type: text/plain; charset=utf-8 Content-Language: en-US Content-Transfer-Encoding: 7bit Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On 10/08/2021 19:51, Sam Protsenko wrote: > On Tue, 10 Aug 2021 at 12:32, Krzysztof Kozlowski > wrote: >> >> Convert Samsung Exynos5250 clock controller bindings to DT schema format >> using json-schema. >> >> Signed-off-by: Krzysztof Kozlowski >> --- >> .../bindings/clock/exynos5250-clock.txt | 41 ---------------- >> .../bindings/clock/samsung,exynos-clock.yaml | 48 +++++++++++++++++++ >> MAINTAINERS | 1 + >> 3 files changed, 49 insertions(+), 41 deletions(-) >> delete mode 100644 Documentation/devicetree/bindings/clock/exynos5250-clock.txt >> create mode 100644 Documentation/devicetree/bindings/clock/samsung,exynos-clock.yaml >> >> diff --git a/Documentation/devicetree/bindings/clock/exynos5250-clock.txt b/Documentation/devicetree/bindings/clock/exynos5250-clock.txt >> deleted file mode 100644 >> index aff266a12eeb..000000000000 >> --- a/Documentation/devicetree/bindings/clock/exynos5250-clock.txt >> +++ /dev/null >> @@ -1,41 +0,0 @@ >> -* Samsung Exynos5250 Clock Controller >> - >> -The Exynos5250 clock controller generates and supplies clock to various >> -controllers within the Exynos5250 SoC. >> - >> -Required Properties: >> - >> -- compatible: should be one of the following. >> - - "samsung,exynos5250-clock" - controller compatible with Exynos5250 SoC. >> - >> -- reg: physical base address of the controller and length of memory mapped >> - region. >> - >> -- #clock-cells: should be 1. >> - >> -Each clock is assigned an identifier and client nodes can use this identifier >> -to specify the clock which they consume. >> - >> -All available clocks are defined as preprocessor macros in >> -dt-bindings/clock/exynos5250.h header and can be used in device >> -tree sources. >> - >> -Example 1: An example of a clock controller node is listed below. >> - >> - clock: clock-controller@10010000 { >> - compatible = "samsung,exynos5250-clock"; >> - reg = <0x10010000 0x30000>; >> - #clock-cells = <1>; >> - }; >> - >> -Example 2: UART 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. >> - >> - serial@13820000 { >> - compatible = "samsung,exynos4210-uart"; >> - reg = <0x13820000 0x100>; >> - interrupts = <0 54 0>; >> - clocks = <&clock CLK_UART2>, <&clock CLK_SCLK_UART2>; >> - clock-names = "uart", "clk_uart_baud0"; >> - }; >> diff --git a/Documentation/devicetree/bindings/clock/samsung,exynos-clock.yaml b/Documentation/devicetree/bindings/clock/samsung,exynos-clock.yaml >> new file mode 100644 >> index 000000000000..cd6567bd8cc7 >> --- /dev/null >> +++ b/Documentation/devicetree/bindings/clock/samsung,exynos-clock.yaml >> @@ -0,0 +1,48 @@ >> +# SPDX-License-Identifier: (GPL-2.0-only OR BSD-2-Clause) >> +%YAML 1.2 >> +--- >> +$id: http://devicetree.org/schemas/clock/samsung,exynos-clock.yaml# >> +$schema: http://devicetree.org/meta-schemas/core.yaml# >> + >> +title: Samsung Exynos SoC clock controller >> + >> +maintainers: >> + - Chanwoo Choi >> + - Krzysztof Kozlowski >> + - Sylwester Nawrocki >> + - Tomasz Figa >> + >> +description: | >> + All available clocks are defined as preprocessor macros in >> + dt-bindings/clock/ headers. >> + >> +properties: >> + compatible: >> + const: samsung,exynos5250-clock >> + >> + assigned-clocks: true >> + assigned-clock-parents: true >> + assigned-clock-rates: true >> + clocks: true >> + >> + "#clock-cells": >> + const: 1 >> + >> + reg: >> + maxItems: 1 >> + >> +required: >> + - compatible >> + - "#clock-cells" >> + - reg >> + >> +additionalProperties: false >> + >> +examples: >> + - | >> + #include >> + clock: clock-controller@10010000 { >> + compatible = "samsung,exynos5250-clock"; >> + reg = <0x10010000 0x30000>; >> + #clock-cells = <1>; >> + }; >> diff --git a/MAINTAINERS b/MAINTAINERS >> index 36aee8517ab0..2dbacacac3f5 100644 >> --- a/MAINTAINERS >> +++ b/MAINTAINERS >> @@ -16491,6 +16491,7 @@ L: linux-samsung-soc@vger.kernel.org >> S: Supported >> T: git git://git.kernel.org/pub/scm/linux/kernel/git/snawrocki/clk.git >> F: Documentation/devicetree/bindings/clock/exynos*.txt > > Are there any exynos*.txt bindings actually left after this series? If > no, maybe it's worth to remove this line while at it. Yes, there are. These are the bindings which expect specific external fixed clock and I don't know yet how to model it in dtschema. Best regards, Krzysztof