CameraProvider进程启动流程

已于 2022-05-12 08:20:07 修改
阅读量2k 收藏 12
点赞数 3
分类专栏： 相机开发 文章标签： android stm32 单片机
于 2022-05-01 16:18:30 首次发布
原文链接：http://www.javashuo.com/article/p-ghdvyhzt-mk.html
版权

cameraprovider进程是Camer HAL所在进程，在分析HAL启动流程前，必须先分析下cameraprovider的启动流程
本文在此对cameraprovider的启动流程作简要的分析

rc启动脚本：linux
//hardware\interfaces\camera\provider\2.4\default\android.hardware.camera.provider@2.4-service.rc
service camera-provider-2-4 /vendor/bin/hw/android.hardware.camera.provider@2.4-service
    class hal
    user root
    group audio camera input drmrpc
    ioprio rt 4
    capabilities SYS_NICE
    writepid /dev/cpuset/camera-daemon/tasks /dev/stune/foreground/tasks

从rc脚本看:
cameraprovider进程名：camera-provider-2-4 ，
bin文件：/vendor/bin/hw/android.hardware.camera.provider@2.4-service

编译文件：c++

//hardware\interfaces\camera\provider\2.4\default\
cc_binary {
    name: "android.hardware.camera.provider@2.4-service",//name
    defaults: ["hidl_defaults"],
    proprietary: true,
    relative_install_path: "hw",//install目录位/vendor/lib/hw
    srcs: ["service.cpp"],//源码
    compile_multilib: "32",//编译为32位
    init_rc: ["android.hardware.camera.provider@2.4-service.rc"],//rc文件
    shared_libs: [
        "libhidlbase",
        "libhidltransport",
        "libbinder",
        "liblog",
        "libutils",
        "android.hardware.camera.device@1.0",
        "vendor.qti.hardware.camera.device@1.0_vendor",
        "android.hardware.camera.device@3.2",
        "android.hardware.camera.device@3.3",
        "android.hardware.camera.provider@2.4",
        "android.hardware.camera.common@1.0",
    ],
}

从上边看，服务源码为：service.cpp，服务入口以下：

//hardware\interfaces\camera\provider\2.4\default\service.cpp
int main()
{
    ALOGI("Camera provider Service is starting.");
    // The camera HAL may communicate to other vendor components via
    // /dev/vndbinder
    android::ProcessState::initWithDriver("/dev/vndbinder");
    //该方法实现了
    //一、经过Passthrough方法（直通式，本人理解为在同一个进程中运行）获取CameraProvider对象
    //二、注册服务给hwservicemanager
    return defaultPassthroughServiceImplementation<ICameraProvider>("legacy/0", /*maxThreads*/ 6);
}

defaultPassthroughServiceImplementation时，使用了ICameraProvider类，
ICameraProvider类是由HIDL接口定义文件ICameraProvider.hal经过hidl-gen编译工具编译生成。
ICameraProvider.hal接口定义文件以下：

//hardware\interfaces\camera\provider\2.4\ICameraProvider.hal
package android.hardware.camera.provider@2.4;
import ICameraProviderCallback;
import android.hardware.camera.common@1.0::types;
import android.hardware.camera.device@1.0::ICameraDevice;
import android.hardware.camera.device@3.2::ICameraDevice;
interface ICameraProvider {
    setCallback(ICameraProviderCallback callback) generates (Status status);
    getVendorTags() generates (Status status, vec<VendorTagSection> sections);
    getCameraIdList()
            generates (Status status, vec<string> cameraDeviceNames);
    isSetTorchModeSupported() generates (Status status, bool support);

    getCameraDeviceInterface_V1_x(string cameraDeviceName) generates
            (Status status,
             android.hardware.camera.device@1.0::ICameraDevice device);
    getCameraDeviceInterface_V3_x(string cameraDeviceName) generates
            (Status status,
             android.hardware.camera.device@3.2::ICameraDevice device);
};

其编译命令以下：

//hardware\interfaces\camera\Android.bp
// This file is autogenerated by hidl-gen. Do not edit manually.
filegroup {
    name: "android.hardware.camera.provider@2.4_hal",
    srcs: [
        "ICameraProvider.hal",
        "ICameraProviderCallback.hal",
    ],
}

genrule {
    name: "android.hardware.camera.provider@2.4_genc++",
    tools: ["hidl-gen"],
    cmd: "$(location hidl-gen) -o $(genDir) -Lc++-sources -randroid.hardware:hardware/interfaces -randroid.hidl:system/libhidl/transport android.hardware.camera.provider@2.4",
    srcs: [
        ":android.hardware.camera.provider@2.4_hal",
    ],
    out: [
        "android/hardware/camera/provider/2.4/CameraProviderAll.cpp",
        "android/hardware/camera/provider/2.4/CameraProviderCallbackAll.cpp",
    ],
}

genrule {
    name: "android.hardware.camera.provider@2.4_genc++_headers",
    tools: ["hidl-gen"],
    cmd: "$(location hidl-gen) -o $(genDir) -Lc++-headers -randroid.hardware:hardware/interfaces -randroid.hidl:system/libhidl/transport android.hardware.camera.provider@2.4",
    srcs: [
        ":android.hardware.camera.provider@2.4_hal",
    ],
    out: [
        "android/hardware/camera/provider/2.4/ICameraProvider.h",
        "android/hardware/camera/provider/2.4/IHwCameraProvider.h",
        "android/hardware/camera/provider/2.4/BnHwCameraProvider.h",
        "android/hardware/camera/provider/2.4/BpHwCameraProvider.h",
        "android/hardware/camera/provider/2.4/BsCameraProvider.h",
       ....
    ],
}

cc_library {
    name: "android.hardware.camera.provider@2.4",
    defaults: ["hidl-module-defaults"],
    generated_sources: ["android.hardware.camera.provider@2.4_genc++"],
    generated_headers: ["android.hardware.camera.provider@2.4_genc++_headers"],
    export_generated_headers: ["android.hardware.camera.provider@2.4_genc++_headers"],
    vendor_available: true,
    vndk: {
        enabled: true,
    },
    ....
}

