From mboxrd@z Thu Jan 1 00:00:00 1970 From: Simon Horman Date: Fri, 13 Dec 2013 00:11:09 +0000 Subject: Re: [PATCH 0/4] mmc: tmio/SDHI fixup patches Message-Id: <20131213001104.GA32101@verge.net.au> List-Id: References: <87iovn8ohs.wl%kuninori.morimoto.gx@renesas.com> <87txee6dvk.fsf@octavius.laptop.org> <871u1ifpa8.wl%kuninori.morimoto.gx@gmail.com> In-Reply-To: <871u1ifpa8.wl%kuninori.morimoto.gx@gmail.com> MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit To: Kuninori Morimoto Cc: Chris Ball , Kuninori Morimoto , Magnus , Linux-SH , linux-mmc@vger.kernel.org On Thu, Dec 12, 2013 at 12:26:42AM -0800, Kuninori Morimoto wrote: > > Hi Chris, Simon > > > > Now, our new board would like to use sh_mobile_sdhi driver, > > > then, it is expecting sh_mobile_sdhi use regulator. > > > But, this regulator is based on GPIO driver, > > > and GPIO driver probe timing is after sh_mobile_sdhi. > > > So, sh_mobile_sdhi (= tmio_mmc_pio) use default ocr_avail, > > > and it doesn't work for us. > > > #1 patch returns -EPROBE_DEFER in such case. > > > it changes tmio_mmc_host_probe() behavior, but > > > in my check, tmio_mmc_pio driver user is sh_mobile_sdhi/tmio-mmc only, > > > and, current user has no conflict by this patch. > > > > > > sh_mobile_sdhi/tmio-mmc is very similar, but, have some difference. > > > #2 - #4 cares such case. > > > > > > These were part of "SDHI support for r8a7790" patch set, > > > but was separated > > > > Sorry for the delay, I've pushed all four patches to mmc-next for > > 3.14. Thanks, > > Chris > Thank you for your hard work about this. > > Simon > Lager SDHI needs these patches. > Can you use this branch ? > If yes, I can re-send patches. Hi Chris, is it possible for you to provide a branch with stable git commit ids that I can use as a base? I'm happy to use mmc-next if you think it is appropriate.