Linux驱动基础：MSM平台AP/CP通信机制

最新推荐文章于 2025-01-22 22:49:29 发布
转载 最新推荐文章于 2025-01-22 22:49:29 发布 · 1.7k 阅读 · 6 ·
CC 4.0 BY-SA版权
原文链接：https://loongembedded.blog.youkuaiyun.com/article/details/51762918?spm=1001.2101.3001.6650.2&utm_medium=distribute.pc_relevant.none-task-blog-2%7Edefault%7ECTRLIST%7ERate-2-51762918-blog-55099024.pc_relevant_3mothn_strategy_and_data_recovery&depth_1-utm_source=
文章标签：

#java #servlet #jvm

 

概述

MSM平台AP和CP封装到一个芯片，共享内容。所以之前也说过，高通的MSM解决方案中，CP的代码都是由AP放到指定地址的内存中以供CP运行。那上传完代码，CP开始跑之后，AP/CP之间的通信又是怎么弄的呢？ 
其实也是在内存中开辟一段共享内存进行通信的。高通文档中有介绍以下三种。

  • SMD : Shared Memory Driver
  • SMEM : Shared Memory Manager
  • SMSM : Shared State Machine

来看一下上面三种共享内存的具体说明：

SMEM :

  • Shared memory service, provides basic SMEM allocation services
  • Section of physical RAM is located at a predetermined location, sharing between 
    processors
  • Provides low-level interprocessor communication primitives (apps processor to 
    modem processor) that can be called from interrupt context

SMSM:

  • Shared memory state machine
  • Provides low-level synchronization between different processors

SMD :

  • Shared memory driver
  • Provides multiple data channels

smd channel setup过程

1.首先Modem会调用sio_open()等函数接口，根据port id打开一个smd port。smd_sio_open()函数会被调用。然后smdi_alloc_channel_info()函数会在shared memory分配一个port.

2.在AP端，msm_smd_probe()会启动一个wrker thread，叫smd_channel_probe_worker()。这个函数会detect所有已经被modem端分配过的smd channel。通过这一步之后，驱动函数就可以通过smd channel名字打开一个smd channel。

实际在smd_init_dt.c的 msm_smd_probe()函数中添加log输出结果为：

 

  1.  
    <6>[0.538769] [0:swapper/0:1] msm_smd_probe remote_pid=1
     
  2.  
    <6>[0.539232] [0:swapper/0:1] msm_smd_probe remote_pid=4
     
  3.  
    <6>[0.539665] [0:swapper/0:1] msm_smd_probe remote_pid=6
     


  


当然这个结果是根据dtsi文件定义里读出来的内容。
 

 

  1.  
    qcom,smd-modem {
     
  2.  
    compatible = "qcom,smd";
     
  3.  
    qcom,smd-edge = <0>;
     
  4.  
    qcom,smd-irq-offset = <0x0>;
     
  5.  
    qcom,smd-irq-bitmask = <0x1000>;
     
  6.  
    interrupts = <0 25 1>;
     
  7.  
    label = "modem";
     
  8.  
    };
     
  9.  
    ...
     
  10.  
    qcom,smd-wcnss {
     
  11.  
    compatible = "qcom,smd";
     
  12.  
    qcom,smd-edge = <6>;
     
  13.  
    qcom,smd-irq-offset = <0x0>;
     
  14.  
    qcom,smd-irq-bitmask = <0x20000>;
     
  15.  
    interrupts = <0 142 1>;
     
  16.  
    label = "wcnss";
     
  17.  
    };
     
  18.  
    ...
     
  19.  
    qcom,smd-rpm {
     
  20.  
    compatible = "qcom,smd";
     
  21.  
    qcom,smd-edge = <15>;
     
  22.  
    qcom,smd-irq-offset = <0x0>;
     
  23.  
    qcom,smd-irq-bitmask = <0x1>;
     
  24.  
    interrupts = <0 168 1>;
     
  25.  
    label = "rpm";
     
  26.  
    qcom,irq-no-suspend;
     
  27.  
    qcom,not-loadable;
     
  28.  
    };
     


  


上面定义的edge，用来根据edge_to_pids变量来转换成remote pid。edge对应的值是以下枚举类型。
 

 

  1.  
    enum {
     
  2.  
    SMD_APPS_MODEM = 0,
     
  3.  
    SMD_APPS_QDSP,
     
  4.  
    SMD_MODEM_QDSP,
     
  5.  
    SMD_APPS_DSPS,
     
  6.  
    SMD_MODEM_DSPS,
     
  7.  
    SMD_QDSP_DSPS,
     
  8.  
    SMD_APPS_WCNSS,
     
  9.  
    SMD_MODEM_WCNSS,
     
  10.  
    SMD_QDSP_WCNSS,
     
  11.  
    SMD_DSPS_WCNSS,
     
  12.  
    SMD_APPS_Q6FW,
     
  13.  
    SMD_MODEM_Q6FW,
     
  14.  
    SMD_QDSP_Q6FW,
     
  15.  
    SMD_DSPS_Q6FW,
     
  16.  
    SMD_WCNSS_Q6FW,
     
  17.  
    SMD_APPS_RPM,
     
  18.  
    SMD_MODEM_RPM,
     
  19.  
    SMD_QDSP_RPM,
     
  20.  
    SMD_WCNSS_RPM,
     
  21.  
    SMD_TZ_RPM,
     
  22.  
    SMD_NUM_TYPE,
     
  23.  
    };
     


  


然后在smd_channel_probe_worker()->scan_alloc_table函数中添加log。
 

 

  1.  
    static void smd_channel_probe_worker(struct work_struct *work)
     
  2.  
    {
     
  3.  
    struct smd_alloc_elm *shared;
     
  4.  
    struct remote_proc_info *r_info;
     
  5.  
    unsigned tbl_size;
     
  7.  
    r_info = container_of(work, struct remote_proc_info, probe_work);
     
  8.  
    //ID_CH_ALLOC_TBL，SMEM_CHANNEL_ALLOC_TBL_2 到底是什么？？
     
  9.  
    shared = smem_get_entry(ID_CH_ALLOC_TBL, &tbl_size,
     
  10.  
    r_info->remote_pid, 0);
     
  12.  
    if (!shared) {
     
  13.  
    pr_err("%s: allocation table not initialized\n", __func__);
     
  14.  
    return;
     
  15.  
    }
     
  17.  
    mutex_lock(&smd_probe_lock);
     
  19.  
    scan_alloc_table(shared, r_info->ch_allocated, PRI_ALLOC_TBL,
     
  20.  
    tbl_size / sizeof(*shared),
     
  21.  
    r_info);
     
  23.  
    shared = smem_get_entry(SMEM_CHANNEL_ALLOC_TBL_2, &tbl_size,
     
  24.  
    r_info->remote_pid, 0);
     
  25.  
    if (shared)
     
  26.  
    scan_alloc_table(shared,
     
  27.  
    &(r_info->ch_allocated[SMEM_NUM_SMD_STREAM_CHANNELS]),
     
  28.  
    SEC_ALLOC_TBL,
     
  29.  
    tbl_size / sizeof(*shared),
     
  30.  
    r_info);
     
  32.  
    mutex_unlock(&smd_probe_lock);
     
  33.  
    }
     
  35.  
    static void scan_alloc_table(struct smd_alloc_elm *shared,
     
  36.  
    char *smd_ch_allocated,
     
  37.  
    int table_id,
     
  38.  
    unsigned num_entries,
     
  39.  
    struct remote_proc_info *r_info)
     
  40.  
    {
     
  41.  
    if (!smd_alloc_channel(&shared[n], table_id, r_info)) {
     
  42.  
    pr_info("shared[%d].name = %s, r_info->remote_pid = %d table_id=%d\n",n,shared[n].name,r_info->remote_pid,table_id);
     
  43.  
    smd_ch_allocated[n] = 1;
     
  44.  
    }
     
  45.  
    else
     
  46.  
    SMD_INFO(
     
  47.  
    "Probe skipping proc %d, tbl %d, ch %d, not allocated\n",
     
  48.  
    r_info->remote_pid, table_id, n);
     
  49.  
    }
     


  


 

输出的log结果为：
 

 

  1.  
    //以下log里边shared[x]中,x代表port ID，和打印所有的qc_smd_ch_xxx.log里边的ID对应！
     
  2.  
    <6>[0.544016][0:kworker/0:1:34] shared[4].name = rpm_requests, r_info->remote_pid = 6 table_id=1
     
  3.  
    <6>[10.294419][0:kworker/0:1:34] shared[1].name = IPCRTR, r_info->remote_pid = 1 table_id=1
     
  4.  
    <6>[10.295081][0:kworker/0:1:34] shared[2].name = SSM_RTR_MODEM_APPS, r_info->remote_pid = 1 table_id=1
     
  5.  
    <6>[10.848152][0:kworker/0:1:34] shared[3].name = sys_mon, r_info->remote_pid = 1 table_id=1
     
  6.  
    <6>[10.863365][0:kworker/0:1:34] shared[4].name = DIAG_2_CMD, r_info->remote_pid = 1 table_id=1
     
  7.  
    <6>[10.864631][0:kworker/0:1:34] shared[5].name = DIAG_2, r_info->remote_pid = 1 table_id=1
     
  8.  
    <6>[10.866978][0:kworker/0:1:34] shared[6].name = DIAG_CNTL, r_info->remote_pid = 1 table_id=1
     
  9.  
    <6>[10.868057][0:kworker/0:1:34] shared[7].name = DIAG_CMD, r_info->remote_pid = 1 table_id=1
     
  10.  
    <6>[10.869126][0:kworker/0:1:34] shared[8].name = DIAG, r_info->remote_pid = 1 table_id=1
     
  11.  
    <6>[10.874224][0:kworker/0:1:34] shared[9].name = apr_audio_svc, r_info->remote_pid = 1 table_id=1
     
  12.  
    <6>[10.874991][0:kworker/0:1:34] shared[10].name = apr_apps2, r_info->remote_pid = 1 table_id=1
     
  13.  
    <6>[12.453190][0:kworker/0:1:34] shared[1].name = IPCRTR, r_info->remote_pid = 4 table_id=1
     
  14.  
    <6>[12.454124][0:kworker/0:1:34] shared[2].name = sys_mon, r_info->remote_pid = 4 table_id=1
     
  15.  
    <6>[12.455103][0:kworker/0:1:34] shared[3].name = APPS_RIVA_CTRL, r_info->remote_pid = 4 table_id=1
     
  16.  
    <6>[12.456004][0:kworker/0:1:34] shared[4].name = APPS_RIVA_DATA, r_info->remote_pid = 4 table_id=1
     
  17.  
    <6>[12.583796][0:kworker/0:1:34] shared[5].name = WCNSS_CTRL, r_info->remote_pid = 4 table_id=1
     
  18.  
    <6>[12.584751][0:kworker/0:1:34] shared[6].name = WLAN_CTRL, r_info->remote_pid = 4 table_id=1
     
  19.  
    <6>[12.836919][0:kworker/0:1:34] shared[7].name = APPS_RIVA_BT_CMD, r_info->remote_pid = 4 table_id=1
     
  20.  
    <6>[12.837876][0:kworker/0:1:34] shared[8].name = APPS_RIVA_BT_ACL, r_info->remote_pid = 4 table_id=1
     
  21.  
    <6>[12.838729][0:kworker/0:1:34] shared[9].name = APPS_RIVA_ANT_CMD, r_info->remote_pid = 4 table_id=1
     
  22.  
    <6>[12.839399][0:kworker/0:1:34] shared[10].name = APPS_RIVA_ANT_DATA, r_info->remote_pid = 4 table_id=1
     
  23.  
    <6>[12.843247][0:kworker/0:1:34] shared[11].name = APPS_FM, r_info->remote_pid = 4 table_id=1
     


  


 

