Lines Matching refs:binder
6 Android binderfs is a filesystem for the Android binder IPC mechanism. It
7 allows to dynamically add and remove binder devices at runtime. Binder devices
8 located in a new binderfs instance are independent of binder devices located in
10 to get a set of private binder devices.
18 mount -t binder binder /dev/binderfs
21 In a fresh instance of binderfs no binder devices will be present. There will
22 only be a ``binder-control`` device which serves as the request handler for
31 binderfs instances can be mounted with a limit on the number of binder
34 of binder devices can be allocated in this binderfs instance.
37 Using ``stats=global`` enables global binder statistics.
42 Allocating binder Devices
47 To allocate a new binder device in a binderfs instance a request needs to be
48 sent through the ``binder-control`` device node. A request is sent in the form
51 What a program needs to do is to open the ``binder-control`` device node and
53 tell the kernel which name the new binder device should get. By default a name
58 binder_device`` with the name to the kernel it will allocate a new binder
62 binder device located under /dev/binderfs with the chosen name.
64 Deleting binder Devices
70 Binderfs binder devices can be deleted via `unlink() <unlink_>`_. This means
72 ``binder-control`` device cannot be deleted since this would make the binderfs
73 instance unusable. The ``binder-control`` device will be deleted when the
80 features supported by the binder driver can be located under