经过上述编译命令看，ICameraProvider.hal经过hidl-gen编译生成了ICameraProvider.h，BnHwCameraProvider.h，BpHwCameraProvider.h，BsCameraProvider.h等头文件和一个CameraProviderAll.cpp CPP文件
并最终生成了android.hardware.camera.provider@2.4.so文件

接着继续分析下defaultPassthroughServiceImplementation函数

//system\libhidl\transport\include\hidl\LegacySupport.h
//模板方法，class为ICameraProvider
template<class Interface>
__attribute__((warn_unused_result))
status_t defaultPassthroughServiceImplementation(std::string name,
                                            size_t maxThreads = 1) {
    //打开/dev/hwbinder
    //通知kernel，当前进程最大容许的线程数量maxThreads
    configureRpcThreadpool(maxThreads, true);
    //获取Passthrough（直通）的服务实现
    //而后将获取的服务注册给hwservicemanager
    status_t result = registerPassthroughServiceImplementation<Interface>(name);
    ...
    joinRpcThreadpool();
    return 0;
}

分析下configureRpcThreadpool工具

//system\libhidl\transport\HidlTransportSupport.cpp
void configureRpcThreadpool(size_t maxThreads, bool callerWillJoin) {
    // TODO(b/32756130) this should be transport-dependent
    configureBinderRpcThreadpool(maxThreads, callerWillJoin);
}
//system\libhidl\transport\HidlBinderSupport.cpp
void configureBinderRpcThreadpool(size_t maxThreads, bool callerWillJoin) {
    ProcessState::self()->setThreadPoolConfiguration(maxThreads, callerWillJoin /*callerJoinsPool*/);
}

ProcessState::self()获取ProcessState的全局单例变量gProcess

//system\libhwbinder\ProcessState.cpp
sp<ProcessState> ProcessState::self()
{
    Mutex::Autolock _l(gProcessMutex);
    if (gProcess != NULL) {
        return gProcess;
    }
    gProcess = new ProcessState;
    return gProcess;
}

ProcessState的构造函数会打开/dev/hwbinder设备节点，并将内存映射到当前进程

//system\libhwbinder\ProcessState.cpp
ProcessState::ProcessState()
    : mDriverFD(open_driver())//打开/dev/hwbinder节点
    , mVMStart(MAP_FAILED)
    , mThreadCountLock(PTHREAD_MUTEX_INITIALIZER)
    , mThreadCountDecrement(PTHREAD_COND_INITIALIZER)
    , mExecutingThreadsCount(0)
    , mMaxThreads(DEFAULT_MAX_BINDER_THREADS)
    , mStarvationStartTimeMs(0)
    , mManagesContexts(false)
    , mBinderContextCheckFunc(NULL)
    , mBinderContextUserData(NULL)
    , mThreadPoolStarted(false)
    , mSpawnThreadOnStart(true)
    , mThreadPoolSeq(1)
{
    if (mDriverFD >= 0) {
        // mmap the binder, providing a chunk of virtual address space to receive transactions.
        //内存映射
        mVMStart = mmap(0, BINDER_VM_SIZE, PROT_READ, MAP_PRIVATE | MAP_NORESERVE, mDriverFD, 0);
        if (mVMStart == MAP_FAILED) {
            // *sigh*
            ALOGE("Using /dev/hwbinder failed: unable to mmap transaction memory.\n");
            close(mDriverFD);
            mDriverFD = -1;
        }
    }
    else {
        ALOGE("Binder driver could not be opened. Terminating.");
    }
}

打开/dev/hwbinder的代码

//system\libhwbinder\ProcessState.cpp
static int open_driver()
{
    int fd = open("/dev/hwbinder", O_RDWR | O_CLOEXEC);
    if (fd >= 0) {
        int vers = 0;
        status_t result = ioctl(fd, BINDER_VERSION, &vers);
        if (result == -1) {
            ALOGE("Binder ioctl to obtain version failed: %s", strerror(errno));
            close(fd);
            fd = -1;
        }
        if (result != 0 || vers != BINDER_CURRENT_PROTOCOL_VERSION) {
          ALOGE("Binder driver protocol(%d) does not match user space protocol(%d)!", vers, BINDER_CURRENT_PROTOCOL_VERSION);
            close(fd);
            fd = -1;
        }
        size_t maxThreads = DEFAULT_MAX_BINDER_THREADS;
        result = ioctl(fd, BINDER_SET_MAX_THREADS, &maxThreads);
        if (result == -1) {
            ALOGE("Binder ioctl to set max threads failed: %s", strerror(errno));
        }
    } else {
        ALOGW("Opening '/dev/hwbinder' failed: %s\n", strerror(errno));
    }
    return fd;
}

从上述代码看，configureRpcThreadpool主要做用有：

  1. 打开/dev/hwbinder节点，并将内存映射到当前进程
  2. 经过ioctl(fd, BINDER_SET_MAX_THREADS, &maxThreads)设置binder最大线程数

接着继续分析下registerPassthroughServiceImplementation

//system\libhidl\transport\include\hidl\LegacySupport.h
/** * Registers passthrough service implementation. */
 //Interface为ICameraProvider
 //
template<class Interface>
__attribute__((warn_unused_result))
status_t registerPassthroughServiceImplementation(
        std::string name = "default") {
    //调用的是ICameraProvider::getService("legacy/0",true)
    //是以passthrough方法获取的ICameraProvider子类CameraProvider对象
    sp<Interface> service = Interface::getService(name, true /* getStub */);

    if (service == nullptr) {
        ALOGE("Could not get passthrough implementation for %s/%s.",
            Interface::descriptor, name.c_str());
        return EXIT_FAILURE;
    }
    //若是获取的对象是remote，则打印该异常log
    //ICameraProvider.h isRemote()为false，passthrough方式获取的是ICameraProvider对象，isRemote()为false
    //BpHwCameraProvider.h isRemote()为true
    LOG_FATAL_IF(service->isRemote(), "Implementation of %s/%s is remote!",
            Interface::descriptor, name.c_str());
   //注册服务给hwservicemanager
    status_t status = service->registerAsService(name);
    ...
    return status;
}

