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

最新推荐文章于 2022-06-20 09:12:43 发布
最新推荐文章于 2022-06-20 09:12:43 发布
阅读量2k 收藏 9
点赞数 1
分类专栏： Linux驱动基础
版权声明：本文为博主原创文章，遵循 CC 4.0 BY-SA 版权协议，转载请附上原文出处链接和本声明。
本文链接：https://blog.csdn.net/hongzg1982/article/details/56516480
版权

概述

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输出结果为：

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

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

        qcom,smd-modem {
            compatible = "qcom,smd";
            qcom,smd-edge = <0>;
            qcom,smd-irq-offset = <0x0>;
            qcom,smd-irq-bitmask = <0x1000>;
            interrupts = <0 25 1>;
            label = "modem";
        };
        ...
        qcom,smd-wcnss {
            compatible = "qcom,smd";
            qcom,smd-edge = <6>;
            qcom,smd-irq-offset = <0x0>;
            qcom,smd-irq-bitmask = <0x20000>;
            interrupts = <0 142 1>;
            label = "wcnss";
        };
        ...
        qcom,smd-rpm {
            compatible = "qcom,smd";
            qcom,smd-edge = <15>;
            qcom,smd-irq-offset = <0x0>;
            qcom,smd-irq-bitmask = <0x1>;
            interrupts = <0 168 1>;
            label = "rpm";
            qcom,irq-no-suspend;
            qcom,not-loadable;
        };

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

enum {
    SMD_APPS_MODEM = 0,
    SMD_APPS_QDSP,
    SMD_MODEM_QDSP,
    SMD_APPS_DSPS,
    SMD_MODEM_DSPS,
    SMD_QDSP_DSPS,
    SMD_APPS_WCNSS,
    SMD_MODEM_WCNSS,
    SMD_QDSP_WCNSS,
    SMD_DSPS_WCNSS,
    SMD_APPS_Q6FW,
    SMD_MODEM_Q6FW,
    SMD_QDSP_Q6FW,
    SMD_DSPS_Q6FW,
    SMD_WCNSS_Q6FW,
    SMD_APPS_RPM,
    SMD_MODEM_RPM,
    SMD_QDSP_RPM,
    SMD_WCNSS_RPM,
    SMD_TZ_RPM,
    SMD_NUM_TYPE,
};

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

static void smd_channel_probe_worker(struct work_struct *work)
{
    struct smd_alloc_elm *shared;
    struct remote_proc_info *r_info;
    unsigned tbl_size;

    r_info = container_of(work, struct remote_proc_info, probe_work);
    //ID_CH_ALLOC_TBL，SMEM_CHANNEL_ALLOC_TBL_2 到底是什么？？
    shared = smem_get_entry(ID_CH_ALLOC_TBL, &tbl_size,
                            r_info->remote_pid, 0);

    if (!shared) {
        pr_err("%s: allocation table not initialized\n", __func__);
        return;
    }

    mutex_lock(&smd_probe_lock);

    scan_alloc_table(shared, r_info->ch_allocated, PRI_ALLOC_TBL,
                        tbl_size / sizeof(*shared),
                        r_info);

    shared = smem_get_entry(SMEM_CHANNEL_ALLOC_TBL_2, &tbl_size,
                            r_info->remote_pid, 0);
    if (shared)
        scan_alloc_table(shared,
            &(r_info->ch_allocated[SMEM_NUM_SMD_STREAM_CHANNELS]),
            SEC_ALLOC_TBL,
            tbl_size / sizeof(*shared),
            r_info);

    mutex_unlock(&smd_probe_lock);
}

static void scan_alloc_table(struct smd_alloc_elm *shared,
                char *smd_ch_allocated,
                int table_id,
                unsigned num_entries,
                struct remote_proc_info *r_info)
{
        if (!smd_alloc_channel(&shared[n], table_id, r_info)) {
            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);
            smd_ch_allocated[n] = 1;
        }
        else
            SMD_INFO(
                "Probe skipping proc %d, tbl %d, ch %d, not allocated\n",
                r_info->remote_pid, table_id, n);
}

输出的log结果为：

//以下log里边shared[x]中,x代表port ID，和打印所有的qc_smd_ch_xxx.log里边的ID对应！
<6>[0.544016][0:kworker/0:1:34] shared[4].name =  rpm_requests, r_info->remote_pid = 6 table_id=1
<6>[10.294419][0:kworker/0:1:34] shared[1].name =  IPCRTR, r_info->remote_pid = 1 table_id=1
<6>[10.295081][0:kworker/0:1:34] shared[2].name =  SSM_RTR_MODEM_APPS, r_info->remote_pid = 1 table_id=1
<6>[10.848152][0:kworker/0:1:34] shared[3].name =  sys_mon, r_info->remote_pid = 1 table_id=1
<6>[10.863365][0:kworker/0:1:34] shared[4].name =  DIAG_2_CMD, r_info->remote_pid = 1 table_id=1
<6>[10.864631][0:kworker/0:1:34] shared[5].name =  DIAG_2, r_info->remote_pid = 1 table_id=1
<6>[10.866978][0:kworker/0:1:34] shared[6].name =  DIAG_CNTL, r_info->remote_pid = 1 table_id=1
<6>[10.868057][0:kworker/0:1:34] shared[7].name =  DIAG_CMD, r_info->remote_pid = 1 table_id=1
<6>[10.869126][0:kworker/0:1:34] shared[8].name =  DIAG, r_info->remote_pid = 1 table_id=1
<6>[10.874224][0:kworker/0:1:34] shared[9].name =  apr_audio_svc, r_info->remote_pid = 1 table_id=1
<6>[10.874991][0:kworker/0:1:34] shared[10].name =  apr_apps2, r_info->remote_pid = 1 table_id=1
<6>[12.453190][0:kworker/0:1:34] shared[1].name =  IPCRTR, r_info->remote_pid = 4 table_id=1
<6>[12.454124][0:kworker/0:1:34] shared[2].name =  sys_mon, r_info->remote_pid = 4 table_id=1
<6>[12.455103][0:kworker/0:1:34] shared[3].name =  APPS_RIVA_CTRL, r_info->remote_pid = 4 table_id=1
<6>[12.456004][0:kworker/0:1:34] shared[4].name =  APPS_RIVA_DATA, r_info->remote_pid = 4 table_id=1
<6>[12.583796][0:kworker/0:1:34] shared[5].name =  WCNSS_CTRL, r_info->remote_pid = 4 table_id=1
<6>[12.584751][0:kworker/0:1:34] shared[6].name =  WLAN_CTRL, r_info->remote_pid = 4 table_id=1
<6>[12.836919][0:kworker/0:1:34] shared[7].name =  APPS_RIVA_BT_CMD, r_info->remote_pid = 4 table_id=1
<6>[12.837876][0:kworker/0:1:34] shared[8].name =  APPS_RIVA_BT_ACL, r_info->remote_pid = 4 table_id=1
<6>[12.838729][0:kworker/0:1:34] shared[9].name =  APPS_RIVA_ANT_CMD, r_info->remote_pid = 4 table_id=1
<6>[12.839399][0:kworker/0:1:34] shared[10].name =  APPS_RIVA_ANT_DATA, r_info->remote_pid = 4 table_id=1
<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/目录下是看得到的。

