From: Lukasz Majewski <lukma@denx.de>
To: u-boot@lists.denx.de
Subject: [U-Boot] [PATCH] pico-imx6ul: Fix eMMC boot after DM_MMC conversion
Date: Wed, 27 Mar 2019 14:20:23 +0100 [thread overview]
Message-ID: <20190327142023.6420abfc@jawa> (raw)
In-Reply-To: <CAOMZO5DwOKx4D1gautyD1+DHqM=jTF6OayoJC_L9_yWEFwZa4g@mail.gmail.com>
Hi Fabio,
> Hi Lukasz,
>
> On Wed, Mar 27, 2019 at 6:23 AM Lukasz Majewski <lukma@denx.de> wrote:
>
> > This seems like a temporary solution - the u-boot proper is
> > converted to use DM_MMC, but the pinmux setup code is moved to SPL
> > instead.
> >
> > The proper solution would be to add support for pinmux in SPL and
> > setup those pins there.
>
> Thanks for the suggestion.
>
> The problem is that we are too close of 2019.04 and pico-mx6ul is
> currently broken.
>
> This is the least invasive fix we can have to avoid breakage at the
> moment.
I see. Let's fix the board first before release.
>
> Can we go with this patch for 2019.04 and then revisit the pinctrl
> setting in SPL afterwards?
Yes, no problem. I just wanted to show that a similar work has been
done previously.
>
> Thanks
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-59 Fax: (+49)-8142-66989-80 Email: lukma 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/20190327/4e2ef7f2/attachment.sig>
next prev parent reply other threads:[~2019-03-27 13:20 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-03-21 13:59 [U-Boot] [PATCH] pico-imx6ul: Fix eMMC boot after DM_MMC conversion Fabio Estevam
2019-03-27 9:23 ` Lukasz Majewski
2019-03-27 12:44 ` Fabio Estevam
2019-03-27 13:20 ` Lukasz Majewski [this message]
2019-03-30 20:59 ` Fabio Estevam
2019-03-31 18:23 ` Stefano Babic
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=20190327142023.6420abfc@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