1. 下边分析下ICameraProvider::getService(const std::string &serviceName, const bool getStub)的流程

ICameraProvider::getService的实现是ICameraProvider.hal编译生成的，实现以下：

//out\soong\.intermediates\hardware\interfaces\camera\provider\2.4\android.hardware.camera.provider@2.4_genc++\gen\android\hardware\camera\provider\2.4\CameraProviderAll.cpp
::android::sp<ICameraProvider> ICameraProvider::getService(const std::string &serviceName, const bool getStub) {
    using ::android::hardware::defaultServiceManager;
    using ::android::hardware::details::waitForHwService;
    using ::android::hardware::getPassthroughServiceManager;
    using ::android::hardware::Return;
    using ::android::sp;
    using Transport = ::android::hidl::manager::V1_0::IServiceManager::Transport;

    sp<ICameraProvider> iface = nullptr;
    //获取IServiceManager代理对象BpHwServiceManager
    const sp<::android::hidl::manager::V1_0::IServiceManager> sm = defaultServiceManager();
    if (sm == nullptr) {
        ALOGE("getService: defaultServiceManager() is null");
        return nullptr;
    }
    //获取服务的Transport属性
    //属性定义在device\qcom\projectName\manifest.xml
    Return<Transport> transportRet = sm->getTransport(ICameraProvider::descriptor, serviceName);

    if (!transportRet.isOk()) {
        ALOGE("getService: defaultServiceManager()->getTransport returns %s", transportRet.description().c_str());
        return nullptr;
    }
    //ICameraProvider的transport为Transport::HWBINDER，其定义在device\qcom\projectName\manifest.xml，下边会讲解
    //因此vintfHwbinder 为true
    //vintfPassthru为false
    Transport transport = transportRet;
    const bool vintfHwbinder = (transport == Transport::HWBINDER);
    const bool vintfPassthru = (transport == Transport::PASSTHROUGH);

     ...
    //getStub 为false且transport 属性为Transport::HWBINDER或者transport 属性为Transport::EMPTY
    //该条件不知足，没有进入该循环
    //在CameraSercvice获取cameraProvider服务时会进入该循环
    for (int tries = 0; !getStub && (vintfHwbinder || (vintfLegacy && tries == 0)); tries++) {
        if (tries > 1) {
            ALOGI("getService: Will do try %d for %s/%s in 1s...", tries, ICameraProvider::descriptor, serviceName.c_str());
            sleep(1);
        }
        if (vintfHwbinder && tries > 0) {
            waitForHwService(ICameraProvider::descriptor, serviceName);
        }
        Return<sp<::android::hidl::base::V1_0::IBase>> ret = 
                sm->get(ICameraProvider::descriptor, serviceName);
        if (!ret.isOk()) {
            ALOGE("ICameraProvider: defaultServiceManager()->get returns %s", ret.description().c_str());
            break;
        }
        sp<::android::hidl::base::V1_0::IBase> base = ret;
        if (base == nullptr) {
            if (tries > 0) {
                ALOGW("ICameraProvider: found null hwbinder interface");
            }continue;
        }
        Return<sp<ICameraProvider>> castRet = ICameraProvider::castFrom(base, true /* emitError */);
        if (!castRet.isOk()) {
            if (castRet.isDeadObject()) {
                ALOGW("ICameraProvider: found dead hwbinder service");
                continue;
            } else {
                ALOGW("ICameraProvider: cannot call into hwbinder service: %s; No permission? Check for selinux denials.", castRet.description().c_str());
                break;
            }
        }
        iface = castRet;
        if (iface == nullptr) {
            ALOGW("ICameraProvider: received incompatible service; bug in hwservicemanager?");
            break;
        }
        return iface;
    }
    //getStub 为true或者transport 属性为Transport::PASSTHROUGH或者为transport 属性为Transport::EMPTY
    //cameraprovider 启动时getStub为true；vintfPassthru为false；vintfLegacy为false，知足该循环进入条件
    if (getStub || vintfPassthru || vintfLegacy) {
        const sp<::android::hidl::manager::V1_0::IServiceManager> pm = getPassthroughServiceManager();
        if (pm != nullptr) {
           //ICameraProvider::descriptor为android.hardware.camera.provider@2.4::ICameraProvider
           //serviceName为"legacy/0"
            Return<sp<::android::hidl::base::V1_0::IBase>> ret = 
                    pm->get(ICameraProvider::descriptor, serviceName);
            if (ret.isOk()) {
                sp<::android::hidl::base::V1_0::IBase> baseInterface = ret;
                if (baseInterface != nullptr) {
                    //baseInterface转换为ICameraProvider类型
                    iface = ICameraProvider::castFrom(baseInterface);
                    if (!getStub || trebleTestingOverride) {
                        iface = new BsCameraProvider(iface);
                    }
                }
            }
        }
    }
    //返回ICameraProvider对象
    return iface;
}

camerarpovider的transport属性定义以下：

//device\qcom\projectName\manifest.xml
    <!-- fingerprint hal: using remote service instead of Google's default service-->
    <hal format="hidl">
	<name>android.hardware.camera.provider</name>
	<transport>hwbinder</transport>
        <impl level="generic"></impl>
        <version>2.4</version>
        <interface>
            <name>ICameraProvider</name>
            <instance>legacy/0</instance>
        </interface>
    </hal>

接着分析下getPassthroughServiceManager

//system\libhidl\transport\ServiceManagement.cpp
sp<IServiceManager1_0> getPassthroughServiceManager() {
    return getPassthroughServiceManager1_1();
}
sp<IServiceManager1_1> getPassthroughServiceManager1_1() {
    //新建PassthroughServiceManager对象
    static sp<PassthroughServiceManager> manager(new PassthroughServiceManager());
    return manager;
}

经过上述代码看，getPassthroughServiceManager实现的是建立一个新的PassthroughServiceManager对象并返回该对象。

接着分析下PassthroughServiceManager的get方法：

