diff options
author | Viresh Kumar | 2012-04-19 08:18:15 +0200 |
---|---|---|
committer | Grant Likely | 2012-04-27 20:07:40 +0200 |
commit | ea505bc99f77f3f9db02bb965bd59ac5db063f60 (patch) | |
tree | de89dabcfede2797cdecc224aa5224854db5232a /drivers/rtc/rtc-pl031.c | |
parent | spi/bcm63xx: set master driver mode_bits. (diff) | |
download | kernel-qcow2-linux-ea505bc99f77f3f9db02bb965bd59ac5db063f60.tar.gz kernel-qcow2-linux-ea505bc99f77f3f9db02bb965bd59ac5db063f60.tar.xz kernel-qcow2-linux-ea505bc99f77f3f9db02bb965bd59ac5db063f60.zip |
spi/pl022: Allow request for higher frequency than maximum possible
Currently, if we request for frequency greater than maximum possible, spi driver
returns error.
For example, if the spi block src frequency is 333/4 MHz, i.e. 83.33.. MHz,
maximum frequency programmable would be src/2. Which would come around 41.6...
It is difficult to pass frequency in these figures. We normally try to program
in round figures, like 42 MHz and it should get programmed to <=
requested_frequency, i.e. 41.6...
For this to happen, we must not return error even if requested freq is higher
than max possible. But should program it to max possible.
Reported-by: Vinit Kamalaksha Shenoy <vinit.shenoy@st.com>
Signed-off-by: Viresh Kumar <viresh.kumar@st.com>
Acked-by: Linus Walleij <linus.walleij@linaro.org>
Signed-off-by: Grant Likely <grant.likely@secretlab.ca>
Diffstat (limited to 'drivers/rtc/rtc-pl031.c')
0 files changed, 0 insertions, 0 deletions