On 7/3/07, Albert Lee <albertcc@xxxxxxxxxx> wrote:
Recently the PLL input clock of Promise 2027x is sometimes detected higer than expected (e.g. 20.027 MHz compared to 16.714 MHz). It seems sometimes the mdelay() function is not as precise as it used to be. Per Alan's advice, HT or power management might affect the precision of mdelay(). This patch calls gettimeofday() to mesure the time elapsed and calculate the PLL input clock accordingly. Signed-off-by: Albert Lee <albertcc@xxxxxxxxxx> Cc: Alan Cox <alan@xxxxxxxxxxxxxxxxxxx> ---
Maybe Bahadir could also help to verify if it helps to his "hda lost interrupt" problem.
Hi, As per the "hda lost interrupt" problem, I tried 2.6.22 and it didn't make any difference. Then I tried 2.6.21 with pdc202xx_new.c file from 2.6.19 (the working one). I had to only retain pdcnew_config_drive_xfer_rate() from 2.6.21 to make it compile, and I still had the same result. I guess this means its a change outside the driver that breaks it on my platform? I will git-bisect and see. Thanks, Bahadir - To unsubscribe from this list: send the line "unsubscribe linux-ide" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