//smd相关的platform设备会根据SIM卡或者网络条件有不同。
root@gtelwifiue:/sys/devices/platform # ls
APPS_FM.6
APPS_RIVA_ANT_CMD.6
APPS_RIVA_ANT_DATA.6
APPS_RIVA_BT_ACL.6
APPS_RIVA_BT_CMD.6
APPS_RIVA_CTRL.6
APPS_RIVA_DATA.6
DIAG.0
DIAG_2.0
DIAG_2_CMD.0
DIAG_CMD.0
DIAG_CNTL.0
IPCRTR.0
IPCRTR.6
SSM_RTR_MODEM_APPS.0
SVC0000000e:00000001.1
SVC0000000f:00000001.1
SVC0000000f:00000001.2
SVC00000010:00000002.1
SVC00000016:00000101.1
SVC00000017:00000001.1
SVC00000018:00000001.1
SVC0000001c:00000001.1
SVC0000001c:00000101.1
SVC00000022:00000001.1
SVC0000002b:00000001.1
SVC00000034:00000101.1
SVC000000e8:00000101.1
SVC00000100:00000100.1
SVC00000100:00000100.2
WCNSS_CTRL.6
WLAN_CTRL.6
alarmtimer
apr_apps2.0
apr_audio_svc.0
msm_hsusb
msm_hsusb_host
power
reg-dummy
regulatory.0
rpm_requests.15
sec-thermistor
secgpio_dvs
snd-soc-dummy
sys_mon.0
sys_mon.6
uevent

qc_smd_ch_xxx.log

Primary allocation table:
ID|CHANNEL NAME       |T|PROC |STATE  |FIFO SZ|RDPTR  |WRPTR  |FLAGS   |DATAPEN
-------------------------------------------------------------------------------
 4|rpm_requests       |P|APPS |OPENED |0x00400|0x00188|0x00188|DCCiwRsB|0x00000
  |                   | |RPM  |OPENED |0x00400|0x000A0|0x000A0|DCCiwrsB|0x00000
-------------------------------------------------------------------------------
 5|rpm_requests       |P|MDMSW| Access Restricted
  |                   | |RPM  | Access Restricted
-------------------------------------------------------------------------------
 6|rpm_requests       |P|WCNSS| Access Restricted
  |                   | |RPM  | Access Restricted
-------------------------------------------------------------------------------
 7|rpm_requests       |P|TZ   | Access Restricted
  |                   | |RPM  | Access Restricted
-------------------------------------------------------------------------------


APPS <-> MDMSW Primary allocation table:
ID|CHANNEL NAME       |T|PROC |STATE  |FIFO SZ|RDPTR  |WRPTR  |FLAGS   |DATAPEN
-------------------------------------------------------------------------------
 0|DS                 |S|APPS |OPENED |0x02000|0x00000|0x00000|DCCiwrsB|0x00000
  |                   | |MDMSW|OPENED |0x02000|0x00000|0x00000|dCciwrsb|0x00000
-------------------------------------------------------------------------------
 1|IPCRTR             |P|APPS |OPENED |0x02000|0x00F28|0x00F28|DCCiwrsB|0x00000
  |                   | |MDMSW|OPENED |0x02000|0x00DAC|0x00DAC|DCCiwrsB|0x00000
-------------------------------------------------------------------------------
 2|SSM_RTR_MODEM_APPS |P|APPS |CLOSED |0x02000|0x00000|0x00000|dcciwrsb|0x00000
  |                   | |MDMSW|OPENING|0x02000|0x00000|0x00000|DCCiwrSb|0x00000
-------------------------------------------------------------------------------
 3|sys_mon            |P|APPS |OPENED |0x00400|0x002BE|0x002BE|DCCiwrsB|0x00000
  |                   | |MDMSW|OPENED |0x00400|0x00060|0x00060|DCCiwrsB|0x00000
-------------------------------------------------------------------------------
 4|DIAG_2_CMD         |P|APPS |OPENED |0x02000|0x00000|0x00000|DCCiwrsb|0x00000
  |                   | |MDMSW|OPENED |0x02000|0x00000|0x00000|DCCiwrsb|0x00000
-------------------------------------------------------------------------------
 5|DIAG_2             |P|APPS |OPENED |0x02000|0x00000|0x00000|DCCiwrsb|0x00000
  |                   | |MDMSW|OPENED |0x02000|0x00000|0x00000|DCCiwrsb|0x00000
-------------------------------------------------------------------------------
 6|DIAG_CNTL          |P|APPS |OPENED |0x02000|0x00083|0x00083|DCCiwrsb|0x00000
  |                   | |MDMSW|OPENED |0x02000|0x00471|0x00471|DCCiwrsB|0x00000
-------------------------------------------------------------------------------
 7|DIAG_CMD           |P|APPS |OPENED |0x02000|0x00000|0x00000|DCCiwrsb|0x00000
  |                   | |MDMSW|OPENED |0x02000|0x00000|0x00000|DCCiwrsb|0x00000
-------------------------------------------------------------------------------
 8|DIAG               |P|APPS |OPENED |0x02000|0x00000|0x00000|DCCiwrsb|0x00000
  |                   | |MDMSW|OPENED |0x02000|0x00026|0x00026|DCCiwrsB|0x00000
-------------------------------------------------------------------------------
 9|apr_audio_svc      |P|APPS |OPENED |0x02000|0x0064E|0x0064E|DCCiwrsB|0x00000
  |                   | |MDMSW|OPENED |0x02000|0x01C70|0x01C70|DCCiwrsB|0x00000
