linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Christian Eggers <ceggers@arri.de>
To: <devicetree@vger.kernel.org>, <linux-kernel@vger.kernel.org>,
	Jiri Prchal <jiri.prchal@aksignal.cz>
Cc: Rob Herring <robh+dt@kernel.org>, Jiri Prchal <jiri.prchal@aksignal.cz>
Subject: Re: [PATCH 0/3] nvmem: eeprom: add support for FRAM
Date: Fri, 9 Apr 2021 19:21:47 +0200	[thread overview]
Message-ID: <4311739.LvFx2qVVIh@n95hx1g2> (raw)
In-Reply-To: <20210409154720.130902-1-jiri.prchal@aksignal.cz>

Hi Jiri,

I have two Fujitsu different FRAMs running with the stock at25 driver. I set
the page size equal to the device size (as FRAMs have no pages).  

Are you able to run your FRAM with the unmodified driver?

I assume that getting the device geometry from the chip is vendor specific (in
contrast to flash devices which have standard commands for this).  I suppose
that there is no much value getting vendor specific information from a chip. If
the drivers knows the vendor, it should also know the chip (e.g. from the dt).

regards
Christian

On Friday, 9 April 2021, 17:47:17 CEST, Jiri Prchal wrote:
> Adds sopport for Cypress FRAMs.
> 
> Jiri Prchal (3):
>   nvmem: eeprom: at25: add support for FRAM
>   nvmem: eeprom: at25: add support for FRAM
>   nvmem: eeprom: add documentation for FRAM
> 
>  .../devicetree/bindings/eeprom/at25.yaml      |  12 +-
>  drivers/misc/eeprom/Kconfig                   |   5 +-
>  drivers/misc/eeprom/at25.c                    | 151 ++++++++++++++----
>  drivers/nvmem/core.c                          |   4 +
>  include/linux/nvmem-provider.h                |   1 +
>  5 files changed, 139 insertions(+), 34 deletions(-)
> 
> 





  parent reply	other threads:[~2021-04-09 17:55 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-04-09 15:47 [PATCH 0/3] nvmem: eeprom: add support for FRAM Jiri Prchal
2021-04-09 15:47 ` [PATCH 1/3] nvmem: add things " Jiri Prchal
2021-04-09 15:47 ` [PATCH 2/3] nvmem: eeprom: at25: add support " Jiri Prchal
2021-04-09 18:34   ` kernel test robot
2021-04-09 15:47 ` [PATCH 3/3] nvmem: eeprom: add documentation " Jiri Prchal
2021-04-09 18:57   ` Rob Herring
2021-04-09 17:21 ` Christian Eggers [this message]
2021-04-12  6:06   ` [PATCH 0/3] nvmem: eeprom: add support " Jiří 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=4311739.LvFx2qVVIh@n95hx1g2 \
    --to=ceggers@arri.de \
    --cc=devicetree@vger.kernel.org \
    --cc=jiri.prchal@aksignal.cz \
    --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).