//\system\libhidl\transport\ServiceManagement.cpp
//PassthroughServiceManager::get
    Return<sp<IBase>> get(const hidl_string& fqName,
                          const hidl_string& name) override {
        sp<IBase> ret = nullptr;
        //调用openLibs方法
        openLibs(fqName, [&](void* handle, const std::string &lib, const std::string &sym) {
            IBase* (*generator)(const char* name);
            *(void **)(&generator) = dlsym(handle, sym.c_str());
            if(!generator) {
                const char* error = dlerror();
                LOG(ERROR) << "Passthrough lookup opened " << lib
                           << " but could not find symbol " << sym << ": "
                           << (error == nullptr ? "unknown error" : error);
                dlclose(handle);
                return true;
            }

            ret = (*generator)(name.c_str());

            if (ret == nullptr) {
                dlclose(handle);
                return true; // this module doesn't provide this instance name
            }

            registerReference(fqName, name);
            return false;
        });

        return ret;
    }
先分析下openLibs方法：

​​​​​​​//system\libhidl\transport\ServiceManagement.cpp
//PassthroughServiceManager::openLibs方法
//fqName为android.hardware.camera.provider@2.4::ICameraProvider
    static void openLibs(const std::string& fqName,
            std::function<bool /* continue */(void* /* handle */,
                const std::string& /* lib */, const std::string& /* sym */)> eachLib) {
        //fqName looks like android.hardware.foo@1.0::IFoo
        size_t idx = fqName.find("::");

        if (idx == std::string::npos ||
                idx + strlen("::") + 1 >= fqName.size()) {
            LOG(ERROR) << "Invalid interface name passthrough lookup: " << fqName;
            return;
        }
       //对应cameraprovider packageAndVersion为android.hardware.camera.provider@2.4
        std::string packageAndVersion = fqName.substr(0, idx);
       //对应cameraprovider ifaceName为ICameraProvider
        std::string ifaceName = fqName.substr(idx + strlen("::"));
       //对应cameraprovider prefix为android.hardware.camera.provider@2.4-impl
        const std::string prefix = packageAndVersion + "-impl";
           //对应cameraprovider sym 为HIDL_FETCH_ICameraProvider
        const std::string sym = "HIDL_FETCH_" + ifaceName;

        const int dlMode = RTLD_LAZY;
        void *handle = nullptr;

        dlerror(); // clear
       //查找的几个路径为/odm/lib(64)/hw/;/vendor/lib(64)/hw/;/system/lib(64)/vndk-sp/hw/;system/lib(64)/hw/
        std::vector<std::string> paths = {HAL_LIBRARY_PATH_ODM, HAL_LIBRARY_PATH_VENDOR,
                                          HAL_LIBRARY_PATH_VNDK_SP, HAL_LIBRARY_PATH_SYSTEM};
        .....
        for (const std::string& path : paths) {
        //查找名字为android.hardware.camera.provider@2.4-impl.so的so
            std::vector<std::string> libs = search(path, prefix, ".so");

            for (const std::string &lib : libs) {
                const std::string fullPath = path + lib;
                //若是so不在system/lib(64)/hw/下边，调用android_load_sphal_library打开so获取其句柄值handle
                //android_load_sphal_library这个函数就不分析了。其实现和 dlopen类似，
                if (path != HAL_LIBRARY_PATH_SYSTEM) {
                    handle = android_load_sphal_library(fullPath.c_str(), dlMode);
                } else {
                    handle = dlopen(fullPath.c_str(), dlMode);
                }

                if (handle == nullptr) {
                    const char* error = dlerror();
                    LOG(ERROR) << "Failed to dlopen " << lib << ": "
                               << (error == nullptr ? "unknown error" : error);
                    continue;
                }
                //调用eachLib函数将handle，lib=android.hardware.camera.provider@2.4-impl.so，
                //sym=HIDL_FETCH_ICameraProvider
                //回调给上层调用openLibs
                if (!eachLib(handle, lib, sym)) {
                    return;
                }
            }
        }
    }

接着分析下eachLib，其是一个lamda函数，实现为：

std::function<bool /* continue */(void* /* handle */,const std::string& /* lib */, const std::string& /* sym */)> eachLib =
[&](void* handle, const std::string &lib, const std::string &sym) {
            //定义一个类型为IBase*（*）(const char* )的变量generator
            IBase* (*generator)(const char* name);
            //调用dlsym方法获取HIDL_FETCH_ICameraProvider方法并赋值给generator
            *(void **)(&generator) = dlsym(handle, sym.c_str());
            if(!generator) {
                const char* error = dlerror();
                LOG(ERROR) << "Passthrough lookup opened " << lib
                           << " but could not find symbol " << sym << ": "
                           << (error == nullptr ? "unknown error" : error);
                dlclose(handle);
                return true;
            }
            //调用HIDL_FETCH_ICameraProvider方法
            //ret的类型为 sp<IBase> ret
            ret = (*generator)(name.c_str());

            if (ret == nullptr) {
                dlclose(handle);
                return true; // this module doesn't provide this instance name
            }

            registerReference(fqName, name);
            return false;
        }
接着分析下


HIDL_FETCH_ICameraProvider：
//hardware\interfaces\camera\provider\2.4\default\CameraProvider.cpp
ICameraProvider* HIDL_FETCH_ICameraProvider(const char* name) {
    if (strcmp(name, kLegacyProviderName) != 0) {
        return nullptr;
    }
    //新建一个CameraProvider对象
    CameraProvider* provider = new CameraProvider();
    if (provider == nullptr) {
        ALOGE("%s: cannot allocate camera provider!", __FUNCTION__);
        return nullptr;
    }
    if (provider->isInitFailed()) {
        ALOGE("%s: camera provider init failed!", __FUNCTION__);
        delete provider;
        return nullptr;
    }
    return provider;
}
经过上述分析，HIDL_FETCH_ICameraProvider方法，新建一个CameraProvider对象，而后返回该对象。

经过上述分析，Return<sp<IBase>>PassthroughServiceManager::get(const hidl_string& fqName，const hidl_string& name)方法，是经过dlopen的方式打开cameraprovider定义的so：android.hardware.camera.provider@2.4-impl.so，而后经过dlsym获取其内部的c方法HIDL_FETCH_ICameraProvider，来获取对应的CameraProvider对象。整个该过程，都是在本进程中完成的，即Passthrough（直通）式。

