Hi Niklas,
On Thu, Nov 1, 2018 at 12:26 AM Niklas Söderlund
<niklas.soderlund@xxxxxxxxxxxx> wrote:
> This is the result of the SDHI hackathon for a possible solution to the
> clock issue on early ES versions. It is based on the Gen2 solution where
> a row of the possible clock settings are ignored on the effected SoC+ES
> versions. The first row is not effected when reading settings left by
> the bootloader, only when the setting the clock.
To clarify, you decided not to describe the SDH clock in DT, but went for
heuristics with a quirk instead?
Is there any chance this can start to bite us in the future?
Thanks!
Gr{oetje,eeting}s,
Geert
--
Geert Uytterhoeven -- There's lots of Linux beyond ia32 -- geert@xxxxxxxxxxxxxx
In personal conversations with technical people, I call myself a hacker. But
when I'm talking to journalists I just say "programmer" or something like that.
-- Linus Torvalds
