From: Boris Brezillon <boris.brezillon@free-electrons.com>
To: Moritz Fischer <moritz.fischer@ettus.com>
Cc: David Woodhouse <dwmw2@infradead.org>,
Brian Norris <computersforpeace@gmail.com>,
linux-mtd@lists.infradead.org,
Linux Kernel Mailing List <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 19:14:07 +0200 [thread overview]
Message-ID: <20160516191407.1dbb3028@bbrezillon> (raw)
In-Reply-To: <CAAtXAHcbjH0FzK=tuvwFSjUA7jJ4CT76NWQR31YR1UmXcAX9sQ@mail.gmail.com>
On Mon, 16 May 2016 09:30:10 -0700
Moritz Fischer <moritz.fischer@ettus.com> wrote:
> Hi Boris,
>
> On Mon, May 16, 2016 at 1:05 AM, Boris Brezillon
> <boris.brezillon@free-electrons.com> wrote:
>
> >> 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
>
> Well in my case I actually planned to use it with the OTP partition of my QSPI
> device using spi_nor_read_usr_prot_reg and friends and I just needed a way
> to get to the struct mtd_info from a child of my network device.
>
> Right now the OTP 'partitions' are not really exposed to device tree afaik.
> Maybe that would be worthwhile to further look into? Maybe exposing
> (wrapping) that as nvmem
> would be the way to go?
I think so. Now that MTD partitions are defined in a 'partitions'
subnode (see MTD binding doc), we can define an 'otp-partitions'
subnode and define nvmem cells in there.
--
Boris Brezillon, Free Electrons
Embedded Linux and Kernel engineering
http://free-electrons.com
prev parent reply other threads:[~2016-05-16 17:14 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
2016-05-16 16:30 ` Moritz Fischer
2016-05-16 17:14 ` Boris Brezillon [this message]
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=20160516191407.1dbb3028@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