Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S942734AbcJ0Ujf (ORCPT ); Thu, 27 Oct 2016 16:39:35 -0400 Received: from mail-oi0-f66.google.com ([209.85.218.66]:34419 "EHLO mail-oi0-f66.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S937573AbcJ0Ujc (ORCPT ); Thu, 27 Oct 2016 16:39:32 -0400 MIME-Version: 1.0 In-Reply-To: <20161027014509.GB14832@jelly> References: <1476761253-13450-1-git-send-email-deepa.kernel@gmail.com> <1476761253-13450-2-git-send-email-deepa.kernel@gmail.com> <20161027014509.GB14832@jelly> From: Deepa Dinamani Date: Thu, 27 Oct 2016 13:39:30 -0700 Message-ID: Subject: Re: [PATCH v2 1/4] uinput: Add ioctl for using monotonic/ boot times To: Peter Hutterer Cc: Dmitry Torokhov , linux-input@vger.kernel.org, Linux Kernel Mailing List , Arnd Bergmann , y2038 Mailman List Content-Type: text/plain; charset=UTF-8 Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 747 Lines: 18 > hmm, I'm a bit confused here. This is an in-kernel bit only (passing the > time through uinput events has no effect). So why do we need an ioctl here? > it's an in-kernel decision only anyway and the time in the events sent to > the evdev client should be dictated by what that client sets for the clock > type, right? This is for input events queued by the uinput driver for the virtual input device. This can be read through uinput_read() fops. I don't think anybody is doing a read on uinput nodes, so another option(Arnd and I considered this) could be not supporting reads on these nodes at all. This is not related to evdev events in the kernel. Currently, this timestamp could be the same format as the evdev timestamps or not. -Deepa