From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1753305Ab2L0Q74 (ORCPT ); Thu, 27 Dec 2012 11:59:56 -0500 Received: from hqemgate03.nvidia.com ([216.228.121.140]:6425 "EHLO hqemgate03.nvidia.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1752749Ab2L0Q7y (ORCPT ); Thu, 27 Dec 2012 11:59:54 -0500 X-PGP-Universal: processed; by hqnvupgp07.nvidia.com on Thu, 27 Dec 2012 08:56:37 -0800 Message-ID: <50DC7E8A.8000605@nvidia.com> Date: Thu, 27 Dec 2012 22:29:54 +0530 From: Laxman Dewangan User-Agent: Mozilla/5.0 (X11; U; Linux x86_64; en-US; rv:1.9.2.13) Gecko/20101208 Thunderbird/3.1.7 MIME-Version: 1.0 To: Marc Dietrich CC: "akpm@linuxfoundation.org" , "a.zummo@towertech.it" , "rtc-linux@googlegroups.com" , "linux-kernel@vger.kernel.org" , Stephen Warren Subject: Re: [PATCH V2] rtc: add RTC driver for TPS6586x References: <1356102748-722-1-git-send-email-ldewangan@nvidia.com> <7345841.MepJzddHFh@ax5200p> <50DC6242.1000404@nvidia.com> <2152592.FqkQ6Iyssd@ax5200p> In-Reply-To: <2152592.FqkQ6Iyssd@ax5200p> Content-Type: text/plain; charset="ISO-8859-1"; format=flowed Content-Transfer-Encoding: 7bit Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Thursday 27 December 2012 09:26 PM, Marc Dietrich wrote: > On Thursday 27 December 2012 20:29:14 Laxman Dewangan wrote: >> On Thursday 27 December 2012 08:26 PM, Marc Dietrich wrote: >>> Hi Laxman, >>> >>> On Friday 21 December 2012 20:42:28 you wrote: >>>> + >>>> + /* Set epoch start as 00:00:00:01:01:2000 */ >>>> + rtc->epoch_start = mktime(2000, 1, 1, 0, 0, 0); >>> any reason why you hard coded it to 2000? All boards I know use 2009, so >>> with this patch, everyone needs to set his clock again. >> No specific reason. If 2009 should be default then I can push patch to >> set it as 2009. > At least myself would appreciate this. > > Stephen said on IRC, that this could be configurable via a property node from > device tree (and also the IRQ which now comes from platform_data). Maybe this > can be added later on. I really like to see this driver in mainline now. I have not added platform data for setting epoch start time. I think we should be fine to hardcode in probe itself. The irq support is there as the mfd driver put proper alarm irq for rtc when it adds mfd sub devices. The ultimate irq number allocated run time through ird domain. I tested with RTC test wwhich is part of Documentation/rtc.txt.