Re: [PATCH v1] mtd: rawnand: meson: always use OOB bytes during write

Hi, thanks! On 17.03.2025 09:09, Michael Nazzareno Trimarchi wrote: > Hi Arseniy > > On Sun, Dec 22, 2024 at 10:23 PM Arseniy Krasnov < > avkras...@salutedevices.com> wrote: > >> If 'oob_required' is not set by the caller (for example 'oobbuf' is NULL), >> then driver doesn't copy OOB data from

Re: [PATCH v1] mtd: rawnand: meson: always use OOB bytes during write

Hi Arseniy On Sun, Dec 22, 2024 at 10:23 PM Arseniy Krasnov < avkras...@salutedevices.com> wrote: > If 'oob_required' is not set by the caller (for example 'oobbuf' is NULL), > then driver doesn't copy OOB data from 'oob_poi' to special controller > structures, so zeroes will be written as OOB. B

Re: [PATCH v1] mtd: rawnand: meson: always use OOB bytes during write

Hi, sorry, but i don't see it merged. Is it ok? Thanks On 24.12.2024 16:56, Michael Nazzareno Trimarchi wrote: > Hi > > Yes > > Michael > > On Tue, Dec 24, 2024 at 8:55 AM Arseniy Krasnov > wrote: >> >> >> >> On 23.12.2024 15:57, Michael Nazzareno Trimarchi wrote: >>> On Sun, Dec 22, 2024 at

Re: [PATCH v1] mtd: rawnand: meson: always use OOB bytes during write

Hi Yes Michael On Tue, Dec 24, 2024 at 8:55 AM Arseniy Krasnov wrote: > > > > On 23.12.2024 15:57, Michael Nazzareno Trimarchi wrote: > > On Sun, Dec 22, 2024 at 10:23 PM Arseniy Krasnov > > wrote: > >> > >> If 'oob_required' is not set by the caller (for example 'oobbuf' is NULL), > >> then d

Re: [PATCH v1] mtd: rawnand: meson: always use OOB bytes during write

On 23.12.2024 15:57, Michael Nazzareno Trimarchi wrote: > On Sun, Dec 22, 2024 at 10:23 PM Arseniy Krasnov > wrote: >> >> If 'oob_required' is not set by the caller (for example 'oobbuf' is NULL), >> then driver doesn't copy OOB data from 'oob_poi' to special controller >> structures, so zeroes

Re: [PATCH v1] mtd: rawnand: meson: always use OOB bytes during write

On Sun, Dec 22, 2024 at 10:23 PM Arseniy Krasnov wrote: > > If 'oob_required' is not set by the caller (for example 'oobbuf' is NULL), > then driver doesn't copy OOB data from 'oob_poi' to special controller > structures, so zeroes will be written as OOB. But, generic raw NAND logic > in 'nand_bas

[PATCH v1] mtd: rawnand: meson: always use OOB bytes during write

If 'oob_required' is not set by the caller (for example 'oobbuf' is NULL), then driver doesn't copy OOB data from 'oob_poi' to special controller structures, so zeroes will be written as OOB. But, generic raw NAND logic in 'nand_base.c' already handles case when OOB is not required to write by fill