All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Jiří Prchal" <jiri.prchal@aksignal.cz>
To: Christian Eggers <ceggers@arri.de>,
	devicetree@vger.kernel.org, linux-kernel@vger.kernel.org
Cc: Rob Herring <robh+dt@kernel.org>
Subject: Re: [PATCH 0/3] nvmem: eeprom: add support for FRAM
Date: Mon, 12 Apr 2021 08:06:52 +0200	[thread overview]
Message-ID: <5624cedb-e9e2-d1c3-2fb3-b03f7fe51a99@aksignal.cz> (raw)
In-Reply-To: <4311739.LvFx2qVVIh@n95hx1g2>



On 09. 04. 21 19:21, Christian Eggers wrote:
> 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).

Hi Christian,
main purpose of this patch is to get serial number from this chip. I 
don't have it done yet, in older kernels I expose it as separate file in 
sysfs, but in this kernel no luck. So a post first things while I'm 
working on sernum exposing.

Does your chip has serial number? Can you read it?

Any help welcomed.
Thanks
Jiri

PS: If standard EEPROMs has some commands to get size etc., why it's not 
used? I guess that size is increased as time goes while board is still 
the same, so isn't it annoying changing dt every new lot with bigger 
eeproms.

      reply	other threads:[~2021-04-12  6:06 UTC|newest]

Thread overview: 9+ 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 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 ` [PATCH 0/3] nvmem: eeprom: add support " Christian Eggers
2021-04-12  6:06   ` Jiří Prchal [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=5624cedb-e9e2-d1c3-2fb3-b03f7fe51a99@aksignal.cz \
    --to=jiri.prchal@aksignal.cz \
    --cc=ceggers@arri.de \
    --cc=devicetree@vger.kernel.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.