58301e1c15
After merging spdx tree for linux-next testing, Stephen Rothwell reported
htmldocs warning:
Documentation/arm/samsung-s3c24xx/cpufreq.rst:2: WARNING: Explicit markup ends without a blank line; unexpected unindent.
It is due to missing blank line separator between SPDX directive and
page title.
Add the blank line to fix the warning.
Link: https://lore.kernel.org/linux-next/20220614164506.6afd65a6@canb.auug.org.au/
Fixes: b7bc1c9e5b ("treewide: Replace GPLv2 boilerplate/reference with SPDX - gpl-2.0_147.RULE")
Cc: Jonathan Corbet <corbet@lwn.net>
Cc: Allison Randal <allison@lohutok.net>
Cc: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
Cc: Thomas Gleixner <tglx@linutronix.de>
Cc: linux-kernel@vger.kernel.org
Reported-by: Stephen Rothwell <sfr@canb.auug.org.au>
Signed-off-by: Bagas Sanjaya <bagasdotme@gmail.com>
Signed-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
78 lines
2.2 KiB
ReStructuredText
78 lines
2.2 KiB
ReStructuredText
.. SPDX-License-Identifier: GPL-2.0-only
|
|
|
|
=======================
|
|
S3C24XX CPUfreq support
|
|
=======================
|
|
|
|
Introduction
|
|
------------
|
|
|
|
The S3C24XX series support a number of power saving systems, such as
|
|
the ability to change the core, memory and peripheral operating
|
|
frequencies. The core control is exported via the CPUFreq driver
|
|
which has a number of different manual or automatic controls over the
|
|
rate the core is running at.
|
|
|
|
There are two forms of the driver depending on the specific CPU and
|
|
how the clocks are arranged. The first implementation used as single
|
|
PLL to feed the ARM, memory and peripherals via a series of dividers
|
|
and muxes and this is the implementation that is documented here. A
|
|
newer version where there is a separate PLL and clock divider for the
|
|
ARM core is available as a separate driver.
|
|
|
|
|
|
Layout
|
|
------
|
|
|
|
The code core manages the CPU specific drivers, any data that they
|
|
need to register and the interface to the generic drivers/cpufreq
|
|
system. Each CPU registers a driver to control the PLL, clock dividers
|
|
and anything else associated with it. Any board that wants to use this
|
|
framework needs to supply at least basic details of what is required.
|
|
|
|
The core registers with drivers/cpufreq at init time if all the data
|
|
necessary has been supplied.
|
|
|
|
|
|
CPU support
|
|
-----------
|
|
|
|
The support for each CPU depends on the facilities provided by the
|
|
SoC and the driver as each device has different PLL and clock chains
|
|
associated with it.
|
|
|
|
|
|
Slow Mode
|
|
---------
|
|
|
|
The SLOW mode where the PLL is turned off altogether and the
|
|
system is fed by the external crystal input is currently not
|
|
supported.
|
|
|
|
|
|
sysfs
|
|
-----
|
|
|
|
The core code exports extra information via sysfs in the directory
|
|
devices/system/cpu/cpu0/arch-freq.
|
|
|
|
|
|
Board Support
|
|
-------------
|
|
|
|
Each board that wants to use the cpufreq code must register some basic
|
|
information with the core driver to provide information about what the
|
|
board requires and any restrictions being placed on it.
|
|
|
|
The board needs to supply information about whether it needs the IO bank
|
|
timings changing, any maximum frequency limits and information about the
|
|
SDRAM refresh rate.
|
|
|
|
|
|
|
|
|
|
Document Author
|
|
---------------
|
|
|
|
Ben Dooks, Copyright 2009 Simtec Electronics
|