input_report APIs

最新推荐文章于 2024-07-23 17:59:33 发布
原创 最新推荐文章于 2024-07-23 17:59:33 发布 · 747 阅读 · 0 ·
CC 4.0 BY-SA版权
版权声明：本文为博主原创文章，遵循 CC 4.0 BY-SA 版权协议，转载请附上原文出处链接和本声明。

本文详细介绍了输入设备报告函数的实现细节，包括按键输入、相对输入、绝对输入、功能状态和开关状态的报告方法，以及同步和多触点报告的处理。
static inline void input_report_key(struct input_dev *dev, unsigned int code, int value)
{
    input_event(dev, EV_KEY, code, !!value);
}

static inline void input_report_rel(struct input_dev *dev, unsigned int code, int value)
{
    input_event(dev, EV_REL, code, value);
}

static inline void input_report_abs(struct input_dev *dev, unsigned int code, int value)
{
    input_event(dev, EV_ABS, code, value);
}

static inline void input_report_ff_status(struct input_dev *dev, unsigned int code, int value)
{
    input_event(dev, EV_FF_STATUS, code, value);
}

static inline void input_report_switch(struct input_dev *dev, unsigned int code, int value)
{
    input_event(dev, EV_SW, code, !!value);
}

static inline void input_sync(struct input_dev *dev)
{
    input_event(dev, EV_SYN, SYN_REPORT, 0);
}

static inline void input_mt_sync(struct input_dev *dev)
{
    input_event(dev, EV_SYN, SYN_MT_REPORT, 0);

}

by zhangshaoyan at May 20,2015.

