[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <44e544735066391b2ad1682badae4462.sboyd@kernel.org>
Date: Wed, 10 Apr 2024 23:42:41 -0700
From: Stephen Boyd <sboyd@...nel.org>
To: Baolin Wang <baolin.wang@...ux.alibaba.com>, Chunyan Zhang <zhang.lyra@...il.com>, Conor Dooley <conor+dt@...nel.org>, Krzysztof Kozlowski <krzysztof.kozlowski+dt@...aro.org>, Michael Turquette <mturquette@...libre.com>, Orson Zhai <orsonzhai@...il.com>, Philipp Zabel <p.zabel@...gutronix.de>, Rob Herring <robh+dt@...nel.org>, Zhifeng Tang <zhifeng.tang@...soc.com>
Cc: linux-clk@...r.kernel.org, devicetree@...r.kernel.org, linux-kernel@...r.kernel.org, Zhifeng Tang <zhifeng.tang23@...il.com>, Wenming Wu <wenming.wu@...soc.com>
Subject: Re: [PATCH V4 0/3] Add reset controller driver for ums512
Quoting Zhifeng Tang (2024-01-22 18:56:10)
> From: "zhifeng.tang" <zhifeng.tang@...soc.com>
>
> In most of Sprd SOCs,The clock controller register block also
> contains reset bits for some of these peripherals,so reset
> controller and clock provider are combined together as a block,
> and put it under the driver/clk/.
>
> Changes in v4:
> - Add description why reset controller put it under the driver/clk/
Please use an auxiliary device and put the code almost entirely under
drivers/reset/. You can still have the data tables in the clk driver if
you want, but I don't see why an auxiliary device can't be used.
Powered by blists - more mailing lists