这里显示的都是在启动的时候扫描smd之后，调用smd_alloc_channel()函数初始化相应的数据结构之后的结果。 
 在smd_alloc_channel()函数中，会根据上面的名字，初始化一个platform device！！之后也是会根据这个名字来注册platform driver。这些platform driver当然可以在/sys/devices/platform/目录下是看得到的。
 

 

  1.  
    //smd相关的platform设备会根据SIM卡或者网络条件有不同。
     
  2.  
    root@gtelwifiue:/sys/devices/platform # ls
     
  3.  
    APPS_FM.6
     
  4.  
    APPS_RIVA_ANT_CMD.6
     
  5.  
    APPS_RIVA_ANT_DATA.6
     
  6.  
    APPS_RIVA_BT_ACL.6
     
  7.  
    APPS_RIVA_BT_CMD.6
     
  8.  
    APPS_RIVA_CTRL.6
     
  9.  
    APPS_RIVA_DATA.6
     
  10.  
    DIAG.0
     
  11.  
    DIAG_2.0
     
  12.  
    DIAG_2_CMD.0
     
  13.  
    DIAG_CMD.0
     
  14.  
    DIAG_CNTL.0
     
  15.  
    IPCRTR.0
     
  16.  
    IPCRTR.6
     
  17.  
    SSM_RTR_MODEM_APPS.0
     
  18.  
    SVC0000000e:00000001.1
     
  19.  
    SVC0000000f:00000001.1
     
  20.  
    SVC0000000f:00000001.2
     
  21.  
    SVC00000010:00000002.1
     
  22.  
    SVC00000016:00000101.1
     
  23.  
    SVC00000017:00000001.1
     
  24.  
    SVC00000018:00000001.1
     
  25.  
    SVC0000001c:00000001.1
     
  26.  
    SVC0000001c:00000101.1
     
  27.  
    SVC00000022:00000001.1
     
  28.  
    SVC0000002b:00000001.1
     
  29.  
    SVC00000034:00000101.1
     
  30.  
    SVC000000e8:00000101.1
     
  31.  
    SVC00000100:00000100.1
     
  32.  
    SVC00000100:00000100.2
     
  33.  
    WCNSS_CTRL.6
     
  34.  
    WLAN_CTRL.6
     
  35.  
    alarmtimer
     
  36.  
    apr_apps2.0
     
  37.  
    apr_audio_svc.0
     
  38.  
    msm_hsusb
     
  39.  
    msm_hsusb_host
     
  40.  
    power
     
  41.  
    reg-dummy
     
  42.  
    regulatory.0
     
  43.  
    rpm_requests.15
     
  44.  
    sec-thermistor
     
  45.  
    secgpio_dvs
     
  46.  
    snd-soc-dummy
     
  47.  
    sys_mon.0
     
  48.  
    sys_mon.6
     


  


 

