Julian Margetson <runaway@xxxxxxxx> writes: > On 12/21/2015 2:27 PM, Måns Rullgård wrote: >> Julian Margetson <runaway@xxxxxxxx> writes: >> >>> On 12/21/2015 1:55 PM, Andy Shevchenko wrote: >>>> On Mon, Dec 21, 2015 at 7:26 PM, Julian Margetson <runaway@xxxxxxxx> wrote: >>>>> On 12/21/2015 12:48 PM, Andy Shevchenko wrote: >>>>>> On Sun, 2015-12-20 at 22:55 +0200, Andy Shevchenko wrote: >>>>>>> On Sun, Dec 20, 2015 at 10:17 PM, Andy Shevchenko >>>>>>> <andy.shevchenko@xxxxxxxxx> wrote: >>>>>>>> On Sun, Dec 20, 2015 at 8:49 PM, Måns Rullgård <mans@xxxxxxxxx> >>>>>>>> wrote: >>>>>>>> I noticed thanks to DWC_PARAMS that burst size is hardcoded to 32 >>>>>>>> items on this board, however registers for SATA program it to 64. I >>>>>>>> remember that I got no interrupt when I programmed transfer width >>>>>>>> wrongly (64 bits against 32 bits) when I ported dw_dmac to be used >>>>>>>> on >>>>>>>> Intel SoCs. >>>>>>> One more thing, I have a patch to monitor DMA IO, we may check what >>>>>>> exactly the values are written / read in DMA. I can share it >>>>>>> tomorrow. >>>>>> As promised the patch I have to debug IO of DW DMA. Didn't check though >>>>>> if it applies cleanly on top of recent vanilla kernel. >>>> So, the original driver (with patch from Måns) works, right? >>>> >>> The hard drive is recognized . >>> These system gets unresponsive with USB devices like the mouse and >>> keyboard not responding when I start Gparted. >> Did you disable the SATA and DMA debug messages? >> > It is working. That's good news. Thanks a lot for helping to test this. -- Måns Rullgård -- To unsubscribe from this list: send the line "unsubscribe linux-ide" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
