public inbox for u-boot@lists.denx.de
 help / color / mirror / Atom feed
From: Chee, Tien Fong <tien.fong.chee@intel.com>
To: u-boot@lists.denx.de
Subject: [U-Boot] [PATCH] Add support for initializing MMC
Date: Mon, 24 Dec 2018 03:41:26 +0000	[thread overview]
Message-ID: <1545622886.16143.0.camel@intel.com> (raw)
In-Reply-To: <CAPnjgZ3_rr2UDPExJOh1ACkLbvHcmWAnD+3bfEHKmEAdpUFd-Q@mail.gmail.com>

On Sat, 2018-12-22 at 13:51 -0700, Simon Glass wrote:
> Hi Tien,
> 
> On Fri, 21 Dec 2018 at 10:50, Chee, Tien Fong <tien.fong.chee@intel.c
> om> wrote:
> > 
> > 
> > On Fri, 2018-12-21 at 10:16 -0700, Simon Glass wrote:
> > > 
> > > Hi,
> > > 
> > > On Fri, 21 Dec 2018 at 01:25, Chee, Tien Fong <tien.fong.chee@int
> > > el.c
> > > om> wrote:
> > > > 
> > > > 
> > > > 
> > > > On Fri, 2018-12-14 at 14:53 +0800, tien.fong.chee at intel.com
> > > > wrote:
> > > > > 
> > > > > 
> > > > > From: Tien Fong Chee <tien.fong.chee@intel.com>
> > > > > 
> > > > > Firmware loader would encounter problem if the MMC is
> > > > > accessed
> > > > > before
> > > > > initializing it. This patch would adding the support of
> > > > > initializing
> > > > > MMC before the MMC is accessed by firmware loader.
> > > > > 
> > > > > Signed-off-by: Tien Fong Chee <tien.fong.chee@intel.com>
> > > > > ---
> > > > >  drivers/misc/fs_loader.c |   31
> > > > > +++++++++++++++++++++++++++++++
> > > > >  1 files changed, 31 insertions(+), 0 deletions(-)
> > > > > 
> > > > Any comment for this patch?
> > > This should not be needed with CONFIG_DM_MMC enabled as it should
> > > be
> > > enough to probe the mmc device. Is that right?
> > No, CONFIG_DM_MMC is required, otherwise compiler would tell you
> > error.
> > This whole mechanism is always developed in DM context.
> > What's your concern? You want me to add CONFIG_DM_MMC or replace
> > with
> > CONFIG_MMC? or You want to improve the document?
> Well, mmc_blk_probe() calls mmc_init() on the device. So instead of
> the code you have, would it be possible to probe the blk device? You
> can use device_find_first_child() for that. Perhaps write a function
> in blk.h which probes the first block device for a parent?
Yeah, sure. Let me find out more info.
> 
> Regards,
> Simon

  reply	other threads:[~2018-12-24  3:41 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-12-14  6:53 [U-Boot] [PATCH] Add support for initializing MMC tien.fong.chee at intel.com
2018-12-21  8:25 ` Chee, Tien Fong
2018-12-21 17:16   ` Simon Glass
2018-12-21 17:50     ` Chee, Tien Fong
2018-12-22 20:51       ` Simon Glass
2018-12-24  3:41         ` Chee, Tien Fong [this message]
  -- strict thread matches above, loose matches on Subject: below --
2018-12-13 15:32 tien.fong.chee at intel.com
2018-12-13 16:22 ` Chee, Tien Fong

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=1545622886.16143.0.camel@intel.com \
    --to=tien.fong.chee@intel.com \
    --cc=u-boot@lists.denx.de \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox