path: root/wpa_supplicant/binder
Commit message (Collapse)AuthorAgeFilesLines
* wpa_supplicant: Fix typosYegor Yefremov2020-10-191-1/+1
| | | | Signed-off-by: Yegor Yefremov <yegorslists@googlemail.com>
* binder: Clang format the source codeRoshan Pius2016-08-0711-107/+105
| | | | | | | Add a ".clang-format" file which is pretty close to the rest of wpa_supplicant code base and reformat the binder codebase. Signed-off-by: Roshan Pius <rpius@google.com>
* binder: Expose an aidl interface moduleRoshan Pius2016-08-074-5/+41
| | | | | | | | | | | Restructure the binder related makefile sections to expose a separate |libwpa_binder_interface| which can be imported by clients/tests. While there, Change the name of the binder service to the name used in the selinux permissions. Signed-off-by: Roshan Pius <rpius@google.com>
* binder: Implement interface add/remove methodsRoshan Pius2016-04-027-0/+259
| | | | | | | | | | | | | This commit implements the methods defined in Supplicant service: 1. CreateInterface 2. RemoveInterface 3. GetInterface The binder service returns the corresponding iface binder object references which can be used by clients to control a specific interface. Signed-off-by: Roshan Pius <rpius@google.com>
* binder: Add binder skeletal code for AndroidRoshan Pius2016-04-0212-0/+426
Create the skeletal binder interface for wpa_supplicant. The interface hierarchy is based off the existing dbus interface(https://w1.fi/wpa_supplicant/devel/dbus.html). Since we use libbinder, the binder interface codebase needs to be written in C++ and can only be compiled on Android platform for now. The aidl files define binder RPC interfaces. The Android build system generates the corresponding C++ interface classes which needs to be implemented by the server process. The clients can obtain a reference to the binder service (root object) using: android::String16 service_name("fi.w1.wpa_supplicant"); android::sp<android::IBinder> binder = android::defaultServiceManager()->getService(service_name); Once a reference to the root object is retrieved, the clients can obtain references to other RPC objects using that root object methods. Signed-off-by: Roshan Pius <rpius@google.com>