-------------------------------------------------------------------------------
10|apr_apps2          |P|APPS |CLOSED |0x02000|0x00000|0x00000|dcciwrsb|0x00000
  |                   | |MDMSW|OPENING|0x02000|0x00000|0x00000|DCCiwrSb|0x00000
-------------------------------------------------------------------------------
11|DATA1              |P|APPS |CLOSED |0x02000|0x00000|0x00000|dcciwrsb|0x00000
  |                   | |MDMSW|OPENING|0x02000|0x00000|0x00000|dCciwrSb|0x00000
-------------------------------------------------------------------------------
12|DATA2              |P|APPS |CLOSED |0x02000|0x00000|0x00000|dcciwrsb|0x00000
  |                   | |MDMSW|OPENING|0x02000|0x00000|0x00000|dCciwrSb|0x00000
-------------------------------------------------------------------------------
13|DATA3              |P|APPS |CLOSED |0x02000|0x00000|0x00000|dcciwrsb|0x00000
  |                   | |MDMSW|OPENING|0x02000|0x00000|0x00000|dCciwrSb|0x00000
-------------------------------------------------------------------------------
14|DATA4              |P|APPS |CLOSED |0x02000|0x00000|0x00000|dcciwrsb|0x00000
  |                   | |MDMSW|OPENING|0x02000|0x00000|0x00000|dCciwrSb|0x00000
-------------------------------------------------------------------------------
15|DATA11             |S|APPS |CLOSED |0x02000|0x00000|0x00000|dcciwrsb|0x00000
  |                   | |MDMSW|OPENING|0x02000|0x00000|0x00000|dCciwrSb|0x00000
-------------------------------------------------------------------------------
16|DATA40             |P|APPS |CLOSED |0x02000|0x00000|0x00000|dcciwrsb|0x00000
  |                   | |MDMSW|OPENING|0x02000|0x00000|0x00000|dcciwrSb|0x00000
-------------------------------------------------------------------------------
17|DATA5_CNTL         |P|APPS |OPENED |0x00400|0x001AA|0x001AA|DCCiwrsB|0x00000
  |                   | |MDMSW|OPENED |0x00400|0x00208|0x00208|DCCiwrsB|0x00000
-------------------------------------------------------------------------------
18|DATA6_CNTL         |P|APPS |OPENED |0x00400|0x00338|0x00338|DCCiwrsB|0x00000
  |                   | |MDMSW|OPENED |0x00400|0x00363|0x00363|DCCiwrsB|0x00000
-------------------------------------------------------------------------------
19|DATA7_CNTL         |P|APPS |OPENED |0x00400|0x001A2|0x001A2|DCCiwrsB|0x00000
  |                   | |MDMSW|OPENED |0x00400|0x001F7|0x001F7|DCCiwrsB|0x00000
-------------------------------------------------------------------------------
20|DATA8_CNTL         |P|APPS |OPENED |0x00400|0x001A2|0x001A2|DCCiwrsB|0x00000
  |                   | |MDMSW|OPENED |0x00400|0x001F7|0x001F7|DCCiwrsB|0x00000
-------------------------------------------------------------------------------
21|DATA9_CNTL         |P|APPS |OPENED |0x00400|0x001A2|0x001A2|DCCiwrsB|0x00000
  |                   | |MDMSW|OPENED |0x00400|0x001F7|0x001F7|DCCiwrsB|0x00000
-------------------------------------------------------------------------------
22|DATA12_CNTL        |P|APPS |OPENED |0x00400|0x001A2|0x001A2|DCCiwrsB|0x00000
  |                   | |MDMSW|OPENED |0x00400|0x001F7|0x001F7|DCCiwrsB|0x00000
-------------------------------------------------------------------------------
23|DATA13_CNTL        |P|APPS |OPENED |0x00400|0x001A2|0x001A2|DCCiwrsB|0x00000
  |                   | |MDMSW|OPENED |0x00400|0x001F7|0x001F7|DCCiwrsB|0x00000
-------------------------------------------------------------------------------
24|DATA14_CNTL        |P|APPS |OPENED |0x00400|0x001A2|0x001A2|DCCiwrsB|0x00000
  |                   | |MDMSW|OPENED |0x00400|0x001F7|0x001F7|DCCiwrsB|0x00000
-------------------------------------------------------------------------------
25|DATA15_CNTL        |P|APPS |CLOSED |0x00400|0x00000|0x00000|dcciwrsb|0x00000
  |                   | |MDMSW|OPENING|0x00400|0x00000|0x00000|DCCiwrSb|0x00000
-------------------------------------------------------------------------------
26|DATA16_CNTL        |P|APPS |CLOSED |0x00400|0x00000|0x00000|dcciwrsb|0x00000
  |                   | |MDMSW|OPENING|0x00400|0x00000|0x00000|DCCiwrSb|0x00000
-------------------------------------------------------------------------------
27|DATA40_CNTL        |P|APPS |CLOSED |0x02000|0x00000|0x00000|dcciwrsb|0x00000
  |                   | |MDMSW|OPENING|0x02000|0x00000|0x00000|DCCiwrSb|0x00000
-------------------------------------------------------------------------------


APPS <-> WCNSS Primary allocation table:
ID|CHANNEL NAME       |T|PROC |STATE  |FIFO SZ|RDPTR  |WRPTR  |FLAGS   |DATAPEN
-------------------------------------------------------------------------------
 1|IPCRTR             |P|APPS |OPENED |0x02000|0x00168|0x00168|DCCiwrsB|0x00000
  |                   | |WCNSS|OPENED |0x02000|0x000D8|0x000D8|DCCiwrsB|0x00000
-------------------------------------------------------------------------------
 2|sys_mon            |P|APPS |OPENED |0x00400|0x00267|0x00267|DCCiwRsB|0x00000
  |                   | |WCNSS|OPENED |0x00400|0x003D4|0x003D4|DCCiwrsB|0x00000
-------------------------------------------------------------------------------
 3|APPS_RIVA_CTRL     |P|APPS |OPENED |0x02000|0x00062|0x00062|DCCiwrsb|0x00000
  |                   | |WCNSS|OPENED |0x02000|0x00282|0x00282|DCCiwrsB|0x00000
-------------------------------------------------------------------------------
 4|APPS_RIVA_DATA     |P|APPS |OPENED |0x02000|0x00000|0x00000|DCCiwrsb|0x00000
  |                   | |WCNSS|OPENED |0x02000|0x00000|0x00000|DCCiwrsb|0x00000
