2010/5/26 Peter Zijlstra <peterz@xxxxxxxxxxxxx>: > On Wed, 2010-05-26 at 03:17 -0700, Arve Hjønnevåg wrote: >> > With a single suspend manager process that manages the suspend state you >> > can achieve the same goal. >> > >> >> Yes we don't need the /dev interface, but it is useful. Without it any >> program that needs to block suspend has to make a blocking ipc call >> into the suspend manager process. Android already does this for java >> code, but system processes written in C block suspend directly with >> the kernel since they cannot use the java APIs. > > So provide a C interface to it as well? > > Surely you can have the java thing have a unix socket or something a C > app can talk to. That shouldn't be hard at all. > > Or make the suspend manager a C proglet and provide a JNI interface, or > whatever. Android already has D-Bus: http://android.git.kernel.org/?p=platform/external/dbus.git;a=summary Which has Java bindings: http://dbus.freedesktop.org/doc/dbus-java/ D-Bus can be from C to send messages to the Java daemon. So why not use that if this seems to be a problem. It even brings serialized typing and all that funny stuff. Yours, Linus Walleij -- To unsubscribe from this list: send the line "unsubscribe linux-doc" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html