From: Chee, Tien Fong <tien.fong.chee@intel.com>
To: u-boot@lists.denx.de
Subject: [U-Boot] [PATCH v2] misc: fs_loader: Add support for initializing MMC
Date: Thu, 10 Jan 2019 03:35:53 +0000 [thread overview]
Message-ID: <1547091351.10039.11.camel@intel.com> (raw)
In-Reply-To: <CAPnjgZ2QB71A4KUvZCnErNif79cNgRpWv=niENJF01rJUiCwMw@mail.gmail.com>
On Wed, 2019-01-09 at 09:19 -0700, Simon Glass wrote:
> Hi Tien Fong,
>
> On Sat, 29 Dec 2018 at 18:36, <tien.fong.chee@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 probing
> > block
> > device and initializing MMC before the MMC is accessed by firmware
> > loader.
> >
> > Signed-off-by: Tien Fong Chee <tien.fong.chee@intel.com>
> > ---
> >
> > Changes in v2:
> > - Initializing MMC through probing the blk device
> > ---
> > drivers/misc/fs_loader.c | 33 +++++++++++++++++++++++++++++++++
> > 1 file changed, 33 insertions(+)
> >
> > diff --git a/drivers/misc/fs_loader.c b/drivers/misc/fs_loader.c
> > index 57a14a3..5858073 100644
> > --- a/drivers/misc/fs_loader.c
> > +++ b/drivers/misc/fs_loader.c
> > @@ -12,6 +12,7 @@
> > #include <linux/string.h>
> > #include <mapmem.h>
> > #include <malloc.h>
> > +#include <mmc.h>
> > #include <spl.h>
> >
> > DECLARE_GLOBAL_DATA_PTR;
> > @@ -252,6 +253,38 @@ static int fs_loader_ofdata_to_platdata(struct
> > udevice *dev)
> >
> > static int fs_loader_probe(struct udevice *dev)
> > {
> > +#if defined(CONFIG_DM_MMC) && defined(CONFIG_BLK)
> > + int ret;
> > + struct device_platdata *plat = dev->platdata;
> > +
> > + ret = mmc_initialize(NULL);
> You should not need this since the MMC device should init itself when
> probed.
Noted.
>
> >
> > + if (ret) {
> > + debug("MMC: could not initialize mmc. error: %d\n",
> > ret);
> > +
> > + return ret;
> > + }
> > +
> > + if (plat->phandlepart.phandle) {
> > + ofnode node = ofnode_get_by_phandle(plat-
> > >phandlepart.phandle);
> > +
> > + struct udevice *mmc_dev = NULL;
> > +
> > + ret = device_get_global_by_ofnode(node, &mmc_dev);
> You could use this?
>
> uclass_get_device_by_ofnode(UCLASS_MMC, node, &mmc_dev)
Okay.
>
> But actually I think you should drop any mention of MMC so that your
> code can work for any storage uclass.
I agree with you, we should made the probing generic to any storage
uclass.
But now i'm not familiar with all storage uclass yet, so my strategy is
getting one storage uclass in at a time, and restructure the probing if
there is commonality for the next storage uclass. With that, we can
control the quality and achieving the goal step by step.
What do you think?
>
> >
> > + if (!ret) {
> > + struct mmc *mmc = mmc_get_mmc_dev(mmc_dev);
> > + struct udevice *dev;
> > +
> > + ret = blk_get_from_parent(mmc->dev, &dev);
> You are going from mmc_dev -> mmc -> mmc->dev, but unless I am
> mistaken, mmc_dev == mmc->dev. So you should be able to simplify this
> to:
>
> ret = blk_get_from_parent(mmc_dev, &dev);
Okay,noted.
>
> Also you should be able to rename mmc to something more generic, e.g.
> to make this work with SATA.
Replied in above.
>
> >
> > + if (ret) {
> > + debug("MMC: No block device: %d\n",
> > + ret);
> > +
> > + return ret;
> > + }
> > + }
> > + }
> > +#endif
> > +
> > return 0;
> > };
> >
> > --
> > 2.2.0
> >
> Regards,
> Simon
next prev parent reply other threads:[~2019-01-10 3:35 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-12-30 1:36 [U-Boot] [PATCH v2] misc: fs_loader: Add support for initializing MMC tien.fong.chee at intel.com
2019-01-03 7:20 ` Chee, Tien Fong
2019-01-09 16:19 ` Simon Glass
2019-01-10 3:35 ` Chee, Tien Fong [this message]
2019-01-10 12:57 ` Simon Glass
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=1547091351.10039.11.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