qc_smd_ch_xxx.log
 

 

  1.  
    Primary allocation table:
     
  2.  
    ID|CHANNEL NAME |T|PROC |STATE |FIFO SZ|RDPTR |WRPTR |FLAGS |DATAPEN
     
  3.  
    -------------------------------------------------------------------------------
     
  4.  
    4|rpm_requests |P|APPS |OPENED |0x00400|0x00188|0x00188|DCCiwRsB|0x00000
     
  5.  
    | | |RPM |OPENED |0x00400|0x000A0|0x000A0|DCCiwrsB|0x00000
     
  6.  
    -------------------------------------------------------------------------------
     
  7.  
    5|rpm_requests |P|MDMSW| Access Restricted
     
  8.  
    | | |RPM | Access Restricted
     
  9.  
    -------------------------------------------------------------------------------
     
  10.  
    6|rpm_requests |P|WCNSS| Access Restricted
     
  11.  
    | | |RPM | Access Restricted
     
  12.  
    -------------------------------------------------------------------------------
     
  13.  
    7|rpm_requests |P|TZ | Access Restricted
     
  14.  
    | | |RPM | Access Restricted
     
  15.  
    -------------------------------------------------------------------------------
     
  18.  
    APPS <-> MDMSW Primary allocation table:
     
  19.  
    ID|CHANNEL NAME |T|PROC |STATE |FIFO SZ|RDPTR |WRPTR |FLAGS |DATAPEN
     
  20.  
    -------------------------------------------------------------------------------
     
  21.  
    0|DS |S|APPS |OPENED |0x02000|0x00000|0x00000|DCCiwrsB|0x00000
     
  22.  
    | | |MDMSW|OPENED |0x02000|0x00000|0x00000|dCciwrsb|0x00000
     
  23.  
    -------------------------------------------------------------------------------
     
  24.  
    1|IPCRTR |P|APPS |OPENED |0x02000|0x00F28|0x00F28|DCCiwrsB|0x00000
     
  25.  
    | | |MDMSW|OPENED |0x02000|0x00DAC|0x00DAC|DCCiwrsB|0x00000
     
  26.  
    -------------------------------------------------------------------------------
     
  27.  
    2|SSM_RTR_MODEM_APPS |P|APPS |CLOSED |0x02000|0x00000|0x00000|dcciwrsb|0x00000
     
  28.  
    | | |MDMSW|OPENING|0x02000|0x00000|0x00000|DCCiwrSb|0x00000
     
  29.  
    -------------------------------------------------------------------------------
     
  30.  
    3|sys_mon |P|APPS |OPENED |0x00400|0x002BE|0x002BE|DCCiwrsB|0x00000
     
  31.  
    | | |MDMSW|OPENED |0x00400|0x00060|0x00060|DCCiwrsB|0x00000
     
  32.  
    -------------------------------------------------------------------------------
     
  33.  
    4|DIAG_2_CMD |P|APPS |OPENED |0x02000|0x00000|0x00000|DCCiwrsb|0x00000
     
  34.  
    | | |MDMSW|OPENED |0x02000|0x00000|0x00000|DCCiwrsb|0x00000
     
  35.  
    -------------------------------------------------------------------------------
     
  36.  
    5|DIAG_2 |P|APPS |OPENED |0x02000|0x00000|0x00000|DCCiwrsb|0x00000
     
  37.  
    | | |MDMSW|OPENED |0x02000|0x00000|0x00000|DCCiwrsb|0x00000
     
  38.  
    -------------------------------------------------------------------------------
     
  39.  
    6|DIAG_CNTL |P|APPS |OPENED |0x02000|0x00083|0x00083|DCCiwrsb|0x00000
     
  40.  
    | | |MDMSW|OPENED |0x02000|0x00471|0x00471|DCCiwrsB|0x00000
     
  41.  
    -------------------------------------------------------------------------------
     
  42.  
    7|DIAG_CMD |P|APPS |OPENED |0x02000|0x00000|0x00000|DCCiwrsb|0x00000
     
  43.  
    | | |MDMSW|OPENED |0x02000|0x00000|0x00000|DCCiwrsb|0x00000
     
  44.  
    -------------------------------------------------------------------------------
     
  45.  
    8|DIAG |P|APPS |OPENED |0x02000|0x00000|0x00000|DCCiwrsb|0x00000
     
  46.  
    | | |MDMSW|OPENED |0x02000|0x00026|0x00026|DCCiwrsB|0x00000
     
  47.  
    -------------------------------------------------------------------------------
     
  48.  
    9|apr_audio_svc |P|APPS |OPENED |0x02000|0x0064E|0x0064E|DCCiwrsB|0x00000
     
  49.  
    | | |MDMSW|OPENED |0x02000|0x01C70|0x01C70|DCCiwrsB|0x00000
     
  50.  
    -------------------------------------------------------------------------------
     
  51.  
    10|apr_apps2 |P|APPS |CLOSED |0x02000|0x00000|0x00000|dcciwrsb|0x00000
     
  52.  
    | | |MDMSW|OPENING|0x02000|0x00000|0x00000|DCCiwrSb|0x00000
     
  53.  
    -------------------------------------------------------------------------------
     
  54.  
    11|DATA1 |P|APPS |CLOSED |0x02000|0x00000|0x00000|dcciwrsb|0x00000
     
  55.  
    | | |MDMSW|OPENING|0x02000|0x00000|0x00000|dCciwrSb|0x00000
     
  56.  
    -------------------------------------------------------------------------------
     
  57.  
    12|DATA2 |P|APPS |CLOSED |0x02000|0x00000|0x00000|dcciwrsb|0x00000
     
  58.  
    | | |MDMSW|OPENING|0x02000|0x00000|0x00000|dCciwrSb|0x00000
     
  59.  
    -------------------------------------------------------------------------------
     
  60.  
    13|DATA3 |P|APPS |CLOSED |0x02000|0x00000|0x00000|dcciwrsb|0x00000
     
  61.  
    | | |MDMSW|OPENING|0x02000|0x00000|0x00000|dCciwrSb|0x00000
     
  62.  
    -------------------------------------------------------------------------------
     
  63.  
    14|DATA4 |P|APPS |CLOSED |0x02000|0x00000|0x00000|dcciwrsb|0x00000
     
  64.  
    | | |MDMSW|OPENING|0x02000|0x00000|0x00000|dCciwrSb|0x00000
     
  65.  
    -------------------------------------------------------------------------------
     
  66.  
    15|DATA11 |S|APPS |CLOSED |0x02000|0x00000|0x00000|dcciwrsb|0x00000
     
  67.  
    | | |MDMSW|OPENING|0x02000|0x00000|0x00000|dCciwrSb|0x00000
     
  68.  
    -------------------------------------------------------------------------------
     
  69.  
    16|DATA40 |P|APPS |CLOSED |0x02000|0x00000|0x00000|dcciwrsb|0x00000
     
  70.  
    | | |MDMSW|OPENING|0x02000|0x00000|0x00000|dcciwrSb|0x00000
     
  71.  
    -------------------------------------------------------------------------------
     
  72.  
    17|DATA5_CNTL |P|APPS |OPENED |0x00400|0x001AA|0x001AA|DCCiwrsB|0x00000
     
  73.  
    | | |MDMSW|OPENED |0x00400|0x00208|0x00208|DCCiwrsB|0x00000
     
  74.  
    -------------------------------------------------------------------------------
     
  75.  
    18|DATA6_CNTL |P|APPS |OPENED |0x00400|0x00338|0x00338|DCCiwrsB|0x00000
     
  76.  
    | | |MDMSW|OPENED |0x00400|0x00363|0x00363|DCCiwrsB|0x00000
     
  77.  
    -------------------------------------------------------------------------------
     
  78.  
    19|DATA7_CNTL |P|APPS |OPENED |0x00400|0x001A2|0x001A2|DCCiwrsB|0x00000
     
  79.  
    | | |MDMSW|OPENED |0x00400|0x001F7|0x001F7|DCCiwrsB|0x00000
     
  80.  
    -------------------------------------------------------------------------------
     
  81.  
    20|DATA8_CNTL |P|APPS |OPENED |0x00400|0x001A2|0x001A2|DCCiwrsB|0x00000
     
  82.  
    | | |MDMSW|OPENED |0x00400|0x001F7|0x001F7|DCCiwrsB|0x00000
     
  83.  
    -------------------------------------------------------------------------------
     
  84.  
    21|DATA9_CNTL |P|APPS |OPENED |0x00400|0x001A2|0x001A2|DCCiwrsB|0x00000
     
  85.  
    | | |MDMSW|OPENED |0x00400|0x001F7|0x001F7|DCCiwrsB|0x00000
     
  86.  
    -------------------------------------------------------------------------------
     
  87.  
    22|DATA12_CNTL |P|APPS |OPENED |0x00400|0x001A2|0x001A2|DCCiwrsB|0x00000
     
  88.  
    | | |MDMSW|OPENED |0x00400|0x001F7|0x001F7|DCCiwrsB|0x00000
     
  89.  
    -------------------------------------------------------------------------------
     
  90.  
    23|DATA13_CNTL |P|APPS |OPENED |0x00400|0x001A2|0x001A2|DCCiwrsB|0x00000
     
  91.  
    | | |MDMSW|OPENED |0x00400|0x001F7|0x001F7|DCCiwrsB|0x00000
     
  92.  
    -------------------------------------------------------------------------------
     
  93.  
    24|DATA14_CNTL |P|APPS |OPENED |0x00400|0x001A2|0x001A2|DCCiwrsB|0x00000
     
  94.  
    | | |MDMSW|OPENED |0x00400|0x001F7|0x001F7|DCCiwrsB|0x00000
     
  95.  
    -------------------------------------------------------------------------------
     
  96.  
    25|DATA15_CNTL |P|APPS |CLOSED |0x00400|0x00000|0x00000|dcciwrsb|0x00000
     
  97.  
    | | |MDMSW|OPENING|0x00400|0x00000|0x00000|DCCiwrSb|0x00000
     
  98.  
    -------------------------------------------------------------------------------
     
  99.  
    26|DATA16_CNTL |P|APPS |CLOSED |0x00400|0x00000|0x00000|dcciwrsb|0x00000
     
  100.  
    | | |MDMSW|OPENING|0x00400|0x00000|0x00000|DCCiwrSb|0x00000
     
  101.  
    -------------------------------------------------------------------------------
     
  102.  
    27|DATA40_CNTL |P|APPS |CLOSED |0x02000|0x00000|0x00000|dcciwrsb|0x00000
     
  103.  
    | | |MDMSW|OPENING|0x02000|0x00000|0x00000|DCCiwrSb|0x00000
     
  104.  
    -------------------------------------------------------------------------------
     
  107.  
    APPS <-> WCNSS Primary allocation table:
     
  108.  
    ID|CHANNEL NAME |T|PROC |STATE |FIFO SZ|RDPTR |WRPTR |FLAGS |DATAPEN
     
  109.  
    -------------------------------------------------------------------------------
     
  110.  
    1|IPCRTR |P|APPS |OPENED |0x02000|0x00168|0x00168|DCCiwrsB|0x00000
     
  111.  
    | | |WCNSS|OPENED |0x02000|0x000D8|0x000D8|DCCiwrsB|0x00000
     
  112.  
    -------------------------------------------------------------------------------
     
  113.  
    2|sys_mon |P|APPS |OPENED |0x00400|0x00267|0x00267|DCCiwRsB|0x00000
     
  114.  
    | | |WCNSS|OPENED |0x00400|0x003D4|0x003D4|DCCiwrsB|0x00000
     
  115.  
    -------------------------------------------------------------------------------
     
  116.  
    3|APPS_RIVA_CTRL |P|APPS |OPENED |0x02000|0x00062|0x00062|DCCiwrsb|0x00000
     
  117.  
    | | |WCNSS|OPENED |0x02000|0x00282|0x00282|DCCiwrsB|0x00000
     
  118.  
    -------------------------------------------------------------------------------
     
  119.  
    4|APPS_RIVA_DATA |P|APPS |OPENED |0x02000|0x00000|0x00000|DCCiwrsb|0x00000
     
  120.  
    | | |WCNSS|OPENED |0x02000|0x00000|0x00000|DCCiwrsb|0x00000
     
  121.  
    -------------------------------------------------------------------------------
     
  122.  
    5|WCNSS_CTRL |P|APPS |OPENED |0x02000|0x01638|0x01638|DCCiwrsB|0x00000
     
  123.  
    | | |WCNSS|OPENED |0x02000|0x00175|0x00175|DCCiwrsB|0x00000
     
  124.  
    -------------------------------------------------------------------------------
     
  125.  
    6|WLAN_CTRL |P|APPS |OPENED |0x02000|0x00277|0x00277|DCCiwrsB|0x00000
     
  126.  
    | | |WCNSS|OPENED |0x02000|0x01115|0x01115|DCCiwrsB|0x00000
     
  127.  
    -------------------------------------------------------------------------------
     
  128.  
    7|APPS_RIVA_BT_CMD |P|APPS |OPENED |0x02000|0x0182C|0x0182C|DCCiwrsB|0x00000
     
  129.  
    | | |WCNSS|OPENED |0x02000|0x01AE5|0x01AE5|DCCiwrsB|0x00000
     
  130.  
    -------------------------------------------------------------------------------
     
  131.  
    8|APPS_RIVA_BT_ACL |P|APPS |OPENED |0x02000|0x01904|0x01904|DCCiwrsB|0x00000
     
  132.  
    | | |WCNSS|OPENED |0x02000|0x015E8|0x015E8|DCCiwrsB|0x00000
     
  133.  
    -------------------------------------------------------------------------------
     
  134.  
    9|APPS_RIVA_ANT_CMD |P|APPS |CLOSED |0x00400|0x00000|0x00000|dcciwrsb|0x00000
     
  135.  
    | | |WCNSS|OPENING|0x00400|0x00000|0x00000|DCCiwrSb|0x00000
     
  136.  
    -------------------------------------------------------------------------------
     
  137.  
    10|APPS_RIVA_ANT_DATA |P|APPS |CLOSED |0x00800|0x00000|0x00000|dcciwrsb|0x00000
     
  138.  
    | | |WCNSS|OPENING|0x00800|0x00000|0x00000|DCCiwrSb|0x00000
     
  139.  
    -------------------------------------------------------------------------------
     
  140.  
    11|APPS_FM |P|APPS |CLOSED |0x02000|0x00000|0x00000|dcciwrsb|0x00000
     
  141.  
    | | |WCNSS|OPENING|0x02000|0x00000|0x00000|DCCiwrSb|0x00000
     
  142.  
    -------------------------------------------------------------------------------
     


  • 1
  • 2
  • 3


  


 