2. 下边分析下ICameraProvider::registerAsService(const std::string &serviceName)的流程
上一步已经经过passthrough的方式获取了ICameraProvider的子类对象CameraProvider
接着分析下其注册服务给hwServiceManager的流程

//out\soong\.intermediates\hardware\interfaces\camera\provider\2.4\android.hardware.camera.provider@2.4_genc++\gen\android\hardware\camera\provider\2.4\CameraProviderAll.cpp
::android::status_t ICameraProvider::registerAsService(const std::string &serviceName) {
    ::android::hardware::details::onRegistration("android.hardware.camera.provider@2.4", "ICameraProvider", serviceName);
   //获取IServiceManager的代理对象BpHwServiceManager
    const ::android::sp<::android::hidl::manager::V1_0::IServiceManager> sm
            = ::android::hardware::defaultServiceManager();
    if (sm == nullptr) {
        return ::android::INVALID_OPERATION;
    }
    //调用add注册服务ICameraProvider
    ::android::hardware::Return<bool> ret = sm->add(serviceName.c_str(), this);
    return ret.isOk() && ret ? ::android::OK : ::android::UNKNOWN_ERROR;
}

接着分析下

BpHwServiceManager::add(const ::android::hardware::hidl_string& name, const ::android::sp<::android::hidl::base::V1_0::IBase>& service)方法

//out\soong\.intermediates\system\libhidl\transport\manager\1.1\android.hidl.manager@1.1_genc++\gen\android\hidl\manager\1.1\ServiceManagerAll.cpp
//name为"legacy/0";service为passthrough方式得到的ICameraProvider对象
::android::hardware::Return<bool> BpHwServiceManager::add(const ::android::hardware::hidl_string& name, const ::android::sp<::android::hidl::base::V1_0::IBase>& service){
    ::android::hardware::Return<bool>  _hidl_out = ::android::hidl::manager::V1_0::BpHwServiceManager::_hidl_add(this, this, name, service);

    return _hidl_out;
}
接着调用了::android::hidl::manager::V1_0::BpHwServiceManager::_hidl_add方法

//out\soong\.intermediates\system\libhidl\transport\manager\1.0\android.hidl.manager@1.0_genc++\gen\android\hidl\manager\1.0\ServiceManagerAll.cpp
::android::hardware::Return<bool> BpHwServiceManager::_hidl_add(::android::hardware::IInterface *_hidl_this, ::android::hardware::details::HidlInstrumentor *_hidl_this_instrumentor, const ::android::hardware::hidl_string& name, const ::android::sp<::android::hidl::base::V1_0::IBase>& service) {
    ....
    ::android::hardware::Parcel _hidl_data;
    ::android::hardware::Parcel _hidl_reply;
    ::android::status_t _hidl_err;
    ::android::hardware::Status _hidl_status;

    bool _hidl_out_success;

    _hidl_err = _hidl_data.writeInterfaceToken(BpHwServiceManager::descriptor);
    if (_hidl_err != ::android::OK) { goto _hidl_error; }

    size_t _hidl_name_parent;

    _hidl_err = _hidl_data.writeBuffer(&name, sizeof(name), &_hidl_name_parent);
    if (_hidl_err != ::android::OK) { goto _hidl_error; }

    _hidl_err = ::android::hardware::writeEmbeddedToParcel(
            name,
            &_hidl_data,
            _hidl_name_parent,
            0 /* parentOffset */);

    if (_hidl_err != ::android::OK) { goto _hidl_error; }

    if (service == nullptr) {
        _hidl_err = _hidl_data.writeStrongBinder(nullptr);
    } else {
    //将ICameraProvider对象转换为BnHwCameraProvider对象，
    //::android::hardware::toBinder的实如今
    ///system/libhidl/transport/include/hidl/HidlBinderSupport.h
    //稍后重点分析下
    ::android::sp<::android::hardware::IBinder> _hidl_binder = ::android::hardware::toBinder<
                ::android::hidl::base::V1_0::IBase>(service);
        if (_hidl_binder.get() != nullptr) {
            _hidl_err = _hidl_data.writeStrongBinder(_hidl_binder);
        } else {
            _hidl_err = ::android::UNKNOWN_ERROR;
        }
    }
    if (_hidl_err != ::android::OK) { goto _hidl_error; }

    ::android::hardware::ProcessState::self()->startThreadPool();
    //给BnHwServiceManager发送消息添加服务
    _hidl_err = ::android::hardware::IInterface::asBinder(_hidl_this)->transact(2 /* add */, _hidl_data, &_hidl_reply);
    if (_hidl_err != ::android::OK) { goto _hidl_error; }

    _hidl_err = ::android::hardware::readFromParcel(&_hidl_status, _hidl_reply);
    if (_hidl_err != ::android::OK) { goto _hidl_error; }

    if (!_hidl_status.isOk()) { return _hidl_status; }

    _hidl_err = _hidl_reply.readBool(&_hidl_out_success);
    if (_hidl_err != ::android::OK) { goto _hidl_error; }

    atrace_end(ATRACE_TAG_HAL);
     ....

    _hidl_status.setFromStatusT(_hidl_err);
    return ::android::hardware::Return<bool>(_hidl_out_success);

_hidl_error:
    _hidl_status.setFromStatusT(_hidl_err);
    return ::android::hardware::Return<bool>(_hidl_status);
}

接下来分析下如何将::android::hidl::base::V1_0::IBase转换为::android::hardware::IBinder

