diff options
| author | Seungwon Jeon <tgih.jun@samsung.com> | 2013-08-31 00:13:31 +0900 |
|---|---|---|
| committer | Chris Ball <cjb@laptop.org> | 2013-09-25 21:34:12 -0400 |
| commit | 1f44a2a55787faa08a50266fa5dc99f0dcd36b7c (patch) | |
| tree | 8f09f1a0e9d5967a20fc409bf3d244a8d3c0d8c1 /mm | |
| parent | 10b498419f41ffaca7510286c0db8ea34300576d (diff) | |
| download | talos-op-linux-1f44a2a55787faa08a50266fa5dc99f0dcd36b7c.tar.gz talos-op-linux-1f44a2a55787faa08a50266fa5dc99f0dcd36b7c.zip | |
mmc: dw_mmc: set the supported max/min frequency
Both f_max and f_min will be informed for core layer to request
valid clock rate. But current setting from 'host->bus_hz' may
not represent the max/min frequency properly. Even if host can
actually support high speed than bus_hz, core layer will not
request clock rate over bus_hz. Basically, f_max/f_min can be set
with the values according to spec. And then host will make its best
effort to meet the rate.
Signed-off-by: Seungwon Jeon <tgih.jun@samsung.com>
Tested-by: Alim Akhtar <alim.akhtar@samsung.com>
Signed-off-by: Chris Ball <cjb@laptop.org>
Diffstat (limited to 'mm')
0 files changed, 0 insertions, 0 deletions
