mirror of
https://github.com/hardkernel/linux.git
synced 2026-06-07 03:15:31 +09:00
c18fd2aea2
As we mask our SDHCI controller as SDHCI_QUIRK_CAP_CLOCK_BASE_BROKEN, host->max_clk is derived from core clock in the first place. Then f_max works together with it. If we adjust loader's core clk setting, such as 50MHz, we will get 50MHz for host->max_clk, because .get_max_clock() reads core clk when probing driver. That will lead f_max be set to 50MHz as well, no matter if max-frequency is set higher than 50MHz. We can simple solve this problem by assigning core clk as 200MHz in the first place and then let max-frequency property takes over it. Signed-off-by: Shawn Lin <shawn.lin@rock-chips.com> Change-Id: Idb2fdb8f68881d0286d977dc3718b74c30d3bc67
Linux kernel
============
There are several guides for kernel developers and users. These guides can
be rendered in a number of formats, like HTML and PDF. Please read
Documentation/admin-guide/README.rst first.
In order to build the documentation, use ``make htmldocs`` or
``make pdfdocs``. The formatted documentation can also be read online at:
https://www.kernel.org/doc/html/latest/
There are various text files in the Documentation/ subdirectory,
several of them using the Restructured Text markup notation.
See Documentation/00-INDEX for a list of what is contained in each file.
Please read the Documentation/process/changes.rst file, as it contains the
requirements for building and running the kernel, and information about
the problems which may result by upgrading your kernel.