[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <YMMn3T/cz2FxEt8X@kroah.com>
Date: Fri, 11 Jun 2021 11:07:41 +0200
From: Greg Kroah-Hartman <gregkh@...uxfoundation.org>
To: Jiří Prchal <jiri.prchal@...ignal.cz>
Cc: devicetree@...r.kernel.org, linux-kernel@...r.kernel.org,
Rob Herring <robh+dt@...nel.org>,
Christian Eggers <ceggers@...i.de>,
Arnd Bergmann <arnd@...db.de>
Subject: Re: [PATCH v9 5/5] nvmem: eeprom: add documentation of sysfs fram
and sernum file
On Fri, Jun 11, 2021 at 11:01:57AM +0200, Jiří Prchal wrote:
>
>
> On 11. 06. 21 10:53, Greg Kroah-Hartman wrote:
> > On Fri, Jun 11, 2021 at 07:26:52AM +0200, Jiri Prchal wrote:
> > > +Description:
> > > + Contains the FRAM binary data. Same as EEPROM, just another file
> > > + name to indicate that it employs ferroelectric process.
> > > + It performs write operations at bus speed - no write delays, capable
> > > + of 10^14 read/write cycles and 151 years data retention.
> >
> > Are you sure of these statistics? Don't promise something here that
> > might not be true, this is not a marketing document :)
>
> Just copied from datasheet. Is write at bus speed OK? And about others: much
> more then EEPROM would be OK? Or don't write about it?
I would not even mention it :)
Powered by blists - more mailing lists