Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1752423AbaKJT0X (ORCPT ); Mon, 10 Nov 2014 14:26:23 -0500 Received: from mail-vc0-f177.google.com ([209.85.220.177]:53100 "EHLO mail-vc0-f177.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1751746AbaKJT0V (ORCPT ); Mon, 10 Nov 2014 14:26:21 -0500 MIME-Version: 1.0 In-Reply-To: <20141110095325.GC12126@ulmo> References: <1415388855-35074-1-git-send-email-anatol.pomozov@gmail.com> <20141110095325.GC12126@ulmo> Date: Mon, 10 Nov 2014 11:26:20 -0800 Message-ID: Subject: Re: [PATCH] timekeeping: Move persistent clock registration code from ARM to kernel From: Anatol Pomozov To: Thierry Reding Cc: Stephen Warren , Daniel Lezcano , linux@arm.linux.org.uk, "tglx@linutronix.de" , LKML , "linux-tegra@vger.kernel.org" , Tony Lindgren , Mark Rutland Content-Type: text/plain; charset=UTF-8 Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Hi On Mon, Nov 10, 2014 at 1:53 AM, Thierry Reding wrote: > On Fri, Nov 07, 2014 at 11:34:15AM -0800, Anatol Pomozov wrote: >> ARM timekeeping functionality allows to register persistent/boot clock dynamically. >> This code is arch-independent and can be useful on other plaforms as well. >> >> As a byproduct of this change, tegra20_timer becomes ARM64 compatible. >> >> Tested: backported the change to chromeos-3.14 kernel ran on tegra 64bit >> board, made sure high-resolution clock works. > > Using this on an upstream kernel doesn't work, though, because 64-bit > ARM doesn't implement struct delay_timer which the driver needs since > v3.17. > > But I suppose the delay timer infrastructure could be moved into the > core similar to the persistent and boot clock as this patch does. Thanks. It makes sense, I will send it in a separate patch, once this one will be reviewed. On our kernel I haven't seen this issue as we still use 3.14. In fact none of arch/arm/lib/delay.c code seems ARM32 related. -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/