-------------------------------------------------------------------------------
 5|WCNSS_CTRL         |P|APPS |OPENED |0x02000|0x01638|0x01638|DCCiwrsB|0x00000
  |                   | |WCNSS|OPENED |0x02000|0x00175|0x00175|DCCiwrsB|0x00000
-------------------------------------------------------------------------------
 6|WLAN_CTRL          |P|APPS |OPENED |0x02000|0x00277|0x00277|DCCiwrsB|0x00000
  |                   | |WCNSS|OPENED |0x02000|0x01115|0x01115|DCCiwrsB|0x00000
-------------------------------------------------------------------------------
 7|APPS_RIVA_BT_CMD   |P|APPS |OPENED |0x02000|0x0182C|0x0182C|DCCiwrsB|0x00000
  |                   | |WCNSS|OPENED |0x02000|0x01AE5|0x01AE5|DCCiwrsB|0x00000
-------------------------------------------------------------------------------
 8|APPS_RIVA_BT_ACL   |P|APPS |OPENED |0x02000|0x01904|0x01904|DCCiwrsB|0x00000
  |                   | |WCNSS|OPENED |0x02000|0x015E8|0x015E8|DCCiwrsB|0x00000
-------------------------------------------------------------------------------
 9|APPS_RIVA_ANT_CMD  |P|APPS |CLOSED |0x00400|0x00000|0x00000|dcciwrsb|0x00000
  |                   | |WCNSS|OPENING|0x00400|0x00000|0x00000|DCCiwrSb|0x00000
-------------------------------------------------------------------------------
10|APPS_RIVA_ANT_DATA |P|APPS |CLOSED |0x00800|0x00000|0x00000|dcciwrsb|0x00000
  |                   | |WCNSS|OPENING|0x00800|0x00000|0x00000|DCCiwrSb|0x00000
-------------------------------------------------------------------------------
11|APPS_FM            |P|APPS |CLOSED |0x02000|0x00000|0x00000|dcciwrsb|0x00000
  |                   | |WCNSS|OPENING|0x02000|0x00000|0x00000|DCCiwrSb|0x00000
-------------------------------------------------------------------------------

