From: Srinivas Kandagatla <srinivas.kandagatla@linaro.org>
To: Joakim Zhang <qiangqing.zhang@nxp.com>,
robh+dt@kernel.org, shawnguo@kernel.org, a.fatoum@pengutronix.de
Cc: kernel@pengutronix.de, devicetree@vger.kernel.org,
linux-kernel@vger.kernel.org, linux-imx@nxp.com
Subject: Re: [PATCH V2 0/6] nvmem: add "cell-type" property to support mac-address
Date: Tue, 28 Sep 2021 15:44:19 +0100 [thread overview]
Message-ID: <2194172f-a362-a328-993b-45ebec539f9d@linaro.org> (raw)
In-Reply-To: <20210923110109.29785-1-qiangqing.zhang@nxp.com>
Hi Joakim,
I pushed some WIP changes to
https://git.kernel.org/pub/scm/linux/kernel/git/srini/nvmem.git/log/?h=topic/post-processing
with Rob's feedback,
Do you think you could try it out and see if this works for you?
--srini
On 23/09/2021 12:01, Joakim Zhang wrote:
> This patch set adds "cell-type" property to parse mac address, take i.MX
> as an example, which need reverse byte for mac address.
>
> ChangeLogs:
> V1->V2:
> * correct comments: @cell_read_callback -> @cell_post_process
> * s/imx8mm/imx8m/ in commit message title
> * add reviewed-by tags
>
> Joakim Zhang (2):
> arm64: dts: imx8m: add "cell-type" property for mac-address
> arm64: dts: imx8m: remove unused "nvmem_macaddr_swap" property for FEC
>
> Srinivas Kandagatla (4):
> dt-bindings: nvmem: add cell-type to nvmem cells
> nvmem: core: parse nvmem cell-type from device tree
> nvmem: core: add nvmem cell post processing callback
> nvmem: imx-ocotp: add support for post porcessing.
>
> .../devicetree/bindings/nvmem/nvmem.yaml | 11 +++++++
> arch/arm64/boot/dts/freescale/imx8mm.dtsi | 3 +-
> arch/arm64/boot/dts/freescale/imx8mn.dtsi | 3 +-
> arch/arm64/boot/dts/freescale/imx8mp.dtsi | 10 ++++++-
> arch/arm64/boot/dts/freescale/imx8mq.dtsi | 3 +-
> drivers/nvmem/core.c | 12 ++++++++
> drivers/nvmem/imx-ocotp.c | 30 +++++++++++++++++++
> include/dt-bindings/nvmem/nvmem.h | 8 +++++
> include/linux/nvmem-provider.h | 5 ++++
> 9 files changed, 81 insertions(+), 4 deletions(-)
> create mode 100644 include/dt-bindings/nvmem/nvmem.h
>
next prev parent reply other threads:[~2021-09-28 14:44 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-09-23 11:01 [PATCH V2 0/6] nvmem: add "cell-type" property to support mac-address Joakim Zhang
2021-09-23 11:01 ` [PATCH V2 1/6] dt-bindings: nvmem: add cell-type to nvmem cells Joakim Zhang
2021-09-27 20:42 ` Rob Herring
2021-09-28 13:16 ` Srinivas Kandagatla
2021-09-23 11:01 ` [PATCH V2 2/6] nvmem: core: parse nvmem cell-type from device tree Joakim Zhang
2021-09-23 11:01 ` [PATCH V2 3/6] nvmem: core: add nvmem cell post processing callback Joakim Zhang
2021-09-23 11:01 ` [PATCH V2 4/6] nvmem: imx-ocotp: add support for post porcessing Joakim Zhang
2021-09-23 11:01 ` [PATCH V2 5/6] arm64: dts: imx8m: add "cell-type" property for mac-address Joakim Zhang
2021-09-23 11:01 ` [PATCH V2 6/6] arm64: dts: imx8m: remove unused "nvmem_macaddr_swap" property for FEC Joakim Zhang
2021-09-28 14:44 ` Srinivas Kandagatla [this message]
2021-09-29 8:07 ` [PATCH V2 0/6] nvmem: add "cell-type" property to support mac-address Joakim Zhang
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=2194172f-a362-a328-993b-45ebec539f9d@linaro.org \
--to=srinivas.kandagatla@linaro.org \
--cc=a.fatoum@pengutronix.de \
--cc=devicetree@vger.kernel.org \
--cc=kernel@pengutronix.de \
--cc=linux-imx@nxp.com \
--cc=linux-kernel@vger.kernel.org \
--cc=qiangqing.zhang@nxp.com \
--cc=robh+dt@kernel.org \
--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 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).