RE: [PATCH v1] i2c: designware: save the preset value of DW_IC_SDA_HOLD

2016-08-30 Thread Lee, Zhuo-hao
l be called >> to reconfigure i2c controller. If sda_hold_time is zero, the chipset >> default hold time will be used, that will be too short for some >> platforms. Therefore, to have a better tolerance, the DW_IC_SDA_HOLD >> value should be kept by sda_hold_time. >

RE: [PATCH v1] i2c: designware: save the preset value of DW_IC_SDA_HOLD

2016-08-30 Thread Lee, Zhuo-hao
>On Sat, Aug 27, 2016 at 03:39:30PM +0800, Zhuo-hao Lee wrote: >> There are several ways to set the SDA hold time for i2c controller, >> including: Device Tree, built-in device properties and ACPI. However, >> if the SDA hold time is not specified by above method, we should read >> the value,

RE: [PATCH v3] alarmtimer: fix unexpected rtc interrupt when system resume from S3

2015-11-22 Thread Lee, Zhuo-hao
behavior. Thanks Lee, Zhuo-hao

RE: [PATCH v3] alarmtimer: fix unexpected rtc interrupt when system resume from S3

2015-11-22 Thread Lee, Zhuo-hao
behavior. Thanks Lee, Zhuo-hao

RE: [PATCH v2] alarmtimer: fix unexpected rtc interrupt when system resume from S3

2015-11-16 Thread Lee, Zhuo-hao
o reduce this periodic interrupt. The following call path enable hpet timer when system go to suspend, just for you reference :) alarmtimer_suspend --rtc_timer_start rtc_timer_enqueue --__rtc_set_alarm cmos_set_alarm ----------cmos_irq_enable hpet_set_rtc_irq_bit Than

RE: [PATCH v2] alarmtimer: fix unexpected rtc interrupt when system resume from S3

2015-11-16 Thread Lee, Zhuo-hao
o reduce this periodic interrupt. The following call path enable hpet timer when system go to suspend, just for you reference :) alarmtimer_suspend --rtc_timer_start rtc_timer_enqueue --__rtc_set_alarm cmos_set_alarm ----------cmos_irq_enable hpet_set_rtc_irq_bit Than

RE: [PATCH v2] alarmtimer: fix unexpected rtc interrupt when system resume from S3

2015-11-14 Thread Lee, Zhuo-hao
et_rtc_interrupt continuously until timer timeout. This patch only fixed (1). Fixing (1) can avoid (2). However, The (2) is another story which it is not covered by this patch. Thanks Lee, Zhuo-hao

RE: [PATCH v2] alarmtimer: fix unexpected rtc interrupt when system resume from S3

2015-11-14 Thread Lee, Zhuo-hao
et_rtc_interrupt continuously until timer timeout. This patch only fixed (1). Fixing (1) can avoid (2). However, The (2) is another story which it is not covered by this patch. Thanks Lee, Zhuo-hao

RE: [PATCH v2] alarmtimer: fix unexpected rtc interrupt when system resume from S3

2015-11-08 Thread Lee, Zhuo-hao
{ s = read(fd, , sizeof(uint64_t)); if (s != sizeof(uint64_t)) handle_error("read"); system("cat /proc/driver/rtc |grep rtc_time"); system("cat /proc/interrupts | grep -E 'CPU0|rtc0'"); exit(EXIT_SUCCESS);

RE: [PATCH v2] alarmtimer: fix unexpected rtc interrupt when system resume from S3

2015-11-08 Thread Lee, Zhuo-hao
{ s = read(fd, , sizeof(uint64_t)); if (s != sizeof(uint64_t)) handle_error("read"); system("cat /proc/driver/rtc |grep rtc_time"); system("cat /proc/interrupts | grep -E 'CPU0|rtc0'"); exit(EXIT_SUCCESS);