每个port名字和对应的生成的节点之间的关系，可以再msm8916.dtsi文件中找得到。 
 比如在msm_smd_pkt.c文件中，parse_smdpkt_devicetree()函数中可以看到在读qcom,smdpkt-dev-name的信息，然后后面会根据这个名字调用device_create()函数！！虽然msm_smd_tty.c对应的”qcom,smdtty”中没有用”qcom,smdpkt-dev-name”定义设备名字，但一般在alias{}那里都定义了一个别名，好像都是根据这个别名来定的设备的名字！！
 

 

  1.  
    aliases {
     
  2.  
    sdhc1 = &sdhc_1; /* SDC1 eMMC slot */
     
  3.  
    sdhc2 = &sdhc_2; /* SDC2 SD card slot */
     
  5.  
    /* smdtty devices */
     
  6.  
    smd0 = &smdtty_ds;
     
  7.  
    smd1 = &smdtty_apps_fm;
     
  8.  
    smd2 = &smdtty_apps_riva_bt_acl;
     
  9.  
    smd3 = &smdtty_apps_riva_bt_cmd;
     
  10.  
    smd4 = &smdtty_mbalbridge;
     
  11.  
    smd5 = &smdtty_apps_riva_ant_cmd;
     
  12.  
    smd6 = &smdtty_apps_riva_ant_data;
     
  13.  
    smd7 = &smdtty_data1;
     
  14.  
    smd8 = &smdtty_data4;
     
  15.  
    smd11 = &smdtty_data11;
     
  16.  
    smd21 = &smdtty_data21;
     
  17.  
    smd36 = &smdtty_loopback;
     
  19.  
    //spi0 = &spi_0; /* SPI0 controller device */
     
  20.  
    i2c0 = &i2c_0; /* I2C0 controller device */
     
  21.  
    i2c1 = &i2c_1; /* I2C1 controller device */
     
  22.  
    i2c5 = &i2c_5; /* I2C5 controller device */
     
  23.  
    i2c6 = &i2c_6; /* I2C6 NFC qup6 device */
     
  24.  
    i2c4 = &i2c_4; /* I2C4 controller device */
     
  25.  
    };
     
  27.  
    qcom,smdtty {
     
  28.  
    compatible = "qcom,smdtty";
     
  30.  
    smdtty_ds: qcom,smdtty-ds {
     
  31.  
    qcom,smdtty-remote = "modem";
     
  32.  
    qcom,smdtty-port-name = "DS";
     
  33.  
    };
     
  35.  
    smdtty_apps_fm: qcom,smdtty-apps-fm {
     
  36.  
    qcom,smdtty-remote = "wcnss";
     
  37.  
    qcom,smdtty-port-name = "APPS_FM";
     
  38.  
    };
     
  40.  
    smdtty_apps_riva_bt_acl: smdtty-apps-riva-bt-acl {
     
  41.  
    qcom,smdtty-remote = "wcnss";
     
  42.  
    qcom,smdtty-port-name = "APPS_RIVA_BT_ACL";
     
  43.  
    };
     
  45.  
    smdtty_apps_riva_bt_cmd: qcom,smdtty-apps-riva-bt-cmd {
     
  46.  
    qcom,smdtty-remote = "wcnss";
     
  47.  
    qcom,smdtty-port-name = "APPS_RIVA_BT_CMD";
     
  48.  
    };
     
  50.  
    smdtty_mbalbridge: qcom,smdtty-mbalbridge {
     
  51.  
    qcom,smdtty-remote = "modem";
     
  52.  
    qcom,smdtty-port-name = "MBALBRIDGE";
     
  53.  
    };
     
  55.  
    smdtty_apps_riva_ant_cmd: smdtty-apps-riva-ant-cmd {
     
  56.  
    qcom,smdtty-remote = "wcnss";
     
  57.  
    qcom,smdtty-port-name = "APPS_RIVA_ANT_CMD";
     
  58.  
    };
     
  60.  
    smdtty_apps_riva_ant_data: smdtty-apps-riva-ant-data {
     
  61.  
    qcom,smdtty-remote = "wcnss";
     
  62.  
    qcom,smdtty-port-name = "APPS_RIVA_ANT_DATA";
     
  63.  
    };
     
  65.  
    smdtty_data1: qcom,smdtty-data1 {
     
  66.  
    qcom,smdtty-remote = "modem";
     
  67.  
    qcom,smdtty-port-name = "DATA1";
     
  68.  
    };
     
  70.  
    smdtty_data4: qcom,smdtty-data4 {
     
  71.  
    qcom,smdtty-remote = "modem";
     
  72.  
    qcom,smdtty-port-name = "DATA4";
     
  73.  
    };
     
  75.  
    smdtty_data11: qcom,smdtty-data11 {
     
  76.  
    qcom,smdtty-remote = "modem";
     
  77.  
    qcom,smdtty-port-name = "DATA11";
     
  78.  
    };
     
  80.  
    smdtty_data21: qcom,smdtty-data21 {
     
  81.  
    qcom,smdtty-remote = "modem";
     
  82.  
    qcom,smdtty-port-name = "DATA21";
     
  83.  
    };
     
  85.  
    smdtty_loopback: smdtty-loopback {
     
  86.  
    qcom,smdtty-remote = "modem";
     
  87.  
    qcom,smdtty-port-name = "LOOPBACK";
     
  88.  
    qcom,smdtty-dev-name = "LOOPBACK_TTY";
     
  89.  
    };
     
  90.  
    };
     
  92.  
    //tty和pkt不一样，分别对应msm_smd_tty.c和msm_smd_pkt.c文件！！
     
  93.  
    qcom,smdpkt {
     
  94.  
    compatible = "qcom,smdpkt";
     
  96.  
    qcom,smdpkt-data5-cntl {
     
  97.  
    qcom,smdpkt-remote = "modem";
     
  98.  
    qcom,smdpkt-port-name = "DATA5_CNTL";
     
  99.  
    qcom,smdpkt-dev-name = "smdcntl0";
     
  100.  
    };
     
  102.  
    qcom,smdpkt-data6-cntl {
     
  103.  
    qcom,smdpkt-remote = "modem";
     
  104.  
    qcom,smdpkt-port-name = "DATA6_CNTL";
     
  105.  
    qcom,smdpkt-dev-name = "smdcntl1";
     
  106.  
    };
     
  108.  
    qcom,smdpkt-data7-cntl {
     
  109.  
    qcom,smdpkt-remote = "modem";
     
  110.  
    qcom,smdpkt-port-name = "DATA7_CNTL";
     
  111.  
    qcom,smdpkt-dev-name = "smdcntl2";
     
  112.  
    };
     
  114.  
    qcom,smdpkt-data8-cntl {
     
  115.  
    qcom,smdpkt-remote = "modem";
     
  116.  
    qcom,smdpkt-port-name = "DATA8_CNTL";
     
  117.  
    qcom,smdpkt-dev-name = "smdcntl3";
     
  118.  
    };
     
  120.  
    qcom,smdpkt-data9-cntl {
     
  121.  
    qcom,smdpkt-remote = "modem";
     
  122.  
    qcom,smdpkt-port-name = "DATA9_CNTL";
     
  123.  
    qcom,smdpkt-dev-name = "smdcntl4";
     
  124.  
    };
     
  126.  
    qcom,smdpkt-data12-cntl {
     
  127.  
    qcom,smdpkt-remote = "modem";
     
  128.  
    qcom,smdpkt-port-name = "DATA12_CNTL";
     
  129.  
    qcom,smdpkt-dev-name = "smdcntl5";
     
  130.  
    };
     
  132.  
    qcom,smdpkt-data13-cntl {
     
  133.  
    qcom,smdpkt-remote = "modem";
     
  134.  
    qcom,smdpkt-port-name = "DATA13_CNTL";
     
  135.  
    qcom,smdpkt-dev-name = "smdcntl6";
     
  136.  
    };
     
  138.  
    qcom,smdpkt-data14-cntl {
     
  139.  
    qcom,smdpkt-remote = "modem";
     
  140.  
    qcom,smdpkt-port-name = "DATA14_CNTL";
     
  141.  
    qcom,smdpkt-dev-name = "smdcntl7";
     
  142.  
    };
     
  144.  
    qcom,smdpkt-data15-cntl {
     
  145.  
    qcom,smdpkt-remote = "modem";
     
  146.  
    qcom,smdpkt-port-name = "DATA15_CNTL";
     
  147.  
    qcom,smdpkt-dev-name = "smdcntl9";
     
  148.  
    };
     
  150.  
    qcom,smdpkt-data16-cntl {
     
  151.  
    qcom,smdpkt-remote = "modem";
     
  152.  
    qcom,smdpkt-port-name = "DATA16_CNTL";
     
  153.  
    qcom,smdpkt-dev-name = "smdcntl10";
     
  154.  
    };
     
  156.  
    qcom,smdpkt-data17-cntl {
     
  157.  
    qcom,smdpkt-remote = "modem";
     
  158.  
    qcom,smdpkt-port-name = "DATA17_CNTL";
     
  159.  
    qcom,smdpkt-dev-name = "smdcntl11";
     
  160.  
    };
     
  162.  
    qcom,smdpkt-data22 {
     
  163.  
    qcom,smdpkt-remote = "modem";
     
  164.  
    qcom,smdpkt-port-name = "DATA22";
     
  165.  
    qcom,smdpkt-dev-name = "smd22";
     
  166.  
    };
     
  168.  
    qcom,smdpkt-data23-cntl {
     
  169.  
    qcom,smdpkt-remote = "modem";
     
  170.  
    qcom,smdpkt-port-name = "DATA23_CNTL";
     
  171.  
    qcom,smdpkt-dev-name = "smdcnt_rev0";
     
  172.  
    };
     
  174.  
    qcom,smdpkt-data24-cntl {
     
  175.  
    qcom,smdpkt-remote = "modem";
     
  176.  
    qcom,smdpkt-port-name = "DATA24_CNTL";
     
  177.  
    qcom,smdpkt-dev-name = "smdcnt_rev1";
     
  178.  
    };
     
  180.  
    qcom,smdpkt-data25-cntl {
     
  181.  
    qcom,smdpkt-remote = "modem";
     
  182.  
    qcom,smdpkt-port-name = "DATA25_CNTL";
     
  183.  
    qcom,smdpkt-dev-name = "smdcnt_rev2";
     
  184.  
    };
     
  186.  
    qcom,smdpkt-data26-cntl {
     
  187.  
    qcom,smdpkt-remote = "modem";
     
  188.  
    qcom,smdpkt-port-name = "DATA26_CNTL";
     
  189.  
    qcom,smdpkt-dev-name = "smdcnt_rev3";
     
  190.  
    };
     
  192.  
    qcom,smdpkt-data27-cntl {
     
  193.  
    qcom,smdpkt-remote = "modem";
     
  194.  
    qcom,smdpkt-port-name = "DATA27_CNTL";
     
  195.  
    qcom,smdpkt-dev-name = "smdcnt_rev4";
     
  196.  
    };
     
  198.  
    qcom,smdpkt-data28-cntl {
     
  199.  
    qcom,smdpkt-remote = "modem";
     
  200.  
    qcom,smdpkt-port-name = "DATA28_CNTL";
     
  201.  
    qcom,smdpkt-dev-name = "smdcnt_rev5";
     
  202.  
    };
     
  204.  
    qcom,smdpkt-data29-cntl {
     
  205.  
    qcom,smdpkt-remote = "modem";
     
  206.  
    qcom,smdpkt-port-name = "DATA29_CNTL";
     
  207.  
    qcom,smdpkt-dev-name = "smdcnt_rev6";
     
  208.  
    };
     
  210.  
    qcom,smdpkt-data30-cntl {
     
  211.  
    qcom,smdpkt-remote = "modem";
     
  212.  
    qcom,smdpkt-port-name = "DATA30_CNTL";
     
  213.  
    qcom,smdpkt-dev-name = "smdcnt_rev7";
     
  214.  
    };
     
  216.  
    qcom,smdpkt-data31-cntl {
     
  217.  
    qcom,smdpkt-remote = "modem";
     
  218.  
    qcom,smdpkt-port-name = "DATA31_CNTL";
     
  219.  
    qcom,smdpkt-dev-name = "smdcnt_rev8";
     
  220.  
    };
     
  222.  
    qcom,smdpkt-data40-cntl {
     
  223.  
    qcom,smdpkt-remote = "modem";
     
  224.  
    qcom,smdpkt-port-name = "DATA40_CNTL";
     
  225.  
    qcom,smdpkt-dev-name = "smdcntl8";
     
  226.  
    };
     
  228.  
    qcom,smdpkt-apr-apps2 {
     
  229.  
    qcom,smdpkt-remote = "modem";
     
  230.  
    qcom,smdpkt-port-name = "apr_apps2";
     
  231.  
    qcom,smdpkt-dev-name = "apr_apps2";
     
  232.  
    };
     
  234.  
    qcom,smdpkt-loopback {
     
  235.  
    qcom,smdpkt-remote = "modem";
     
  236.  
    qcom,smdpkt-port-name = "LOOPBACK";
     
  237.  
    qcom,smdpkt-dev-name = "smd_pkt_loopback";
     
  238.  
    };
     
  239.  
    }
     


  


