[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-Id: <f47f86aa2bc1b96fbe47737f795ea1aee642caa0.1505973912.git.baolin.wang@linaro.org>
Date: Thu, 21 Sep 2017 14:18:08 +0800
From: Baolin Wang <baolin.wang@...aro.org>
To: perex@...ex.cz, tiwai@...e.com
Cc: lgirdwood@...il.com, mingo@...nel.org, o-takashi@...amocchi.jp,
elfring@...rs.sourceforge.net, dan.carpenter@...cle.com,
jeeja.kp@...el.com, vinod.koul@...el.com, dharageswari.r@...el.com,
guneshwor.o.singh@...el.com, bhumirks@...il.com,
gudishax.kranthikumar@...el.com, naveen.m@...el.com,
hardik.t.shah@...el.com, arvind.yadav.cs@...il.com, fabf@...net.be,
arnd@...db.de, broonie@...nel.org, deepa.kernel@...il.com,
baolin.wang@...aro.org, alsa-devel@...a-project.org,
linux-kernel@...r.kernel.org
Subject: [RFC PATCH 6/7] uapi: sound: Avoid using timespec for struct snd_ctl_elem_value
The struct snd_ctl_elem_value will use 'timespec' type variables to record
timestamp, which is not year 2038 safe on 32bits system.
Since there are no drivers will implemented the tstamp member of the
struct snd_ctl_elem_value, and also the stucture size will not be changed
if we change timespec to s64 for tstamp member of struct snd_ctl_elem_value.
Thus we can simply change timespec to s64 for tstamp member to avoid
using the type which is not year 2038 safe on 32bits system.
Signed-off-by: Baolin Wang <baolin.wang@...aro.org>
---
include/uapi/sound/asound.h | 4 ++--
1 file changed, 2 insertions(+), 2 deletions(-)
diff --git a/include/uapi/sound/asound.h b/include/uapi/sound/asound.h
index 1949923..71bce52 100644
--- a/include/uapi/sound/asound.h
+++ b/include/uapi/sound/asound.h
@@ -943,8 +943,8 @@ struct snd_ctl_elem_value {
} bytes;
struct snd_aes_iec958 iec958;
} value; /* RO */
- struct timespec tstamp;
- unsigned char reserved[128-sizeof(struct timespec)];
+ struct { s64 tv_sec; s64 tv_nsec; } tstamp;
+ unsigned char reserved[128-sizeof(struct { s64 tv_sec; s64 tv_nsec; })];
};
struct snd_ctl_tlv {
--
1.7.9.5
Powered by blists - more mailing lists