Received: by 2002:a05:6a10:1d13:0:0:0:0 with SMTP id pp19csp207695pxb; Tue, 17 Aug 2021 23:55:27 -0700 (PDT) X-Google-Smtp-Source: ABdhPJzWpZdgQWBBpgOAlT2fYB3MIQOZVKh5Ra9Byt3rqLYd7RtRio/aUGrlICkPhwlbiiIg9TOS X-Received: by 2002:a5e:9743:: with SMTP id h3mr6138882ioq.52.1629269727136; Tue, 17 Aug 2021 23:55:27 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; t=1629269727; cv=none; d=google.com; s=arc-20160816; b=OR0tgZ+wnfFuNyfyn6KHezEDG7XUQPpUaejyvzxdj3G3cIU9FSnW5JI0JUsvYe/uyF veXklvAfX4rtknSTufe0OLbALRec4imh7UHNz6PnRKwWPW8PdMe3R/9R57ibKN0SsFX3 hmmDQosgA5nUw4VkN2FIAqaLCTQsHKUL6ztjsykKvK2uQnHcNcqIwxDdNaN9Z7JANqgw LpvSKXbMLZkC3832N9Y0JHC4BLR2wK+bsDj11dwJIs1HlmoI9TtZvFBA7rjWS1Yji8qg 2rw2jiT6SoQrQUNJpGDBIuXVU3So5Bty3Bnye0sqGFqrPH1wOi8mjM5gxwPyAUypegX4 ExSQ== 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=+VHxmC5l70aOpP0chSpMVVPtyabgSrUdWjrTOo5Mr8s=; b=W7qN7t9xwl0sjpEqH2mP/XR4p7OJmh7jRLzq6f9ysG63H+Ebrtbp4iqXj66i0TQiYo uXxu+PeOAxYmvqxEFQwXmTSk9C7Fz8wqlYML7yot+q66HG9cL0/dzKxDrw0Y3pQ/rjDI vducCpq4vyuEjAZrng1DuBcnS0RlVim/YfmOhoB/8uc+mLAsMnWWU7iDQooi/hHroHve 4LEcncc5J3GClK7qbXPUDoWLPl/HrdNE9GhRSqXZtskPzIrT3TgtJ+o78S1awym6DD8B naMbROnxmOEmvkWX9JC9MhdA0zBrDqGHYBj245fLINPk/QJGRhjaXzZObfqqK07y+665 REnQ== ARC-Authentication-Results: i=1; mx.google.com; dkim=pass header.i=@canonical.com header.s=20210705 header.b=Yzl7gruW; 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 k16si5823632iow.1.2021.08.17.23.55.15; Tue, 17 Aug 2021 23:55:27 -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=Yzl7gruW; 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 S238440AbhHRGxp (ORCPT + 99 others); Wed, 18 Aug 2021 02:53:45 -0400 Received: from smtp-relay-canonical-0.canonical.com ([185.125.188.120]:50426 "EHLO smtp-relay-canonical-0.canonical.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S238081AbhHRGxp (ORCPT ); Wed, 18 Aug 2021 02:53:45 -0400 Received: from mail-ej1-f71.google.com (mail-ej1-f71.google.com [209.85.218.71]) (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-0.canonical.com (Postfix) with ESMTPS id 378C040CCD for ; Wed, 18 Aug 2021 06:53:10 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=canonical.com; s=20210705; t=1629269590; bh=+VHxmC5l70aOpP0chSpMVVPtyabgSrUdWjrTOo5Mr8s=; h=Subject:To:Cc:References:From:Message-ID:Date:MIME-Version: In-Reply-To:Content-Type; b=Yzl7gruWkkqaLWV/muBiGy4CdcqfbdJ8ul5L+5I4xyiYV5djPk5AHlgMiuSloyNCy 5jM18gRxMI8TdlNBZ+HJDgfMMxR2PA0rh+MNrh/Idn45XVi8tRPcrHFiVTQzFjbB2z FK6H76FVxO8Lov8qhGrquUeJRKgmlDO285oCKwxOIcYUMl3dxkUvbo+VnT9H3xKuz+ /fExpZ2OD1Bud8QQb331/dd1fWImaj9++Wy/84509t4cLohGC+0tL4LLHyyYfMtz9M AyEwPhA0anqXMnU6Zb0qz5K5mFVaia631GB4sQFj/Vs4KatWdV8ZPtkyE2WcwZvsrQ Z4U17Y+Im3y7A== Received: by mail-ej1-f71.google.com with SMTP id gg1-20020a170906e281b029053d0856c4cdso491739ejb.15 for ; Tue, 17 Aug 2021 23:53:10 -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=+VHxmC5l70aOpP0chSpMVVPtyabgSrUdWjrTOo5Mr8s=; b=gITmqy8GU/2fpoiHWuMrDUomwAp2L5jxqSs7qlK7uratEs7DiBGnzUvCo6t3T4i8t3 t9gixmY2/OffGIQmMJvSqOp9FN2HoMfIP3wvmlL1szLTMHEWxzs9IpjWHykeHvaUxipA f9ObG0t+9sRriuA5mgXRx5V7iuvDzuocmn4HHYFzXguWLm04z0oltXSEGW+X70tnhtFw Q1HjZlk+8F/KQfM0szEmDGYmQ1qX+tAKjhoc+l/sAFWE1Im0jIuz0jStMNwX71iwMoaT vFEaPug+LNnA2g4rqc3QlgJ2kLqUHrEuHCH7soTcP7qyKEr7sIhQnksDT3jFUZfcIAxB ILxA== X-Gm-Message-State: AOAM5326hBONOZM+Kr96opBZjBvl4apQj6LSVXkgYbn4HbqzUxncywKh PGnW7WZrI1b8wjM+XP6sJ1z29HTkt4IviHWvDsHmiAxmWEzj90J2+pPGvVDyAOd/icYV+Pvs7au ErIDrtvnxOTimav91vSbI+kmSPRc3B3LzOZN4+3zY9A== X-Received: by 2002:a17:906:c091:: with SMTP id f17mr8342444ejz.134.1629269589689; Tue, 17 Aug 2021 23:53:09 -0700 (PDT) X-Received: by 2002:a17:906:c091:: with SMTP id f17mr8342431ejz.134.1629269589552; Tue, 17 Aug 2021 23:53:09 -0700 (PDT) Received: from [192.168.8.102] ([86.32.42.198]) by smtp.gmail.com with ESMTPSA id r19sm2047214edd.49.2021.08.17.23.53.08 (version=TLS1_3 cipher=TLS_AES_128_GCM_SHA256 bits=128/128); Tue, 17 Aug 2021 23:53:09 -0700 (PDT) Subject: Re: [PATCH v2 3/8] dt-bindings: clock: samsung: convert Exynos542x to dtschema To: Rob Herring Cc: Michael Turquette , Stephen Boyd , Sylwester Nawrocki , Tomasz Figa , Chanwoo Choi , linux-clk@vger.kernel.org, devicetree@vger.kernel.org, linux-arm-kernel@lists.infradead.org, linux-samsung-soc@vger.kernel.org, linux-kernel@vger.kernel.org, Sam Protsenko References: <20210810093145.26153-1-krzysztof.kozlowski@canonical.com> <20210810093145.26153-4-krzysztof.kozlowski@canonical.com> From: Krzysztof Kozlowski Message-ID: <4ac27c04-5ee5-b15c-29bd-fce841429522@canonical.com> Date: Wed, 18 Aug 2021 08:53:07 +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 17/08/2021 22:21, Rob Herring wrote: > On Tue, Aug 10, 2021 at 11:31:40AM +0200, Krzysztof Kozlowski wrote: >> Merge Exynos542x clock controller bindings to existing DT schema. >> >> Signed-off-by: Krzysztof Kozlowski >> --- >> .../bindings/clock/exynos5420-clock.txt | 42 ------------------- >> .../bindings/clock/samsung,exynos-clock.yaml | 11 ++++- >> 2 files changed, 10 insertions(+), 43 deletions(-) >> delete mode 100644 Documentation/devicetree/bindings/clock/exynos5420-clock.txt >> >> diff --git a/Documentation/devicetree/bindings/clock/exynos5420-clock.txt b/Documentation/devicetree/bindings/clock/exynos5420-clock.txt >> deleted file mode 100644 >> index 717a7b1531c7..000000000000 >> --- a/Documentation/devicetree/bindings/clock/exynos5420-clock.txt >> +++ /dev/null >> @@ -1,42 +0,0 @@ >> -* Samsung Exynos5420 Clock Controller >> - >> -The Exynos5420 clock controller generates and supplies clock to various >> -controllers within the Exynos5420 SoC and for the Exynos5800 SoC. >> - >> -Required Properties: >> - >> -- compatible: should be one of the following. >> - - "samsung,exynos5420-clock" - controller compatible with Exynos5420 SoC. >> - - "samsung,exynos5800-clock" - controller compatible with Exynos5800 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/exynos5420.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,exynos5420-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 >> index cd6567bd8cc7..b0f58a1cf6cb 100644 >> --- a/Documentation/devicetree/bindings/clock/samsung,exynos-clock.yaml >> +++ b/Documentation/devicetree/bindings/clock/samsung,exynos-clock.yaml >> @@ -18,7 +18,16 @@ description: | >> >> properties: >> compatible: >> - const: samsung,exynos5250-clock >> + oneOf: >> + - enum: >> + - samsung,exynos5250-clock >> + - samsung,exynos5420-clock >> + - samsung,exynos5800-clock >> + - items: >> + - enum: >> + - samsung,exynos5420-clock >> + - samsung,exynos5800-clock > > Is there a reason these are supported with or without 'syscon'? > Yes, the syscon is optional and needed only by the Exynos5422 DMC driver (exynos5422-dmc.txt/samsung,exynos5422-dmc.yaml with samsung,exynos5422-dmc compatible). Without that driver, there is no need for syscon. Best regards, Krzysztof