linux input设备驱动
paomadi的专栏
12-21 4765
一. 输入设备结构体      1. input_dev 输入设备 struct input_dev { const char *name; //设备名 const char *phys; //设备系统层的物理路径 const char *uniq; // struct input_id id; //输入设备id 总线类型;厂商编号,产品id,产品版本 unsig
MT8788 Android11 tp 启动流程
weixin_69497160的博客
10-24 1855
MT8788 Android11 tp 启动流程
input驱动框架
鹤冲云霄的专栏
06-13 972
1. input框架介绍： linux input子系统主要
INPUT子系统驱动框架
weixin_56755662的博客
04-02 679
input 就是输入的意思，因此 input 子系统就是管理输入的子系统，和 pinctrl、gpio 子系统 一样，都是 Linux 内核针对某一类设备而创建的框架。比如按键输入、键盘、鼠标、触摸屏等 等这些都属于输入设备，不同的输入设备所代表的含义不同，按键和键盘就是代表按键信息， 鼠标和触摸屏代表坐标信息，因此在应用层的处理就不同，对于驱动编写者而言不需要去关心 应用层的事情，我们只需要按照要求上报这些输入事件即可。 #include <linux/types.h> #inclu..
input_report_XXX函数
02-06 1344
输入子系统设备通告各种事件通过input_report_XXX族函数   /* include/linux/input.h */   static inline void input_report_key(struct input_dev *dev, unsigned int code, int value) {          input_event(dev, EV_KEY, c
Linux驱动之INPUT子系统框架
Wang_XB_3434的博客
09-18 771
每日一个简单的驱动，日久方长，对Linux驱动就越来越熟悉，也越来容易学会写驱动程序。今日进行Linux INPUT子系统框架介绍。
Bluetooth HID Device example This example aims to show how to implement a Bluetooth HID device using the APIs provided by Classic Bluetooth HID profile. This example simulates a Bluetooth HID mouse device that periodically sends report to remote Bluetooth HID host after connection. The report indicates a horizontally moving pointer and can be observed on the display on the HID host side. If you want to build an HID device, this can be your first example to look at. How to use example Hardware Required This example is able to run on any commonly available ESP32 development board, e.g. ESP32-DevKitC. This example is supposed to connect to a Classic Bluetooth HID Host device, e.g. laptop or tablet. Configure the project idf.py menuconfig Check and enable Classic Bluetooth and Classic BT HID Device under Component config --> Bluetooth --> Bluedroid Options Build and Flash Build the project and flash it to the board, then run monitor tool to view serial output: idf.py -p PORT flash monitor (Replace PORT with the name of the serial port to use.) (To exit the serial monitor, type Ctrl-].) See the Getting Started Guide for full steps to configure and use ESP-IDF to build projects. Example Output The following log will be shown on the IDF monitor console: I (572) cpu_start: Starting scheduler on PRO CPU. I (0) cpu_start: Starting scheduler on APP CPU. I (663) BTDM_INIT: BT controller compile version [5688ed5] I (663) system_api: Base MAC address is not set I (663) system_api: read default base MAC address from EFUSE I (673) phy_init: phy_version 4670,719f9f6,Feb 18 2021,17:07:07 W (683) phy_init: failed to load RF calibration data (0xffffffff), falling back to full calibration I (1533) app_main: setting device name I (1533) esp_bt_gap_cb: event: 10 I (1543) app_main: setting cod major, peripheral I (3543) app_main: register hid device callback I (3543) app_main: starting hid device I (3543) esp_bt_hidd_cb: setting hid parameters I (3543) esp_bt_gap_cb: event: 10 I (3543) esp_bt_hidd_cb: setting hid parameters success! I (3553) esp_bt_hidd_cb: setting to connectable, discoverable I (3563) bt_address: my bluetooth address is 78:E3:6D:CD:02:2A I (3563) app_main: exiting The messages show the successful initialization of Bluetooth stack and HID application. ESP32 will become discoverable with the Bluetooth device name as "HID Mouse Example", by nearby Bluetooth HID Host device. Connect to ESP32 on the HID Host side, then finish bonding. After that the HID connection will be established. IDF monitor console will continue to print messages like: I (50663) esp_bt_gap_cb: authentication success: privacy_k65 I (50663) esp_bt_gap_cb: 64 a2 f9 69 57 a4 W (51443) BT_APPL: new conn_srvc id:20, app_id:1 I (51443) esp_bt_hidd_cb: connected to 64:a2:f9:69:57:a4 I (51443) esp_bt_hidd_cb: making self non-discoverable and non-connectable. I (51443) mouse_move_task: starting I (51463) esp_bt_hidd_cb: ESP_HIDD_SEND_REPORT_EVT id:0x00, type:1 I (51493) esp_bt_gap_cb: ESP_BT_GAP_MODE_CHG_EVT mode:2 I (51503) esp_bt_hidd_cb: ESP_HIDD_SEND_REPORT_EVT id:0x00, type:1 I (51553) esp_bt_hidd_cb: ESP_HIDD_SEND_REPORT_EVT id:0x00, type:1 I (51603) esp_bt_hidd_cb: ESP_HIDD_SEND_REPORT_EVT id:0x00, type:1 I (51653) esp_bt_hidd_cb: ESP_HIDD_SEND_REPORT_EVT id:0x00, type:1 I (51703) esp_bt_hidd_cb: ESP_HIDD_SEND_REPORT_EVT id:0x00, type:1 I (51753) esp_bt_hidd_cb: ESP_HIDD_SEND_REPORT_EVT id:0x00, type:1 I (51803) esp_bt_hidd_cb: ESP_HIDD_SEND_REPORT_EVT id:0x00, type:1 ESP32 will generate and send HID mouse reports periodically. On the screen of HID Host, the cursor will move horizontally from left to right and then right to left, and so on so forth. Troubleshooting For any technical queries, please open an issue on GitHub. We will get back to you soon. Example Breakdown Initial settings for Bluetooth HID device profile Bluetooth HID device requires the specific major and minor device type in the Class of Device (CoD), the following lines of source code performs the configuration of CoD: void app_main(void) { ... ESP_LOGI(TAG, "setting cod major, peripheral"); esp_bt_cod_t cod; cod.major = ESP_BT_COD_MAJOR_DEV_PERIPHERAL; esp_bt_gap_set_cod(cod, ESP_BT_SET_COD_MAJOR_MINOR); ... } Bluetooth HID device profile requires the information of service name, provide, device subclass, report descriptor for SDP server, as well as L2CAP QoS configurations from the application. Following lines in function app_main initialize these information fields: void app_main(void) { ... // Initialize HID SDP information and L2CAP parameters. // to be used in the call of `esp_bt_hid_device_register_app` after profile initialization finishes do { s_local_param.app_param.name = "Mouse"; s_local_param.app_param.description = "Mouse Example"; s_local_param.app_param.provider = "ESP32"; s_local_param.app_param.subclass = ESP_HID_CLASS_MIC; s_local_param.app_param.desc_list = hid_mouse_descriptor; s_local_param.app_param.desc_list_len = hid_mouse_descriptor_len; memset(&s_local_param.both_qos, 0, sizeof(esp_hidd_qos_param_t)); // don't set the qos parameters } while (0); // Report Protocol Mode is the default mode, according to Bluetooth HID specification s_local_param.protocol_mode = ESP_HIDD_REPORT_MODE; ESP_LOGI(TAG, "register hid device callback"); esp_bt_hid_device_register_callback(esp_bt_hidd_cb); ESP_LOGI(TAG, "starting hid device"); esp_bt_hid_device_init(); ... } The information is set to global struct s_local_param and will be used upon successful profile initialization, i.e. reception of ESP_HIDD_INIT_EVT which is generated after the call of esp_bt_hid_device_init(): void esp_bt_hidd_cb(esp_hidd_cb_event_t event, esp_hidd_cb_param_t *param) { ... switch (event) { case ESP_HIDD_INIT_EVT: if (param->init.status == ESP_HIDD_SUCCESS) { ESP_LOGI(TAG, "setting hid parameters"); esp_bt_hid_device_register_app(&s_local_param.app_param, &s_local_param.both_qos, &s_local_param.both_qos); } else { ESP_LOGE(TAG, "init hidd failed!"); } break; ... } ... } Determination of HID Report Mode There are two HID report modes: Report Protocol Mode and Boot Protocol Mode. The former is the default mode. The two report modes differ in the report contents and format. The example supports both of the two modes. Report Mode requires report descriptor to describe the usage and format of the reports. For Bluetooth HID device, the report descriptor shall be provided in the SDP server, which can be discovered and used by remote HID Host. Boot Mode only supports keyboards and mice, with pre-defined report formats. Therefore it does not require a report descriptor parser on the remote HID Host. It is originally used to simplify the design of PC BIOSs. The following code lines set Report Protocol Mode as the default Report Mode: void app_main(void) { ... // Report Protocol Mode is the default mode, according to Bluetooth HID specification s_local_param.protocol_mode = ESP_HIDD_REPORT_MODE; ... } Report Mode can be choosen by remote HID Host through the SET_PROTOCOL request: void esp_bt_hidd_cb(esp_hidd_cb_event_t event, esp_hidd_cb_param_t *param) { ... switch (event) { ... case ESP_HIDD_SET_PROTOCOL_EVT: ESP_LOGI(TAG, "ESP_HIDD_SET_PROTOCOL_EVT"); if (param->set_protocol.protocol_mode == ESP_HIDD_BOOT_MODE) { ESP_LOGI(TAG, " - boot protocol"); xSemaphoreTake(s_local_param.mouse_mutex, portMAX_DELAY); s_local_param.x_dir = -1; xSemaphoreGive(s_local_param.mouse_mutex); } else if (param->set_protocol.protocol_mode == ESP_HIDD_REPORT_MODE) { ESP_LOGI(TAG, " - report protocol"); } xSemaphoreTake(s_local_param.mouse_mutex, portMAX_DELAY); s_local_param.protocol_mode = param->set_protocol.protocol_mode; xSemaphoreGive(s_local_param.mouse_mutex); break; .... } .... } Report generation The example simulates a mouse by creating a FreeRTOS task that periodically generates and sends the HID mouse report: // move the mouse left and right void mouse_move_task(void* pvParameters) { const char* TAG = "mouse_move_task"; ESP_LOGI(TAG, "starting"); for(;;) { s_local_param.x_dir = 1; int8_t step = 10; for (int i = 0; i < 2; i++) { xSemaphoreTake(s_local_param.mouse_mutex, portMAX_DELAY); s_local_param.x_dir *= -1; xSemaphoreGive(s_local_param.mouse_mutex); for (int j = 0; j < 100; j++) { send_mouse_report(0, s_local_param.x_dir * step, 0, 0); vTaskDelay(50 / portTICK_PERIOD_MS); } } vTaskDelay(1000 / portTICK_PERIOD_MS); } } Function send_mouse_report is used to pack the information into a mouse HID report and sends it to HID Host, according to the Report Mode applied: // send the buttons, change in x, and change in y void send_mouse_report(uint8_t buttons, char dx, char dy, char wheel) { uint8_t report_id; uint16_t report_size; xSemaphoreTake(s_local_param.mouse_mutex, portMAX_DELAY); if (s_local_param.protocol_mode == ESP_HIDD_REPORT_MODE) { report_id = 0; report_size = REPORT_PROTOCOL_MOUSE_REPORT_SIZE; s_local_param.buffer[0] = buttons; s_local_param.buffer[1] = dx; s_local_param.buffer[2] = dy; s_local_param.buffer[3] = wheel; } else { // Boot Mode report_id = ESP_HIDD_BOOT_REPORT_ID_MOUSE; report_size = ESP_HIDD_BOOT_REPORT_SIZE_MOUSE - 1; s_local_param.buffer[0] = buttons; s_local_param.buffer[1] = dx; s_local_param.buffer[2] = dy; } esp_bt_hid_device_send_report(ESP_HIDD_REPORT_TYPE_INTRDATA, report_id, report_size, s_local_param.buffer); xSemaphoreGive(s_local_param.mouse_mutex); }
最新发布
08-11
### 3.1 ESP-IDF Bluetooth HID 设备示例概述 ESP-IDF 提供了 Bluetooth HID ...esp_ble_gatts_send_indicate(gattc_if, param->write.conn_id, report_handle, sizeof(report_data), report_data, false); ``` ###
nova源码分析--API（1）
lemonwsx的专栏
11-13 716
pike版的nova/cmd/api.py代码如下 import sys from oslo_log import log as logging from oslo_reports import guru_meditation_report as gmr import nova.conf from nova import config from nova import exception ...
MT6853 android11 TP fts_ts 驱动框架解析
look_distance的博客
10-22 975
MT6853 android11 TP fts_ts 驱动框架解析
ESP-IDF BT/BLE HID Host Demo ESP-IDF BLE HID Host Demo This demo use APIs which esp_hid component provided to create a Bluetooth dual mode hid host. After the program is started, the HID host will scan the surrounding Bluetooth HID device and try to connect to the last device which has been scanned. When the connection is successfully established, the HID host will dump the HID device information and can receive the data sent by the HID device. This example works in companion with the BLE HID Device Example How to Use Example Before project configuration and build, be sure to set the correct chip target using: idf.py set-target Hardware Required A development board with ESP32 SoC (e.g., ESP32-DevKitC, ESP-WROVER-KIT, etc.) A USB cable for Power supply and programming See Development Boards for more information about it. Configure the Project Build and Flash Build the project and flash it to the board, then run monitor tool to view serial output. idf.py -p PORT flash monitor (To exit the serial monitor, type Ctrl-].) See the Getting Started Guide for full steps to configure and use ESP-IDF to build projects. Example Output I (0) cpu_start: Starting scheduler on APP CPU. I (602) BTDM_INIT: BT controller compile version [d03a5d3] I (612) system_api: Base MAC address is not set I (612) system_api: read default base MAC address from EFUSE I (612) phy_init: phy_version 4670,719f9f6,Feb 18 2021,17:07:07 I (1332) ESP_HIDH_DEMO: SCAN... I (7212) ESP_HIDH_DEMO: SCAN: 1 results BLE: fc:f5:c4:3c:62:92, RSSI: -29, USAGE: GENERIC, APPEARANCE: 0x03c0, ADDR_TYPE: 'PUBLIC', NAME: ESP BLE HID2 I (7332) ESP_HID_GAP: BLE GAP SEC_REQ E (7702) BT_SMP: Value for numeric comparison = 125657 I (7702) ESP_HID_GAP: BLE GAP NC_REQ passkey:125657 W (7742) BT_SMP: FOR LE SC LTK IS USED INSTEAD OF STK I (7892) ESP_HID_GAP: BLE GAP KEY type = ESP_LE_KEY_PID I (7892) ESP_HID_GAP: BLE GAP KEY type = ESP_LE_KEY_LENC I (7892) ESP_HID_GAP: BLE GAP KEY type = ESP_LE_KEY_PENC I (7892) ESP_HID_GAP: BLE GAP KEY type = ESP_LE_KEY_LID I (8142) ESP_HID_GAP: BLE GAP AUTH SUCCESS I (9332) ESP_HIDH_DEMO: fc:f5:c4:3c:62:92 OPEN: ESP BLE HID2 BDA:fc:f5:c4:3c:62:92, Appearance: 0x03c0, Connection ID: 0 Name: ESP BLE HID2, Manufacturer: Espressif, Serial Number: 1234567890 PID: 0x05df, VID: 0x16c0, VERSION: 0x0100 Battery: Handle: 42, CCC Handle: 43 Report Maps: 2 Report Map Length: 38 VENDOR FEATURE REPORT, ID: 1, Length: 8, Permissions: 0x0a, Handle: 71, CCC Handle: 0 VENDOR OUTPUT REPORT, ID: 1, Length: 8, Permissions: 0x0a, Handle: 68, CCC Handle: 0 VENDOR INPUT REPORT, ID: 1, Length: 8, Permissions: 0x12, Handle: 64, CCC Handle: 65 Report Map Length: 111 CCONTROL INPUT REPORT, ID: 3, Length: 2, Permissions: 0x12, Handle: 85, CCC Handle: 86 I (9722) ESP_HIDH_DEMO: fc:f5:c4:3c:62:92 INPUT: CCONTROL, MAP: 1, ID: 3, Len: 2, Data: I (9722) ESP_HIDH_DEMO: 40 00 I (9812) ESP_HIDH_DEMO: fc:f5:c4:3c:62:92 INPUT: CCONTROL, MAP: 1, ID: 3, Len: 2, Data: I (9812) ESP_HIDH_DEMO: 00 00 I (11822) ESP_HIDH_DEMO: fc:f5:c4:3c:62:92 INPUT: CCONTROL, MAP: 1, ID: 3, Len: 2, Data: I (11822) ESP_HIDH_DEMO: 80 00 I (11912) ESP_HIDH_DEMO: fc:f5:c4:3c:62:92 INPUT: CCONTROL, MAP: 1, ID: 3, Len: 2, Data: I (11912) ESP_HIDH_DEMO: 00 00 I (13922) ESP_HIDH_DEMO: fc:f5:c4:3c:62:92 INPUT: CCONTROL, MAP: 1, ID: 3, Len: 2, Data: I (13922) ESP_HIDH_DEMO: 40 00 I (14012) ESP_HIDH_DEMO: fc:f5:c4:3c:62:92 INPUT: CCONTROL, MAP: 1, ID: 3, Len: 2, Data: I (14012) ESP_HIDH_DEMO: 00 00 I (16022) ESP_HIDH_DEMO: fc:f5:c4:3c:62:92 INPUT: CCONTROL, MAP: 1, ID: 3, Len: 2, Data: I (16022) ESP_HIDH_DEMO: 80 00 I (16112) ESP_HIDH_DEMO: fc:f5:c4:3c:62:92 INPUT: CCONTROL, MAP: 1, ID: 3, Len: 2, Data: I (16112) ESP_HIDH_DEMO: 00 00 I (18122) ESP_HIDH_DEMO: fc:f5:c4:3c:62:92 INPUT: CCONTROL, MAP: 1, ID: 3, Len: 2, Data: I (18122) ESP_HIDH_DEMO: 40 00 I (18212) ESP_HIDH_DEMO: fc:f5:c4:3c:62:92 INPUT: CCONTROL, MAP: 1, ID: 3, Len: 2, Data: I (18212) ESP_HIDH_DEMO: 00 00 ... Troubleshooting For any technical queries, please open an issue on GitHub. We will get back to you soon.
08-11
CCONTROL INPUT REPORT, ID: 3, Length: 2, Permissions: 0x12, Handle: 85, CCC Handle: 86 I (9722) ESP_HIDH_DEMO: fc:f5:c4:3c:62:92 INPUT: CCONTROL, MAP: 1, ID: 3, Len: 2, Data: I (9722) ESP_HIDH_DEMO: ...
Linux内核Input子系统初始化驱动架构.pdf
08-02
讲述linux 内核input 系统的框架，逻辑关系，驱动模型等。
嵌入式系统驱动高级【5】——input子系统
imysy_22_的博客
08-11 863
Input子系统
Input子系统框架（编写触摸屏驱动程序_基于QEMU）
xace007的博客
07-23 1181
这张图片展示了Linux输入系统的工作流程，从物理硬件获取输入数据，通过硬件驱动转换为标准事件，然后通过内核的输入子系统处理这些事件，最终提供给用户空间的应用程序使用。在实际使用中，你需要根据实际的硬件设计来调整设备树中的属性，确保它们正确地反映了你的硬件配置。图片展示了一个简化的流程图，描述了在Linux内核中，I2C输入设备驱动程序的组件和它们之间的交互方式。这个图示提供了一个高层次的视图，展示了Linux内核中输入设备驱动程序的组件和它们之间的交互方式。：字符串属性，用于标识设备的兼容信息。
8.input设备（input子系统）驱动
luoguoxian12的博客
07-07 2372
转自 https://edu.youkuaiyun.com/lecturer/505 朱老师物联网大讲堂 《5.linux驱动开发-第5部分-5.8.input子系统基础之按键》 第一部分、章节目录 5.8.1.什么是input子系统 5.8.2.input设备应用层编程实践1 5.8.3.input设备应用层编程实践2 5.8.4.input子系统架构总览1 5.8.5.input子系统架构总览2 5.8.6.输入核心层源码分析1 5.8.7.输入核心层源码分析2 5.8.8.输入事件驱动层源码分析 5.8.9.输
手把手教你写Linux设备驱动---input子系统(二)--按键驱动实现(一)(基于友善之臂4412开发板)...
weixin_34390105的博客
04-11 304
在上一节里，我们用一个应用程序实现了鼠标的控制，并控制鼠标用相对位移不断的画一个正方形，感觉非常有意思，这一节，我们将通过一个简单按键实例来真正的实现一个input设备驱动程序。 http://blog.youkuaiyun.com/morixinguan/article/details/69808832 在写Input驱动之前，我们要了解下这个结构体，在此，我们要...
嵌入式软件开发之------浅析linux驱动模型（六）input框架
lujian186的博客
07-22 602
Linux代码版本：linux3.0 开发板环境: tiny4412 导读：input框架是是针对的输入设备的特点抽象出来的驱动模型，如常见的鼠标、键盘、陀螺仪、ADC和温度传感等等各种各样的输入设备，都有一个明显的特点，就是采集到数据向系统报告，过程有高度的相似性。所以就将相似的地方抽象出来，驱动开发就剩下和硬件相关的部分。如input设备，只需要完成input_dev的相关参数设置，然后调用 ...
【嵌入式环境下linux内核及驱动学习笔记-（16）linux总线、设备、驱动模型之input框架】
weixin_45499326的博客
06-11 2762
qquad这部分可以在阅读完其它部分后，再来看这个总结，会有更清晰的认识。1、input子系统是一个针对输入类型硬件的高度标准化的驱动框架。2、在充分的归纳驱动行为的基础上，把驱动由3层1事件来实现。这3层从上到下就是（事件处理层、核心层、设备驱动层），而一个事件指的就是struct input_event。3、开发者只需要编写设备驱动层对应的驱动程序即可。事件处理层以及核心层的处理，由内核实现。而串起这些内核 处理的核心又是事件类型（EVENT TYPE)与事件码（EVENT CODE）。
input设备驱动开发
四季帆的博客
03-22 671
1. 作为输入设备的驱动开发者，需要做以下几步： 在驱动加载模块中，设置你的input设备支持的事件类型，类型参见表1设置； 注册中断处理函数，例如键盘设备需要编写按键的抬起、放下，触摸屏设备需要编写按下、抬起、绝对移动，鼠标设备需要编写单击、抬起、相对移动，并且需要在必要的时候提交硬件数据（键值/坐标/状态等等）； 将输入设备注册到输入子系统中。 表1：事件类型 EV_SYN 0x00 同步事件 EV_KEY 0x01 ...
Linux Input输入驱动架构记录
a372048518的专栏
05-01 894
Linux 输入驱动框架有三部分组成：输入设备驱动程序，输入子系统核心，输入事件驱动程序； 1，输入设备驱动程序初始化硬件设备寄存器，读取硬件信息，构造struct input_dev结构体实例，并将struct input_dev结构体实例注册到输入子系统核心；struct input_dev{ char *name; struct inp
评论
添加红包

请填写红包祝福语或标题

个

红包个数最小为10个

元

红包金额最低5元

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

抵扣说明：

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

余额充值