From: Horatiu Vultur <horatiu.vultur@microchip.com>
To: <devicetree@vger.kernel.org>, <linux-kernel@vger.kernel.org>
Cc: <srinivas.kandagatla@linaro.org>, <robh+dt@kernel.org>,
<krzysztof.kozlowski+dt@linaro.org>,
<UNGLinuxDriver@microchip.com>,
"Horatiu Vultur" <horatiu.vultur@microchip.com>
Subject: [PATCH v2 0/2] nvmem: lan9662-otpc: add support
Date: Thu, 25 Aug 2022 22:40:39 +0200 [thread overview]
Message-ID: <20220825204041.1485731-1-horatiu.vultur@microchip.com> (raw)
Add support for lan9662 OTP controller that is available on lan9662.
The driver gives access to non-volatile memory. It allows both write
and read access to it.
v1->V2:
- remove unneed quotes for $ref: nvmem.yaml#
- rename lan966x to lan9662 as not to have any wildcards
- remove compatible string syscon
Horatiu Vultur (2):
dt-bindings: lan9662-otpc: document Lan9662 OTPC
nvmem: lan9662-otp: add support.
.../nvmem/microchip,lan9662-otpc.yaml | 42 +++
drivers/nvmem/Kconfig | 8 +
drivers/nvmem/Makefile | 2 +
drivers/nvmem/lan9662-otpc.c | 249 ++++++++++++++++++
4 files changed, 301 insertions(+)
create mode 100644 Documentation/devicetree/bindings/nvmem/microchip,lan9662-otpc.yaml
create mode 100644 drivers/nvmem/lan9662-otpc.c
--
2.33.0
next reply other threads:[~2022-08-25 20:36 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-08-25 20:40 Horatiu Vultur [this message]
2022-08-25 20:40 ` [PATCH v2 1/2] dt-bindings: lan9662-otpc: document Lan9662 OTPC Horatiu Vultur
2022-08-26 6:42 ` Krzysztof Kozlowski
2022-08-26 7:31 ` Horatiu Vultur
2022-08-26 17:37 ` Krzysztof Kozlowski
2022-08-29 6:35 ` Horatiu Vultur
2022-08-30 10:10 ` Krzysztof Kozlowski
2022-08-26 16:05 ` Rob Herring
2022-08-25 20:40 ` [PATCH v2 2/2] nvmem: lan9662-otp: add support Horatiu Vultur
2022-08-26 6:43 ` Krzysztof Kozlowski
2022-08-30 12:08 ` Srinivas Kandagatla
2022-08-30 20:07 ` Horatiu Vultur
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=20220825204041.1485731-1-horatiu.vultur@microchip.com \
--to=horatiu.vultur@microchip.com \
--cc=UNGLinuxDriver@microchip.com \
--cc=devicetree@vger.kernel.org \
--cc=krzysztof.kozlowski+dt@linaro.org \
--cc=linux-kernel@vger.kernel.org \
--cc=robh+dt@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).