每个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{}那里都定义了一个别名，好像都是根据这个别名来定的设备的名字！！

    aliases {
        sdhc1 = &sdhc_1; /* SDC1 eMMC slot */
        sdhc2 = &sdhc_2; /* SDC2 SD card slot */

        /* smdtty devices */
        smd0 = &smdtty_ds;
        smd1 = &smdtty_apps_fm;
        smd2 = &smdtty_apps_riva_bt_acl;
        smd3 = &smdtty_apps_riva_bt_cmd;
        smd4 = &smdtty_mbalbridge;
        smd5 = &smdtty_apps_riva_ant_cmd;
        smd6 = &smdtty_apps_riva_ant_data;
        smd7 = &smdtty_data1;
        smd8 = &smdtty_data4;
        smd11 = &smdtty_data11;
        smd21 = &smdtty_data21;
        smd36 = &smdtty_loopback;

        //spi0 = &spi_0; /* SPI0 controller device */
        i2c0 = &i2c_0; /* I2C0 controller device */
        i2c1 = &i2c_1; /* I2C1 controller device */
        i2c5 = &i2c_5; /* I2C5 controller device */
        i2c6 = &i2c_6; /* I2C6 NFC qup6 device */
        i2c4 = &i2c_4; /* I2C4 controller device */
    };

    qcom,smdtty {
        compatible = "qcom,smdtty";

        smdtty_ds: qcom,smdtty-ds {
            qcom,smdtty-remote = "modem";
            qcom,smdtty-port-name = "DS";
        };

        smdtty_apps_fm: qcom,smdtty-apps-fm {
            qcom,smdtty-remote = "wcnss";
            qcom,smdtty-port-name = "APPS_FM";
        };

        smdtty_apps_riva_bt_acl: smdtty-apps-riva-bt-acl {
            qcom,smdtty-remote = "wcnss";
            qcom,smdtty-port-name = "APPS_RIVA_BT_ACL";
        };

        smdtty_apps_riva_bt_cmd: qcom,smdtty-apps-riva-bt-cmd {
            qcom,smdtty-remote = "wcnss";
            qcom,smdtty-port-name = "APPS_RIVA_BT_CMD";
        };

        smdtty_mbalbridge: qcom,smdtty-mbalbridge {
            qcom,smdtty-remote = "modem";
            qcom,smdtty-port-name = "MBALBRIDGE";
        };

        smdtty_apps_riva_ant_cmd: smdtty-apps-riva-ant-cmd {
            qcom,smdtty-remote = "wcnss";
            qcom,smdtty-port-name = "APPS_RIVA_ANT_CMD";
        };

        smdtty_apps_riva_ant_data: smdtty-apps-riva-ant-data {
            qcom,smdtty-remote = "wcnss";
            qcom,smdtty-port-name = "APPS_RIVA_ANT_DATA";
        };

        smdtty_data1: qcom,smdtty-data1 {
            qcom,smdtty-remote = "modem";
            qcom,smdtty-port-name = "DATA1";
        };

        smdtty_data4: qcom,smdtty-data4 {
            qcom,smdtty-remote = "modem";
            qcom,smdtty-port-name = "DATA4";
        };

        smdtty_data11: qcom,smdtty-data11 {
            qcom,smdtty-remote = "modem";
            qcom,smdtty-port-name = "DATA11";
        };

        smdtty_data21: qcom,smdtty-data21 {
            qcom,smdtty-remote = "modem";
            qcom,smdtty-port-name = "DATA21";
        };

        smdtty_loopback: smdtty-loopback {
            qcom,smdtty-remote = "modem";
            qcom,smdtty-port-name = "LOOPBACK";
            qcom,smdtty-dev-name = "LOOPBACK_TTY";
        };
    };

    //tty和pkt不一样，分别对应msm_smd_tty.c和msm_smd_pkt.c文件！！
    qcom,smdpkt {
        compatible = "qcom,smdpkt";

        qcom,smdpkt-data5-cntl {
            qcom,smdpkt-remote = "modem";
            qcom,smdpkt-port-name = "DATA5_CNTL";
            qcom,smdpkt-dev-name = "smdcntl0";
        };

        qcom,smdpkt-data6-cntl {
            qcom,smdpkt-remote = "modem";
            qcom,smdpkt-port-name = "DATA6_CNTL";
            qcom,smdpkt-dev-name = "smdcntl1";
        };

        qcom,smdpkt-data7-cntl {
            qcom,smdpkt-remote = "modem";
            qcom,smdpkt-port-name = "DATA7_CNTL";
            qcom,smdpkt-dev-name = "smdcntl2";
        };

        qcom,smdpkt-data8-cntl {
            qcom,smdpkt-remote = "modem";
            qcom,smdpkt-port-name = "DATA8_CNTL";
            qcom,smdpkt-dev-name = "smdcntl3";
        };

        qcom,smdpkt-data9-cntl {
            qcom,smdpkt-remote = "modem";
            qcom,smdpkt-port-name = "DATA9_CNTL";
            qcom,smdpkt-dev-name = "smdcntl4";
        };

        qcom,smdpkt-data12-cntl {
            qcom,smdpkt-remote = "modem";
            qcom,smdpkt-port-name = "DATA12_CNTL";
            qcom,smdpkt-dev-name = "smdcntl5";
        };

        qcom,smdpkt-data13-cntl {
            qcom,smdpkt-remote = "modem";
            qcom,smdpkt-port-name = "DATA13_CNTL";
            qcom,smdpkt-dev-name = "smdcntl6";
        };

        qcom,smdpkt-data14-cntl {
            qcom,smdpkt-remote = "modem";
            qcom,smdpkt-port-name = "DATA14_CNTL";
            qcom,smdpkt-dev-name = "smdcntl7";
        };

        qcom,smdpkt-data15-cntl {
            qcom,smdpkt-remote = "modem";
            qcom,smdpkt-port-name = "DATA15_CNTL";
            qcom,smdpkt-dev-name = "smdcntl9";
        };

        qcom,smdpkt-data16-cntl {
            qcom,smdpkt-remote = "modem";
            qcom,smdpkt-port-name = "DATA16_CNTL";
            qcom,smdpkt-dev-name = "smdcntl10";
        };

        qcom,smdpkt-data17-cntl {
            qcom,smdpkt-remote = "modem";
            qcom,smdpkt-port-name = "DATA17_CNTL";
            qcom,smdpkt-dev-name = "smdcntl11";
        };

        qcom,smdpkt-data22 {
            qcom,smdpkt-remote = "modem";
            qcom,smdpkt-port-name = "DATA22";
            qcom,smdpkt-dev-name = "smd22";
        };

        qcom,smdpkt-data23-cntl {
            qcom,smdpkt-remote = "modem";
            qcom,smdpkt-port-name = "DATA23_CNTL";
            qcom,smdpkt-dev-name = "smdcnt_rev0";
        };

        qcom,smdpkt-data24-cntl {
            qcom,smdpkt-remote = "modem";
            qcom,smdpkt-port-name = "DATA24_CNTL";
            qcom,smdpkt-dev-name = "smdcnt_rev1";
        };

        qcom,smdpkt-data25-cntl {
            qcom,smdpkt-remote = "modem";
            qcom,smdpkt-port-name = "DATA25_CNTL";
            qcom,smdpkt-dev-name = "smdcnt_rev2";
        };

        qcom,smdpkt-data26-cntl {
            qcom,smdpkt-remote = "modem";
            qcom,smdpkt-port-name = "DATA26_CNTL";
            qcom,smdpkt-dev-name = "smdcnt_rev3";
        };

        qcom,smdpkt-data27-cntl {
            qcom,smdpkt-remote = "modem";
            qcom,smdpkt-port-name = "DATA27_CNTL";
            qcom,smdpkt-dev-name = "smdcnt_rev4";
        };

        qcom,smdpkt-data28-cntl {
            qcom,smdpkt-remote = "modem";
            qcom,smdpkt-port-name = "DATA28_CNTL";
            qcom,smdpkt-dev-name = "smdcnt_rev5";
        };

        qcom,smdpkt-data29-cntl {
            qcom,smdpkt-remote = "modem";
            qcom,smdpkt-port-name = "DATA29_CNTL";
            qcom,smdpkt-dev-name = "smdcnt_rev6";
        };

        qcom,smdpkt-data30-cntl {
            qcom,smdpkt-remote = "modem";
            qcom,smdpkt-port-name = "DATA30_CNTL";
            qcom,smdpkt-dev-name = "smdcnt_rev7";
        };

        qcom,smdpkt-data31-cntl {
            qcom,smdpkt-remote = "modem";
            qcom,smdpkt-port-name = "DATA31_CNTL";
            qcom,smdpkt-dev-name = "smdcnt_rev8";
        };

        qcom,smdpkt-data40-cntl {
            qcom,smdpkt-remote = "modem";
            qcom,smdpkt-port-name = "DATA40_CNTL";
            qcom,smdpkt-dev-name = "smdcntl8";
        };

        qcom,smdpkt-apr-apps2 {
            qcom,smdpkt-remote = "modem";
            qcom,smdpkt-port-name = "apr_apps2";
            qcom,smdpkt-dev-name = "apr_apps2";
        };

        qcom,smdpkt-loopback {
            qcom,smdpkt-remote = "modem";
            qcom,smdpkt-port-name = "LOOPBACK";
            qcom,smdpkt-dev-name = "smd_pkt_loopback";
        };
    }

至此，就知道在哪里会初始化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目录下。这个是因为~~看下面代码注释

//msm_smd_debug_mask这个默认没有打开debug信息，需要调试更多可以加一个MSM_SMD_DEBUG。
#define SMD_DBG(x...) do {              \
        if (msm_smd_debug_mask & MSM_SMD_DEBUG) \
            IPC_LOG_SMD(KERN_DEBUG, x); \
    } while (0)
#define SMD_INFO(x...) do {             \
        if (msm_smd_debug_mask & MSM_SMD_INFO)  \
            IPC_LOG_SMD(KERN_INFO, x);  \
    } while (0)

//如果smd_log_ctx已经像下面这样定义，那就是到/d/ipc_logging目录下找相应名字的文件夹下看
//或者如果不想的话，就可以把smd_log_ctx的定义去掉，直接打印到内核里边。当然内核的debug level那块自己需要改一下！！
smd_log_ctx = ipc_log_context_create(NUM_LOG_PAGES, "smd", 0);
#define IPC_LOG_SMD(level, x...) do { \
    if (smd_log_ctx) \
        ipc_log_string(smd_log_ctx, x); \
    else \
        printk(level x); \
    } while (0)

以下是qc_smdpkt_xxx.log：

