linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Andrey Smirnov <andrew.smirnov@gmail.com>
To: Srinivas Kandagatla <srinivas.kandagatla@linaro.org>
Cc: Andrey Smirnov <andrew.smirnov@gmail.com>,
	linux-kernel@vger.kernel.org, Chris Healy <cphealy@gmail.com>,
	Lucas Stach <l.stach@pengutronix.de>,
	Aleksander Morgado <aleksander@aleksander.es>
Subject: [PATCH 0/2] RAVE SP EEPROM driver
Date: Wed, 21 Mar 2018 06:47:08 -0700	[thread overview]
Message-ID: <20180321134710.29757-1-andrew.smirnov@gmail.com> (raw)

Srinivas:

This series is a first iteration of the patchset adding NVMEM support
for EEPROMs connected to RAVE SP MFD device (support for which landed
in 4.15).

NOTE: This patchset depends on the following patches:

"nvmem: Document struct nvmem_config"
"nvmem: core: Allow specifying device name verbatim"
"nvmem: Introduce devm_nvmem_(un)register()"

which are still trickling down from 'char-misc' to Linus' tree.

Feedback is wellcome!

Thanks,
Andrey Smirnov

Andrey Smirnov (2):
  dt-bindings: nvmem: Add binding for RAVE SP EEPROM driver
  nvmem: Add RAVE SP EEPROM driver

 .../bindings/nvmem/zii,rave-sp-eeprom.txt          |  23 ++
 drivers/nvmem/Kconfig                              |   6 +
 drivers/nvmem/Makefile                             |   3 +
 drivers/nvmem/rave-sp-eeprom.c                     | 356 +++++++++++++++++++++
 4 files changed, 388 insertions(+)
 create mode 100644 Documentation/devicetree/bindings/nvmem/zii,rave-sp-eeprom.txt
 create mode 100644 drivers/nvmem/rave-sp-eeprom.c

-- 
2.14.3

             reply	other threads:[~2018-03-21 13:47 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-03-21 13:47 Andrey Smirnov [this message]
2018-03-21 13:47 ` [PATCH 1/2] dt-bindings: nvmem: Add binding for RAVE SP EEPROM driver Andrey Smirnov
2018-03-26 22:24   ` Rob Herring
2018-04-11  0:12     ` Andrey Smirnov
2018-03-21 13:47 ` [PATCH 2/2] nvmem: Add " Andrey Smirnov
2018-03-23 10:20   ` kbuild test robot

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=20180321134710.29757-1-andrew.smirnov@gmail.com \
    --to=andrew.smirnov@gmail.com \
    --cc=aleksander@aleksander.es \
    --cc=cphealy@gmail.com \
    --cc=l.stach@pengutronix.de \
    --cc=linux-kernel@vger.kernel.org \
    --cc=srinivas.kandagatla@linaro.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).