Hi!
On Mon, Apr 4, 2022 at 6:28 PM Miquel Raynal <miquel.raynal@xxxxxxxxxxx> wrote:
> [...]
> > > > +
> > > > + // This driver ignores any ECC capability configured by user or
> > > > + // requested by the nand chip because the BootROM and MTK bootloader
> > > > + // expects the page format to be the exact one as calculated in
> > > > + // setup_pagefmt.
> > >
> > > I don't like this :)
> > >
> > > I understand that the boot partition might have specific constraints,
> > > but other partitions (or if we don't use the NAND to boot?) should
> > > probably be usable with other ECC schemes.
> >
> > In this controller, the ECC step size is fixed and it can only change
> > ECC strength.
>
> That's fine.
>
> > The calculated ECC correction capability is the max
> > possible one supported by the controller.
> > I still want the default behavior to match the boot partition
> > requirement,
>
> That is okay, but that does not mean you can only support this one.
>
> > because we can't just tell end-users to customize
> > their dts by taking apart their device and figure out which flash
> > is used.
>
> They don't have to do so. In theory they should not request anything,
> the core would take care of all of that. But they can request specific
> values by using the DT and you must follow them in the driver.
>
> On his side the core is responsible of telling you which strength
> should be used otherwise and the driver is expected to use it.
The core provided ecc strength may be smaller than the
calculated one. e.g. A nand chip may only have a requirement
of 8/512bits ECC. But if it has a 2k+128 pagesize, this
controller can do 12/512bits ECC and the bootrom expects the
latter.
> You should take the user requirements first. If there are no
> user inputs, you should in theory look at the device's requirements.
I'll take the user requirements if there is one. If there isn't, I'll
follow the calculated strength instead of the device requirement
so that user doesn't have to specify a custom strength in dt.
> [...]
> > > > +static struct nand_ecc_engine_ops mtk_snfi_ecc_engine_ops = {
> > > > + .init_ctx = mtk_snand_ecc_init_ctx,
> > > > + .prepare_io_req = mtk_snand_ecc_prepare_io_req,
> > > > + .finish_io_req = mtk_snand_ecc_finish_io_req,
> > >
> > > I believe you need to take care of the bounce buffer in the exit path?
> >
> > No. The buffer should be left there for non-ecc spi-mem operations.
>
> AFAIR you initialize the buffer in the ECC part, so if it must be used
> without ECC you should probably allocate it for the SPI controller.
I did. the setup_pagefmt is called once with the minimal page+oob size
in probe.
> In
> any way, you need to free that memory at some point (when removing the
> driver).
I was using the devm api for this allocation so kernel should take
care of that.
I'll change the DMA to use streamed API in the next version to avoid
an extra memory copy in reading, and the allocated buffer will be
freed in remove().
--
Regards,
Chuanhong Guo
