From: Sascha Hauer <s.hauer@pengutronix.de>
To: Barebox List <barebox@lists.infradead.org>
Subject: [PATCH] Add nvmem support
Date: Wed, 3 Feb 2016 17:27:08 +0100 [thread overview]
Message-ID: <1454516830-26387-1-git-send-email-s.hauer@pengutronix.de> (raw)
This ports over the nvmem framework from the kernel. I probably won't
apply it as is since it doesn't make me very happy. While it generally
works the very first test already reveals that it can't properly handle
the different layouts of nvmem cells. The MAC addresses for the i.MX
FEC are stored in different byte orders in the IIM/OCOTP units. There's
simply no proper place to encode these different byte orders, see patch
[2/2].
Sascha
----------------------------------------------------------------
Sascha Hauer (1):
nvmem: Test it with fec/ocotp
Steffen Trumtrar (1):
drivers: add nvmem framework from kernel
arch/arm/dts/imx6qdl-phytec-pfla02.dtsi | 9 +
arch/arm/mach-imx/ocotp.c | 8 +
drivers/Kconfig | 1 +
drivers/Makefile | 1 +
drivers/net/fec_imx.c | 30 ++
drivers/nvmem/Kconfig | 8 +
drivers/nvmem/Makefile | 6 +
drivers/nvmem/core.c | 749 ++++++++++++++++++++++++++++++++
include/linux/nvmem-consumer.h | 157 +++++++
include/linux/nvmem-provider.h | 49 +++
10 files changed, 1018 insertions(+)
create mode 100644 drivers/nvmem/Kconfig
create mode 100644 drivers/nvmem/Makefile
create mode 100644 drivers/nvmem/core.c
create mode 100644 include/linux/nvmem-consumer.h
create mode 100644 include/linux/nvmem-provider.h
_______________________________________________
barebox mailing list
barebox@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/barebox
next reply other threads:[~2016-02-03 16:27 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-02-03 16:27 Sascha Hauer [this message]
2016-02-03 16:27 ` [PATCH 1/2] drivers: add nvmem framework from kernel Sascha Hauer
2016-02-03 16:27 ` [PATCH 2/2] nvmem: Test it with fec/ocotp Sascha Hauer
2016-02-03 19:01 ` Trent Piepho
2016-02-04 7:05 ` Sascha Hauer
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=1454516830-26387-1-git-send-email-s.hauer@pengutronix.de \
--to=s.hauer@pengutronix.de \
--cc=barebox@lists.infradead.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