mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Schrempf Frieder <frieder.schrempf@kontron.de>
To: Krzysztof Kozlowski <krzk@kernel.org>,
	Rob Herring <robh+dt@kernel.org>,
	Mark Rutland <mark.rutland@arm.com>,
	Shawn Guo <shawnguo@kernel.org>,
	"Sascha Hauer" <s.hauer@pengutronix.de>,
	Pengutronix Kernel Team <kernel@pengutronix.de>,
	Fabio Estevam <festevam@gmail.com>,
	NXP Linux Team <linux-imx@nxp.com>,
	"devicetree@vger.kernel.org" <devicetree@vger.kernel.org>,
	"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
	"linux-arm-kernel@lists.infradead.org" 
	<linux-arm-kernel@lists.infradead.org>
Cc: "notify@kernel.org" <notify@kernel.org>
Subject: Re: [PATCH v4 2/3] dt-bindings: eeprom: at25: Add Anvo ANV32E61W
Date: Thu, 8 Aug 2019 18:09:05 +0000	[thread overview]
Message-ID: <de032954-2b6e-5aa9-0d91-c37417c8e162@kontron.de> (raw)
In-Reply-To: <20190808172616.11728-2-krzk@kernel.org>

On 08.08.19 19:26, Krzysztof Kozlowski wrote:
> Document the compatible for ANV32E61W EEPROM chip.

This chip is actually not an EEPROM, but a SPI nvSRAM. It can be 
interfaced by the at25 driver similar to an EEPROM. This is not the 
ideal solution, but it works until there's a proper driver for such 
chips. Maybe you can add some of these details to the commit message 
here. Also there is more information on this topic here: 
https://patchwork.ozlabs.org/patch/1043950/.

> 
> Signed-off-by: Krzysztof Kozlowski <krzk@kernel.org>
> Reviewed-by: Fabio Estevam <festevam@gmail.com>
> 
> ---
> 
> New patch
> ---
>   Documentation/devicetree/bindings/eeprom/at25.txt | 1 +
>   1 file changed, 1 insertion(+)
> 
> diff --git a/Documentation/devicetree/bindings/eeprom/at25.txt b/Documentation/devicetree/bindings/eeprom/at25.txt
> index b3bde97dc199..42577dd113dd 100644
> --- a/Documentation/devicetree/bindings/eeprom/at25.txt
> +++ b/Documentation/devicetree/bindings/eeprom/at25.txt
> @@ -3,6 +3,7 @@ EEPROMs (SPI) compatible with Atmel at25.
>   Required properties:
>   - compatible : Should be "<vendor>,<type>", and generic value "atmel,at25".
>     Example "<vendor>,<type>" values:
> +    "anvo,anv32e61w"
>       "microchip,25lc040"
>       "st,m95m02"
>       "st,m95256"
> 

  reply	other threads:[~2019-08-08 18:09 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-08-08 17:26 [PATCH v4 1/3] dt-bindings: vendor-prefixes: Add Anvo-Systems Krzysztof Kozlowski
2019-08-08 17:26 ` [PATCH v4 2/3] dt-bindings: eeprom: at25: Add Anvo ANV32E61W Krzysztof Kozlowski
2019-08-08 18:09   ` Schrempf Frieder [this message]
2019-08-12  6:43     ` Krzysztof Kozlowski
2019-08-08 17:26 ` [PATCH v4 3/3] ARM: dts: imx6ul-kontron-n6310: Add Kontron i.MX6UL N6310 SoM and boards Krzysztof Kozlowski

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=de032954-2b6e-5aa9-0d91-c37417c8e162@kontron.de \
    --to=frieder.schrempf@kontron.de \
    --cc=devicetree@vger.kernel.org \
    --cc=festevam@gmail.com \
    --cc=kernel@pengutronix.de \
    --cc=krzk@kernel.org \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-imx@nxp.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mark.rutland@arm.com \
    --cc=notify@kernel.org \
    --cc=robh+dt@kernel.org \
    --cc=s.hauer@pengutronix.de \
    --cc=shawnguo@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

all inboxes | Powered by JetHome®