Re: input_polldev interval (was Re: [sur40] Debugging a race condition)?

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



On March 24, 2015 11:52:54 PM PDT, Florian Echtler <floe@xxxxxxxxxxxxxx> wrote:
>Sorry for the continued noise, but this bug/crash is proving quite
>difficult to nail down.
>
>Currently, I'm setting the interval for input_polldev to 10 ms.
>However, with video data being retrieved at the same time, it's quite
>possible that one iteration of poll() will take longer than that. Could
>this ultimately be the reason? What happens if a new poll() call is
>scheduled before the previous one completes?

This can't happen as we schedule the next poll only after current one completes.

Hi Florian,
Thanks.

-- 
Dmitry
--
To unsubscribe from this list: send the line "unsubscribe linux-media" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at  http://vger.kernel.org/majordomo-info.html




[Index of Archives]     [Linux Input]     [Video for Linux]     [Gstreamer Embedded]     [Mplayer Users]     [Linux USB Devel]     [Linux Audio Users]     [Linux Kernel]     [Linux SCSI]     [Yosemite Backpacking]
  Powered by Linux