至此，就知道在哪里会初始化smd channel，然后AP检测到smd channel之后打开相应的smd channel等内容了。相应的节点创建也可以知道了，但这些节点不管smd channel有没有打开都会创建！！ 
 在Ril代码中，可以看到有打开/dev/smd0等节点。 
 这些节点的ops函数组其实都差不多，msm_smd_pkt.c中是smd_pkt_fops，msm_smd_tty中是smd_tty_ops。 
 都是在调用到之后，才根据文件名等，再找出来是哪个smd channel，然后调用smd_named_open_on_edge函数打开smd channel。读写等操作的话，还要看当初smd_alloc_channel()的时候的相应的channel是packet传输还是stream传输！！这个估计都不是AP这边决定的，但可以在smd_alloc_channel()函数中打log查看每个smd channel的类型。
 

SMD_DBG()这种函数用来输出smd等log信息。看这些内容可以在/d/ipc_logging下看的到的，如果是SMD_INFO和SMD_DBG内容就是在/d/ipc_logging/smd目录下。这个是因为~~看下面代码注释
 

 

  1.  
    //msm_smd_debug_mask这个默认没有打开debug信息，需要调试更多可以加一个MSM_SMD_DEBUG。
     
  2.  
    #define SMD_DBG(x...) do { \
     
  3.  
    if (msm_smd_debug_mask & MSM_SMD_DEBUG) \
     
  4.  
    IPC_LOG_SMD(KERN_DEBUG, x); \
     
  5.  
    } while (0)
     
  6.  
    #define SMD_INFO(x...) do { \
     
  7.  
    if (msm_smd_debug_mask & MSM_SMD_INFO) \
     
  8.  
    IPC_LOG_SMD(KERN_INFO, x); \
     
  9.  
    } while (0)
     
  11.  
    //如果smd_log_ctx已经像下面这样定义，那就是到/d/ipc_logging目录下找相应名字的文件夹下看
     
  12.  
    //或者如果不想的话，就可以把smd_log_ctx的定义去掉，直接打印到内核里边。当然内核的debug level那块自己需要改一下！！
     
  13.  
    smd_log_ctx = ipc_log_context_create(NUM_LOG_PAGES, "smd", 0);
     
  14.  
    #define IPC_LOG_SMD(level, x...) do { \
     
  15.  
    if (smd_log_ctx) \
     
  16.  
    ipc_log_string(smd_log_ctx, x); \
     
  17.  
    else \
     
  18.  
    printk(level x); \
     
  19.  
    } while (0)
     


 

