From: Oliver Graute <oliver.graute@gmail.com>
To: u-boot@lists.denx.de
Subject: imx8qxp mek: Booting mainline kernel with mainline U-Boot
Date: Thu, 23 Jan 2020 14:53:05 +0100 [thread overview]
Message-ID: <20200123135305.GA17950@optiplex> (raw)
In-Reply-To: <39592224-4f2d-a1b2-b8e5-3004db942f6b@ti.com>
On 17/01/20, Lokesh Vutla wrote:
> >>> Just wondering if anyone else managed to boot mainline U-Boot with
> >>> mainline kernel on i.MX8QXP.
> >> I can test it for you with the revert patch for f0cc4eae9a applied tomorrow.
> >
> > Adding in Lokesh as he nak'd the revert before because that would break
> > other platforms and I chimed in saying that breaking one set of
> > platforms to unbreak another set of platforms isn't a trade-off I like.
> >
>
> Right, the mentioned patch f0cc4eae9a1 ("core: device: use dev_power_domain_on")
> checks for power_domain return status when dm core tries to enable pd during
> probe. If power domain enabling is failed then no point proceeding further to probe.
>
> There are 2 ways to solve this:
> 1) Drop the return check like below. Which IMHO is a hack:
>
> diff --git a/drivers/core/device.c b/drivers/core/device.c
> index 9f39218423..c80ce16fbd 100644
> --- a/drivers/core/device.c
> +++ b/drivers/core/device.c
> @@ -432,11 +432,8 @@ int device_probe(struct udevice *dev)
>
> if (CONFIG_IS_ENABLED(POWER_DOMAIN) && dev->parent &&
> (device_get_uclass_id(dev) != UCLASS_POWER_DOMAIN) &&
> - !(drv->flags & DM_FLAG_DEFAULT_PD_CTRL_OFF)) {
> - ret = dev_power_domain_on(dev);
> - if (ret)
> - goto fail;
> - }
> + !(drv->flags & DM_FLAG_DEFAULT_PD_CTRL_OFF))
> + dev_power_domain_on(dev);
>
> ret = uclass_pre_probe_device(dev);
> if (ret)
ok very thx, this works for me together with fresh a compiled scfw
(1.2.5) from advantech. Now I'am running into this phy issue:
U-Boot 2020.01-00001-g7b3e47a09f (Jan 23 2020 - 14:30:03 +0100)
CPU: NXP i.MX8QM RevB A53 at 1200 MHz
Model: Advantech iMX8QM Qseven series
Board: ROM-7720-A1 4GB
Build: SCFW 494c97f3, SECO-FW 5ea79733, ATF d6451cc
Boot: SD2
DRAM: 4 GiB
MMC: FSL_SDHC: 0, FSL_SDHC: 1, FSL_SDHC: 2
Loading Environment from MMC... *** Warning - bad CRC, using default environment
In: serial at 5a060000
Out: serial at 5a060000
Err: serial at 5a060000
Net: Could not get PHY for FEC0: addr 0
Could not get PHY for FEC0: addr 0
Can't find FEC0 clk rate: -19
Could not get PHY for FEC1: addr 1
No ethernet found.
Hit any key to stop autoboot: 0
switch to partitions #0, OK
mmc2 is current device
** No partition table - mmc 2 **
** No partition table - mmc 2 **
Booting from net ...
Could not get PHY for FEC0: addr 0
Could not get PHY for FEC0: addr 0
Could not get PHY for FEC0: addr 0
Could not get PHY for FEC0: addr 0
No ethernet found.
Could not get PHY for FEC0: addr 0
Could not get PHY for FEC0: addr 0
Could not get PHY for FEC0: addr 0
Could not get PHY for FEC0: addr 0
Could not get PHY for FEC0: addr 0
No ethernet found.
Could not get PHY for FEC0: addr 0
Best Regards,
Oliver
next prev parent reply other threads:[~2020-01-23 13:53 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-01-13 15:36 imx8qxp mek: Booting mainline kernel with mainline U-Boot Fabio Estevam
2020-01-13 15:53 ` Anatolij Gustschin
2020-01-13 16:03 ` Fabio Estevam
2020-01-14 23:04 ` Anatolij Gustschin
2020-01-16 16:38 ` Fabio Estevam
2020-01-16 16:57 ` Anatolij Gustschin
2020-01-16 18:03 ` Igor Opaniuk
2020-01-16 18:16 ` Tom Rini
2020-01-17 6:07 ` Lokesh Vutla
2020-01-23 13:53 ` Oliver Graute [this message]
2020-01-23 14:07 ` Lokesh Vutla
2020-01-27 13:13 ` Peng Fan
2020-01-14 0:46 ` Peng Fan
2020-01-14 1:08 ` Fabio Estevam
2020-01-14 19:01 ` Fabio Estevam
2020-01-21 17:39 ` Fabio Estevam
2020-01-27 13:11 ` Peng Fan
2021-06-12 12:51 ` vmuthusu
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=20200123135305.GA17950@optiplex \
--to=oliver.graute@gmail.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