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=-15.8 required=3.0 tests=BAYES_00,DKIM_SIGNED, DKIM_VALID,DKIM_VALID_AU,HEADER_FROM_DIFFERENT_DOMAINS,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 CAEE9C4320A for ; Tue, 10 Aug 2021 18:16:58 +0000 (UTC) Received: from vger.kernel.org (vger.kernel.org [23.128.96.18]) by mail.kernel.org (Postfix) with ESMTP id B3CB86056C for ; Tue, 10 Aug 2021 18:16:58 +0000 (UTC) Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S238067AbhHJSRT (ORCPT ); Tue, 10 Aug 2021 14:17:19 -0400 Received: from lindbergh.monkeyblade.net ([23.128.96.19]:59392 "EHLO lindbergh.monkeyblade.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S239492AbhHJSPV (ORCPT ); Tue, 10 Aug 2021 14:15:21 -0400 Received: from mail-ua1-x932.google.com (mail-ua1-x932.google.com [IPv6:2607:f8b0:4864:20::932]) by lindbergh.monkeyblade.net (Postfix) with ESMTPS id 7B3D6C043CC3 for ; Tue, 10 Aug 2021 10:50:05 -0700 (PDT) Received: by mail-ua1-x932.google.com with SMTP id ay13so1151636uab.5 for ; Tue, 10 Aug 2021 10:50:05 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=linaro.org; s=google; h=mime-version:references:in-reply-to:from:date:message-id:subject:to :cc; bh=n8NnT+9Uof6uRiwYL8q6ZdxasPN6RvJnAmBwT0HbVyY=; b=H+l1xmwQ18K5CXNmDkCE0LNLXpAPnWJdYZA9rsY/mEzsWZj1x/cS1fZSYn73iMUSz3 mltE03ujZDanRXDcNFdIwKLxn3q/IHFM1/43JndiMHOezAA/NqSTua3z+/tj6bFWigEP fhfnzR4GjEL4tefCI7DXQo7+8v0rpqy3lx9NMvVmDaa768w9+JaNS46KTbqAfYHDw1S5 xsOmgSeFPsPwl0WkaHe18gmVu+7V0U5QW7Ow+VCg3lUTF/NmPwbNFGvLmqPvuBFf93Ad UZqmYPSoM6ryBPNL3Dt0xlt/IuG56vZUeIMKFWSv1tJdiR1GHBvocU747WXiCxh+0BlW EaKg== 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=n8NnT+9Uof6uRiwYL8q6ZdxasPN6RvJnAmBwT0HbVyY=; b=KmSlyvOtnDfojKfnKETnEs1ZozuQnhrBe+rTAGcSRSIN+j5Q+3Ems/zzZEKr0PLBye uUde31+Zul1HpYnsTyUuD1racKoeOg2LrQNyz0Bt+fENfn1DXENq3rsNH/Z9+sETEyQN oxTNyOHTEPafFNbsjxFRp1n/tErvo5qETjOQ1yOlcb5ZdYrBZz5PFKufs/js2avKPJEd xAGxkmjzWZbMgc0jtvXO9MeoiGzg1ujZKEQ8CPPPgiBkgVaFCqky5XZTVnBvu4uc5/On eRUbCPFjsJr6C5MfFIVpt1ZiFRJ50PBVOn+dsN5v/cNuP/kQXGYVbdEKZnTo/PsAXaZa 2fsQ== X-Gm-Message-State: AOAM533Xwwva0LCphJY4Vlmixf2FHFSc+PtKKe8pfRyyGNcWyXCaV98M KPqsGSiz/T9WStnH6eaYpPggjOPZWnPG/8KmMvzzkrqzd4FrCC+8 X-Google-Smtp-Source: ABdhPJw6Y1Kyo5HEPoPohSS4X1DN2xa+9jW7WH/BO4BIObQiUTUdOewJoelWT5DuTZk5RwiiUThK6skuR78poH9yagQ= X-Received: by 2002:ab0:7014:: with SMTP id k20mr8457678ual.9.1628617804659; Tue, 10 Aug 2021 10:50:04 -0700 (PDT) MIME-Version: 1.0 References: <20210810093145.26153-1-krzysztof.kozlowski@canonical.com> <20210810093145.26153-3-krzysztof.kozlowski@canonical.com> In-Reply-To: <20210810093145.26153-3-krzysztof.kozlowski@canonical.com> From: Sam Protsenko Date: Tue, 10 Aug 2021 20:49:52 +0300 Message-ID: Subject: Re: [PATCH v2 2/8] dt-bindings: clock: samsung: add bindings for Exynos external clock To: Krzysztof Kozlowski 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 Content-Type: text/plain; charset="UTF-8" Precedence: bulk List-ID: X-Mailing-List: linux-samsung-soc@vger.kernel.org On Tue, 10 Aug 2021 at 12:32, Krzysztof Kozlowski wrote: > > Document the bindings for Samsung Exynos external to SoC > (oscclk/XXTI/XusbXTI) clock provided on boards. The bindings are > already implemented in most of the Exynos clock drivers and DTS files. > > Signed-off-by: Krzysztof Kozlowski > --- Just want to mention that remaining users of such fixed clocks can be converted to regular fixed-rate-clock, and then this binding can be removed along with samsung_clk_of_register_fixed_ext() API? Just a thought. > .../clock/samsung,exynos-ext-clock.yaml | 46 +++++++++++++++++++ > 1 file changed, 46 insertions(+) > create mode 100644 Documentation/devicetree/bindings/clock/samsung,exynos-ext-clock.yaml > > diff --git a/Documentation/devicetree/bindings/clock/samsung,exynos-ext-clock.yaml b/Documentation/devicetree/bindings/clock/samsung,exynos-ext-clock.yaml > new file mode 100644 > index 000000000000..64d027dbe3b2 > --- /dev/null > +++ b/Documentation/devicetree/bindings/clock/samsung,exynos-ext-clock.yaml > @@ -0,0 +1,46 @@ > +# SPDX-License-Identifier: (GPL-2.0-only OR BSD-2-Clause) > +%YAML 1.2 > +--- > +$id: http://devicetree.org/schemas/clock/samsung,exynos-ext-clock.yaml# > +$schema: http://devicetree.org/meta-schemas/core.yaml# > + > +title: Samsung SoC external/osc/XXTI/XusbXTI clock > + > +maintainers: > + - Chanwoo Choi > + - Krzysztof Kozlowski > + - Sylwester Nawrocki > + - Tomasz Figa > + > +description: | > + Samsung SoCs require an external clock supplied through XXTI or XusbXTI pins. > + > +properties: > + compatible: > + enum: > + - samsung,clock-xxti > + - samsung,clock-xusbxti > + - samsung,exynos5420-oscclk > + > + "#clock-cells": > + const: 0 > + > + clock-frequency: true > + > + clock-output-names: > + maxItems: 1 > + > +required: > + - compatible > + - clock-frequency > + > +additionalProperties: false > + > +examples: > + - | > + fixed-rate-clocks { > + clock { > + compatible = "samsung,clock-xxti"; > + clock-frequency = <24000000>; > + }; > + }; > -- > 2.30.2 >