devicetree.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Srinivas Kandagatla <srinivas.kandagatla@linaro.org>
To: Horatiu Vultur <horatiu.vultur@microchip.com>,
	devicetree@vger.kernel.org, linux-kernel@vger.kernel.org
Cc: robh+dt@kernel.org, krzysztof.kozlowski+dt@linaro.org,
	UNGLinuxDriver@microchip.com
Subject: Re: [PATCH v5 0/2] nvmem: lan9662-otpc: add support
Date: Fri, 16 Sep 2022 11:54:07 +0100	[thread overview]
Message-ID: <1b27b135-73c3-07f9-5054-be828b756871@linaro.org> (raw)
In-Reply-To: <20220902064540.484967-1-horatiu.vultur@microchip.com>



On 02/09/2022 07:45, Horatiu Vultur wrote:
> 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.
> 

Applied after fixing some conflicts thanks,

--srini
> v4->v5:
> - add reviewed-by tag for patch 1
> - drop the full-stop from subject
> 
> v3->v4:
> - remove lan9668 compatible string from driver
> - fix the bindings by changing the order of entries under items for
>    compatible property
> 
> v2->v3:
> - fix dt-bindings, make sure that make dt_binding_check passes
> - remove lan9662_writel/readl/clrbits/setbits and use writel/readl
> - remove WARN_ON(offset >= OTP_MEM_SIZE) as it can't happen
> 
> 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         |  45 ++++
>   drivers/nvmem/Kconfig                         |   8 +
>   drivers/nvmem/Makefile                        |   2 +
>   drivers/nvmem/lan9662-otpc.c                  | 222 ++++++++++++++++++
>   4 files changed, 277 insertions(+)
>   create mode 100644 Documentation/devicetree/bindings/nvmem/microchip,lan9662-otpc.yaml
>   create mode 100644 drivers/nvmem/lan9662-otpc.c
> 

      parent reply	other threads:[~2022-09-16 11:02 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-09-02  6:45 [PATCH v5 0/2] nvmem: lan9662-otpc: add support Horatiu Vultur
2022-09-02  6:45 ` [PATCH v5 1/2] dt-bindings: lan9662-otpc: document Lan9662 OTPC Horatiu Vultur
2022-09-02  6:45 ` [PATCH v5 2/2] nvmem: lan9662-otp: add support Horatiu Vultur
2022-09-16 10:54 ` Srinivas Kandagatla [this message]

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=1b27b135-73c3-07f9-5054-be828b756871@linaro.org \
    --to=srinivas.kandagatla@linaro.org \
    --cc=UNGLinuxDriver@microchip.com \
    --cc=devicetree@vger.kernel.org \
    --cc=horatiu.vultur@microchip.com \
    --cc=krzysztof.kozlowski+dt@linaro.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 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).