linux-kernel - Re: [PATCH 1/3] clk: ralink: mtmips: fix clock plan for Ralink SoC RT3883

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: <4d2c2fa787da390add0a4509b9d3ae6b.sboyd@kernel.org>
Date: Thu, 14 Nov 2024 12:49:55 -0800
From: Stephen Boyd <sboyd@...nel.org>
To: Sergio Paracuellos <sergio.paracuellos@...il.com>, linux-clk@...r.kernel.org
Cc: mturquette@...libre.com, tsbogend@...ha.franken.de, yangshiji66@...look.com, linux-kernel@...r.kernel.org
Subject: Re: [PATCH 1/3] clk: ralink: mtmips: fix clock plan for Ralink SoC RT3883

Quoting Sergio Paracuellos (2024-09-09 21:40:22)
> Clock plan for Ralink SoC RT3883 needs an extra 'periph' clock to properly
> set some peripherals that has this clock as their parent. When this driver
> was mainlined we could not find any active users of this SoC so we cannot
> perform any real tests for it. Now, one user of a Belkin f9k1109 version 1
> device which uses this SoC appear and reported some issues in openWRT:
> - https://github.com/openwrt/openwrt/issues/16054
> The peripherals that are wrong are 'uart', 'i2c', 'i2s' and 'uartlite' which
> has a not defined 'periph' clock as parent. Hence, introduce it to have a
> properly working clock plan for this SoC.
> 
> Fixes: 6f3b15586eef ("clk: ralink: add clock and reset driver for MTMIPS SoCs")
> Signed-off-by: Sergio Paracuellos <sergio.paracuellos@...il.com>
> ---

Applied to clk-next