[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <58cba30d-af53-47a6-9258-8b36eab6cbfb@kernel.org>
Date: Sat, 13 Jul 2024 12:21:46 +0200
From: Krzysztof Kozlowski <krzk@...nel.org>
To: Frank Wunderlich <linux@...web.de>,
Michael Turquette <mturquette@...libre.com>, Stephen Boyd
<sboyd@...nel.org>, Rob Herring <robh@...nel.org>,
Krzysztof Kozlowski <krzk+dt@...nel.org>, Conor Dooley
<conor+dt@...nel.org>, Matthias Brugger <matthias.bgg@...il.com>,
AngeloGioacchino Del Regno <angelogioacchino.delregno@...labora.com>,
Wim Van Sebroeck <wim@...ux-watchdog.org>, Guenter Roeck <linux@...ck-us.net>
Cc: Frank Wunderlich <frank-w@...lic-files.de>,
Daniel Golle <daniel@...rotopia.org>, linux-clk@...r.kernel.org,
devicetree@...r.kernel.org, linux-kernel@...r.kernel.org,
linux-arm-kernel@...ts.infradead.org, linux-mediatek@...ts.infradead.org,
linux-watchdog@...r.kernel.org
Subject: Re: [PATCH v1 1/4] dt-bindings: watchdog: mediatek,mtk-wdt: add
MT7988 syscon requirement
On 09/07/2024 12:13, Frank Wunderlich wrote:
> From: Frank Wunderlich <frank-w@...lic-files.de>
>
> This is needed by u-boot-driver when using OF_UPSTREAM.
Thanks for providing context. What we miss here still, is the
description of the hardware and for what this syscon is used. Why this
become system controller and before was not? Or this is just for regmap
- then it does not work that way... You cannot have whatever driver
poking all around then claim - I have crappy driver poking to every
driver without implementing proper driver model, so I add syscon to
bindings.
Best regards,
Krzysztof
Powered by blists - more mailing lists