//system\libhidl\transport\include\hidl\HidlBinderSupport.h
//IType为::android::hidl::base::V1_0::IBase
//可是传入的是IBase的子类ICameraProvider对象
template <typename IType>
sp<IBinder> toBinder(sp<IType> iface) {
    IType *ifacePtr = iface.get();
    if (ifacePtr == nullptr) {
        return nullptr;
    }
    //ICameraProvider的isRemote为false
    if (ifacePtr->isRemote()) {
        return ::android::hardware::IInterface::asBinder(
            static_cast<BpInterface<IType>*>(ifacePtr));
    } else {
       //
        std::string myDescriptor = details::getDescriptor(ifacePtr);
        //获取的myDescriptor为android.hardware.camera.provider@2.4::ICameraProvider
        if (myDescriptor.empty()) {
            // interfaceDescriptor fails
            return nullptr;
        }

        // for get + set
        std::unique_lock<std::mutex> _lock = details::gBnMap.lock();

        wp<BHwBinder> wBnObj = details::gBnMap.getLocked(ifacePtr, nullptr);
        sp<IBinder> sBnObj = wBnObj.promote();

        if (sBnObj == nullptr) {
            //获取的func为static_constructor设置的一个lamda函数，
            //为value为[](void *iIntf) -> ::android::sp<::android::hardware::IBinder> {
            // return new BnHwCameraProvider(static_cast<ICameraProvider *>(iIntf));
            //} 的lamda函数
            auto func = details::gBnConstructorMap.get(myDescriptor, nullptr);
            if (!func) {
                return nullptr;
            }
            //调用上一步获取的lamda函数，获取BnHwCameraProvider对象
            sBnObj = sp<IBinder>(func(static_cast<void*>(ifacePtr)));

            if (sBnObj != nullptr) {
                details::gBnMap.setLocked(ifacePtr, static_cast<BHwBinder*>(sBnObj.get()));
            }
        }
        //返回BnHwCameraProvider对象
        return sBnObj;
    }
}

下边介绍下gBnConstructorMap的设置过程

//out\soong\.intermediates\hardware\interfaces\camera\provider\2.4\android.hardware.camera.provider@2.4_genc++\gen\android\hardware\camera\provider\2.4\CameraProviderAll.cpp
__attribute__((constructor))static void static_constructor() {
      //该方法为gBnConstructorMap设置了一个key为android.hardware.camera.provider@2.4::ICameraProvider
      //value为[](void *iIntf) -> ::android::sp<::android::hardware::IBinder> {
      // return new BnHwCameraProvider(static_cast<ICameraProvider *>(iIntf));
      // }
      //的lamda函数
    ::android::hardware::details::gBnConstructorMap.set(ICameraProvider::descriptor,
            [](void *iIntf) -> ::android::sp<::android::hardware::IBinder> {
                return new BnHwCameraProvider(static_cast<ICameraProvider *>(iIntf));
            });
      //该方法为gBsConstructorMap设置了一个key为android.hardware.camera.provider@2.4::ICameraProvider
      //value为[](void *iIntf) -> ::android::sp<::android::hidl::base::V1_0::IBase> {
       // return new BsCameraProvider(static_cast<ICameraProvider *>(iIntf));
       // }
      // 的lamda函数，
    ::android::hardware::details::gBsConstructorMap.set(ICameraProvider::descriptor,
            [](void *iIntf) -> ::android::sp<::android::hidl::base::V1_0::IBase> {
                return new BsCameraProvider(static_cast<ICameraProvider *>(iIntf));
            });
};

调用该lamda函数，会建立一个BnHwCameraProvider，BnHwCameraProvider构造函数实现以下：

//out\soong\.intermediates\hardware\interfaces\camera\provider\2.4\android.hardware.camera.provider@2.4_genc++\gen\android\hardware\camera\provider\2.4\CameraProviderAll.cpp
BnHwCameraProvider::BnHwCameraProvider(const ::android::sp<ICameraProvider> &_hidl_impl)
        : ::android::hidl::base::V1_0::BnHwBase(_hidl_impl, "android.hardware.camera.provider@2.4", "ICameraProvider") { 
            //_hidl_mImpl成员变量是getPassThrough得到的ICameraProvider对象指针
            _hidl_mImpl = _hidl_impl;
            auto prio = ::android::hardware::details::gServicePrioMap.get(_hidl_impl, {SCHED_NORMAL, 0});
            mSchedPolicy = prio.sched_policy;
            mSchedPriority = prio.prio;
}

接着继续分析下BnHwServiceManager的_hidl_add

