From: Maxime Ripard <maxime.ripard@free-electrons.com>
To: Marek Vasut <marek.vasut@gmail.com>
Cc: Moritz Fischer <moritz.fischer@ettus.com>, Alban <albeu@free.fr>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
Srinivas Kandagatla <srinivas.kandagatla@linaro.org>,
Rob Herring <robh+dt@kernel.org>,
Mark Rutland <mark.rutland@arm.com>,
David Woodhouse <dwmw2@infradead.org>,
Brian Norris <computersforpeace@gmail.com>,
Boris Brezillon <boris.brezillon@free-electrons.com>,
Richard Weinberger <richard@nod.at>,
Cyrille Pitchen <cyrille.pitchen@atmel.com>,
Devicetree List <devicetree@vger.kernel.org>,
linux-mtd@lists.infradead.org
Subject: Re: [PATCH v2 1/2] doc: bindings: Add bindings documentation for mtd nvmem
Date: Fri, 10 Mar 2017 07:38:10 +0100 [thread overview]
Message-ID: <20170310063810.2efkb6j2kdgadalv@lukather> (raw)
In-Reply-To: <eb8f93fd-0534-2b91-7fec-7d40ddf7b8cb@gmail.com>
[-- Attachment #1: Type: text/plain, Size: 2059 bytes --]
Hi Marek,
On Fri, Mar 10, 2017 at 05:52:36AM +0100, Marek Vasut wrote:
> On 03/10/2017 05:06 AM, Moritz Fischer wrote:
> > On Thu, Mar 9, 2017 at 7:17 PM, Marek Vasut <marek.vasut@gmail.com> wrote:
> >> On 03/07/2017 09:26 AM, Alban wrote:
> >>> Config data for drivers, like MAC addresses, is often stored in MTD.
> >>> Add a binding that define how such data storage can be represented in
> >>> device tree.
> >>>
> >>> Signed-off-by: Alban <albeu@free.fr>
> >>> ---
> >>> Changelog:
> >>> v2: * Added a "Required properties" section with the nvmem-provider
> >>> property
> >>> ---
> >>> .../devicetree/bindings/nvmem/mtd-nvmem.txt | 33 ++++++++++++++++++++++
> >>> 1 file changed, 33 insertions(+)
> >>> create mode 100644 Documentation/devicetree/bindings/nvmem/mtd-nvmem.txt
> >>>
> >>> diff --git a/Documentation/devicetree/bindings/nvmem/mtd-nvmem.txt b/Documentation/devicetree/bindings/nvmem/mtd-nvmem.txt
> >>> new file mode 100644
> >>> index 0000000..8ed25e6
> >>> --- /dev/null
> >>> +++ b/Documentation/devicetree/bindings/nvmem/mtd-nvmem.txt
> >>> @@ -0,0 +1,33 @@
> >>> += NVMEM in MTD =
> >>> +
> >>> +Config data for drivers, like MAC addresses, is often stored in MTD.
> >>> +This binding define how such data storage can be represented in device tree.
> >>> +
> >>> +An MTD can be defined as an NVMEM provider by adding the `nvmem-provider`
> >>> +property to their node. Data cells can then be defined as child nodes
> >>> +of the partition as defined in nvmem.txt.
> >>
> >> Why don't we just read the data from MTD and be done with it ? What's
> >> the benefit of complicating things by using nvmem ?
> >
> > Well because usually stuff like MAC addresses etc are stored in eeproms.
>
> But eeproms are already supported, see drivers/misc/ .
This the old, free for all, way to support eeproms. We have a proper
framework for them now, and it's called nvmem.
Maxime
--
Maxime Ripard, Free Electrons
Embedded Linux and Kernel engineering
http://free-electrons.com
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 801 bytes --]
next prev parent reply other threads:[~2017-03-10 6:38 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-03-07 8:26 [PATCH v2 0/2] mtd: Add support for reading MTD devices via the nvmem API Alban
2017-03-07 8:26 ` [PATCH v2 1/2] doc: bindings: Add bindings documentation for mtd nvmem Alban
2017-03-07 21:01 ` Boris Brezillon
2017-03-08 15:20 ` Alban
2017-03-08 16:25 ` Boris Brezillon
[not found] ` <1488875164-30440-2-git-send-email-albeu-GANU6spQydw@public.gmane.org>
2017-03-10 3:17 ` Marek Vasut
[not found] ` <9f54978c-6d61-cf2c-fb2d-f5ef2af19e0f-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
2017-03-10 4:06 ` Moritz Fischer
[not found] ` <CAAtXAHc34fG_TZbHrRp=oB_e=-o18zDesT73YSEx1Tr5ZE0oSw-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2017-03-10 4:52 ` Marek Vasut
2017-03-10 6:38 ` Maxime Ripard [this message]
2017-03-10 7:28 ` Marek Vasut
2017-03-15 17:24 ` Rob Herring
2017-03-15 19:41 ` Alban
2017-03-18 20:58 ` Rob Herring
2017-03-19 11:16 ` Alban
2017-03-07 8:26 ` [PATCH v2 2/2] mtd: Add support for reading MTD devices via the nvmem API Alban
[not found] ` <1488875164-30440-3-git-send-email-albeu-GANU6spQydw@public.gmane.org>
2017-03-07 18:52 ` Boris Brezillon
2017-03-13 2:18 ` [lkp-robot] [mtd] 88eb23fa5e: kernel_BUG_at_fs/sysfs/file.c kernel test robot
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=20170310063810.2efkb6j2kdgadalv@lukather \
--to=maxime.ripard@free-electrons.com \
--cc=albeu@free.fr \
--cc=boris.brezillon@free-electrons.com \
--cc=computersforpeace@gmail.com \
--cc=cyrille.pitchen@atmel.com \
--cc=devicetree@vger.kernel.org \
--cc=dwmw2@infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mtd@lists.infradead.org \
--cc=marek.vasut@gmail.com \
--cc=mark.rutland@arm.com \
--cc=moritz.fischer@ettus.com \
--cc=richard@nod.at \
--cc=robh+dt@kernel.org \
--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).