[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <20250227133509.GA2021892-robh@kernel.org>
Date: Thu, 27 Feb 2025 07:35:09 -0600
From: Rob Herring <robh@...nel.org>
To: Inochi Amaoto <inochiama@...il.com>
Cc: Philipp Zabel <p.zabel@...gutronix.de>,
Krzysztof Kozlowski <krzk+dt@...nel.org>,
Conor Dooley <conor+dt@...nel.org>,
Chen Wang <unicorn_wang@...look.com>,
Paul Walmsley <paul.walmsley@...ive.com>,
Palmer Dabbelt <palmer@...belt.com>,
Albert Ou <aou@...s.berkeley.edu>,
Uwe Kleine-König <u.kleine-koenig@...libre.com>,
Guo Ren <guoren@...nel.org>, devicetree@...r.kernel.org,
linux-kernel@...r.kernel.org, sophgo@...ts.linux.dev,
linux-riscv@...ts.infradead.org, Yixun Lan <dlan@...too.org>,
Longbin Li <looong.bin@...il.com>
Subject: Re: [PATCH v2 1/5] dt-bindings: reset: add generic bit reset
controller
On Thu, Feb 27, 2025 at 07:42:29AM +0800, Inochi Amaoto wrote:
> Some SoCs from Aspeed, Allwinner, Sophgo and Synopsys have
> a simple reset controller by toggling bit. It is a hard time
> for each device to add its own compatible to the driver.
It's a 1 line change. That isn't hard.
> Since these devices share a common design, it is possible to
> add a common device to reduce these unnecessary change for
> the driver.
>
> Add common binding for these kind generic reset controller.
> Check the binding description for its requirement and
> suitable scenarios.
We generally don't want 1 register per node type bindings. That level of
detail in DT has proven impossible to get right.
Rob
Powered by blists - more mailing lists