//out\soong\.intermediates\system\libhidl\transport\manager\1.0\android.hidl.manager@1.0_genc++\gen\android\hidl\manager\1.0\ServiceManagerAll.cpp
::android::status_t BnHwServiceManager::_hidl_add(
        ::android::hidl::base::V1_0::BnHwBase* _hidl_this,
        const ::android::hardware::Parcel &_hidl_data,
        ::android::hardware::Parcel *_hidl_reply,
        TransactCallback _hidl_cb) {
   ....

    ::android::status_t _hidl_err = ::android::OK;
    if (!_hidl_data.enforceInterface(BnHwServiceManager::Pure::descriptor)) {
        _hidl_err = ::android::BAD_TYPE;
        return _hidl_err;
    }

    const ::android::hardware::hidl_string* name;
    ::android::sp<::android::hidl::base::V1_0::IBase> service;

    size_t _hidl_name_parent;

    _hidl_err = _hidl_data.readBuffer(sizeof(*name), &_hidl_name_parent,  reinterpret_cast<const void **>(&name));

    if (_hidl_err != ::android::OK) { return _hidl_err; }

    _hidl_err = ::android::hardware::readEmbeddedFromParcel(
            const_cast<::android::hardware::hidl_string &>(*name),
            _hidl_data,
            _hidl_name_parent,
            0 /* parentOffset */);

    if (_hidl_err != ::android::OK) { return _hidl_err; }

    {
        ::android::sp<::android::hardware::IBinder> _hidl_service_binder;
        _hidl_err = _hidl_data.readNullableStrongBinder(&_hidl_service_binder);
        if (_hidl_err != ::android::OK) { return _hidl_err; }

        service = ::android::hardware::fromBinder<::android::hidl::base::V1_0::IBase,::android::hidl::base::V1_0::BpHwBase,::android::hidl::base::V1_0::BnHwBase>(_hidl_service_binder);
    }

    atrace_begin(ATRACE_TAG_HAL, "HIDL::IServiceManager::add::server");
     ....
    //调用ServiceManager的add方法，_hidl_mImpl变量是BnHwServiceManager构造函数赋值的ServiceManager对象
    bool _hidl_out_success = static_cast<BnHwServiceManager*>(_hidl_this)->_hidl_mImpl->add(*name, service);

    ::android::hardware::writeToParcel(::android::hardware::Status::ok(), _hidl_reply);

    _hidl_err = _hidl_reply->writeBool(_hidl_out_success);
    /* _hidl_err ignored! */

    atrace_end(ATRACE_TAG_HAL);
    ....

    _hidl_cb(*_hidl_reply);
    return _hidl_err;
}
接着分析下ServiceManager的add方法
//system\hwservicemanager\ServiceManager.cpp
Return<bool> ServiceManager::add(const hidl_string& name, const sp<IBase>& service) {
    bool isValidService = false;

    if (service == nullptr) {
        return false;
    }

    // TODO(b/34235311): use HIDL way to determine this
    // also, this assumes that the PID that is registering is the pid that is the service
    pid_t pid = IPCThreadState::self()->getCallingPid();
    auto context = mAcl.getContext(pid);
   //interfaceChain的定义在system\libhidl\transport\base\1.0\IBase.hal
   //cameraProvider 返回的interfaceChain，size=1，
   //interfaceChain[0]= android.hardware.camera.provider@2.4::ICameraProvider
    auto ret = service->interfaceChain([&](const auto &interfaceChain) {
        if (interfaceChain.size() == 0) {
            return;
        }

        // First, verify you're allowed to add() the whole interface hierarchy
        for(size_t i = 0; i < interfaceChain.size(); i++) {
            std::string fqName = interfaceChain[i];

            if (!mAcl.canAdd(fqName, context, pid)) {
                return;
            }
        }

        for(size_t i = 0; i < interfaceChain.size(); i++) {
           //fqName为android.hardware.camera.provider@2.4::ICameraProvider获取PackageInterfaceMap
            std::string fqName = interfaceChain[i];
           //经过fqName获取PackageInterfaceMap
            PackageInterfaceMap &ifaceMap = mServiceMap[fqName];
            //name为legacy/0，经过name获取HidlService
            HidlService *hidlService = ifaceMap.lookup(name);
           //若是hidlService为空，则将该服务插入到mServiceMap中，
           //key值为android.hardware.camera.provider@2.4::ICameraProvider
           //若是hidlService不为空，则替换mServiceMap中的值
            if (hidlService == nullptr) {
                ifaceMap.insertService(
                    std::make_unique<HidlService>(fqName, name, service, pid));
            } else {
                if (hidlService->getService() != nullptr) {
                    auto ret = hidlService->getService()->unlinkToDeath(this);
                    ret.isOk(); // ignore
                }
                hidlService->setService(service, pid);
            }

            ifaceMap.sendPackageRegistrationNotification(fqName, name);
        }

        auto linkRet = service->linkToDeath(this, 0 /*cookie*/);
        linkRet.isOk(); // ignore

        isValidService = true;
    });

    if (!ret.isOk()) {
        LOG(ERROR) << "Failed to retrieve interface chain.";
        return false;
    }

    return isValidService;
}
总结下registerAsService的流程。
  1. 将ICameraProvider::getService(..)得到的ICameraProvider对象转换为BnHwCameraProvider对象
  2. 经过hwbinder，将BnHwCameraProvider注册个hwservicemanager**

至此，分析完成了CameraProvider服务启动的完整流程。

liujun3512159
关注
  • 3
    点赞
  • 踩
  • 12
    收藏
    觉得还不错? 一键收藏
  • 0
    评论
