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 Received: from vger.kernel.org (vger.kernel.org [23.128.96.18]) by smtp.lore.kernel.org (Postfix) with ESMTP id 6BB3DC433F5 for ; Fri, 30 Sep 2022 21:27:29 +0000 (UTC) Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S231548AbiI3V12 (ORCPT ); Fri, 30 Sep 2022 17:27:28 -0400 Received: from lindbergh.monkeyblade.net ([23.128.96.19]:37062 "EHLO lindbergh.monkeyblade.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S231643AbiI3V10 (ORCPT ); Fri, 30 Sep 2022 17:27:26 -0400 Received: from ams.source.kernel.org (ams.source.kernel.org [IPv6:2604:1380:4601:e00::1]) by lindbergh.monkeyblade.net (Postfix) with ESMTPS id CDE8112EDA2; Fri, 30 Sep 2022 14:27:23 -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 ams.source.kernel.org (Postfix) with ESMTPS id 7D327B82A3A; Fri, 30 Sep 2022 21:27:22 +0000 (UTC) Received: by smtp.kernel.org (Postfix) with ESMTPSA id 3536DC433D6; Fri, 30 Sep 2022 21:27:21 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=kernel.org; s=k20201202; t=1664573241; bh=P8NA+en/6c9Bm7nWmBSLkFNlLYFM+Q1/d9B9HsJdrW4=; h=In-Reply-To:References:Subject:From:Cc:To:Date:From; b=H30+7E3sibpk8Ecub+Tq2fXn8sr0/Y/uJdBhVbrdNMZmEzjPuPAZCIRJ8lm7bsKJw 7jQxpMb5DhFoAA2NpczFYWAN7unzcEPxpR4+99WofgBfCagNHYQdkQqUHeY5UFFwde Z25K44RavYhJPIAoHmI7UjXgXumXAjUaNK7CDVy4VhHXWvnmHoTaSZbVC4ypBI5tlA FziW71ppfedNDRZb4HS6IknCbuvqOKK5N+dT8NKhWGMZWu4/UCh82gvx3QoXByqhFW Qd3SRxjClGsPpNyAhjbJQXERFM57B+Da9oNcrWeZBuqaZlEnFMcsiOrJOza2/UJ4/7 nECNmoTVuIypw== Content-Type: text/plain; charset="utf-8" MIME-Version: 1.0 Content-Transfer-Encoding: quoted-printable In-Reply-To: <20220929225402.9696-8-Sergey.Semin@baikalelectronics.ru> References: <20220929225402.9696-1-Sergey.Semin@baikalelectronics.ru> <20220929225402.9696-8-Sergey.Semin@baikalelectronics.ru> Subject: Re: [PATCH RESEND v12 7/8] clk: baikal-t1: Add DDR/PCIe directly controlled resets support 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:27:17 -0700 User-Agent: alot/0.10 Message-Id: <20220930212721.3536DC433D6@smtp.kernel.org> Precedence: bulk List-ID: X-Mailing-List: linux-mips@vger.kernel.org Quoting Serge Semin (2022-09-29 15:54:01) > Aside with a set of the trigger-like resets Baikal-T1 CCU provides two > additional blocks with directly controlled reset signals. In particular it > concerns DDR full and initial resets and various PCIe sub-domains resets. > Let's add the direct reset assertion/de-assertion of the corresponding > flags support into the Baikal-T1 CCU driver then. It will be required at > least for the PCIe platform driver. Obviously the DDR controller isn't > supposed to be fully reset in the kernel, so the corresponding controls > are added just for the sake of the interface implementation completeness. >=20 > Signed-off-by: Serge Semin > Reviewed-by: Philipp Zabel >=20 > --- Applied to clk-next