lists.openwall.net   lists  /  announce  owl-users  owl-dev  john-users  john-dev  passwdqc-users  yescrypt  popa3d-users  /  oss-security  kernel-hardening  musl  sabotage  tlsify  passwords  /  crypt-dev  xvendor  /  Bugtraq  Full-Disclosure  linux-kernel  linux-netdev  linux-ext4  linux-hardening  linux-cve-announce  PHC 
Open Source and information security mailing list archives
 
Hash Suite: Windows password security audit tool. GUI, reports in PDF.
[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20231208123338.37f1a141@xps-13>
Date:   Fri, 8 Dec 2023 12:33:38 +0100
From:   Miquel Raynal <miquel.raynal@...tlin.com>
To:     Nikita Shubin <nikita.shubin@...uefel.me>
Cc:     Andy Shevchenko <andriy.shevchenko@...el.com>,
        Richard Weinberger <richard@....at>,
        Vignesh Raghavendra <vigneshr@...com>,
        Arnd Bergmann <arnd@...db.de>,
        Linus Walleij <linus.walleij@...aro.org>,
        Neil Armstrong <neil.armstrong@...aro.org>,
        Daniel Golle <daniel@...rotopia.org>,
        Jean Delvare <jdelvare@...e.de>,
        Christophe Kerello <christophe.kerello@...s.st.com>,
        Chris Packham <chris.packham@...iedtelesis.co.nz>,
        Johan Jonker <jbx6244@...il.com>, linux-kernel@...r.kernel.org,
        linux-mtd@...ts.infradead.org,
        Alexander Sverdlin <alexander.sverdlin@...il.com>
Subject: Re: [PATCH v5 19/39] mtd: rawnand: add support for ts72xx

Hi Nikita,

> > > +               for (i = 0; i < instr->ctx.addr.naddrs; i++)
> > > +                       iowrite8(instr->ctx.addr.addrs[i], data-  
> > > >base);  
> > 
> > iowrite8_rep() ?
> >   
> > > +       case NAND_OP_DATA_IN_INSTR:
> > > +               ioread8_rep(data->base, instr->ctx.data.buf.in,
> > > instr->ctx.data.len);  
> > 
> > Hehe, you are even using it...
> > 
> > ...
> >   
> > > +       if (instr->delay_ns)  
> > 
> > What will happen if you drop this check?
> >   
> > > +               ndelay(instr->delay_ns);  
> 
> No idea! I was asked to keep it by Miquel:

Your controller is very simple and just queues whatever command you
ask, precisely when you ask it to do so. But the NAND bus is a bit more
complex and there are minimum delays between certain instructions. This
delay is meant to respect that. Sometimes it will be 0, and sometimes
not. It depends what NAND op you do. You can check the value of these
delays in the core.

Thanks,
Miquèl

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