专栏目录
深入理解Camera HAL 硬件抽象层
程序员Android
04-22 1062
和你一起终身学习，这里是程序员Android经典好文推荐，通过阅读本文，您将收获以下知识点:一、概览二、Camera HIDL 接口三 、Camera Provider 主程序四、Camera HAL3 接口相机硬件抽象层一、概览始于谷歌的Treble开源项目，基于接口与实现的分离的设计原则，谷歌加入了Camera Provider这一抽象层，该层作为一个独立进程存在于整个系统中，并且通过HIDL...
CameraProvider启动流程分析
转载和创作优秀的博客
01-28 1171
CameraProvider进程中hidl文件 HIDL文件 服务端 客户端 BinderName ICameraProvider.hidl CameraProvider进程(CameraProvider.cpp) CameraService进程中使用（CameraProviderManager:: ProviderInfo） legacy/0 ICameraDevice.hidl CameraProvder进程中(CameraDevice.cpp)
Camera Provider
最新发布
m0_71008721的博客
05-17 390
由图中可以看出Camera Provider进程由两部分组成，一是运行在系统中的主程序通过提供了标准的HIDL接口保持了与Camera Service的跨进程通讯，二是为了进一步扩展其功能，通过dlopen方式加载了一系列So库，而其中就包括了实现了Camera HAL3接口的So库，而HAL3接口主要定义了主要用于实现图像控制的功能，其实现主要交由平台厂商或者开发者来完成，所以Camera HAL3 So库的实现各式各样，各个手机厂商都有不同，本文重点需要分析的RK 的hal3框架。
Android HAL接口自定义
转载和创作优秀的博客
05-01 1177
HIDL接口定义 创建hidl目录 在aosp中的hardware/interfaces目录下创建自己的hal目录 mkdir -p hardware/interfaces/qmiller/1.0/default 创建hal文件 在我们刚才创建的hardware/interfaces/qmiller/1.0/目录下新建IQmiller.hal文件,传入string name，返回string类型的result。 package android.hardware.qmiller@1.0;
自定义hal 接口实现流程
点滴的岁月
10-31 1442
实现自定义的hal 接口
Camera源码分析（一）--CameraService与CameraProvider的联系
qq_41679626的博客
04-17 3563
有参考： 作者：StoneDemo 原文：https://blog.csdn.net/qq_16775897/article/details/81240600 简书: 作者：JeffMony Android Camera原理之camera provider启动 原文： https://www.jianshu.com/p/5758f14f924e 简书: 作者：JeffMony Android Camera原理之cameraserver与cameraprovider是怎样联系的 原文：https://w
虚拟摄像头之六: 《详解 CameraService 都做了什么》之 CameraService 与 CameraProvider 通讯
weixin_38387929的博客
08-12 1882
上一篇梳理了 CameraProvider 是独立服务、通过 v4l2 框架管理物理摄像头,本篇主要描述的是 CameraService 如何与 CameraProvider 通讯; android 的 CameraService 是 Camera 子系统核心模块,Camera Api1 和 Api2 的接口、是如何与CameraService 通讯呢？笔者将分两篇来介绍。...
Android 12 S HIDL Service创建流程
weixin_41028555的博客
04-28 3607
HIDL 这个机制的目的，主要是为了把框架（framework）与 HAL 进行隔离，使得框架部分可以直接被覆盖、更新，而不需要重新对 HAL 进行编译。HAL 的部分将会放在设备的 /vendor 分区中，并且是由设备供应商（vendors）或 SOC 制造商来构建。这使得框架部分可以通过 OTA 方式更新，同时不需要重新编译 HAL。这种设计被称为Treble机制，从Android 8.0引入。
[Android O] Camera 服务启动流程简析
转载和创作优秀的博客
01-11 941
前言 去年正式进入框架组的时候，啥也不会，瞎jb分析了一通 Android N 上面的 Camera 相关流程。其实基本上都是跟着别人的分析日志看代码，然后按照自己的理解记了些笔记而已。 不过当时感觉受益匪浅，并且后来在项目开发、维护的时候，很多相关的内容都派上了用场。 从正式进入项目到现在大概有 10 个月了吧，其中大概有一半时间在 Android N 上填坑，另一半就是填 Android O 上的坑了（虽然这些坑基本上都是自己人挖的）。现在终于感觉自己对 Android Camera 这块的架构也有
Android Camera(一) Provider启动流程 (androidP)(HIDL)
we1less的博客
11-02 1493
本章开始分析camera框架 主要是自己用来加深理解的 camera provider android.hardware.camera.provider@2.4-service.rc 路径 hardware/interfaces/camera/provider/2.4/default/android.hardware.camera.provider@2.4-service.rc 跟普通服务类似就是以一个rc文件启动的，在之前的文章中我们分析过rc文件是如何启动服务的 android8.1系统启..
HIDL说明
sui1005316018的博客
06-19 1568
目录 1、Android O Treble 计划 1.1、Treble 计划概览 1.2、Android 7.x vs Android O  2、HIDL 基本概念 3、HIDL 的使用例子-- 蓝牙 HCI 服务进程 3.1、定义 & 实现接口 3.2、编译生成的文件 3.3、启动 HIDL service 3.4、Client 端获...
【01 Provider HAL and Device HAL】
Sugar_wolf的博客
03-28 338
【01 Provider HAL and Device HAL】
Android Camera原理之camera provider启动
qq_42538455的博客
06-15 1271
camera provider
高通mm-camera_vendor
h_8410435的博客
06-14 2139
高通 mm-camera_vendor code 分析
AndroidO Treble架构（二）：CameraProvider 及其守护进程
QGov的博客
08-31 6085
AndroidO Treble 架构之 CameraProvider 分析 相关的文件如下： hardware/interfaces/camera/provider/2.4/default/service.cpp hardware/interfaces/camera/provider/2.4/default/android.hardware.camera.provider@2.4-servi...
Android 7.0 Camera架构源码分析1 - CameraService启动
热门推荐
lb377463323的博客
12-13 1万+
本系列教程主要讲解Camera从APP层到HAL层的整个流程，第一篇先讲解CameraService的启动，后面会讲解open、preview、takepicture的流程。
android treble项目&&HIDL学习总结
转载和创作优秀的博客
02-23 1587
概念介绍 Treble项目—HIDL产生背景，独立升级framework需求 Android Ｏ（8.0） 重新设计了 Android 操作系统框架，在一个名为Treble的项目中，以便让制造商能够以更低的成本更轻松、更快速地将设备更新到新版 Android 系统。在这种新架构中，HAL 接口定义语言HIDL指定了 HAL 和其用户之间的接口，让用户能够替换 android framework，而无需重新编译 HAL。 HIDL概念—HAL 接口定义语言，目标framework和HAL解耦 HIDL：
安卓8.0 WIFI差异分析
Zach-Zona的博客
12-16 8544
======================================================================== /packages/apps/Settings/src/com/android/settings/wifi/WifiMasterSwitchPreferenceController.java mWifiEnabler = new WifiEnabler ...
camx 的启动流程
11-10
CamX的启动流程主要包括以下几个步骤： 1. 注册CameraProvider：在启动CamX之前，需要先注册CameraProvider，以便CameraServer能够找到它。这个过程很简单，只需要在代码中注册即可。 2. 实例化CameraProvider：在CameraServer启动时，会通过CameraProvider的实例来管理所有的相机设备。因此，在注册完CameraProvider之后，需要实例化它。 3. 初始化CameraProvider：在实例化CameraProvider之后，需要对其进行初始化。这个过程包括加载配置文件、初始化相机设备等。 4. 启动相机设备：在CameraProvider初始化完成之后，需要启动相机设备。这个过程包括打开相机设备、设置相机参数等。 5. 启动CamX服务：在相机设备启动完成之后，就可以启动CamX服务了。这个过程包括启动CamX线程、监听客户端请求等。 6. 处理客户端请求：在CamX服务启动之后，会一直监听客户端请求。当有客户端请求时，CamX会根据请求类型进行相应的处理，并返回结果给客户端。

“相关推荐”对你有帮助么？

  • 非常没帮助
  • 没帮助
  • 一般
  • 有帮助
  • 非常有帮助
提交
评论
添加红包

请填写红包祝福语或标题

个

红包个数最小为10个

元

红包金额最低5元

当前余额3.43元 前往充值 >
需支付：10.00元
成就一亿技术人!
领取后你会自动成为博主和红包主的粉丝 规则
hope_wisdom
发出的红包
实付元
使用余额支付
点击重新获取
扫码支付
钱包余额 0

抵扣说明：

1.余额是钱包充值的虚拟货币，按照1:1的比例进行支付金额的抵扣。
2.余额无法直接购买下载，可以购买VIP、付费专栏及课程。

余额充值