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 bombadil.infradead.org (bombadil.infradead.org [198.137.202.133]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by smtp.lore.kernel.org (Postfix) with ESMTPS id BB1D0CA101B for ; Fri, 30 Aug 2024 22:18:12 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/relaxed; d=lists.infradead.org; s=bombadil.20210309; h=Sender:List-Subscribe:List-Help :List-Post:List-Archive:List-Unsubscribe:List-Id:Date:To:From:Subject: References:In-Reply-To:Content-Transfer-Encoding:MIME-Version:Content-Type: Message-ID:Reply-To:Cc:Content-ID:Content-Description:Resent-Date:Resent-From :Resent-Sender:Resent-To:Resent-Cc:Resent-Message-ID:List-Owner; bh=I7H81hQF268KAroQBxNa0F30Khcefp1vM0KlS38dQhQ=; b=jX0cdleIK8gTMVcSZ2Ia0AoiKg 2nzFeqifGHon4tGq0DHO4od/WGDnqzgcfzKrluc3BtHw5HNRfVNeX/uFq0c7d55ZuGSMNHsJ1wOC/ rUeOBCxMCqFesgAFoLUdbu+4wNL9l6YKnI0zMyo5GhUxr6xmQKP/rQoTU6kvB3aOcuf1aEy7smTik oh7Fs8t0dFREFvBPrGSIBhkakWj3pCX/Q6v5nHt0o8OqTMSyhFchugwzWHLs8+oKJLb06lqR9kIN2 Qorawf0Ge4i4pZfLDgmATL430mL8aFxlGH90qBSWjqgMbEX+mPWy+q+22ZpST/vkE3QxNVzQcfcmE h+2sARWQ==; Received: from localhost ([::1] helo=bombadil.infradead.org) by bombadil.infradead.org with esmtp (Exim 4.97.1 #2 (Red Hat Linux)) id 1sk9wO-00000007qYB-1ESb; Fri, 30 Aug 2024 22:18:00 +0000 Received: from nyc.source.kernel.org ([2604:1380:45d1:ec00::3]) by bombadil.infradead.org with esmtps (Exim 4.97.1 #2 (Red Hat Linux)) id 1sk9un-00000007qE9-2HkH for linux-arm-kernel@lists.infradead.org; Fri, 30 Aug 2024 22:16:22 +0000 Received: from smtp.kernel.org (transwarp.subspace.kernel.org [100.75.92.58]) by nyc.source.kernel.org (Postfix) with ESMTP id 9E68DA44548; Fri, 30 Aug 2024 22:16:13 +0000 (UTC) Received: by smtp.kernel.org (Postfix) with ESMTPSA id 2966AC4CEC2; Fri, 30 Aug 2024 22:16:20 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=kernel.org; s=k20201202; t=1725056180; bh=fJOk64w1KvNsgFSNifgZViqLAi1eNKi+j0BhblwmrqI=; h=In-Reply-To:References:Subject:From:To:Date:From; b=M71grJzlvDD6cLtOVpcRPMqiP3ECPrxcF6jYFTtWUOZYK2zIxVVnixshiJ/zCiqU0 HGNwMPngVcz3Cxkt5qRTeLfER3GJScGke3fhsK+eQwPWJa4lzZEdI0pxwgak+e3Pdi DUk+1AEFZ7ds7SlcKDm3YeDFgOVb72p50fn2HAzr4Of7uONRlzlrZ48aPAykaP7CsZ G6ZBalQyGL5+OpO9l7XEGqbx27MtkJ6qBivaU1/djv5FJYti9h58Lrhhy8Xn0k/Orq m9L/ofkc3+rmzH1SyDr0iGe4vNrZuSaOXePM/e4DhXUnHA8t6JhTFgS96MlL6N4Pge 8c3BWK9Y0ebKQ== Message-ID: <45c7cf75876c5822f8c51f05375af507.sboyd@kernel.org> Content-Type: text/plain; charset="utf-8" MIME-Version: 1.0 Content-Transfer-Encoding: quoted-printable In-Reply-To: References: <20240828062740.1614744-1-ryan_chen@aspeedtech.com> <20240828062740.1614744-4-ryan_chen@aspeedtech.com> <61c8234139fcd2b27610ef18e9d9fbf7.sboyd@kernel.org> <3569ef6d81adc41330c4002752ba3aa9.sboyd@kernel.org> Subject: RE: [PATCH v2 3/3] clk: aspeed: add AST2700 clk driver From: Stephen Boyd To: Ryan Chen , andrew@codeconstruct.com.au, conor+dt@kernel.org, devicetree@vger.kernel.org, joel@jms.id.au, krzk+dt@kernel.org, linux-arm-kernel@lists.infradead.org, linux-aspeed@lists.ozlabs.org, linux-clk@vger.kernel.org, linux-kernel@vger.kernel.org, mturquette@baylibre.com, p.zabel@pengutronix.de, robh@kernel.org Date: Fri, 30 Aug 2024 15:16:18 -0700 User-Agent: alot/0.10 X-CRM114-Version: 20100106-BlameMichelson ( TRE 0.8.0 (BSD) ) MR-646709E3 X-CRM114-CacheID: sfid-20240830_151621_667778_CFF6C1B6 X-CRM114-Status: GOOD ( 19.90 ) X-BeenThere: linux-arm-kernel@lists.infradead.org X-Mailman-Version: 2.1.34 Precedence: list List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Sender: "linux-arm-kernel" Errors-To: linux-arm-kernel-bounces+linux-arm-kernel=archiver.kernel.org@lists.infradead.org Quoting Ryan Chen (2024-08-30 00:50:21) > > Subject: RE: [PATCH v2 3/3] clk: aspeed: add AST2700 clk driver > >=20 > > Quoting Ryan Chen (2024-08-29 00:09:12) > > > > Subject: Re: [PATCH v2 3/3] clk: aspeed: add AST2700 clk driver > > > > > > > > Quoting Ryan Chen (2024-08-27 23:27:40) > > > > > a/drivers/clk/clk-ast2700.c b/drivers/clk/clk-ast2700.c new file > > > > > mode > > > > > 100644 index 000000000000..7e0466e73980 > > > > > --- /dev/null > > > > > +++ b/drivers/clk/clk-ast2700.c > > > > > @@ -0,0 +1,1198 @@ > > > > > +// SPDX-License-Identifier: GPL-2.0 > > > > > +/* > > > > > + * Copyright (c) 2024 ASPEED Technology Inc. > > > > > + * Author: Ryan Chen */ > > > > > + > > > > > +#include > > > > > +#include > > > > [...] > > > > > + > > > > > +struct ast2700_reset { > > > > > + void __iomem *base; > > > > > + struct ast2700_reset_signal const *signal; > > > > > + struct reset_controller_dev rcdev; }; > > > > > > > > Please move the reset controller to the drivers/reset directory by > > > > means of using an auxiliary device. There are some existing examples > > > > in there if you grep for auxiliary_device in drivers/reset to help = guide. > > > > > > Do you mean to have another reset controller driver? > > > If yes, I may need syscon for remap two drivers. > >=20 > > Yes. A syscon is not necessary to do that. > Thanks for point out auxiliary device. > Since our SoC reset and clock share the same register region. > Your recommend will use clk auxiliary_device_add for reset driver am I ri= ght? Yes. Either the clk or the reset driver can be a platform driver and the other an auxiliary driver.