以下是qc_smdpkt_xxx.log：
 

 

  1.  
    [ 11247.679255802] <SMD_PKT>: ch_notify: DATA event in smd_pkt_dev id:0
     
  2.  
    [ 11247.679286896] <SMD_PKT>: check_and_wakeup_reader: wake_up smd_pkt_dev id:0
     
  3.  
    [ 11247.679292469] <SMD_PKT>: check_and_wakeup_writer: 1000 bytes write space in smd_pkt_dev id:0
     
  4.  
    [ 11247.679332781] <SMD_PKT>: smd_pkt_poll sets POLLIN for smd_pkt_dev id: 0
     
  5.  
    [ 11247.679372521] <SMD_PKT>: Begin smd_pkt_read on smd_pkt_dev id:0 buffer_size 5086
     
  6.  
    [ 11247.679430594] <SMD_PKT>: smd_pkt_read unlocked smd_pkt_dev id:0 wakeup_source
     
  7.  
    [ 11247.679436479] <SMD_PKT>: Finished smd_pkt_read on smd_pkt_dev id:0 20 bytes
     
  8.  
    [ 11247.679462677] <SMD_PKT>: check_and_wakeup_reader: No packet in smd_pkt_dev id:0
     
  9.  
    [ 11253.959471134] <SMD_PKT>: Begin smd_pkt_write on smd_pkt_dev id:0 data_size 13
     
  10.  
    [ 11253.959521967] <SMD_PKT>: Finished smd_pkt_write on smd_pkt_dev id:0 13 bytes
     
  11.  
    [ 11253.959942853] <SMD_PKT>: ch_notify: DATA event in smd_pkt_dev id:0
     
  12.  
    [ 11253.959981186] <SMD_PKT>: check_and_wakeup_reader: wake_up smd_pkt_dev id:0
     
  13.  
    [ 11253.959982748] <SMD_PKT>: smd_pkt_poll sets POLLIN for smd_pkt_dev id: 0
     
  14.  
    [ 11253.959985248] <SMD_PKT>: check_and_wakeup_writer: 1000 bytes write space in smd_pkt_dev id:0
     
  15.  
    [ 11253.960014207] <SMD_PKT>: Begin smd_pkt_read on smd_pkt_dev id:0 buffer_size 5086
     
  16.  
    [ 11253.960050561] <SMD_PKT>: smd_pkt_read unlocked smd_pkt_dev id:0 wakeup_source
     
  17.  
    [ 11253.960054780] <SMD_PKT>: Finished smd_pkt_read on smd_pkt_dev id:0 20 bytes
     
  18.  
    [ 11253.960072123] <SMD_PKT>: check_and_wakeup_reader: No packet in smd_pkt_dev id:0
     
  19.  
    [ 11260.707648550] <SMD_PKT>: Begin smd_pkt_write on smd_pkt_dev id:0 data_size 13
     
  20.  
    [ 11260.707704800] <SMD_PKT>: Finished smd_pkt_write on smd_pkt_dev id:0 13 bytes
     
  21.  
    [ 11260.708084957] <SMD_PKT>: ch_notify: DATA event in smd_pkt_dev id:0
     
  22.  
    [ 11260.708118811] <SMD_PKT>: check_and_wakeup_reader: wake_up smd_pkt_dev id:0
     
  23.  
    [ 11260.708123290] <SMD_PKT>: check_and_wakeup_writer: 1000 bytes write space in smd_pkt_dev id:0
     
  24.  
    [ 11260.708154540] <SMD_PKT>: packet_arrival_worker locking smd_pkt_dev id:0 wakeup source
     
  25.  
    [ 11260.708218654] <SMD_PKT>: smd_pkt_poll sets POLLIN for smd_pkt_dev id: 0
     
  26.  
    [ 11260.708571415] <SMD_PKT>: Begin smd_pkt_read on smd_pkt_dev id:0 buffer_size 5086
     
  27.  
    [ 11260.708609384] <SMD_PKT>: smd_pkt_read unlocked smd_pkt_dev id:0 wakeup_source
     
  28.  
    [ 11260.708613863] <SMD_PKT>: Finished smd_pkt_read on smd_pkt_dev id:0 20 bytes
     
  29.  
    [ 11260.708631832] <SMD_PKT>: check_and_wakeup_reader: No packet in smd_pkt_dev id:0
     
  30.  
    [ 11264.686568250] <SMD_PKT>: Begin smd_pkt_write on smd_pkt_dev id:0 data_size 13
     
  31.  
    [ 11264.686618146] <SMD_PKT>: Finished smd_pkt_write on smd_pkt_dev id:0 13 bytes
     
  32.  
    [ 11264.686985281] <SMD_PKT>: ch_notify: DATA event in smd_pkt_dev id:0
     
  33.  
    [ 11264.687013979] <SMD_PKT>: check_and_wakeup_reader: wake_up smd_pkt_dev id:0
     
  34.  
    [ 11264.687018406] <SMD_PKT>: check_and_wakeup_writer: 1000 bytes write space in smd_pkt_dev id:0
     
  35.  
    [ 11264.687091062] <SMD_PKT>: smd_pkt_poll sets POLLIN for smd_pkt_dev id: 0
     
  36.  
    [ 11264.687141010] <SMD_PKT>: packet_arrival_worker locking smd_pkt_dev id:0 wakeup source
     
  37.  
    [ 11264.687145906] <SMD_PKT>: Begin smd_pkt_read on smd_pkt_dev id:0 buffer_size 5086
     
  38.  
    [ 11264.687185073] <SMD_PKT>: smd_pkt_read unlocked smd_pkt_dev id:0 wakeup_source
     
  39.  
    [ 11264.687189917] <SMD_PKT>: Finished smd_pkt_read on smd_pkt_dev id:0 20 bytes
     
  40.  
    [ 11264.687207937] <SMD_PKT>: check_and_wakeup_reader: No packet in smd_pkt_dev id:0
     
  41.  
    [ 11271.507262281] <SMD_PKT>: Begin smd_pkt_write on smd_pkt_dev id:0 data_size 13
     
  42.  
    [ 11271.507305719] <SMD_PKT>: Finished smd_pkt_write on smd_pkt_dev id:0 13 bytes
     
  43.  
    [ 11271.507728167] <SMD_PKT>: ch_notify: DATA event in smd_pkt_dev id:0
     
  44.  
    [ 11271.507759625] <SMD_PKT>: check_and_wakeup_reader: wake_up smd_pkt_dev id:0
     
  45.  
    [ 11271.507763583] <SMD_PKT>: check_and_wakeup_writer: 1000 bytes write space in smd_pkt_dev id:0
     
  46.  
    [ 11271.507796604] <SMD_PKT>: smd_pkt_poll sets POLLIN for smd_pkt_dev id: 0
     
  47.  
    [ 11271.507822854] <SMD_PKT>: Begin smd_pkt_read on smd_pkt_dev id:0 buffer_size 5086
     
  48.  
    [ 11271.507862333] <SMD_PKT>: smd_pkt_read unlocked smd_pkt_dev id:0 wakeup_source
     
  49.  
    [ 11271.507866500] <SMD_PKT>: Finished smd_pkt_read on smd_pkt_dev id:0 20 bytes
     
  50.  
    [ 11271.507884364] <SMD_PKT>: check_and_wakeup_reader: No packet in smd_pkt_dev id:0
     
  51.  
    [ 11274.734097551] <SMD_PKT>: Begin smd_pkt_write on smd_pkt_dev id:0 data_size 13
     
  52.  
    [ 11274.734160676] <SMD_PKT>: Finished smd_pkt_write on smd_pkt_dev id:0 13 bytes
     
  53.  
    [ 11274.734588697] <SMD_PKT>: ch_notify: DATA event in smd_pkt_dev id:0
     
  54.  
    [ 11274.734628333] <SMD_PKT>: check_and_wakeup_reader: wake_up smd_pkt_dev id:0
     
  55.  
    [ 11274.734633645] <SMD_PKT>: check_and_wakeup_writer: 1000 bytes write space in smd_pkt_dev id:0
     
  56.  
    [ 11274.735154999] <SMD_PKT>: packet_arrival_worker locking smd_pkt_dev id:0 wakeup source
     
  57.  
    [ 11274.735238385] <SMD_PKT>: smd_pkt_poll sets POLLIN for smd_pkt_dev id: 0
     
  58.  
    [ 11274.735276614] <SMD_PKT>: Begin smd_pkt_read on smd_pkt_dev id:0 buffer_size 5086
     
  59.  
    [ 11274.735333906] <SMD_PKT>: smd_pkt_read unlocked smd_pkt_dev id:0 wakeup_source
     
  60.  
    [ 11274.735339374] <SMD_PKT>: Finished smd_pkt_read on smd_pkt_dev id:0 20 bytes
     
  61.  
    [ 11274.735361145] <SMD_PKT>: check_and_wakeup_reader: No packet in smd_pkt_dev id:0
     
  62.  
    [ 11281.493969135] <SMD_PKT>: Begin smd_pkt_write on smd_pkt_dev id:0 data_size 13
     
  63.  
    [ 11281.494015593] <SMD_PKT>: Finished smd_pkt_write on smd_pkt_dev id:0 13 bytes
     
  64.  
    [ 11281.496142103] <SMD_PKT>: ch_notify: DATA event in smd_pkt_dev id:0
     
  65.  
    [ 11281.496202520] <SMD_PKT>: check_and_wakeup_reader: wake_up smd_pkt_dev id:0
     
  66.  
    [ 11281.496207780] <SMD_PKT>: check_and_wakeup_writer: 1000 bytes write space in smd_pkt_dev id:0
     
  67.  
    [ 11281.496255801] <SMD_PKT>: packet_arrival_worker locking smd_pkt_dev id:0 wakeup source
     
  68.  
    [ 11281.496423249] <SMD_PKT>: smd_pkt_poll sets POLLIN for smd_pkt_dev id: 0
     
  69.  
    [ 11281.496776582] <SMD_PKT>: Begin smd_pkt_read on smd_pkt_dev id:0 buffer_size 5086
     
  70.  
    [ 11281.496824707] <SMD_PKT>: smd_pkt_read unlocked smd_pkt_dev id:0 wakeup_source
     
  71.  
    [ 11281.496828822] <SMD_PKT>: Finished smd_pkt_read on smd_pkt_dev id:0 20 bytes
     
  72.  
    [ 11281.496848614] <SMD_PKT>: check_and_wakeup_reader: No packet in smd_pkt_dev id:0
     
  73.  
    [ 11284.784395968] <SMD_PKT>: Begin smd_pkt_write on smd_pkt_dev id:0 data_size 13
     
  74.  
    [ 11284.784449301] <SMD_PKT>: Finished smd_pkt_write on smd_pkt_dev id:0 13 bytes
     
  75.  
    [ 11284.786411332] <SMD_PKT>: ch_notify: DATA event in smd_pkt_dev id:0
     
  76.  
    [ 11284.786464301] <SMD_PKT>: check_and_wakeup_reader: wake_up smd_pkt_dev id:0
     
  77.  
    [ 11284.786469197] <SMD_PKT>: check_and_wakeup_writer: 1000 bytes write space in smd_pkt_dev id:0
     
  78.  
    [ 11284.786477790] <SMD_PKT>: smd_pkt_poll sets POLLIN for smd_pkt_dev id: 0
     
  79.  
    [ 11284.786504093] <SMD_PKT>: packet_arrival_worker locking smd_pkt_dev id:0 wakeup source
     
  80.  
    [ 11284.786811645] <SMD_PKT>: Begin smd_pkt_read on smd_pkt_dev id:0 buffer_size 5086
     
  81.  
    [ 11284.786848363] <SMD_PKT>: smd_pkt_read unlocked smd_pkt_dev id:0 wakeup_source
     
  82.  
    [ 11284.786852582] <SMD_PKT>: Finished smd_pkt_read on smd_pkt_dev id:0 20 bytes
     
  83.  
    [ 11284.786870290] <SMD_PKT>: check_and_wakeup_reader: No packet in smd_pkt_dev id:0
     
  84.  
    [ 11288.184812488] <SMD_PKT>: Begin smd_pkt_write on smd_pkt_dev id:0 data_size 13
     
  85.  
    [ 11288.184869311] <SMD_PKT>: Finished smd_pkt_write on smd_pkt_dev id:0 13 bytes
     
  86.  
    [ 11288.187012645] <SMD_PKT>: ch_notify: DATA event in smd_pkt_dev id:0
     
  87.  
    [ 11288.187054572] <SMD_PKT>: check_and_wakeup_reader: wake_up smd_pkt_dev id:0
     
  88.  
    [ 11288.187060145] <SMD_PKT>: check_and_wakeup_writer: 1000 bytes write space in smd_pkt_dev id:0
     
  89.  
    [ 11288.187062592] <SMD_PKT>: smd_pkt_poll sets POLLIN for smd_pkt_dev id: 0
     
  90.  
    [ 11288.187099884] <SMD_PKT>: Begin smd_pkt_read on smd_pkt_dev id:0 buffer_size 5086
     
  91.  
    [ 11288.187139363] <SMD_PKT>: smd_pkt_read unlocked smd_pkt_dev id:0 wakeup_source
     
  92.  
    [ 11288.187143530] <SMD_PKT>: Finished smd_pkt_read on smd_pkt_dev id:0 20 bytes
     
  93.  
    [ 11288.187161499] <SMD_PKT>: check_and_wakeup_reader: No packet in smd_pkt_dev id:0
     
  94.  
    [ 11294.361732247] <SMD_PKT>: Begin smd_pkt_write on smd_pkt_dev id:0 data_size 13
     
  95.  
    [ 11294.361781205] <SMD_PKT>: Finished smd_pkt_write on smd_pkt_dev id:0 13 bytes
     
  96.  
    [ 11294.362070320] <SMD_PKT>: ch_notify: DATA event in smd_pkt_dev id:0
     
  97.  
    [ 11294.362108132] <SMD_PKT>: check_and_wakeup_reader: wake_up smd_pkt_dev id:0
     
  98.  
    [ 11294.362108288] <SMD_PKT>: smd_pkt_poll sets POLLIN for smd_pkt_dev id: 0
     
  99.  
    [ 11294.362112403] <SMD_PKT>: check_and_wakeup_writer: 1000 bytes write space in smd_pkt_dev id:0
     
  100.  
    [ 11294.362459851] <SMD_PKT>: Begin smd_pkt_read on smd_pkt_dev id:0 buffer_size 5086
     
  101.  
    [ 11294.362544070] <SMD_PKT>: smd_pkt_read unlocked smd_pkt_dev id:0 wakeup_source
     
  102.  
    [ 11294.362548393] <SMD_PKT>: Finished smd_pkt_read on smd_pkt_dev id:0 20 bytes
     
  103.  
    [ 11294.362567299] <SMD_PKT>: check_and_wakeup_reader: No packet in smd_pkt_dev id:0
     


  


 

