diff options
| author | Vincent Fazio <vfazio@xes-inc.com> | 2021-09-14 13:19:18 -0500 |
|---|---|---|
| committer | Peter Robinson <pbrobinson@gmail.com> | 2023-03-24 14:43:20 +0000 |
| commit | 0a36afa82356b89ffc66ed7557d115186c5bd7f1 (patch) | |
| tree | 076a90713b5faf285461e6b17ba16a9491cc429b /common/cli_getch.c | |
| parent | 0e8c94054fd80535e868900deb978a9a1ebcab67 (diff) | |
arm: rpi: fallback to max clock rate for MMC clock
In rpi-firmware 25e2b597ebfb2495eab4816a276758dcc6ea21f1,
the GET_CLOCK_RATE mailbox property was changed to return the last
value set by SET_CLOCK_RATE.
https://github.com/raspberrypi/firmware/issues/1619#issuecomment-917025502
Due to this change in firmware behavior, bcm2835_get_mmc_clock now
returns a clock rate of zero since we do not issue SET_CLOCK_RATE.
This results in degraded MMC performance.
SET_CLOCK_RATE fixes the clock to a specific value and disables scaling
so is not an ideal solution.
Instead, fallback to GET_MAX_CLOCK_RATE in bcm2835_get_mmc_clock if
GET_CLOCK_RATE returns zero.
Signed-off-by: Vincent Fazio <vfazio@xes-inc.com>
Signed-off-by: Peter Robinson <pbrobinson@gmail.com>
Diffstat (limited to 'common/cli_getch.c')
0 files changed, 0 insertions, 0 deletions