linux-arm-kernel.lists.infradead.org archive mirror
 help / color / mirror / Atom feed
From: Peng Fan <peng.fan@nxp.com>
To: "michael@walle.cc" <michael@walle.cc>
Cc: Aisheng Dong <aisheng.dong@nxp.com>,
	"linux-arm-kernel@lists.infradead.org"
	<linux-arm-kernel@lists.infradead.org>,
	Srinivas Kandagatla <srinivas.kandagatla@linaro.org>
Subject: issue: could not get #nvmem-cell-cells
Date: Tue, 10 Jan 2023 08:07:58 +0000	[thread overview]
Message-ID: <DU0PR04MB94174EC5A35480EFBAC895BD88FF9@DU0PR04MB9417.eurprd04.prod.outlook.com> (raw)

Hi Michael,

I see you have added nvmem-cell-cells support, but with linux-next, I see error on i.MX8MP-EVK:
[    0.027518] OF: /soc@0: could not get #nvmem-cell-cells for /soc@0/bus@30000000/efuse@30350000/unique-id@8
[    0.027868] OF: /soc@0/bus@30000000/tmu@30260000: could not get #nvmem-cell-cells for /soc@0/bus@30000000/efuse@30350000/calib@264
[    0.030338] OF: /soc@0/bus@30800000/ethernet@30be0000: could not get #nvmem-cell-cells for /soc@0/bus@30000000/efuse@30350000/mac-address@90
[    0.030511] OF: /soc@0/bus@30800000/ethernet@30bf0000: could not get #nvmem-cell-cells for /soc@0/bus@30000000/efuse@30350000/mac-address@96

Do you have ideas?

Thanks,
Peng.



_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel

             reply	other threads:[~2023-01-10  8:09 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-01-10  8:07 Peng Fan [this message]
2023-01-10  8:12 ` issue: could not get #nvmem-cell-cells Michael Walle
2023-01-10  8:14   ` Peng Fan
2023-01-10 10:32   ` Alexander Stein
2023-01-10 10:47     ` Michael Walle
2023-01-10 14:45 ` Michael Walle
2023-01-10 15:52   ` Robert Marko

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=DU0PR04MB94174EC5A35480EFBAC895BD88FF9@DU0PR04MB9417.eurprd04.prod.outlook.com \
    --to=peng.fan@nxp.com \
    --cc=aisheng.dong@nxp.com \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=michael@walle.cc \
    --cc=srinivas.kandagatla@linaro.org \
    /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;
as well as URLs for NNTP newsgroup(s).