Hello. On Sat, 2008-06-14 at 10:07, Daniel Ribeiro wrote: > > Just to summarize what I think that needs to be done for PCAP to get in > good shape: > > 1) Convert it to the generic SPI driver. > 2) API changes on newer kernels.
OK > 3) Look at other interrupt controllers/expanders, and review the irq > demultiplexer. Review in what regard? Kernel coding style or functionality? > 4) Review locking. Newer kernel have some debug features for loocking. Need to investigate this. > I suggest that we work on PCAP at the sime time as UDC, MCI and TS. > This will help with testing. I'm thinking about concentrate on one or two. But if you think you meet the two weeks deadline with all three, fine with me. ;) > The TS Driver is the best code to test at 3) and 4) as it floods PCAP > with interrupts. OK, having at least one other driver that uses the PCAP heavily is indeed good for testing. I'm also thinking about moving the driver over to drivers/mfd/. It's more a multi-function-device then anything else. The next steps how I see them: 1) Copy ezx-pcap.patch, a780-pcap.patch, e680-pcap.patch, pcap-ts.patch, a780-ts.patch and e680-ts.patch over to the linux-2.6-arm branch. Add it to the series file. 2) Move the pcap driver over to drivers/mfd/ 3) Refresh patches (mostly Kconfig and Makefile) 4) Start to covert it to the generic SPI driver again and fix all API changes on the way. Once we have this done and were able to test it one the phone we can start to work on your 3 +4. I'll do the easy steps (1-3) tomorrow if nobody beats me with this. Hopefully I'll also will have some more time then to start reading the code more carefull and begin to work on 4. regards Stefan Schmidt
signature.asc
Description: Digital signature
