All of lore.kernel.org
 help / color / mirror / Atom feed
From: Oliver Graute <oliver.graute@kococonnector.com>
To: u-boot@lists.denx.de
Subject: [U-Boot] [PATCH V3 2/2] core: device: use dev_power_domain_on
Date: Tue, 10 Dec 2019 14:18:27 +0000	[thread overview]
Message-ID: <20191210141754.GA14437@optiplex> (raw)
In-Reply-To: <20190927021230.4175-2-peng.fan@nxp.com>

Hello Peng,

this patch broke my u-boot on a IMX8 QM ROM 7720a1 board.

f0cc4eae9a1702a768817ea25d9f23cece69d021

I bisect it and that is the first broken commit. The commits before are
working fine.

I tried to remove your changes but then  I run into this errrors:

sc_rm_get_memreg_info: mr:38 res:22
Memreg get info failed, -110
mu_hal_sendmsg timeout
sc_rm_is_memreg_owned: mr:39 res:21
sc_rm_is_memreg_owned: mr:39 res:21
mu_hal_sendmsg timeout

Some clue whats wrong here? Do I need to adapt my imx8qm board file?

Best regards,

Oliver

  reply	other threads:[~2019-12-10 14:18 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-09-27  1:55 [U-Boot] [PATCH V3 1/2] power: domain: add dev_power_domain_on Peng Fan
2019-09-27  1:55 ` [U-Boot] [PATCH V3 2/2] core: device: use dev_power_domain_on Peng Fan
2019-12-10 14:18   ` Oliver Graute [this message]
2019-12-11  2:50     ` Peng Fan
2019-12-11  3:15       ` Fabio Estevam
2019-12-11 14:15       ` Fabio Estevam
2019-12-12  7:20         ` Oliver Graute
2019-12-16 15:29           ` Igor Opaniuk
2019-12-16 16:24             ` Fabio Estevam
2019-12-16 21:16               ` Igor Opaniuk
2019-12-16 22:47                 ` Fabio Estevam
2019-12-17 10:56                   ` Igor Opaniuk
2019-12-17 11:21                     ` Igor Opaniuk
2019-12-17 11:23                       ` Fabio Estevam
2019-12-17 11:22                     ` Fabio Estevam
2019-12-17  1:14               ` Peng Fan
2020-01-21 10:36             ` Oliver Graute

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=20191210141754.GA14437@optiplex \
    --to=oliver.graute@kococonnector.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.