gpio_button_init中的错误？ 极性和上拉/下拉

你好，安得烈：
我会调查这个问题，顺便问一下，当你配置GPIO函数时，你会遇到一些问题吗？
你现在使用的是哪个EVB或芯片？



     以下为原文
  Hi Andrew:
 
    I will look into this case, by the way do you meet some issues when you configure the GPIO functions?
and  which evb or chip you are using now?

我看到的问题是，片上PU/PD没有被正确激活。
修补这条线：
返回WICEDEGGPIOIOIIT（Button & Gt；GPIO，（Button & Gt；Durial=＝WieDeIdActhvithHig））？输入：PulthpulLyUp；
GPIOXButnOnEnable（）和WieDig-GPIOIN IpPuthGET（）的相应更改使我的配置与ButnOnMyMeor一样工作。芯片上的PU被打开，IRQ被调用，点击/保持/双击事件是可检测的。
我希望我没有错过一些明显的东西，这个逻辑看起来是颠倒的，但始终通过GPIOXBut纽库。
我不使用EVM，我正在定制设计的硬件（产品原型）。微型是STM32 F4。
我有一个单独的但后续的问题是按钮管理器在一个活跃的低按钮存在一定的噪声或缓慢上升的边缘时表现得很好，并且检测0或1ms持续时间事件，而不是一个限定的“点击”事件。如果有机会，我会跟进范围跟踪。



     以下为原文
  The issue that I was seeing was that that the on-chip PU/PD was not being activated correctly.
 
Patching this line to:
return wiced_gpio_init( button->gpio, ( button->polarity == WICED_ACTIVE_HIGH )? INPUT_PULL_DOWN: INPUT_PULL_UP );
 
and corresponding changes in gpio_button_enable() and wiced_gpio_input_get() make my configuration with button_manager work as expected. On chip PU is switched on, IRQ's are called, and click/hold/double click events are detectable.
 
I hope I am not missing something obvious; this logic just appears to be inverted, but consistently through the gpio_button library.
 
I'm not using an EVM, I am working on custom-designed hardware (product prototype). The micro is STM32F4.
 
A separate but follow-up issue I have is that button manager does perform too well in the presence of certain noise or slow rising edges for an active-low button, and detects 0 or 1ms duration events rather than a qualifying "click" event. I will follow up with scope traces, if I get a chance.

是的，这是一个错误
我提出了一个内部案例。
艾伦



     以下为原文
  Yes that is a bug
 
I filed an internal case.
 
Alan