linux-kernel - Re: [PATCH 3/3] clk: ralink: mtmips: add mmc related clocks for SoCs MT7620, MT7628 and MT7688

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] [day] [month] [year] [list]

Message-ID: <41ef04f7ae003aad19c534839ca902ee.sboyd@kernel.org>
Date: Thu, 14 Nov 2024 12:50:10 -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 3/3] clk: ralink: mtmips: add mmc related clocks for SoCs MT7620, MT7628 and MT7688

Quoting Sergio Paracuellos (2024-09-09 21:40:24)
> Original architecture clock code from where this driver was derived did not
> include nothing related to mmc clocks. OpenWRT people started to use mtk-sd
> upstream driver recently and they were forced to use a dts 'fixed-clock'
> node with 48 MHz clock:
> - https://github.com/openwrt/openwrt/pull/15896
> The proper thing to do to avoid that is to add the mmc related clocks to the
> driver to avoid a dts with fixed clocks nodes. The minimal documentation in
> the mt7620 programming guide says that there is a BBP_PLL clock of 480 MHz
> derived from the 40 MHz XTAL and from there a clock divider by ten produces
> the desired SDHC clock of 48 MHz for the mmc. Hence add a fixed clock 'bbppll'
> and factor clock 'sdhc' ten divider child to properly set the 'mmc' peripheral
> clock with the desired 48 Mhz rate.
> 
> Signed-off-by: Sergio Paracuellos <sergio.paracuellos@...il.com>
> ---

Applied to clk-next