From: Lukasz Majewski <lukma@denx.de>
To: u-boot@lists.denx.de
Subject: [U-Boot] [PATCH 1/5] dm: mmc: updated mmc_of_parse() to not fail because of an invalid bus-width
Date: Wed, 22 Nov 2017 10:07:44 +0100 [thread overview]
Message-ID: <20171122100744.56b9d80c@jawa> (raw)
In-Reply-To: <1511277188-2923-2-git-send-email-jjhiblot@ti.com>
On Tue, 21 Nov 2017 16:13:04 +0100
Jean-Jacques Hiblot <jjhiblot@ti.com> wrote:
> Instead of failing, the driver uses the default: 1-bit bus width.
>
> Signed-off-by: Jean-Jacques Hiblot <jjhiblot@ti.com>
> ---
> drivers/mmc/mmc-uclass.c | 7 ++++---
> 1 file changed, 4 insertions(+), 3 deletions(-)
>
> diff --git a/drivers/mmc/mmc-uclass.c b/drivers/mmc/mmc-uclass.c
> index e30cde7..48fafce 100644
> --- a/drivers/mmc/mmc-uclass.c
> +++ b/drivers/mmc/mmc-uclass.c
> @@ -137,9 +137,10 @@ int mmc_of_parse(const void *fdt, int node,
> struct mmc_config *cfg) cfg->host_caps |= MMC_MODE_1BIT;
> break;
> default:
> - printf("error: %s invalid bus-width property %d\n",
> - fdt_get_name(fdt, node, NULL), val);
> - return -ENOENT;
> + debug("warning: %s invalid bus-width property. using
> 1-bit\n",
> + fdt_get_name(fdt, node, NULL));
> + cfg->host_caps |= MMC_MODE_1BIT;
> + break;
> }
>
> cfg->f_max = fdtdec_get_int(fdt, node, "max-frequency",
> 52000000);
Reviewed-by: Lukasz Majewski <lukma@denx.de>
Best regards,
Lukasz Majewski
--
DENX Software Engineering GmbH, Managing Director: Wolfgang Denk
HRB 165235 Munich, Office: Kirchenstr.5, D-82194 Groebenzell, Germany
Phone: (+49)-8142-66989-10 Fax: (+49)-8142-66989-80 Email: wd at denx.de
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 488 bytes
Desc: OpenPGP digital signature
URL: <http://lists.denx.de/pipermail/u-boot/attachments/20171122/9913faba/attachment.sig>
next prev parent reply other threads:[~2017-11-22 9:07 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <CGME20171121151316epcas1p2f87ac6bca7b8cbd31b9270775443241d@epcas1p2.samsung.com>
2017-11-21 15:13 ` [U-Boot] [PATCH 0/5] mmc: fixes for HS200/UHS core support Jean-Jacques Hiblot
2017-11-21 15:13 ` [U-Boot] [PATCH 1/5] dm: mmc: updated mmc_of_parse() to not fail because of an invalid bus-width Jean-Jacques Hiblot
2017-11-22 9:07 ` Lukasz Majewski [this message]
2017-11-24 22:36 ` Simon Glass
2017-11-21 15:13 ` [U-Boot] [PATCH 2/5] mmc: dm: support "mmc-ddr-1_2v" and "mmc-hs200-1_2v" boolean properties Jean-Jacques Hiblot
2017-11-22 9:08 ` Lukasz Majewski
2017-11-24 22:36 ` Simon Glass
2017-11-21 15:13 ` [U-Boot] [PATCH 3/5] mmc: dump card and host capabilities if debug is enabled Jean-Jacques Hiblot
2017-11-22 9:08 ` Lukasz Majewski
2017-11-24 22:36 ` Simon Glass
2017-11-21 15:13 ` [U-Boot] [PATCH 4/5] mmc: Fixed a problem with old sd or mmc that do not support High speed Jean-Jacques Hiblot
2017-11-22 9:09 ` Lukasz Majewski
2017-11-24 22:36 ` Simon Glass
2017-11-21 15:13 ` [U-Boot] [PATCH 5/5] mmc: all hosts support 1-bit bus width and legacy timings Jean-Jacques Hiblot
2017-11-22 9:09 ` Lukasz Majewski
2017-11-24 22:36 ` Simon Glass
2017-11-27 8:47 ` Jean-Jacques Hiblot
2017-11-22 12:09 ` [U-Boot] [PATCH 0/5] mmc: fixes for HS200/UHS core support Jaehoon Chung
2017-11-22 14:00 ` Marek Vasut
2017-11-23 14:52 ` Jean-Jacques Hiblot
2017-11-23 14:55 ` Marek Vasut
2017-11-24 6:01 ` Jaehoon Chung
2017-11-27 9:45 ` Jaehoon Chung
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=20171122100744.56b9d80c@jawa \
--to=lukma@denx.de \
--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