Received: by 2002:a05:6359:c8b:b0:c7:702f:21d4 with SMTP id go11csp4192890rwb; Fri, 30 Sep 2022 14:29:59 -0700 (PDT) X-Google-Smtp-Source: AMsMyM5whdiMsPXU6ub2fhExM1CCxbUQvZWQNZ91KbRks+UgFkUEce0ywNs96MkZGyNPIt7UfHby X-Received: by 2002:a17:907:7e9d:b0:782:3601:7d01 with SMTP id qb29-20020a1709077e9d00b0078236017d01mr7723996ejc.361.1664573399583; Fri, 30 Sep 2022 14:29:59 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; t=1664573399; cv=none; d=google.com; s=arc-20160816; b=KASWFdHYwrWPgyXM2lfIXm8asFIzp2hu1/3d2Yr3TCTonZEZKj06kUZegH+nem9fGc t2hgLX+zDMN/luBqNQp6Y0uahCoMogIc++uEK8gBm4MtcLis5ENKVGQwZrK4I+h1ssgk gvT24tr3TAkW1RpRqHmAFzwkz0T4X4UnGh6EkM0/YfXK42qop2kepC7OVjtjTZwW7kSH 9O5jCLSlyg9SyZ31STIOGlfnNlpn96m9msU4sLoBIqXmKtUC2IaxMxrl+41G2B7OQYQe z+sUso8bSMbkARpsvQ1RHeZDPhDBonaewJeEFMNis+iiW6OZETa5t4oxuRkbNxvLVToW Uqpg== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:message-id:user-agent:date:to:cc:from:subject :references:in-reply-to:content-transfer-encoding:mime-version :dkim-signature; bh=/8IsS2twG4mpl1zl2+/C8htW4m56Q1+w9dbjIz8qNCU=; b=S9EJqzCKzObpnYyT1RnlmNR5fxtNz4GexK1LCc/1+nPyfGMk53uY+CZwy+vMrQuX8G Jy9Qn5GweWIWw+bNAZumeCXd595ipECuoevpIIGfbeON4WOZSMbpgFK/T8gGoozS09NS vsrTC7CQ9cFgTBtuYcv0V4whdwyRZ+GR9V/E80GMU0Eko/M3xatukQIVg2ALFlQ9VeXD e73KTv5njYozz2TcTtEjTJeD2bj4d6gWBXr85/k/HsBo19hEitYq0hntY6TfTvl7T8H0 3tnhtLu1eDdZKe7NP0ulgbV9LrhhHGC6ljMalK433T5f1GwMzo9FeYmLSFdTsi15Fuc3 oLFQ== ARC-Authentication-Results: i=1; mx.google.com; dkim=pass header.i=@kernel.org header.s=k20201202 header.b=HUiyqKIa; spf=pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 2620:137:e000::1:20 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org; dmarc=pass (p=NONE sp=NONE dis=NONE) header.from=kernel.org Return-Path: Received: from out1.vger.email (out1.vger.email. [2620:137:e000::1:20]) by mx.google.com with ESMTP id gj20-20020a170907741400b0076fbaba1addsi1987195ejc.896.2022.09.30.14.29.15; Fri, 30 Sep 2022 14:29:59 -0700 (PDT) Received-SPF: pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 2620:137:e000::1:20 as permitted sender) client-ip=2620:137:e000::1:20; Authentication-Results: mx.google.com; dkim=pass header.i=@kernel.org header.s=k20201202 header.b=HUiyqKIa; spf=pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 2620:137:e000::1:20 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org; dmarc=pass (p=NONE sp=NONE dis=NONE) header.from=kernel.org Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S232072AbiI3V06 (ORCPT + 99 others); Fri, 30 Sep 2022 17:26:58 -0400 Received: from lindbergh.monkeyblade.net ([23.128.96.19]:35884 "EHLO lindbergh.monkeyblade.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S231806AbiI3V0y (ORCPT ); Fri, 30 Sep 2022 17:26:54 -0400 Received: from dfw.source.kernel.org (dfw.source.kernel.org [139.178.84.217]) by lindbergh.monkeyblade.net (Postfix) with ESMTPS id 01A0110B20C; Fri, 30 Sep 2022 14:26:52 -0700 (PDT) Received: from smtp.kernel.org (relay.kernel.org [52.25.139.140]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by dfw.source.kernel.org (Postfix) with ESMTPS id 17A69624F4; Fri, 30 Sep 2022 21:26:52 +0000 (UTC) Received: by smtp.kernel.org (Postfix) with ESMTPSA id 70EC3C433D6; Fri, 30 Sep 2022 21:26:51 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=kernel.org; s=k20201202; t=1664573211; bh=/8IsS2twG4mpl1zl2+/C8htW4m56Q1+w9dbjIz8qNCU=; h=In-Reply-To:References:Subject:From:Cc:To:Date:From; b=HUiyqKIa18jctP6hVAhL6wD1i3QyFFENAFV1qlVgJuDVNMLpYShDyDJYvoPoXtWAJ g6XUUZ98qKTFDjjonOaB0hLS53PYIPgx3Z7GXagiFeX9ljcjTTCDBXIG387a+qDpU5 irje7TdwFpt9feQOHOtdwfRSDHVPtaGd85BHfhZeyWR7aZr85IQZAHUeg9fGDYeO/C XLDIdLJBJNKgdcLE9Thd78amqMg6j1sadfsnDzMI4nVg+yBhxvSvPa4ddCfDXROInt rayHSEbMATzQcu/OoiRNLQYtWposAlTzGzKzF23uJwIBtqTDU9YW+Gho/NGjf2JSxx 9UVT7mS7FvWCQ== Content-Type: text/plain; charset="utf-8" MIME-Version: 1.0 Content-Transfer-Encoding: quoted-printable In-Reply-To: <20220929225402.9696-6-Sergey.Semin@baikalelectronics.ru> References: <20220929225402.9696-1-Sergey.Semin@baikalelectronics.ru> <20220929225402.9696-6-Sergey.Semin@baikalelectronics.ru> Subject: Re: [PATCH RESEND v12 5/8] clk: baikal-t1: Move reset-controls code into a dedicated module From: Stephen Boyd Cc: Serge Semin , Serge Semin , Alexey Malahov , Pavel Parkhomenko , Philipp Zabel , Krzysztof Kozlowski , Krzysztof Kozlowski , Thomas Bogendoerfer , linux-clk@vger.kernel.org, linux-mips@vger.kernel.org, linux-kernel@vger.kernel.org To: Michael Turquette , Serge Semin Date: Fri, 30 Sep 2022 14:26:48 -0700 User-Agent: alot/0.10 Message-Id: <20220930212651.70EC3C433D6@smtp.kernel.org> X-Spam-Status: No, score=-7.2 required=5.0 tests=BAYES_00,DKIMWL_WL_HIGH, DKIM_SIGNED,DKIM_VALID,DKIM_VALID_AU,DKIM_VALID_EF,RCVD_IN_DNSWL_HI, SPF_HELO_NONE,SPF_PASS autolearn=ham autolearn_force=no version=3.4.6 X-Spam-Checker-Version: SpamAssassin 3.4.6 (2021-04-09) on lindbergh.monkeyblade.net Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Quoting Serge Semin (2022-09-29 15:53:59) > Before adding the directly controlled resets support it's reasonable to > move the existing resets control functionality into a dedicated object for > the sake of the CCU dividers clock driver simplification. After the new > functionality was added clk-ccu-div.c would have got to a mixture of the > weakly dependent clocks and resets methods. Splitting the methods up into > the two objects will make the code easier to read and maintain. It shall > also improve the code scalability (though hopefully we won't need this > part that much in the future). >=20 > The reset control functionality is now implemented in the framework of a > single unit since splitting it up doesn't make much sense due to > relatively simple reset operations. The ccu-rst.c has been designed to be > looking like ccu-div.c or ccu-pll.c with two globally available methods > for the sake of the code unification and better code readability. >=20 > This commit doesn't provide any change in the CCU reset implementation > semantics. As before the driver will support the trigger-like CCU resets > only, which are responsible for the AXI-bus, APB-bus and SATA-ref blocks > reset. The assert/de-assert-capable reset controls support will be added > in the next commit. >=20 > Note the CCU Clock dividers and resets functionality split up was possible > due to not having any side-effects (at least we didn't found ones) of the > regmap-based concurrent access of the common CCU dividers/reset CSRs. >=20 > Signed-off-by: Serge Semin > Reviewed-by: Philipp Zabel >=20 > --- Applied to clk-next