Hello Ulf, Adrian, and anyone interested, On our AT91 products we have an SD/MMC block with an included DLL that does not lock if the SD clock is not configured depending on speed modes, like high speed requires 25 Mhz, HS200 requires 100 Mhz, etc. All the spec and the code configures everything at 400 kHz and then moves to high speed, etc. and in the end , the clock is raised. While this is perfectly fine, on our block we need to raise the clock first and change the speed mode after. Namely, in the function mmc_select_timing , if we call first mmc_set_bus_speed then our DLL will lock correctly when selecting the mode. If we select the mode first, our clock is stuck. My question is actually how (if possible) we could do a quirk in the mmc such that our block will work correctly. So I would need a little guidance about where to place such quirk, if it would be accepted or not, and we are forced to be incompatible with the linux-mmc sdhci . I have seen some patches for something similar a few years ago [1] on the ML, but they were left floating in the end, so that is why I am asking, which would be the proper way to do this. Thanks ! Eugen [1] https://patchwork.kernel.org/patch/7127441/
