[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <yfhta3vfct73udltmz6ri2dsas6wx4g6hww3drdcumreqbi4gu@c6zxqz7fbh7j>
Date: Thu, 13 Feb 2025 19:33:19 +0800
From: Inochi Amaoto <inochiama@...il.com>
To: Philipp Zabel <p.zabel@...gutronix.de>,
Inochi Amaoto <inochiama@...il.com>, Rob Herring <robh@...nel.org>,
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>, Guo Ren <guoren@...nel.org>,
Uwe Kleine-König <u.kleine-koenig@...libre.com>
Cc: 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 0/4] reset: introduct generic bit reset controller
On Thu, Feb 13, 2025 at 11:08:03AM +0100, Philipp Zabel wrote:
> On Do, 2025-02-13 at 10:08 +0800, Inochi Amaoto wrote:
> > Many SoC have a simple reset controller with toggling bit to perform
> > assert/deassert. It is annoyed to add compatiable for each device when
> > coming a new SoC. It is necessary to introduct a generic device to
> > simplify these things.
>
> You'll still have to add a compatible to reset-simple.yaml for each new
> SoC, see patch 3.
>
> regards
> Philipp
Yeah, the binding is can not avoided, but it can avoided adding new
compatible in the driver. I will update the description.
Regards,
Inochi
Powered by blists - more mailing lists