[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <15e9931a-b817-4dd3-abb6-9718e002c6bd@gmail.com>
Date: Tue, 14 Jan 2025 23:57:27 +0200
From: Ivaylo Ivanov <ivo.ivanov.ivanov1@...il.com>
To: Krzysztof Kozlowski <krzk@...nel.org>, Rob Herring <robh@...nel.org>,
Conor Dooley <conor+dt@...nel.org>, Alim Akhtar <alim.akhtar@...sung.com>,
Sam Protsenko <semen.protsenko@...aro.org>,
Peter Griffin <peter.griffin@...aro.org>
Cc: devicetree@...r.kernel.org, linux-arm-kernel@...ts.infradead.org,
linux-samsung-soc@...r.kernel.org, linux-kernel@...r.kernel.org
Subject: Re: [PATCH v5 2/4] soc: samsung: usi: add a routine for unconfiguring
the ip
On 1/14/25 20:03, Krzysztof Kozlowski wrote:
> On 09/01/2025 10:03, Ivaylo Ivanov wrote:
>> +static void exynos_usi_unconfigure(void *data)
>> +{
>> + struct exynos_usi *usi = data;
>> + u32 val;
>> +
>> + /* Make sure that we've stopped providing the clock to USI IP */
>> + val = readl(usi->regs + USI_OPTION);
>> + val &= ~USI_OPTION_CLKREQ_ON;
>> + val |= ~USI_OPTION_CLKSTOP_ON;
>> + writel(val, usi->regs + USI_OPTION);
>> +
>> + /* Set USI block state to reset */
>> + val = readl(usi->regs + USI_CON);
>> + val |= USI_CON_RESET;
>> + writel(val, usi->regs + USI_CON);
> Also shouldn't you enable clocks for accessing these? They are being
> disabled at the end of exynos_usi_enable().
Hm, perhaps. But I find that weird, since I haven't seen it in the downstream
driver implementation.
Best regards,
Ivaylo
>
> Best regards,
> Krzysztof
Powered by blists - more mailing lists