From: Boris Brezillon <boris.brezillon@free-electrons.com>
To: Moritz Fischer <moritz.fischer@ettus.com>
Cc: dwmw2@infradead.org, computersforpeace@gmail.com,
linux-mtd@lists.infradead.org, linux-kernel@vger.kernel.org,
moritz.fischer.private@gmail.com
Subject: Re: [PATCH] mtd: Adding of_mtd_info_get to get mtd_info from devicetree
Date: Mon, 16 May 2016 10:05:11 +0200 [thread overview]
Message-ID: <20160516100511.360c89c9@bbrezillon> (raw)
In-Reply-To: <20160516095534.727fcac6@bbrezillon>
On Mon, 16 May 2016 09:55:34 +0200
Boris Brezillon <boris.brezillon@free-electrons.com> wrote:
> Hi Moritz,
>
> On Wed, 11 May 2016 10:47:39 -0700
> Moritz Fischer <moritz.fischer@ettus.com> wrote:
>
> > This allows for getting a struct mtd_info from a node pointer,
> > allowing mtd devices to e.g. store serial numbers or MAC addresses.
>
> Can you detail a bit what you'll do next. I guess you need to provide
> this information to in-kernel users, and those users will just call
> mtd_read() after retrieving the mtd_info pointer.
>
> Here are a few questions (I'm assuming the netdev + MAC address case):
> - how would you link the net/PHY device to the MTD partition storing
> the MAC address
Sorry, I sent it before asking all my questions :).
- it seems quite specific to MTD devices to me. What if the MAC address
is stored in something that is not exposed as an MTD device. I wonder
if we shouldn't add an nvmem wrapper around MTD devices.
--
Boris Brezillon, Free Electrons
Embedded Linux and Kernel engineering
http://free-electrons.com
next prev parent reply other threads:[~2016-05-16 8:05 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-05-11 17:47 [PATCH] mtd: Adding of_mtd_info_get to get mtd_info from devicetree Moritz Fischer
2016-05-16 7:55 ` Boris Brezillon
2016-05-16 8:05 ` Boris Brezillon [this message]
2016-05-16 16:30 ` Moritz Fischer
2016-05-16 17:14 ` Boris Brezillon
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=20160516100511.360c89c9@bbrezillon \
--to=boris.brezillon@free-electrons.com \
--cc=computersforpeace@gmail.com \
--cc=dwmw2@infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mtd@lists.infradead.org \
--cc=moritz.fischer.private@gmail.com \
--cc=moritz.fischer@ettus.com \
/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