From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1751135AbbIEIrz (ORCPT ); Sat, 5 Sep 2015 04:47:55 -0400 Received: from www.linutronix.de ([62.245.132.108]:57451 "EHLO Galois.linutronix.de" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1750838AbbIEIru (ORCPT ); Sat, 5 Sep 2015 04:47:50 -0400 Date: Sat, 5 Sep 2015 10:46:51 +0200 (CEST) From: Thomas Gleixner To: "Hall, Christopher S" cc: Peter Zijlstra , Richard Cochran , "Kirsher, Jeffrey T" , "hpa@zytor.com" , "mingo@redhat.com" , "john.stultz@linaro.org" , "x86@kernel.org" , "linux-kernel@vger.kernel.org" , "netdev@vger.kernel.org" , "intel-wired-lan@lists.osuosl.org" Subject: RE: [PATCH v3 1/4] Add correlated clocksource deriving system time from an auxiliary clocksource In-Reply-To: Message-ID: References: <1440183128-1384-1-git-send-email-christopher.s.hall@intel.com> <1440183128-1384-2-git-send-email-christopher.s.hall@intel.com> <20150904151021.GF18489@twins.programming.kicks-ass.net> <20150904151743.GB16862@localhost.localdomain> <20150904154133.GI18489@twins.programming.kicks-ass.net> User-Agent: Alpine 2.11 (DEB 23 2013-08-11) MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII X-Linutronix-Spam-Score: -1.0 X-Linutronix-Spam-Level: - X-Linutronix-Spam-Status: No , -1.0 points, 5.0 required, ALL_TRUSTED=-1,SHORTCIRCUIT=-0.0001 Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Fri, 4 Sep 2015, Hall, Christopher S wrote: > > Right, but we still do not know how that is going to be used. And > > that's the key question. As long as that is not answered all can do is > > wild guessing. > > It's not wild guessing. We do have it working on other OSs and have > a pretty good idea of how it will work. The DSP firmware will be > largely identical for Linux. I think now, we have a chicken and egg > problem. You have a totally different problem. You are just refusing to explain how all that stuff is supposed to work and what kind of functionality you need exactly. Is it that hard to describe the technical requirements and the presumably assbackwards restrictions of the firmware? Thanks, tglx