From: Alexander Stein <alexander.stein@ew.tq-group.com>
To: linux-arm-kernel@lists.infradead.org, Michael Walle <michael@walle.cc>
Cc: Peng Fan <peng.fan@nxp.com>, Aisheng Dong <aisheng.dong@nxp.com>,
linux-arm-kernel@lists.infradead.org,
Srinivas Kandagatla <srinivas.kandagatla@linaro.org>
Subject: Re: issue: could not get #nvmem-cell-cells
Date: Tue, 10 Jan 2023 11:32:09 +0100 [thread overview]
Message-ID: <13180287.uLZWGnKmhe@steina-w> (raw)
In-Reply-To: <1a600055e8a21f6a4142b0cb7a0b96f0@walle.cc>
Hi Michael,
Am Dienstag, 10. Januar 2023, 09:12:26 CET schrieb Michael Walle:
> Hi Peng,
>
> Am 2023-01-10 09:07, schrieb Peng Fan:
> > 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?
>
> Do you have [1] applied? It is already in -next but just to be sure.
This patch does fix requesting a non-existing io_impedance_ctrl nvmem cell.
But these errors are about missing '#nvmem-cell-cells' properties.
IIRC there should be another patch assuming '#nvmem-cell-cells = <0>' by
default.
Best regards,
Alexander
> -michael
>
> [1]
> https://lore.kernel.org/lkml/20230105135931.2743351-1-michael@walle.cc/
>
> _______________________________________________
> linux-arm-kernel mailing list
> linux-arm-kernel@lists.infradead.org
> http://lists.infradead.org/mailman/listinfo/linux-arm-kernel
_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel
next prev parent reply other threads:[~2023-01-10 10:33 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-01-10 8:07 issue: could not get #nvmem-cell-cells Peng Fan
2023-01-10 8:12 ` Michael Walle
2023-01-10 8:14 ` Peng Fan
2023-01-10 10:32 ` Alexander Stein [this message]
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=13180287.uLZWGnKmhe@steina-w \
--to=alexander.stein@ew.tq-group.com \
--cc=aisheng.dong@nxp.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=michael@walle.cc \
--cc=peng.fan@nxp.com \
--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