There are no changes you really should need to make between an "gnu/linux" and "android/linux" driver. Some will say you need to add wake_lock's to your driver critical sections but, almost every time I see a wake_lock in the kernel (for the devices I work on) the lock was truly not needed. The few we needed to keep where associated mostly with charging or some platform level operation (FW update). One or two are needed for true wake source devices. Otherwise you don't need any.
Others my have a different opinion on how to use wake locks in kernel. But, my recomendation is that you don't add them until you have a testable failure case that clearly calls for one. Don't protectively add them. They are not like spin locks or mutexes. just write you linux drivers and start testing your target. You will end up with lots and lots of tweaks over time depending on how extensive your testing is. At least that has been my observation. good luck --mark On Thu, Apr 26, 2012 at 2:57 PM, Chirag Shah <chiragatc...@gmail.com> wrote: > Any idea !!! > Which kind of changes i need to make to make it work with Android? > Where can i look for this perticular modifications ? > > -- > unsubscribe: android-kernel+unsubscr...@googlegroups.com > website: http://groups.google.com/group/android-kernel -- create interesting things. -- unsubscribe: android-kernel+unsubscr...@googlegroups.com website: http://groups.google.com/group/android-kernel
