From mboxrd@z Thu Jan 1 00:00:00 1970 From: Luca Ellero Date: Tue, 10 Feb 2015 16:18:12 +0100 Subject: [U-Boot] [PATCH] mtd: nand: mxs: fix PIO_WORD number In-Reply-To: <54DA043F.1020501@denx.de> References: <1418199884-2430-1-git-send-email-luca.ellero@brickedbrain.com> <201412131412.43236.marex@denx.de> <548E9F99.3070606@brickedbrain.com> <201412151214.16493.marex@denx.de> <548FE80A.1040005@brickedbrain.com> <54DA043F.1020501@denx.de> Message-ID: <54DA2134.6030606@brickedbrain.com> List-Id: MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit To: u-boot@lists.denx.de On 10/02/2015 14:14, Stefano Babic wrote: > Hi Luca, > > On 16/12/2014 09:06, Luca Ellero wrote: > >>>> Scheduling the patch for -next it's ok for me. >>>> However there are other two points where pio_words number doesn't >>>> reflect the pio_words really initiated, one is in mxs_nand_read_buf() >>>> and one is in mxs_nand_write_buf(). Each one declares 4 pio_words but >>>> only one is initiated. >>>> I wonder what we should do in this cases. >>> >>> You can fix those as well. I recall that all this goop came from the >>> original >>> (2.6.35) GPMI NAND driver, which is likely where all those bugs came >>> from as >>> well. >>> >>> Thank you! >>> >> >> OK, I will send a patch to fix them. > > Do you plan to send a V2 patch for fixing all the issues at once ? > > Best regards, > Stefano Babic > Hi Stefano, yes, I can send a patch with all the fixes, that's fine. I plan to send it tomorrow. Regards Luca -- Luca Ellero E-mail: luca.ellero at brickedbrain.com Internet: www.brickedbrain.com