From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1751324AbbJEKul (ORCPT ); Mon, 5 Oct 2015 06:50:41 -0400 Received: from muru.com ([72.249.23.125]:55906 "EHLO muru.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1751188AbbJEKui (ORCPT ); Mon, 5 Oct 2015 06:50:38 -0400 Date: Mon, 5 Oct 2015 03:50:34 -0700 From: Tony Lindgren To: Daniel Lezcano Cc: Felipe Balbi , Linux OMAP Mailing List , Linux ARM Kernel Mailing List , Linux Kernel Mailing List , tglx@linutronix.de, John Stultz Subject: Re: [RFC/PATCH 09/11] clocksource: add TI 32.768 Hz counter driver Message-ID: <20151005105034.GU23801@atomide.com> References: <1443559446-26969-1-git-send-email-balbi@ti.com> <1443559446-26969-10-git-send-email-balbi@ti.com> <560DACD8.8000301@linaro.org> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <560DACD8.8000301@linaro.org> User-Agent: Mutt/1.5.23 (2014-03-12) Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org * Daniel Lezcano [151001 15:04]: > >+ clocks_calc_mult_shift(&persistent_mult, &persistent_shift, > >+ 32768, NSEC_PER_SEC, 120000); > >+ > >+ ret = clocksource_mmio_init(sync32k_cnt_reg, "32k_counter", 32768, > >+ 250, 32, clocksource_mmio_readl_up); > >+ if (ret) { > >+ pr_err("32k_counter: can't register clocksource\n"); > >+ return; > >+ } > >+ > >+ sched_clock_register(omap_32k_read_sched_clock, 32, 32768); > >+ register_persistent_clock(NULL, omap_read_persistent_clock64); > > I will let John Stultz to have a look at this part because I have doubt > regarding the usage of the persistent clock. The persistent clock we want to keep for deeper idle states.. Especially when we start changing clocksource for the duration of deeper idle states. I'll post some updated patches on that when I get a chance. Regards, Tony