[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <bb137aef-4ca9-4825-99b7-12f7e17c9550@salutedevices.com>
Date: Tue, 27 Aug 2024 20:57:04 +0300
From: Martin Kurbanov <mmkurbanov@...utedevices.com>
To: Miquel Raynal <miquel.raynal@...tlin.com>
CC: <linux-kernel@...r.kernel.org>, <linux-mtd@...ts.infradead.org>,
<kernel@...utedevices.com>, Richard Weinberger <richard@....at>, "Vignesh
Raghavendra" <vigneshr@...com>, Mika Westerberg
<mika.westerberg@...ux.intel.com>, Michael Walle <michael@...le.cc>, "Mark
Brown" <broonie@...nel.org>, Chia-Lin Kao <acelan.kao@...onical.com>, "Md
Sadre Alam" <quic_mdalam@...cinc.com>, Ezra Buehler
<ezra.buehler@...qvarnagroup.com>, Sridharan S N <quic_sridsn@...cinc.com>,
Frieder Schrempf <frieder.schrempf@...tron.de>, Alexey Romanov
<avromanov@...utedevices.com>
Subject: Re: [PATCH v2 2/5] mtd: spinand: add OTP support
Hello, Miquel. Thank you for the review.
Regarding your question ( https://lore.kernel.org/all/20240717103623.6d6b63be@xps-13/ ):
>> +int spinand_otp_read(struct spinand_device *spinand, loff_t from, size_t len,
>> + u8 *buf, size_t *retlen);
>> +
>> +int spinand_otp_write(struct spinand_device *spinand, loff_t from, size_t len,
>> + const u8 *buf, size_t *retlen);
>> +
>
> Why exposing spinand_otp_read and spinand_otp_write ?
For the SPI-NAND chips we have (Micron, ESMT, FORESEE), the command
sequence for reading/writing OTP is the same. I decided to make these
functions global because other chips probably have similar read/write
OTP operations as well.
--
Best Regards,
Martin Kurbanov
Powered by blists - more mailing lists