> -----Original Message----- > From: Kevin Hilman [mailto:khilman@xxxxxxxxxxxxxxxxxxx] > Sent: Saturday, September 04, 2010 4:20 AM > To: G, Manjunath Kondaiah > Cc: linux-omap@xxxxxxxxxxxxxxx; Cousson, Benoit; Shilimkar, > Santosh; Sawant, Anand > Subject: Re: [PATCH v2 00/11] OMAP: DMA: HWMOD and DMA as > platform driver > > "G, Manjunath Kondaiah" <manjugk@xxxxxx> writes: > > > If there are no further comments, can you please stage this patch > > series on hwmods-omap4 branch? > > Reviewed. Still a long ways to go..., also I didn't see you address > the typo pointed out by Mika Westerberg on PATCH 03/11. Sorry. I fixed it in my internal version and forgot to take that change. Thanks for pointing this. > > Also, testing on omap3430/n900, I noticed an interesting > failure during > boot. During boot (in the middle of omap3_pm_init(), a DMA interrupt > fires and the SPI RX callback is called which faults when > accessing it's > registers. Not sure about n900, I will check if I get N900. > > I did not debug this further, but is something that needs > investigation. > > Also, in the next version, please report how it was tested on the > various OMAPs. In particular, what peripherals using DMA were tested. > Just a boot test is not sufficient when making major > functional changes > like this. Drivers using DMA need to be tested as well. This patch series has been tested with various use cases like: 1. Memory to Memory DMA test cases from test code: http://dev.omapzoom.org/?p=richo/device_driver_test.git;a=shortlog;h=refs/heads/master 2. SD/MMC test cases(on zoom3, omap4 SDP and beagle) 3. Ethernet testing (on omap4 SDP with McSPI interface for both Rx and Tx - Also used NFS file system) I will provide these details in next version patches. -Manjunath -- To unsubscribe from this list: send the line "unsubscribe linux-omap" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
