[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <2089a7cff2eee7213353b0b933815390dc708464.camel@linaro.org>
Date: Sat, 27 Jan 2024 01:38:01 +0000
From: André Draszik <andre.draszik@...aro.org>
To: peter.griffin@...aro.org, robh+dt@...nel.org,
krzysztof.kozlowski+dt@...aro.org, conor+dt@...nel.org
Cc: linux-kernel@...r.kernel.org, kernel-team@...roid.com,
tudor.ambarus@...aro.org, willmcvicker@...gle.com,
semen.protsenko@...aro.org, alim.akhtar@...sung.com,
s.nawrocki@...sung.com, tomasz.figa@...il.com, cw00.choi@...sung.com,
mturquette@...libre.com, sboyd@...nel.org,
linux-arm-kernel@...ts.infradead.org, linux-samsung-soc@...r.kernel.org,
linux-clk@...r.kernel.org, devicetree@...r.kernel.org
Subject: Re: [PATCH 5/5] clk: samsung: gs101: don't mark non-essential
clocks as critical
On Sat, 2024-01-27 at 00:35 +0000, André Draszik wrote:
> The peric0_top1_ipclk_0 and peric0_top1_pclk_0 are the clocks going to
> peric0/uart_usi, with pclk being the bus clock. Without pclk running,
> any bus access will hang.
> Unfortunately, in commit d97b6c902a40 ("arm64: dts: exynos: gs101:
> update USI UART to use peric0 clocks") the gs101 DT ended up specifying
> an incorrect pclkk in the respective node and instead the two clocks
^^^^^
'pclk', I'll send a v2 after collecting any other potential feedback.
Cheers,
Andre'
Powered by blists - more mailing lists