linux-kernel - Re: [PATCH v4 0/2] gs101 oriole: UART clock fixes

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <298d204a7d9c8dce1f1a2f180b12bd3887ea4802.camel@linaro.org>
Date: Thu, 25 Jul 2024 08:12:48 +0100
From: André Draszik <andre.draszik@...aro.org>
To: Stephen Boyd <sboyd@...nel.org>, Alim Akhtar <alim.akhtar@...sung.com>, 
 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: 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
Subject: Re: [PATCH v4 0/2] gs101 oriole: UART clock fixes

Hi Stephen,

On Thu, 2024-07-18 at 13:55 -0700, Stephen Boyd wrote:
> 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?

I didn't think that was necessary (and no, I don't have a binding update at
the moment). It gets the clock associated with the serial port (of_stdout),
if any, and works off that.

Did I miss something?

Cheers,
Andre