Arch_ble_ext_WakeUp_on的目的是什么？

Hi,
我们正在使用SDK 5.0.4，我正在查看user_sleepmode示例。
It looks like the program listens to button-click interrupts in two cases.

The first case is during a connection. To begin listening,user_app_set_button_event被调用并执行：

wkupct_register_callback(user_app_button_press_cb);
wkupct_enable_irq（wkupct_pin_select（gpio_button_port，gpio_button_pin），
WKUPCT_PIN_POLARITY(GPIO_BUTTON_PORT, GPIO_BUTTON_PIN, next_event), // polarity
1，// 1事件
10);

和listening is stopped byuser_app_disable_button.这是一个电话wkupct_disable_irq（）;。
The listening callback (user_app_button_press_cb）也呼叫user_app_set_button_eventto keep listening to button clicks (actually it listens to switches in the button-mode, by choosing the right "next_event").

第二种情况是程序停止广告（10秒后）。什么时候user_app_adv_undirect_complete被称为状态GAP_ERR_CANCELED（即它是一个刻意的adv-stop）它呼叫：

ARCH_BLE_EXT_WAKEUP_ON（）;
// Configure wakeup button
app_button_enable（）;


The purpose ofARCH_BLE_EXT_WAKEUP_ON.是：“将BLE核心放在永久性睡眠中。只有一个外部事件可以唤醒它。”。It simply sets an internal flag to true.
Then,app_button_enable.呼叫:

app_easy_wakeup_set（app_wakeup_cb）;
wkupct_register_callback（app_button_press_cb）;
wkupct_enable_irq（wkupct_pin_select（gpio_button_port，gpio_button_pin），// select pin (GPIO_BUTTON_PORT, GPIO_BUTTON_PIN)
wkupct_pin_polarity（gpio_button_port，gpio_button_pin，wkupct_pin_polarity_low），//极性低
1，// 1事件
40）;


i.e. it savesapp_wakeup_cb.aside to be called in the future byapp_easy_wakeup，并对第一种情况运行类似的代码，以便开始侦听按钮中断。
发生中断时，app_button_press_cb被调用并执行：

if (GetBits16(SYS_STAT_REG, PER_IS_DOWN))
{
periph_init（）;
}
......

If I understand correctly, this code must be called in external wakeup during deep-sleep (Is it harmful to call it when using extended sleep?).
Then, the app_button_press_cb continues by calling:

if（arch_ble_ext_wakeup_get（）））
{
ARCH_SET_SLEEP_MODE（app_default_sleep_mode）;
ARCH_BLE_FORCE_WAKEUP（）;
ARCH_BLE_EXT_WAKEUP_OFF.();
app_easy_wakeup（）;
}

i.e. it checks that the external-wakeup-flag is on, initializes the sleep-mode (app_default_sleep_mode is deep-sleep), wakes up the BLE, turn off the external-wakeup flag (i.e. timers and BLE events can now wake up too) and callsapp_easy_wakeup()(which callsapp_wakeup_cb.as I explained before).

What are the advantages of the mechanism in the second case? We could avoid callingARCH_BLE_EXT_WAKEUP_ON（）然后我们不必重新配置睡眠模式并重新唤醒BLE。什么是呼唤的点ARCH_BLE_EXT_WAKEUP_ON（）if the program doesn't have any timers and doesn't advertise (i.e. timers and BLE events cannot wake up the program无论如何- 只有一个外部唤醒罐）。

Will the program consume less power during deep-sleep if we useARCH_BLE_EXT_WAKEUP_ON.？

第二个案例如何从未拨打电话wkupct_disable_irq()？后会睡觉ARCH_BLE_EXT_WAKEUP_ON.意味着您不必打电话wkupct_disable_irq()醒来后？

谢谢，
oren zomer.