On Thu, Nov 29, 2018 at 01:15:38AM +0100, Niklas Söderlund wrote: > The driver tries to figure out which state a SD clock is in when the > clock is register instead of setting a known state. This can be > problematic for two reasons. > > 1. If the clock driver can't figure out the state of the clock > registration of the clock fails and setting of a known state by a > clock user is not possible. > > 2. The state of the clock depends on if and how the bootloader > configured it. The driver only checks that the rate is known not if > the clock is stopped or not for example. > > Fix this by setting a known state and make sure the clock is stopped. > > Signed-off-by: Niklas Söderlund <niklas.soderlund+renesas@xxxxxxxxxxxx> This patch makes much sense to me, a known state is gold. I can't really think of a reason why it was matched against the bootloader clock. Can someone else? If not, maybe asking the BSP team makes sense to ensure we don't overlook something?