[ 11247.679255802] <SMD_PKT>: ch_notify: DATA event in smd_pkt_dev id:0
[ 11247.679286896] <SMD_PKT>: check_and_wakeup_reader: wake_up smd_pkt_dev id:0
[ 11247.679292469] <SMD_PKT>: check_and_wakeup_writer: 1000 bytes write space in smd_pkt_dev id:0
[ 11247.679332781] <SMD_PKT>: smd_pkt_poll sets POLLIN for smd_pkt_dev id: 0
[ 11247.679372521] <SMD_PKT>: Begin smd_pkt_read on smd_pkt_dev id:0 buffer_size 5086
[ 11247.679430594] <SMD_PKT>: smd_pkt_read unlocked smd_pkt_dev id:0 wakeup_source
[ 11247.679436479] <SMD_PKT>: Finished smd_pkt_read on smd_pkt_dev id:0  20 bytes
[ 11247.679462677] <SMD_PKT>: check_and_wakeup_reader: No packet in smd_pkt_dev id:0
[ 11253.959471134] <SMD_PKT>: Begin smd_pkt_write on smd_pkt_dev id:0 data_size 13
[ 11253.959521967] <SMD_PKT>: Finished smd_pkt_write on smd_pkt_dev id:0 13 bytes
[ 11253.959942853] <SMD_PKT>: ch_notify: DATA event in smd_pkt_dev id:0
[ 11253.959981186] <SMD_PKT>: check_and_wakeup_reader: wake_up smd_pkt_dev id:0
[ 11253.959982748] <SMD_PKT>: smd_pkt_poll sets POLLIN for smd_pkt_dev id: 0
[ 11253.959985248] <SMD_PKT>: check_and_wakeup_writer: 1000 bytes write space in smd_pkt_dev id:0
[ 11253.960014207] <SMD_PKT>: Begin smd_pkt_read on smd_pkt_dev id:0 buffer_size 5086
[ 11253.960050561] <SMD_PKT>: smd_pkt_read unlocked smd_pkt_dev id:0 wakeup_source
[ 11253.960054780] <SMD_PKT>: Finished smd_pkt_read on smd_pkt_dev id:0  20 bytes
[ 11253.960072123] <SMD_PKT>: check_and_wakeup_reader: No packet in smd_pkt_dev id:0
[ 11260.707648550] <SMD_PKT>: Begin smd_pkt_write on smd_pkt_dev id:0 data_size 13
[ 11260.707704800] <SMD_PKT>: Finished smd_pkt_write on smd_pkt_dev id:0 13 bytes
[ 11260.708084957] <SMD_PKT>: ch_notify: DATA event in smd_pkt_dev id:0
[ 11260.708118811] <SMD_PKT>: check_and_wakeup_reader: wake_up smd_pkt_dev id:0
[ 11260.708123290] <SMD_PKT>: check_and_wakeup_writer: 1000 bytes write space in smd_pkt_dev id:0
[ 11260.708154540] <SMD_PKT>: packet_arrival_worker locking smd_pkt_dev id:0 wakeup source
[ 11260.708218654] <SMD_PKT>: smd_pkt_poll sets POLLIN for smd_pkt_dev id: 0
[ 11260.708571415] <SMD_PKT>: Begin smd_pkt_read on smd_pkt_dev id:0 buffer_size 5086
[ 11260.708609384] <SMD_PKT>: smd_pkt_read unlocked smd_pkt_dev id:0 wakeup_source
[ 11260.708613863] <SMD_PKT>: Finished smd_pkt_read on smd_pkt_dev id:0  20 bytes
[ 11260.708631832] <SMD_PKT>: check_and_wakeup_reader: No packet in smd_pkt_dev id:0
[ 11264.686568250] <SMD_PKT>: Begin smd_pkt_write on smd_pkt_dev id:0 data_size 13
[ 11264.686618146] <SMD_PKT>: Finished smd_pkt_write on smd_pkt_dev id:0 13 bytes
[ 11264.686985281] <SMD_PKT>: ch_notify: DATA event in smd_pkt_dev id:0
[ 11264.687013979] <SMD_PKT>: check_and_wakeup_reader: wake_up smd_pkt_dev id:0
[ 11264.687018406] <SMD_PKT>: check_and_wakeup_writer: 1000 bytes write space in smd_pkt_dev id:0
[ 11264.687091062] <SMD_PKT>: smd_pkt_poll sets POLLIN for smd_pkt_dev id: 0
[ 11264.687141010] <SMD_PKT>: packet_arrival_worker locking smd_pkt_dev id:0 wakeup source
[ 11264.687145906] <SMD_PKT>: Begin smd_pkt_read on smd_pkt_dev id:0 buffer_size 5086
[ 11264.687185073] <SMD_PKT>: smd_pkt_read unlocked smd_pkt_dev id:0 wakeup_source
[ 11264.687189917] <SMD_PKT>: Finished smd_pkt_read on smd_pkt_dev id:0  20 bytes
[ 11264.687207937] <SMD_PKT>: check_and_wakeup_reader: No packet in smd_pkt_dev id:0
[ 11271.507262281] <SMD_PKT>: Begin smd_pkt_write on smd_pkt_dev id:0 data_size 13
[ 11271.507305719] <SMD_PKT>: Finished smd_pkt_write on smd_pkt_dev id:0 13 bytes
[ 11271.507728167] <SMD_PKT>: ch_notify: DATA event in smd_pkt_dev id:0
[ 11271.507759625] <SMD_PKT>: check_and_wakeup_reader: wake_up smd_pkt_dev id:0
[ 11271.507763583] <SMD_PKT>: check_and_wakeup_writer: 1000 bytes write space in smd_pkt_dev id:0
[ 11271.507796604] <SMD_PKT>: smd_pkt_poll sets POLLIN for smd_pkt_dev id: 0
[ 11271.507822854] <SMD_PKT>: Begin smd_pkt_read on smd_pkt_dev id:0 buffer_size 5086
[ 11271.507862333] <SMD_PKT>: smd_pkt_read unlocked smd_pkt_dev id:0 wakeup_source
[ 11271.507866500] <SMD_PKT>: Finished smd_pkt_read on smd_pkt_dev id:0  20 bytes
[ 11271.507884364] <SMD_PKT>: check_and_wakeup_reader: No packet in smd_pkt_dev id:0
[ 11274.734097551] <SMD_PKT>: Begin smd_pkt_write on smd_pkt_dev id:0 data_size 13
[ 11274.734160676] <SMD_PKT>: Finished smd_pkt_write on smd_pkt_dev id:0 13 bytes
[ 11274.734588697] <SMD_PKT>: ch_notify: DATA event in smd_pkt_dev id:0
[ 11274.734628333] <SMD_PKT>: check_and_wakeup_reader: wake_up smd_pkt_dev id:0
[ 11274.734633645] <SMD_PKT>: check_and_wakeup_writer: 1000 bytes write space in smd_pkt_dev id:0
[ 11274.735154999] <SMD_PKT>: packet_arrival_worker locking smd_pkt_dev id:0 wakeup source
[ 11274.735238385] <SMD_PKT>: smd_pkt_poll sets POLLIN for smd_pkt_dev id: 0
[ 11274.735276614] <SMD_PKT>: Begin smd_pkt_read on smd_pkt_dev id:0 buffer_size 5086
[ 11274.735333906] <SMD_PKT>: smd_pkt_read unlocked smd_pkt_dev id:0 wakeup_source
[ 11274.735339374] <SMD_PKT>: Finished smd_pkt_read on smd_pkt_dev id:0  20 bytes
[ 11274.735361145] <SMD_PKT>: check_and_wakeup_reader: No packet in smd_pkt_dev id:0
[ 11281.493969135] <SMD_PKT>: Begin smd_pkt_write on smd_pkt_dev id:0 data_size 13
[ 11281.494015593] <SMD_PKT>: Finished smd_pkt_write on smd_pkt_dev id:0 13 bytes
[ 11281.496142103] <SMD_PKT>: ch_notify: DATA event in smd_pkt_dev id:0
[ 11281.496202520] <SMD_PKT>: check_and_wakeup_reader: wake_up smd_pkt_dev id:0
[ 11281.496207780] <SMD_PKT>: check_and_wakeup_writer: 1000 bytes write space in smd_pkt_dev id:0
[ 11281.496255801] <SMD_PKT>: packet_arrival_worker locking smd_pkt_dev id:0 wakeup source
[ 11281.496423249] <SMD_PKT>: smd_pkt_poll sets POLLIN for smd_pkt_dev id: 0
[ 11281.496776582] <SMD_PKT>: Begin smd_pkt_read on smd_pkt_dev id:0 buffer_size 5086
[ 11281.496824707] <SMD_PKT>: smd_pkt_read unlocked smd_pkt_dev id:0 wakeup_source
[ 11281.496828822] <SMD_PKT>: Finished smd_pkt_read on smd_pkt_dev id:0  20 bytes
[ 11281.496848614] <SMD_PKT>: check_and_wakeup_reader: No packet in smd_pkt_dev id:0
[ 11284.784395968] <SMD_PKT>: Begin smd_pkt_write on smd_pkt_dev id:0 data_size 13
[ 11284.784449301] <SMD_PKT>: Finished smd_pkt_write on smd_pkt_dev id:0 13 bytes
[ 11284.786411332] <SMD_PKT>: ch_notify: DATA event in smd_pkt_dev id:0
[ 11284.786464301] <SMD_PKT>: check_and_wakeup_reader: wake_up smd_pkt_dev id:0
[ 11284.786469197] <SMD_PKT>: check_and_wakeup_writer: 1000 bytes write space in smd_pkt_dev id:0
[ 11284.786477790] <SMD_PKT>: smd_pkt_poll sets POLLIN for smd_pkt_dev id: 0
[ 11284.786504093] <SMD_PKT>: packet_arrival_worker locking smd_pkt_dev id:0 wakeup source
[ 11284.786811645] <SMD_PKT>: Begin smd_pkt_read on smd_pkt_dev id:0 buffer_size 5086
[ 11284.786848363] <SMD_PKT>: smd_pkt_read unlocked smd_pkt_dev id:0 wakeup_source
[ 11284.786852582] <SMD_PKT>: Finished smd_pkt_read on smd_pkt_dev id:0  20 bytes
[ 11284.786870290] <SMD_PKT>: check_and_wakeup_reader: No packet in smd_pkt_dev id:0
[ 11288.184812488] <SMD_PKT>: Begin smd_pkt_write on smd_pkt_dev id:0 data_size 13
[ 11288.184869311] <SMD_PKT>: Finished smd_pkt_write on smd_pkt_dev id:0 13 bytes
[ 11288.187012645] <SMD_PKT>: ch_notify: DATA event in smd_pkt_dev id:0
[ 11288.187054572] <SMD_PKT>: check_and_wakeup_reader: wake_up smd_pkt_dev id:0
[ 11288.187060145] <SMD_PKT>: check_and_wakeup_writer: 1000 bytes write space in smd_pkt_dev id:0
[ 11288.187062592] <SMD_PKT>: smd_pkt_poll sets POLLIN for smd_pkt_dev id: 0
[ 11288.187099884] <SMD_PKT>: Begin smd_pkt_read on smd_pkt_dev id:0 buffer_size 5086
[ 11288.187139363] <SMD_PKT>: smd_pkt_read unlocked smd_pkt_dev id:0 wakeup_source
[ 11288.187143530] <SMD_PKT>: Finished smd_pkt_read on smd_pkt_dev id:0  20 bytes
[ 11288.187161499] <SMD_PKT>: check_and_wakeup_reader: No packet in smd_pkt_dev id:0
[ 11294.361732247] <SMD_PKT>: Begin smd_pkt_write on smd_pkt_dev id:0 data_size 13
[ 11294.361781205] <SMD_PKT>: Finished smd_pkt_write on smd_pkt_dev id:0 13 bytes
[ 11294.362070320] <SMD_PKT>: ch_notify: DATA event in smd_pkt_dev id:0
[ 11294.362108132] <SMD_PKT>: check_and_wakeup_reader: wake_up smd_pkt_dev id:0
[ 11294.362108288] <SMD_PKT>: smd_pkt_poll sets POLLIN for smd_pkt_dev id: 0
[ 11294.362112403] <SMD_PKT>: check_and_wakeup_writer: 1000 bytes write space in smd_pkt_dev id:0
[ 11294.362459851] <SMD_PKT>: Begin smd_pkt_read on smd_pkt_dev id:0 buffer_size 5086
[ 11294.362544070] <SMD_PKT>: smd_pkt_read unlocked smd_pkt_dev id:0 wakeup_source
[ 11294.362548393] <SMD_PKT>: Finished smd_pkt_read on smd_pkt_dev id:0  20 bytes
[ 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，但没有找到代码，后续需要说明。

service SMD-daemon /system/bin/smdexe
    class main
    user root
    group system radio inet net_raw

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

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

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.

honghong96
关注
  • 1
    点赞
  • 踩
  • 9
    收藏
    觉得还不错? 一键收藏
  • 0
    评论
专栏目录
AUTOSAR CP VS AP
爱好者的博客
02-01 843
CP和AP两平台差异聚焦于软件架构、接口标准、软件工程文件运行特点、执行任务配置方式、编码语言等。
IPC(中)-进程间通讯方式详解
朱利源的博客
01-22 4562
IPC(中)1 Android中IPC方式在第一篇IPC(上)中我们已经介绍了IPC的基础知识:序列化和Binder,本篇将详细介绍各种跨进程通讯方式.具体有如下几种: Intent中extras传递 共享文件 Binder ContentProvider Socket 1.1 Bundle四大组件中的三大组件(Activity,Service,Receiver)都是支持在Intent中传递Bu
LightningKernel_Xiaomi_msm8953：Mi A1（天梭）基于CAF 4.9源的LightningKernel与linux-stable合并
02-19
LightningKernel_Xiaomi_msm8953：Mi A1（天梭）基于CAF 4.9源的LightningKernel与linux-stable合并
msm audio platform 驱动代码跟踪
weixin_30588729的博客
03-09 256
sound/soc/soc-core.c static int __init snd_soc_init(void) { #ifdef CONFIG_DEBUG_FS snd_soc_debugfs_root = debugfs_create_dir("asoc", NULL); if (IS_ERR(snd_soc_debugfs_root) || !snd_soc_debugf...
android 设备注册,Android平台上PMEM的使用及Platform设备注册(二)
weixin_29137599的博客
06-03 187
三、注册PMEM设备这里我们除了描述PMEM设备，还将注册一个拥有memory空间和IRQ资源的示例设备example_device。对于example_device，定义如下结构体：static struct resource example_resources[] = {[0] = {.start= 0xC0000000,.end= 0xC0020000,.flags= IOR...
Android高通平台处理器间通讯驱动
业余飘向linux深谷
12-21 1420
高通平台AP与CP直接通信由Share Memory负责，这是一块两端可以同时操作的内存区域。由于高通平台Modem占主导作用，在Application Processor启动初始化时，从Share Memory区读取已经由Modem predeclared的一些数据。 Share memory根据功能，分为静态+动态部分，每个部分又分为数个小区，每个区的大小不一，与本区实现的功能相关。Mode
Linux.IPC总结代码测试
qq_35661325的博客
03-04 581
IPC： 一般情况下，系统中运行着大量的进程，而每个进程之间并不是相互独立的，有些进程之间经常需要互相传递消息。 但是每个进程在系统中都有自己的地址空间，操作系统通过页表和实际物理内存所关联，不允许其他进程随意进入。 因此，就必须有一种机制既能保证进程之间的通信，又能保证系统的安全，即进程间通信机制——I P C （Inter_Process Communication）。 在linux下的多个进程间的通信机制叫做IPC(Inter-Process Communication)， 它是多个进程之间相互沟通的
Linux IPC总结（全）
热门推荐
大象大象啥模样。。。
08-02 1万+
IPC进程间通信(Inter-Process Communication)就是指多个进程之间相互通信，交换信息的方法。Linux IPC基本上都是从Unix平台上继承而来的。主要包括最初的Unix IPC，System V IPC以及基于Socket的IPC。另外，Linux也支
android_device_xiaomi_msm8937-常见：WIP
02-26
小米MSM8937的常见设备配置 版权 # # Copyright (C) 2016 The CyanogenMod Project # Copyright (C) 2017 The LineageOS Project # # Licensed under the Apache License, Version 2.0 (the "License"); # you may ...
msm_fbdev.rar_Linux/Unix编程_Unix_Linux_
08-11
fbdev funcs
qualcomm cdma technologies msm 驱动
11-24
qualcomm cdma technologies msm 驱动 Quectel_BG96_Windows_USB_Driver_V1.0-usb驱动 板卡所带，win7平台可用
drm.zip_DRM_VYHJ_duringgbk_linux drm headers_msm_drm.
09-24
linux header for drm as requested
高通wifi芯片常用日志抓取方法
pchaojin123的专栏
06-12 2220
1、icnss日志抓取方法adb shell cat /d/ipc_logging/icnss/log_cont &gt; icnss.log 
关于内核打印信息的查看
LEAD_SOLO的专栏
04-13 1845
第一个ipc_logging cat sys/kernel/debug/ipc_logging/xxxx/xxx 第二个 此外,打印中还经常看到pr_debug函数，可以动态的打印调试信息（http://blog.csdn.net/weiqifa0/article/details/44038907） 如要打开该函数，只需在内核中配置CONFIG_DYNAMIC_DEBUG,并且
ipc logging
Fybon的专栏
02-14 3051
ipc log
【SDX62】IPA log抓取操作说明
wgl307293845的博客
06-20 652
IPA log抓取
Linux ALSA声卡驱动
hong
02-22 9628
概述ALSA是Advanced Linux Sound Architecture 的缩写，目前已经成为了linux的主流音频体系结构，想了解更多的关于ALSA的这一开源项目的信息和知识，请查看以下网址：http://www.alsa-project.org/。在内核设备驱动层，ALSA提供了alsa-driver，同时在应用层，ALSA为我们提供了alsa-lib，应用程序只要调用alsa-lib提
flex: QNX_HOST environment variable not set. make[2]: *** [scripts/Makefile.host:9: scripts/kconfig/lexer.lex.c] Error 1 make[1]: *** [/home/rli16/APU_ANDROID/kernel/msm-5.4/Makefile:608: vendor/autogvm-qgki-debug_defconfig] Error 2 make[1]: Leaving directory '/home/rli16/APU_ANDROID/out/target/product/msmnile_gvmq/obj/kernel/msm-5.4' make: *** [Makefile:183: sub-make] Error 2
最新发布
06-03
如果您使用的是第三方编译工具链，请确保它与您的目标平台兼容，并按照工具链文档进行设置和配置。 3. 如果您仍然遇到问题，请尝试清除编译目录并重新编译。您可以使用以下命令清除编译目录： ``` make clean ``` ...

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

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

请填写红包祝福语或标题

个

红包个数最小为10个

元

红包金额最低5元

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

抵扣说明：

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

余额充值