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 vger.kernel.org (vger.kernel.org [23.128.96.18]) by smtp.lore.kernel.org (Postfix) with ESMTP id E5C3CC43217 for ; Tue, 21 Dec 2021 08:19:51 +0000 (UTC) Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S235508AbhLUITv (ORCPT ); Tue, 21 Dec 2021 03:19:51 -0500 Received: from smtp-relay-internal-1.canonical.com ([185.125.188.123]:53778 "EHLO smtp-relay-internal-1.canonical.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S232095AbhLUITt (ORCPT ); Tue, 21 Dec 2021 03:19:49 -0500 Received: from mail-lf1-f72.google.com (mail-lf1-f72.google.com [209.85.167.72]) (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-internal-1.canonical.com (Postfix) with ESMTPS id 8AC743F20D for ; Tue, 21 Dec 2021 08:19:48 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=canonical.com; s=20210705; t=1640074788; bh=AmwBkgsCQBlvy6a8IJhNBe3rHFIw/oazUsEvZEPNdNw=; h=Message-ID:Date:MIME-Version:Subject:To:Cc:References:From: In-Reply-To:Content-Type; b=p0gp1Ub/qBL4Lo0HnHH0ySOaLrz2zHVSV+jPW6Nlzta9gdEaA0qt7fumUtBmKfRlL gAhkExfiWqLj5PTHrZzK4gQlBtwyNldRXIBzT9EQTwWI7dMfYBcXb+apTs2RmOFW3y XJQ6ujOMPbTi0SOFjwd9DIl1nal4zEr2NHgAlr1s3RTMt1gHDKOaHI4FmapOarKb/O rWX/HxroBATh69wF58tn3VYjyKSKt4uk9xdTzhbRvTyoVX5H98u2NC2+GlmdQcMDYK PICxzYkZmjCg/b8Dp7ok6kW9e1ZZwEkruh9VpkuVCg4F/iACBKIneR8lFjmcf1/sTH 6lRtxU9REfh/A== Received: by mail-lf1-f72.google.com with SMTP id g18-20020a05651222d200b0042612bda352so1588634lfu.11 for ; Tue, 21 Dec 2021 00:19:48 -0800 (PST) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20210112; h=x-gm-message-state:message-id:date:mime-version:user-agent:subject :content-language:to:cc:references:from:in-reply-to :content-transfer-encoding; bh=AmwBkgsCQBlvy6a8IJhNBe3rHFIw/oazUsEvZEPNdNw=; b=V/ELlJWkJMeLTC6ge4iuJoP4BHHQL8kOVuSEjN5bvFnBEb+aJLnvVkIfTt8TlFWQns KyzQCRIE6bslq7i+P+rvyeBU4yexuYB4c++sh/dYQM5JdVZEE3FGayAknoni659cQEoI D1dupIKEZ8xHC23Tbic5WEqzAP57dpKg3SamM3mhh+X+ZZ8y+mjzAY23bI6Uf/6x7C/E vORXtouQOlVYzf2PEno8QO6U7R5d+hE8XkkvAnHryuirELgZj6Kd/q6Rcnf56+XmxJnA +FsWFxhDngxR6o67+Z3vLSyPunQGoBqnN3MQnAAwp7jC3fdPcDGVFA3VZqe77rmHybdm raTw== X-Gm-Message-State: AOAM533rwwu4TJAcXgFOz1og8nZXzT6qWrS8qix5SEO0Gd5Pjee7uVUs hF8uItoUTysFSRgaAoP1d4qnwhZ1ihil6Y31ibtZSmx5SAw5lSilJUgQRoOEtAIfnIkb0hRPiGp N1H3wshS48Bzzr/LdILuZGGryrITtyjFbYOE7hKEv6Q== X-Received: by 2002:a2e:b177:: with SMTP id a23mr1708971ljm.168.1640074787938; Tue, 21 Dec 2021 00:19:47 -0800 (PST) X-Google-Smtp-Source: ABdhPJxy/XhlYssCNLAWRYkWoIWMzAeGZqkYE+7VzTrmhujnAacn27xoPqnMQ2uSgBrGs8xv+IeKow== X-Received: by 2002:a2e:b177:: with SMTP id a23mr1708948ljm.168.1640074787666; Tue, 21 Dec 2021 00:19:47 -0800 (PST) Received: from [192.168.0.27] (89-77-68-124.dynamic.chello.pl. [89.77.68.124]) by smtp.gmail.com with ESMTPSA id z26sm2654830lja.48.2021.12.21.00.19.46 (version=TLS1_3 cipher=TLS_AES_128_GCM_SHA256 bits=128/128); Tue, 21 Dec 2021 00:19:47 -0800 (PST) Message-ID: Date: Tue, 21 Dec 2021 09:19:45 +0100 MIME-Version: 1.0 User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:91.0) Gecko/20100101 Thunderbird/91.3.1 Subject: Re: [PATCH v4 1/7] dt-bindings: clock: exynos850: Add bindings for Exynos850 sysreg clocks Content-Language: en-US To: Sam Protsenko Cc: Sylwester Nawrocki , Jaewon Kim , Chanho Park , David Virag , Youngmin Nam , Tomasz Figa , Chanwoo Choi , Michael Turquette , Stephen Boyd , Linus Walleij , Daniel Palmer , Hao Fang , linux-arm-kernel@lists.infradead.org, linux-samsung-soc@vger.kernel.org, devicetree@vger.kernel.org, linux-kernel@vger.kernel.org, linux-clk@vger.kernel.org, Sylwester Nawrocki , Rob Herring References: <20211217161549.24836-1-semen.protsenko@linaro.org> <20211217161549.24836-2-semen.protsenko@linaro.org> <2fdc5c97-6c19-8e70-d717-28b29d86160c@kernel.org> <5bd5c0bf-4390-22c2-e4e0-cb02b80dfb9c@canonical.com> From: Krzysztof Kozlowski In-Reply-To: Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On 20/12/2021 15:55, Sam Protsenko wrote: > On Mon, 20 Dec 2021 at 11:31, Krzysztof Kozlowski > wrote: >> >> On 19/12/2021 23:29, Sylwester Nawrocki wrote: >>> On 17.12.2021 17:15, Sam Protsenko wrote: >>>> System Register is used to configure system behavior, like USI protocol, >>>> etc. SYSREG clocks should be provided to corresponding syscon nodes, to >>>> make it possible to modify SYSREG registers. >>>> >>>> While at it, add also missing PMU and GPIO clocks, which looks necessary >>>> and might be needed for corresponding Exynos850 features soon. >>>> >>>> Reviewed-by: Krzysztof Kozlowski >>>> Acked-by: Rob Herring >>>> Acked-by: Chanwoo Choi >>>> Signed-off-by: Sam Protsenko >>> >>> Apologies for late reply, this patch is applied now. >>> >> >> Sam, >> >> The clock is used in the DTSI, so since this was applied, there are only >> two choices now: >> 1. wait for next cycle with DTSI and DTS, >> 2. Resubmit with replacing the newly added clocks in DTSI/DTS with >> numbers and a TODO note. >> > > But why? I thought because Sylwester applied my clock patches, those > will get into v5.17, and so DTSI/DTS might rely on those clocks? If I > get it wrong, please let me know why, and I'll go with item (2) you > suggested. If I apply the DTSI+DTS, all my builds will start failing. The linux-next (since Sylwester's tree is included) should build fine, but my tree won't be buildable anymore. Then arm-soc pulls my tree and gets said because it does not build. Later, Linus will be unhappy if he pulls arm-soc (thus mine) before clock tree. Other solution, instead of using raw numbers, is to copy-paste the clock macros you use directly in DTSI and do not include the clock header. This actually might be cleaner choice - changes will be limited to one place in DTSI. Best regards, Krzysztof