后续,,
 

smd,smem,smsm等共享内存所占据的内存范围，大小？？ 
 /system/bin/smdexe 这个代码在哪里，都干嘛的？init.rc里边这样定义了一个service，但没有找到代码，后续需要说明。
 

 

  1.  
    service SMD-daemon /system/bin/smdexe
     
  2.  
    class main
     
  3.  
    user root
     
  4.  
    group system radio inet net_raw
     


  


这个service注册还在oemclientreceiver.cpp文件中添加了下面的一段内容。
 

 

  1.  
    ProcessInfo allowedProcess[] = {
     
  2.  
    ...
     
  3.  
    { AID_SYSTEM, -1, "/system/bin/smdexe" },
     
  4.  
    ...
     
  5.  
    };
     


  


debug需要的一些log抓取
 

Some diag related issues seen when doing factory/RF tests are hard to debug and related to multiple technical areas, like diag/smd/usb/qmsl based tools. 
 we always need comprehensive logs from all sides to begin our analysis and finally find root cause.
 

Here is a list of what logs are expected to be provided to Qcom to begin analysis.
 

QMSL log, Port trace log, USB analyzer log, diag debugfs status dump, ipc logging for diag smd channels, and ramdump with matchable elfs.
 

How the log collected: 
 1. Power on device 
 2. QPST recognized DIAG port 
 3. Echo pr_debug for diagfwd.c/ diagchar_core.c 
 4. Collect ipc_logging for smd channels 
 5. Enable Port trace log 
 6. Start USB analyzer log collection 
 7. Begin the test - -when doing test, qmsl log is collected 
 8. After see failure, stop Port trace log, stop USB analyzer log collection. 
 9. Dump diag debugfs status 
 10. Echo c to sysrq-trigger to trigger a panic and collect ramdump.
 

Where step 3-4 is done by script named “test.bat” 
 If no usb analyzer, ignore step 6. 
 9-10 is done by script named “diag_panic.bat”
 

test.bat
 

adb wait-for-devices 
 adb shell “echo 1 >/sys/module/msm_poweroff/parameters/download_mode” 
 adb shell “echo 1 > /proc/sys/kernel/sysrq” 
 adb shell “echo ‘file diagfwd.c +p’ > /sys/kernel/debug/dynamic_debug/control” 
 adb shell “echo ‘file diagchar_core.c +p’ > /sys/kernel/debug/dynamic_debug/control” 
 adb shell cat /d/ipc_logging/smd/log_cont
 

diag_panic.bat
 

adb shell cat /sys/kernel/debug/diag/work_pending; 
 adb shell cat /sys/kernel/debug/diag/status; 
 adb shell cat /sys/kernel/debug/diag/table; 
 adb shell cat /sys/kernel/debug/diag/mempool; 
 adb shell dmesg >dmesg.txt 
 adb shell “echo c > /proc/sysrq-trigger”
 

Appendix:
 

how to capture port trace log:
 

  1. Bring up “QPST Configuration” and Highlight the port your phone is connected to
  2. Do a Shift+right click on the highlighted item Select “Port Trace” 
     If you do not see ‘Port Trace’ in the drop-down menu, you may not have pressed ‘Shift’ while right-clicking
  3. Set the value to either Turned Off, Debugging or Debugging & Port Traffic (see below for details) Close “QPST Configuration” 
     The port trace log will be saved in following location
  4. Look for QPST Icon on right bottom of the PC, right click & then click on Open the Data Directory . You should see PortTrace_COMx.dbg (where x is the port number).


it is better you can enable the port trace before doing test. and disable it immediately after issue reproduced. 
 Too much logs is not preferred and it is hard for us to do filtering and analysis.

                

        

    


  



    



                



	

		

			

				
					
高通开发系列 - 音频驱动中的APR通道不能打开问题

				
			

			

				

					fulinux的博客
				

				

					05-25
					
					1474
					
				

			

		

		

			
				
高通开发系列 - 音频驱动中的APR通道不能打开问题

			
		

	



                

            
              



	

		

			

				
					
通信行业常用电器术语缩略语（abbr/acro）   -----全面，接近专业词典了

				
			

			

				

					weixin_42082222的博客
				

				

					02-27
					
					4950
					
				

			

		

		

			
				
通信行业常用电器术语缩略语（abbr/acro）
原创qianxuedegushi 最后发布于2019-06-04 14:23:15 阅读数 159 收藏
展开
LEC: linear echo canceller
RVE: receive voice enhancement
PVC：Per Vocoder Calibration 基于语音编解码器的校准
FENS：Far-End Noise...

			
		

	



              


  
              

                


	

		

			

				
					
Qualcomm AP与Modem之间通信机制

				
			

			

				

					Hugo的博客
				

				

					11-11
					
					7013
					
				

			

		

		

			
				
1.https://blog.youkuaiyun.com/whshiyun/article/details/79447959

2.https://blog.youkuaiyun.com/lenk2010/article/details/8720181

3.https://blog.youkuaiyun.com/LoongEmbedded/article/details/51762918

4.https://kerne...

			
		

	





	

		

			

				
					
Android——IPC机制（一）IPC概念以及Binder机制

				
			

			

				

					AkaiC的博客
				

				

					09-20
					
					2734
					
				

			

		

		

			
				
由于IPC机制牵扯的东西比较多，所以这里将分为一个系列进行总结 
主要介绍内如如下：
IPC简介
Android中的多进程模式 
开启多进程模式
多进程模式的运行机制
IPC基础概念介绍 
Serializable接口
Parcelable接口
Binder
Android中的IPC方式 
使用Bundle
使用文件共享
使用Messenger
使用AIDL
使用ContentProvider
使用

			
		

	



		

			
		



	

		

			

				
					
车载软件架构 --- CP和AP作为中央计算平台的软件架构双核心

				
			

			

				

					Soly_kun的博客
				

				

					01-22
					
					1121
					
				

			

		

		

			
				
车载软件架构 ---  CP和AP作为中央计算平台的软件架构双核心

			
		

	





	

		

			

				
					
android 调用smem接口demo

				
			

			

				

					weixin_32104133的博客
				

				

					11-17
					
					699
					
				

			

		

		

			
				
smem 可以干什么？ 通过smem我们可以将sbl中的数据直接传给lk或者kernel，可以不通过cmdline直接将lk中的数据丢给kernel，可以将lk中的数据丢给modem，同样也可以将modem中的一些数据丢给kernel。
sbl中调用smem接口
使用smem 首先需要在h文件中添加对应的factory_smem_type，路径如下所示：BOOT.BF.3.3.2/boot_images/core/boot/secboot3/hw/msm8952/sbl1/sbl1_hw.h
typedef

			
		

	





	

		

			

				
					
使用EDL模式抢救变砖设备：结合QCN恢复魅族20 Pro通信功能的5步急救法

				
			

			

				

					
				

			

		

		

			
				
本文系统探讨了高通平台EDL模式的技术原理及其在手机“变砖”急救中的关键作用，深入分析了EDL模式的底层通信机制，包括Sahara与Firehose协议交互流程及9008端口的触发条件。文章详细梳理了硬件短接、ADB命令和...

			
		

	





	

		

			

				
					
深入剖析大众MIB平台架构：解密866C小标主机软硬件耦合的8大底层逻辑（仅限技术精英）

				
			

			

				

					
				

			

		

		

			
				
![深入剖析大众MIB平台架构：解密866C小标主机软硬件耦合的8大底层逻辑（仅限技术精英）]...在软件层面，探讨了AUTOSAR CP/AP混合部署、QNX与Android虚拟化共存、中间件解耦设计等系统耦合问题。进一

			
		

	





	

		

			

				
					
Qualcomm平台android开发总结

				
			

			

				

					
				

				

					05-04
					
					3109
					
				

			

		

		

			
				
1、高通平台android开发总结
1.1 搭建高通平台环境开发环境
在高通开发板上烧录文件系统
建立高通平台开发环境
高通平台，android和 modem 编译流程分析
高通平台 7620 启动流程分析
qcril 流程分析，设置sim卡锁
python scons 语法学习
Python 语言之 scons 工具流程分析：
 
1.2 搭建高通平台环境开发环境
高通an

			
		

	





	

		

			

				
					
QCN备份失败？7种常见问题排查清单，从驱动异常到权限拒绝全覆盖

				
			

			

				

					
				

			

		

		

			
				
本文系统阐述了QCN备份的底层机制，涵盖其数据结构、驱动交互、权限控制与安全策略，深入分析高通平台在Android/Linux系统下的备份流程及其脆弱点。针对七类典型故障，提出基于日志分析、工具诊断与环境隔离的排查...

			
		

	





	

		

			

				
					
LINUX 安装MegaRAID Storage Manager  (MSM)安装使用教程

				
			

			

				

					08-14
				

			

		

		

			
				
LINUX 安装MegaRAID Storage Manager  (MSM)安装使用教程
linux raid操作

			
		

	





	

		

			

				
					
ipc logging

				
			

			

				

					Fybon的专栏
				

				

					02-14
					
					3741
					
				

			

		

		

			
				
ipc log

			
		

	





	

		

			

				
					
Linux.IPC总结代码测试

				
			

			

				

					qq_35661325的博客
				

				

					03-04
					
					811
					
				

			

		

		

			
				
IPC：
一般情况下，系统中运行着大量的进程，而每个进程之间并不是相互独立的，有些进程之间经常需要互相传递消息。
但是每个进程在系统中都有自己的地址空间，操作系统通过页表和实际物理内存所关联，不允许其他进程随意进入。
因此，就必须有一种机制既能保证进程之间的通信，又能保证系统的安全，即进程间通信机制——I P C （Inter_Process Communication）。
在linux下的多个进程间的通信机制叫做IPC(Inter-Process Communication)，
它是多个进程之间相互沟通的

			
		

	





	

		

			

				
					
