Thanks Magnus - Let me know how it goes. Im posting a patch in a few minutes that alters the way clocks are selected on tmio-mmc - it now picks the closest frequency to that requested. I think this is the better solution because the limited clock selections available are generally only a little higher than those commonly requested, and the next lowest quite a LOT lower (eg. we tend to init at ~200-250kHz on TMIO which is awful IMO). 2009/9/29 Magnus Damm <magnus.damm@xxxxxxxxx>: > On Tue, Sep 29, 2009 at 12:09 PM, Ian Molton <ian@xxxxxxxxxxxxxx> wrote: >> *prod* >> >> After all the fuss about this, no-ones going to comment? >> >> I just found the last tmio-related bug I want to squash before I >> consider this patchset 'good to go' so people actually updatinng their >> drivers / sending me code would be much appreciated. I'd prefer this >> went in with all the affected drivers tested and ASIC3 I _do not have >> one of_ to test. >> >> Its only a few lines - can we get it finished please? > > I have time to try your stuff on SuperH today or tomorrow. Thanks for your help! > > / magnus > -- Ian Molton Linux, Automotive, and other hacking: http://www.mnementh.co.uk/ -- To unsubscribe from this list: send the line "unsubscribe linux-mmc" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
