From: Jiri Prchal <jiri.prchal@aksignal.cz>
To: devicetree@vger.kernel.org, linux-kernel@vger.kernel.org
Cc: Rob Herring <robh+dt@kernel.org>,
Christian Eggers <ceggers@arri.de>, Arnd Bergmann <arnd@arndb.de>,
Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
Jiri Prchal <jiri.prchal@aksignal.cz>
Subject: [PATCH v4 0/4] add support for FRAM
Date: Thu, 20 May 2021 18:01:22 +0200 [thread overview]
Message-ID: <20210520160127.51394-1-jiri.prchal@aksignal.cz> (raw)
Adds support for Cypress FRAMs.
Jiri Prchal (5):
nvmem: eeprom: at25: add support for FRAM
nvmem: eeprom: at25: add support for FRAM
nvmem: eeprom: add documentation for FRAM
nvmem: eeprom: at25: export FRAM serial num
nvmem: eeprom: add documentation of sysfs sernum file
.../ABI/testing/sysfs-class-spi-eeprom | 6 +
.../devicetree/bindings/eeprom/at25.yaml | 31 +++-
drivers/misc/eeprom/Kconfig | 5 +-
drivers/misc/eeprom/at25.c | 167 ++++++++++++++----
drivers/nvmem/core.c | 4 +
include/linux/nvmem-provider.h | 1 +
6 files changed, 176 insertions(+), 38 deletions(-)
create mode 100644 Documentation/ABI/testing/sysfs-class-spi-eeprom
--
v2: fixes in some files
v3: resend and added more recipients
v4: resend
v5: fixes up to Greg comments, add documentation
---
2.25.1
next reply other threads:[~2021-05-20 16:02 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-05-20 16:01 Jiri Prchal [this message]
2021-05-20 16:01 ` [PATCH v5 1/5] nvmem: eeprom: at25: add support for FRAM Jiri Prchal
2021-05-20 16:01 ` [PATCH v5 2/5] " Jiri Prchal
2021-05-20 16:01 ` [PATCH v5 3/5] nvmem: eeprom: add documentation " Jiri Prchal
2021-05-20 16:01 ` [PATCH v5 4/5] nvmem: eeprom: at25: export FRAM serial num Jiri Prchal
2021-05-20 16:01 ` [PATCH v5 5/5] nvmem: eeprom: add documentation of sysfs sernum file Jiri Prchal
2021-06-04 8:16 ` [PATCH v4 0/4] add support for FRAM Greg Kroah-Hartman
-- strict thread matches above, loose matches on Subject: below --
2021-05-20 5:47 Jiri Prchal
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=20210520160127.51394-1-jiri.prchal@aksignal.cz \
--to=jiri.prchal@aksignal.cz \
--cc=arnd@arndb.de \
--cc=ceggers@arri.de \
--cc=devicetree@vger.kernel.org \
--cc=gregkh@linuxfoundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=robh+dt@kernel.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.