MSM平台RPM

				
			

			

				

					hhcs
				

				

					06-08
					
					1549
					
				

			

		

		

			
				
转载https://blog.youkuaiyun.com/loongembedded/article/details/51024610

oftware Component Block Diagram

RPM（Resource Power Manager）是高通MSM平台另外加的一块芯片，虽然与AP芯片打包在一起，但其是一个独立的ARM Core。之所以加这个东西，就是要控制整个电源相关的shared resources，比如ldo，clock。负责与SMP,MPM交互进入睡眠或者唤醒整个系统。
以下是高通文档中.

			
		

	





	

		

			

				
					
Linux IPC总结（全）

					
热门推荐

				
			

			

				

					大象大象啥模样。。。
				

				

					08-02
					
					1万+
					
				

			

		

		

			
				
IPC进程间通信(Inter-Process Communication)就是指多个进程之间相互通信，交换信息的方法。Linux IPC基本上都是从Unix平台上继承而来的。主要包括最初的Unix IPC，System V IPC以及基于Socket的IPC。另外，Linux也支

			
		

	





	

		

			

				
					
Android高通平台处理器间通讯驱动

				
			

			

				

					业余飘向linux深谷
				

				

					12-21
					
					1584
					
				

			

		

		

			
				
高通平台AP与CP直接通信由Share Memory负责，这是一块两端可以同时操作的内存区域。由于高通平台Modem占主导作用，在Application Processor启动初始化时，从Share Memory区读取已经由Modem predeclared的一些数据。
Share memory根据功能，分为静态+动态部分，每个部分又分为数个小区，每个区的大小不一，与本区实现的功能相关。Mode

			
		

	





	

		

			

				
					
关于内核打印信息的查看

				
			

			

				

					LEAD_SOLO的专栏
				

				

					04-13
					
					2233
					
				

			

		

		

			
				
第一个ipc_logging
cat sys/kernel/debug/ipc_logging/xxxx/xxx
第二个


此外,打印中还经常看到pr_debug函数，可以动态的打印调试信息（http://blog.youkuaiyun.com/weiqifa0/article/details/44038907）

如要打开该函数，只需在内核中配置CONFIG_DYNAMIC_DEBUG,并且

			
		

	





	

		

			

				
					
安卓IPC机制

				
			

			

				

					weixin_50961942的博客
				

				

					10-24
					
					2281
					
				

			

		

		

			
				
IPC是Inter-Process Communication的缩写，含义是进程间通信，用于两个进程之间进行数据交互的过程，任何操作系统都有IPC机制，但不同的操作系统有着不同的通信方式，Android系统是一种基于Linux内核的移动操作系统，Linux的跨进程通信主要通过管道、共享内存、内存映射等实现的，但Android有自己的进程间通信机制，最具代表性的就是Binder。线程：CPU调度的最小单元，是一种有限的资源。

			
		

	





	

		

			

				
					
Android：IPC(进程间通信)机制

				
			

			

				

					Tai_Monster的博客
				

				

					05-22
					
					1558
					
				

			

		

		

			
				
本篇文章里我们介绍了如何实现IPC，主要有使用AIDL，Bundle传输，使用文件共享和使用ContentProvider四种方法。名称优点缺点适用场景Bundle简单易用只能传输Bundle支持的数据类型四大组件间的进程间通信文件共享简单易用不适合高并发场景，并且无法做到进程间的即时通信无并发访问情形，交换简单的数据实时性不高的场景Messenger功能一般，支持一对多串行通信，支持实时通信。

			
		

	





	

		

			

				
					
error: kernel_platform/msm-kernel/Android.bp:1:1: module "unifdef" already defined       

					
最新发布

				
			

			

				

					05-27
				

			

		

		

			
				
<think>好的，我现在需要解决用户在Android.bp中遇到的模块'unifdef'重复定义的错误。用户提到这是关于msm-kernel的，所以可能涉及到内核构建过程中的模块定义问题。首先，我得回忆一下Android构建系统，特别是Android.bp文件的结构和常见错误。根据用户提供的错误信息，“module unifdefalready defined”，这通常意味着在同一个Android.bp文件或者多个被包含的Android.bp文件中，存在两个或多个同名的模块定义。Android.bp使用Blueprint语言，每个模块必须有唯一的名称。重复的名称会导致构建失败。接下来，我需要考虑可能的原因。首先，用户可能在同一个文件中不小心定义了两次'unifdef'模块。或者，不同的Android.bp文件被包含到构建中，导致重复。例如，内核源码可能包含多个子目录，每个子目录有自己的Android.bp，如果其中两个都定义了'unifdef'，就会冲突。然后，解决方案方面，首先应该检查所有相关的Android.bp文件，找到重复定义的位置。用户需要搜索整个源码树，特别是kernel目录下的Android.bp文件，查找'unifdef'模块。如果发现重复，可以删除其中一个，或者重命名其中一个模块，确保名称唯一。

另外，可能涉及到模块的依赖或包含问题。比如，某些第三方模块或补丁可能引入了额外的Android.bp文件，导致重复。这时候需要检查最近修改或添加的文件，确认是否有冲突。

还有一个可能性是，unifdef本身是系统预定义的模块，用户可能无意中重新定义它。这时候需要查阅文档，确认是否允许自定义该模块，或者是否需要使用不同的名称。

此外，用户提到msm-kernel，这可能涉及到高通的内核配置。可能需要检查device/qcom/msmnile_gvmq相关的配置，看看是否有重复的模块定义被引入。例如，引用的内容中提到COMMON_LUNCH_CHOICES和加载的.mk文件，这些配置可能会影响模块的包含情况，需要检查是否在配置过程中引入了多个相同的模块。另外，构建系统的缓存问题也可能导致错误。有时候清理out目录或重新生成构建文件可以解决问题，但用户的问题明确是重复定义，所以更可能是源码中的问题，而不是缓存。最后，需要建议用户具体的步骤：使用grep或find命令搜索所有Android.bp文件中的'unifdef'，检查重复位置，修改或删除重复定义，确保模块名称唯一。同时，检查相关的include路径或配置，避免重复包含。</think>在Android内核构建中，遇到`Android.bp: module "unifdef" already defined`错误通常是由于模块重复定义引起。以下是分步解决方案：

### 1. 定位重复模块
使用命令搜索所有Android.bp文件：
```bash
find . -name "Android.bp" | xargs grep -n 'name: *"unifdef"'
```
这会显示所有定义`unifdef`模块的位置及行号，典型结果可能如下：
```
./kernel/Android.bp:23:    name: "unifdef",
./vendor/xxx/Android.bp:45:    name: "unifdef",
```

### 2. 分析重复原因
常见重复场景：
- **内核树与第三方模块冲突**：若`kernel/`和`vendor/xxx/`目录同时包含该模块定义
- **多版本头文件处理冲突**：`unifdef`工具常用于条件编译，可能被不同头文件处理模块重复引用[^3]
- **构建系统包含路径重叠**：如`COMMON_LUNCH_CHOICES`配置包含重复模块路径[^2]

### 3. 修改方案
#### 方案一：删除冗余定义
```diff
# 在次要定义文件中修改
-    name: "unifdef",
+    name: "unifdef_custom",
```

#### 方案二：添加exclude路径
在顶级Android.bp中配置：
```python
bootstrap_go_package {
    name: "soong-build",
    deps: [
        "kernel/...",
    ],
    exclude_dirs: ["vendor/xxx/module"],  // 排除冲突路径
}
```

#### 方案三：条件编译控制
```python
cc_binary {
    name: "unifdef",
    srcs: ["tools/unifdef.c"],
    target: {
        android: { enabled: true },
        linux_glibc: { enabled: false },  // 禁用非必要平台编译
    },
}
```

### 4. 验证修改
清理构建缓存后重新编译：
```bash
make -C kernel O=../out/target/product/pid/obj/KERNEL_OBJ/ clean
make -C kernel O=../out/target/product/pid/obj/KERNEL_OBJ/ ARCH=arm CROSS_COMPILE=arm-eabi- 
```

### 5. 深度关联分析
该错误可能反映以下问题：
- 内核配置碎片化：多项目共用配置时容易产生模块定义冲突[^2]
- Soong构建系统模块可见性控制不足：需检查`visibility: ["//kernel"]`属性设置
- 预编译工具链污染：确认`libtinfo.so.5`等依赖库版本一致性[^4]

			
		

	



              




          




        



    





    



      

      

        
      

      





	

		评论	
	

  

	
    

      

      

      

        
        

          
          

            

              成就一亿技术人!
            

            

              拼手气红包6.0元
            

          

        

        

          

            还能输入1000个字符
          

          

             
          

          

            

              红包
              添加红包
            

            

              表情包
              插入表情
              

                

              

            

            

              表情包
              代码片
              

                
              

            

            

              
              
              
              
              
              
              
            

          

        

      

    

		

			

			

			

					 条评论被折叠 查看
			

			

				
			

		

	

	




  

    

      添加红包
      
    

    

      

        
        

          
          
        

        
请填写红包祝福语或标题

      

      

        
        

          
          个
        

        
红包个数最小为10个

      

      

        
        

          
          元
        

        
红包金额最低5元

      

      

        
        

          当前余额3.43元
          前往充值 >
        

      

      

        

          需支付：10.00元
        

        
        
      

    

  





  

    
    
  

  

    
    
  








  

    

      

        

          

            
            
成就一亿技术人!

          

          

        

        

          

          

            领取后你会自动成为博主和红包主的粉丝
            规则
          

        

      

      

        

          

            
              
            
            

              
hope_wisdom
 发出的红包
            

          

        

        

          

          

          

        

      

    

    

  



      
      

      
实付元

      
使用余额支付

      

        

          

            
            点击重新获取
          

        

        
扫码支付

      

      

        
          
            
          
          
        
      

      

        
        钱包余额
          0
          

            
            

              

                
抵扣说明：

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

              

            

          

      

      余额充值