RE: [PATCH] [v2] sata_fsl: add workaround for data length mismatch on freescale V2 controller

> > > > hstatus = ioread32(hcr_base + HSTATUS); > > > > sata_fsl_scr_read(&ap->link, SCR_ERROR, &SError); > > > > + /* Read command completed register */ > > + done_mask = ioread32(hcr_base + CC); > > + > > + /* Workaround for data length mismatch errata */ > > + if (unlikely(hstatu

Re: [PATCH] [v2] sata_fsl: add workaround for data length mismatch on freescale V2 controller

Hello. On 06-09-2012 8:28, Shaohui Xie wrote: The freescale V2 SATA controller checks if the received data length matches the programmed length 'ttl', if not, it assumes that this is an error. In ATAPI, the 'ttl' is based on max allocation length and not the actual data transfer length, control

[PATCH] [v2] sata_fsl: add workaround for data length mismatch on freescale V2 controller

The freescale V2 SATA controller checks if the received data length matches the programmed length 'ttl', if not, it assumes that this is an error. In ATAPI, the 'ttl' is based on max allocation length and not the actual data transfer length, controller will raise 'DLM' (Data length Mismatch) error