From: srinivas.kandagatla@linaro.org (Srinivas Kandagatla)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH v3 0/2] nvmem: remove regmap dependency
Date: Mon, 2 May 2016 19:36:12 +0100 [thread overview]
Message-ID: <1462214174-469-1-git-send-email-srinivas.kandagatla@linaro.org> (raw)
Hi Greg,
This is v3 patchset for the leftover 2 patches for nvmem regmap
removal series [1]. These patches are based on char-misc tree.
nvmem uses regmap_raw_read/write apis to read/write data from providers,
With recent patch 922a9f936e40 ("regmap: mmio: Convert to regmap_bus
and fix accessor usage") nvmem providers based on regmap-mmio stopped
working, as nvmem core was using raw accessors.
This issue can be fixed temporarly by moving to other regmap apis,
but we might hit same issue in future, and regmap looks like an
overdo for nvmem. Moving to interfaces based on read/write callbacks
from providers would be more robust.
This patchset converts the nvmem core and nvmem provider drivers to
use the new callbacks. Tested this patchset on qfprom and at24 drivers.
Other driver are only compile tested, any testing on them would be great.
Most of the patches have been applied to char-misc tree, these are the
two patches which had some outstanding comments on mxs nvmemprovider,
which are now fixed.
Changes since v2:
- Fixed the mxs size and dt data pointer spotted by Stefan and Fabio
Changes since v1:
- rebased mtk-efuse on top of char-misc
- addressed concerns raised by Stefan Wahren.
[1] https://www.mail-archive.com/linux-kernel at vger.kernel.org/msg1130026.html
Thanks,
srini
Srinivas Kandagatla (2):
nvmem: mtk-efuse: remove nvmem regmap dependency
nvmem: mxs-ocotp: remove nvmem regmap dependency
drivers/nvmem/Kconfig | 1 -
drivers/nvmem/mtk-efuse.c | 47 ++++++++++++++++++---------
drivers/nvmem/mxs-ocotp.c | 83 +++++++++++++----------------------------------
3 files changed, 54 insertions(+), 77 deletions(-)
--
2.5.0
next reply other threads:[~2016-05-02 18:36 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-05-02 18:36 Srinivas Kandagatla [this message]
2016-05-02 18:36 ` [PATCH v3 1/2] nvmem: mtk-efuse: remove nvmem regmap dependency Srinivas Kandagatla
2016-05-02 18:36 ` [PATCH v3 2/2] nvmem: mxs-ocotp: " Srinivas Kandagatla
2016-05-04 11:03 ` Stefan Wahren
2016-05-18 14:30 ` [PATCH v3 0/2] nvmem: remove " Stefan Wahren
2016-05-18 14:36 ` Srinivas Kandagatla
2016-06-01 8:27 ` Stefan Wahren
2016-06-01 17:55 ` Greg Kroah-Hartman
2016-06-23 18:07 ` Stefan Wahren
2016-06-25 14:43 ` Greg Kroah-Hartman
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=1462214174-469-1-git-send-email-srinivas.kandagatla@linaro.org \
--to=srinivas.kandagatla@linaro.org \
--cc=linux-arm-kernel@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;
as well as URLs for NNTP newsgroup(s).