On 03/19/2015 07:55 PM, Bjorn Andersson wrote: > On Thu, Mar 19, 2015 at 9:21 AM, Georgi Djakov <georgi.djakov@xxxxxxxxxx> wrote: > [..] >>> Does the 8916 board you have work without bumping the >>> regulator_set_load() (previously regulator_set_optimum_mode())? None >>> of my 8974 boards work reliably without it. >> >> My 8916 board seems to be working fine with this, at least when doing basic tests >> like mounting filesystems and file transfers. I'm not calling any regulator_set_load() >> functions. Is your board a dragonboard or something else? If you are doing any >> specific tests maybe i can try the same on my board? >> > > My test setup is Xperia Z1, where I get issues when running with > hs200. On Xperia Z3 i can't even read out the partition table during > boot. I'm not sure what causes the difference to the dragonboard - > perhaps just different memories. > Thanks for the information. Currently i do not notice such issues, but however i will do some more testing. > So I have a patch where I hook up the mmc framework with some calls to > regulator_set_load(), but it need some more love before I can send it > out. I postponed it due to the rework of regulator_set_optimum_mode() > that I did. Ok, sounds good. I can test it on a few boards that i have. Thanks, Georgi -- To unsubscribe from this list: send the line "unsubscribe linux-arm-msm" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
