Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1755727AbdC1NHH (ORCPT ); Tue, 28 Mar 2017 09:07:07 -0400 Received: from foss.arm.com ([217.140.101.70]:48196 "EHLO foss.arm.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1755544AbdC1NHC (ORCPT ); Tue, 28 Mar 2017 09:07:02 -0400 Date: Tue, 28 Mar 2017 14:05:52 +0100 From: Mark Rutland To: Fu Wei Cc: Jon Masters , "Rafael J. Wysocki" , Len Brown , Daniel Lezcano , Thomas Gleixner , Marc Zyngier , Lorenzo Pieralisi , Sudeep Holla , Hanjun Guo , linux-arm-kernel@lists.infradead.org, Linaro ACPI Mailman List , Linux Kernel Mailing List , ACPI Devel Maling List , rruigrok@codeaurora.org, "Abdulhamid, Harb" , Christopher Covington , Timur Tabi , G Gregory , Al Stone , Jon Masters , Wei Huang , Arnd Bergmann , Catalin Marinas , Will Deacon , Suravee Suthikulpanit , Leo Duran , Wim Van Sebroeck , Guenter Roeck , linux-watchdog@vger.kernel.org, Tomasz Nowicki , Christoffer Dall , Julien Grall Subject: Re: [PATCH v22 00/11] acpi, clocksource: add GTDT driver and GTDT support in arm_arch_timer Message-ID: <20170328130552.GA8643@leverpostej> References: <20170321163122.9183-1-fu.wei@linaro.org> <1cc5a994-0af6-79ea-930d-44b3fc789427@jonmasters.org> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.5.21 (2010-09-15) Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 1305 Lines: 35 On Tue, Mar 28, 2017 at 08:34:12PM +0800, Fu Wei wrote: > Hi Jon, > > Thanks for your email > An hour ago, I just got some feedback from Lorenzo, will update my > patchset ASAP according to his suggestion. > > But I still need some feedback form Mark, I can see some progress here: > https://git.kernel.org/pub/scm/linux/kernel/git/mark/linux.git/log/?h=arch-timer/gtdt > > I guess I should rebase my patchset to his gtdt branch for v23. > > So now, I am waiting for Mark's feedback to move on. Sorry for the delay; I have not had the time to focus on this as I would like to. I'm happy with patches 1-4, but from patch 5 onwards, there's one change I'd like to see. I'd prefer that mmio timer frame rame N was always stored at arch_timer_mem::frame[N], rather than arch_timer_mem::frame[] being in an arbitrary order. That will make arch_timer_mem_frame::frame_nr redundant. To allow arch_timer_mem::frame[] this to be sparse, I'm happy to have a bool arch_timer_mem_frame::valid field that we set when probing each frame. Then we don't need arch_timer_mem::num_frames. This will make iterating over the frames far less confusing, and makes it simple to detect when a frame number is erroneously reused. Otherwise, I'm largely happy to pick the rest and apply any fixups myself. Thanks, Mark.