[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <d17567eb0ad9a6082d55ca016771abbc.sboyd@kernel.org>
Date: Thu, 18 Jul 2024 13:55:16 -0700
From: Stephen Boyd <sboyd@...nel.org>
To: Alim Akhtar <alim.akhtar@...sung.com>, André Draszik <andre.draszik@...aro.org>, Chanwoo Choi <cw00.choi@...sung.com>, Krzysztof Kozlowski <krzk@...nel.org>, Michael Turquette <mturquette@...libre.com>, Peter Griffin <peter.griffin@...aro.org>, Sam Protsenko <semen.protsenko@...aro.org>, Sylwester Nawrocki <s.nawrocki@...sung.com>, Tudor Ambarus <tudor.ambarus@...aro.org>
Cc: Tudor Ambarus <tudor.ambarus@...aro.org>, Will McVicker <willmcvicker@...gle.com>, kernel-team@...roid.com, linux-arm-kernel@...ts.infradead.org, linux-samsung-soc@...r.kernel.org, linux-clk@...r.kernel.org, linux-kernel@...r.kernel.org, André Draszik <andre.draszik@...aro.org>
Subject: Re: [PATCH v4 0/2] gs101 oriole: UART clock fixes
Quoting André Draszik (2024-07-12 10:09:42)
> Hi,
>
> This series fixes a long-standing issue in the gs101 clocking / uart
> handling.
>
> We can now disable clocks that had previously been marked critical, and
> still get a working earlycon.
>
> There is a preparatory patch, and then a patch to drop an incorrect clock
> counting work-around. That 2nd patch is essentially the last remaining patch
> [1] with all review comments addressed, from the series [2] that was sent
> earlier this year, see lore links below.
Is there a binding update for the chosen node to have a clocks property?
Powered by blists - more mailing lists