From mboxrd@z Thu Jan 1 00:00:00 1970 From: Tony Lindgren Subject: Re: [RFC/PATCH 09/11] clocksource: add TI 32.768 Hz counter driver Date: Mon, 5 Oct 2015 03:50:34 -0700 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 Return-path: Content-Disposition: inline In-Reply-To: <560DACD8.8000301@linaro.org> Sender: linux-kernel-owner@vger.kernel.org To: Daniel Lezcano Cc: Felipe Balbi , Linux OMAP Mailing List , Linux ARM Kernel Mailing List , Linux Kernel Mailing List , tglx@linutronix.de, John Stultz List-Id: linux-omap@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