From: Andrey Smirnov <andrew.smirnov@gmail.com>
To: barebox@lists.infradead.org
Cc: Andrey Smirnov <andrew.smirnov@gmail.com>,
Vivien Didelot <vivien.didelot@savoirfairelinux.com>
Subject: [PATCH 0/7] VF610 OCOTP MAC address layout change
Date: Tue, 22 May 2018 16:05:11 -0700 [thread overview]
Message-ID: <20180522230518.9070-1-andrew.smirnov@gmail.com> (raw)
Everyone:
This patchset is as a result of dealing with VF610 U-Boot OCOTP/MAC
quirk.
- Patch 1 and 2 are the actual patches dealing with U-Boot's
idiosyncrasy (see individual commit messages for more
details)
- Patch 3 and 4 are trivial refactoring made possible with
<linux/bitfield.h>
- Patches 5, 6 and 7 are very much optional. IMHO,
drivers/nvmem is a better place for OCOTP code, but if we
want to keep the code as is, I am more than happy to drop
these from the series.
Feedback is wellcome!
Thanks,
Andrey Smirnov
Andrey Smirnov (7):
i.MX: ocotp: Unify code paths for reading MAC address
i.MX: ocotp: Change MAC address layout for VFxxx
i.MX: ocotp: Simplify OCOTP field packing/unpacking
i.MX: ocotp: Simplify BF macro
i.MX: ocotp: Move OCOTP driver to drivers/nvmem
nvmem: Use name from struct nvmem_config for cdev
nvmem: ocotp: Convert to NVMEM device
arch/arm/mach-imx/Kconfig | 23 +--
arch/arm/mach-imx/Makefile | 1 -
arch/arm/mach-imx/include/mach/ocotp.h | 31 ++-
drivers/nvmem/Kconfig | 21 ++
drivers/nvmem/Makefile | 3 +
drivers/nvmem/core.c | 18 +-
{arch/arm/mach-imx => drivers/nvmem}/ocotp.c | 201 ++++++++++++-------
7 files changed, 183 insertions(+), 115 deletions(-)
rename {arch/arm/mach-imx => drivers/nvmem}/ocotp.c (79%)
--
2.17.0
_______________________________________________
barebox mailing list
barebox@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/barebox
next reply other threads:[~2018-05-22 23:05 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-05-22 23:05 Andrey Smirnov [this message]
2018-05-22 23:05 ` [PATCH 1/7] i.MX: ocotp: Unify code paths for reading MAC address Andrey Smirnov
2018-05-22 23:05 ` [PATCH 2/7] i.MX: ocotp: Change MAC address layout for VFxxx Andrey Smirnov
2018-05-23 8:21 ` Sascha Hauer
2018-05-25 3:06 ` Andrey Smirnov
2018-05-22 23:05 ` [PATCH 3/7] i.MX: ocotp: Simplify OCOTP field packing/unpacking Andrey Smirnov
2018-05-22 23:05 ` [PATCH 4/7] i.MX: ocotp: Simplify BF macro Andrey Smirnov
2018-05-22 23:05 ` [PATCH 5/7] i.MX: ocotp: Move OCOTP driver to drivers/nvmem Andrey Smirnov
2018-05-22 23:05 ` [PATCH 6/7] nvmem: Use name from struct nvmem_config for cdev Andrey Smirnov
2018-05-22 23:05 ` [PATCH 7/7] nvmem: ocotp: Convert to NVMEM device Andrey Smirnov
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=20180522230518.9070-1-andrew.smirnov@gmail.com \
--to=andrew.smirnov@gmail.com \
--cc=barebox@lists.infradead.org \
--cc=vivien.didelot@savoirfairelinux.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