From: Krzysztof Kozlowski <krzk@kernel.org>
To: Alice Guo <alice.guo@nxp.com>
Cc: devicetree@vger.kernel.org, peng.fan@nxp.com,
s.hauer@pengutronix.de, linux-kernel@vger.kernel.org,
robh+dt@kernel.org, linux-imx@nxp.com, shawnguo@kernel.org,
linux-arm-kernel@lists.infradead.org
Subject: Re: [PATCH v6 3/4] arm64: dts: imx8m: add NVMEM provider and consumer to read soc unique ID
Date: Tue, 24 Nov 2020 10:47:43 +0100 [thread overview]
Message-ID: <20201124094743.GB15030@kozik-lap> (raw)
In-Reply-To: <20201124015949.29262-3-alice.guo@nxp.com>
On Tue, Nov 24, 2020 at 09:59:48AM +0800, Alice Guo wrote:
> In order to be able to use NVMEM APIs to read soc unique ID, add the
> nvmem data cell and name for nvmem-cells to the "soc" node, and add a
> nvmem node which provides soc unique ID to efuse@30350000.
>
> Signed-off-by: Alice Guo <alice.guo@nxp.com>
I already reviewed it. Do not ignore received tags.
Reviewed-by: Krzysztof Kozlowski <krzk@kernel.org>
Best regards,
Krzysztof
> ---
>
> v2: remove the subject prefix "LF-2571-3"
> v3: convert register addresses and sizes to hex
> v4: delete "stuff" in subject and commit message, add detailed
> description
> v5: change underscore of device node to hyphen
> v6: none
_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel
WARNING: multiple messages have this Message-ID (diff)
From: Krzysztof Kozlowski <krzk@kernel.org>
To: Alice Guo <alice.guo@nxp.com>
Cc: robh+dt@kernel.org, shawnguo@kernel.org, s.hauer@pengutronix.de,
linux-imx@nxp.com, peng.fan@nxp.com, devicetree@vger.kernel.org,
linux-kernel@vger.kernel.org,
linux-arm-kernel@lists.infradead.org
Subject: Re: [PATCH v6 3/4] arm64: dts: imx8m: add NVMEM provider and consumer to read soc unique ID
Date: Tue, 24 Nov 2020 10:47:43 +0100 [thread overview]
Message-ID: <20201124094743.GB15030@kozik-lap> (raw)
In-Reply-To: <20201124015949.29262-3-alice.guo@nxp.com>
On Tue, Nov 24, 2020 at 09:59:48AM +0800, Alice Guo wrote:
> In order to be able to use NVMEM APIs to read soc unique ID, add the
> nvmem data cell and name for nvmem-cells to the "soc" node, and add a
> nvmem node which provides soc unique ID to efuse@30350000.
>
> Signed-off-by: Alice Guo <alice.guo@nxp.com>
I already reviewed it. Do not ignore received tags.
Reviewed-by: Krzysztof Kozlowski <krzk@kernel.org>
Best regards,
Krzysztof
> ---
>
> v2: remove the subject prefix "LF-2571-3"
> v3: convert register addresses and sizes to hex
> v4: delete "stuff" in subject and commit message, add detailed
> description
> v5: change underscore of device node to hyphen
> v6: none
next prev parent reply other threads:[~2020-11-24 9:48 UTC|newest]
Thread overview: 33+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-11-24 1:59 [PATCH v6 1/4] dt-bindings: soc: imx8m: add DT Binding doc for soc unique ID Alice Guo
2020-11-24 1:59 ` Alice Guo
2020-11-24 1:59 ` [PATCH v6 2/4] arm64: dts: imx8m: add SoC ID compatible Alice Guo
2020-11-24 1:59 ` Alice Guo
2020-11-24 1:59 ` [PATCH v6 3/4] arm64: dts: imx8m: add NVMEM provider and consumer to read soc unique ID Alice Guo
2020-11-24 1:59 ` Alice Guo
2020-11-24 9:47 ` Krzysztof Kozlowski [this message]
2020-11-24 9:47 ` Krzysztof Kozlowski
2020-11-24 1:59 ` [PATCH v6 4/4] soc: imx8m: change to use platform driver Alice Guo
2020-11-24 1:59 ` Alice Guo
2020-11-24 9:48 ` Krzysztof Kozlowski
2020-11-24 9:48 ` Krzysztof Kozlowski
2020-11-25 0:44 ` Adam Ford
2020-11-25 0:44 ` Adam Ford
2020-11-25 7:33 ` Krzysztof Kozlowski
2020-11-25 7:33 ` Krzysztof Kozlowski
2020-11-26 2:15 ` Alice Guo
2020-11-26 2:15 ` Alice Guo
2020-11-26 8:07 ` Krzysztof Kozlowski
2020-11-26 8:07 ` Krzysztof Kozlowski
2020-12-02 1:27 ` kernel test robot
2020-12-02 1:27 ` kernel test robot
2020-12-02 1:27 ` kernel test robot
2020-11-24 9:46 ` [PATCH v6 1/4] dt-bindings: soc: imx8m: add DT Binding doc for soc unique ID Krzysztof Kozlowski
2020-11-24 9:46 ` Krzysztof Kozlowski
2020-11-30 21:57 ` Rob Herring
2020-11-30 21:57 ` Rob Herring
2020-12-01 3:31 ` Alice Guo (OSS)
2020-12-01 3:31 ` Alice Guo (OSS)
2020-12-09 2:30 ` Alice Guo (OSS)
2020-12-09 2:30 ` Alice Guo (OSS)
2020-12-09 7:43 ` Krzysztof Kozlowski
2020-12-09 7:43 ` Krzysztof Kozlowski
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=20201124094743.GB15030@kozik-lap \
--to=krzk@kernel.org \
--cc=alice.guo@nxp.com \
--cc=devicetree@vger.kernel.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-imx@nxp.com \
--cc=linux-kernel@vger.kernel.org \
--cc=peng.fan@nxp.com \
--cc=robh+dt@kernel.org \
--cc=s.hauer@pengutronix.de \
--cc=shawnguo@kernel.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 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.