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: <175848425322.4354.14607215330062561253@lazor>
Date: Sun, 21 Sep 2025 12:50:53 -0700
From: Stephen Boyd <sboyd@...nel.org>
To: Conor Dooley <conor+dt@...nel.org>, Huacai Chen <chenhuacai@...nel.org>, Krzysztof Kozlowski <krzk+dt@...nel.org>, Michael Turquette <mturquette@...libre.com>, Rob Herring <robh@...nel.org>, WANG Xuerui <kernel@...0n.name>, Yao Zi <ziyao@...root.org>, Yinbo Zhu <zhuyinbo@...ngson.cn>
Cc: linux-clk@...r.kernel.org, devicetree@...r.kernel.org, linux-kernel@...r.kernel.org, loongarch@...ts.linux.dev, Mingcong Bai <jeffbai@...c.io>, Kexy Biscuit <kexybiscuit@...c.io>, Yao Zi <ziyao@...root.org>
Subject: Re: [PATCH v4 5/8] clk: loongson2: Avoid hardcoding firmware name of the reference clock

Quoting Yao Zi (2025-09-19 07:26:46)
> Loongson-2K0300 requires a reference clock with a frequency different
> from previous SoCs (120MHz v.s. 100MHz), thus hardcoding the firmware
> name of the reference clock as ref_100m isn't a good idea.
> 
> This patch retrives the clock name of the reference clock dynamically
> during probe, avoiding the hardcoded pdata structure and preparing for
> support of future SoCs.
> 
> Signed-off-by: Yao Zi <ziyao@...root.org>
> ---

Applied to clk-next

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