Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1753123AbbHQBsK (ORCPT ); Sun, 16 Aug 2015 21:48:10 -0400 Received: from mailout2.samsung.com ([203.254.224.25]:54163 "EHLO mailout2.samsung.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1751440AbbHQBsG (ORCPT ); Sun, 16 Aug 2015 21:48:06 -0400 X-AuditID: cbfee68d-f79106d00000728c-77-55d13d537683 Message-id: <55D13D53.3060902@samsung.com> Date: Mon, 17 Aug 2015 10:48:03 +0900 From: Joonyoung Shim User-Agent: Mozilla/5.0 (X11; Linux i686; rv:31.0) Gecko/20100101 Thunderbird/31.7.0 MIME-version: 1.0 To: Krzysztof Kozlowski , rtc-linux@googlegroups.com Cc: linux-samsung-soc@vger.kernel.org, linux-kernel@vger.kernel.org, stable@vger.kernel.org, a.zummo@towertech.it, alexandre.belloni@free-electrons.com, sbkim73@samsung.com Subject: Re: [rtc-linux] [PATCH] rtc: s5m: fix to update ctrl register References: <1439455764-23526-1-git-send-email-jy0922.shim@samsung.com> <55CC6B28.5010707@samsung.com> <55CC7479.6080902@samsung.com> In-reply-to: <55CC7479.6080902@samsung.com> Content-type: text/plain; charset=utf-8 Content-transfer-encoding: 7bit X-Brightmail-Tracker: H4sIAAAAAAAAA+NgFlrOIsWRmVeSWpSXmKPExsWyRsSkWDfY9mKowaYfUhZLLl5lt+i4tpjJ 4vULQ4vLu+awWcw4v4/JYn9nB6PFxRVfmCwWbHzE6MDh8WTTRUaPPRNPsnn0bVnF6DF93k8m j8+b5AJYo7hsUlJzMstSi/TtErgy5p3/w1zwUKBi9utOtgbG5bxdjJwcEgImEhMbTrBD2GIS F+6tZ+ti5OIQEljBKNG9dBJTFyMHWFH3fU+I+FJGidZFz1ghnAdARQ+OM4N08wpoSXx484wJ xGYRUJU4d+cdI4jNJqAncWfbcbC4qECYxJkZHSwQ9YISPybfA7NFBHwlHqw8ygIylFlgA6PE vGNXwU4SFnCTmPDuJxPEtnZGiRmfVrOBJDgFtCX6p38EO49ZQF1iypRckDCzgLzE5jVvmUHq JQQesUv8XLqMHeIiAYlvkw+xQLwjK7HpADPEy5ISB1fcYJnAKDYLyU2zEKbOQjJ1ASPzKkbR 1ILkguKk9CJDveLE3OLSvHS95PzcTYzA+Dv971nvDsbbB6wPMQpwMCrx8Gr8uRAqxJpYVlyZ e4jRFOiIicxSosn5wCjPK4k3NDYzsjA1MTU2Mrc0UxLnVZT6GSwkkJ5YkpqdmlqQWhRfVJqT WnyIkYmDU6qBUciGgZObQ/t03Md+l8Xxjg+mT3Kd8mCO3gs+d9uCqROd+iuE29ZdZNIo+vP0 pJwYX29khrLxvL7VXffnus3VCX9489Ox17+DtuxnCt5p8VDwWeK9rTodK4OXvUk+Pt+l0+Xc pUti5+rZnxvtXL/8XsD/idYSfk+zNk74ZLf0vlba6c8Ss9d3zlBiKc5INNRiLipOBABJL0Dl ugIAAA== X-Brightmail-Tracker: H4sIAAAAAAAAA+NgFvrCIsWRmVeSWpSXmKPExsVy+t9jAd1g24uhBnsPiFosuXiV3aLj2mIm i9cvDC0u75rDZjHj/D4mi/2dHYwWF1d8YbJYsPERowOHx5NNFxk99kw8yebRt2UVo8f0eT+Z PD5vkgtgjWpgtMlITUxJLVJIzUvOT8nMS7dV8g6Od443NTMw1DW0tDBXUshLzE21VXLxCdB1 y8wBukVJoSwxpxQoFJBYXKykb4dpQmiIm64FTGOErm9IEFyPkQEaSFjDmDHv/B/mgocCFbNf d7I1MC7n7WLk4JAQMJHovu/ZxcgJZIpJXLi3nq2LkYtDSGApo0TromesEM4DRonuB8eZQap4 BbQkPrx5xgRiswioSpy7844RxGYT0JO4s+04WFxUIEzizIwOFoh6QYkfk++B2SICvhIPVh5l ARnKLLCBUWLesavsIAlhATeJCe9+MkFsa2eUmPFpNRtIglNAW6J/+kcmkFOZBdQlpkzJBQkz C8hLbF7zlnkCo8AsJDtmIVTNQlK1gJF5FaNEakFyQXFSeq5hXmq5XnFibnFpXrpecn7uJkZw jD+T2sF4cJf7IUYBDkYlHl6NPxdChVgTy4orcw8xSnAwK4nw3hW4GCrEm5JYWZValB9fVJqT WnyI0RQYCBOZpUST84HpJ68k3tDYxMzI0sjc0MLI2FxJnFd2w+ZQIYH0xJLU7NTUgtQimD4m Dk6pBkb5mcf4n57PZFF5eUz1P6/0UR39LZM1T0RYmr9ts326/XJ1iMa2jrWaU0+vtnNYmnJv Vl/PMZFS/9ki4irHOR/v0dr9U+5Kv2HS6yPVesqT1H+0h+paNPkaK+qsd3U9+2BGhNLurhSp kJscZhdSJzGoGfN/OK9q8yRkUsnERU/ML8/XtwjlK1ViKc5INNRiLipOBADriKl1BwMAAA== DLP-Filter: Pass X-MTR: 20000000000000000@CPGS X-CFilter-Loop: Reflected Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 2330 Lines: 65 On 08/13/2015 07:42 PM, Krzysztof Kozlowski wrote: > W dniu 13.08.2015 o 19:02, Krzysztof Kozlowski pisze: >> W dniu 13.08.2015 o 17:49, Joonyoung Shim pisze: >>> According to datasheet, the S2MPS13X and S2MPS14X should update write >>> buffer via setting WUDR bit to high after ctrl register is updated. >> >> Hi, >> >> I cannot find this information in S2MPS14 datasheet. On which page is it? >> >> >>> >>> If not, ALARM interrupt of rtc-s5m doesn't happen first time when i use >>> tools/testing/selftests/timers/rtctest.c test program and hour format is >>> used to 12 hour mode in Odroid-XU3 board. >> >> Two questions here: >> 1. Earlier you mentioned S2MPS1[34], now Odroid XU3 which has S2MPS11. >> Are you sure that this applies to all of them (S2MPS11, S2MPS13 and >> S2MP14)? There are some minor differences between them so I would not be >> surprised if only some of them required this action. >> >> 2. The driver operates in 24-hour omode. Actually it sets the 24-hour >> mode just before your new regmap_update_bits() call. What do you mean by >> 12-hour mode? >> >>> Signed-off-by: Joonyoung Shim >>> Cc: >> >> Thanks for putting a cc-stable tag. How far this should be ported? If >> this is needed only for S2MPS11 then v4.1. If all of them then probably >> for earlier version? >> >> Best regards, >> Krzysztof > > One more doubt. On my Odroid XU3 first and consecutive executions > (including first) of rtctest run fine. They pass. Can you describe > exactly observable issue and how to reproduce it? This is also important > as a reason for stable backport. I just tested it on next-20150810 with Odroid-XU3 board. First rtctest execution is blocked, # ./rtctest RTC Driver Test Example. Counting 5 update (1/sec) interrupts from reading /dev/rtc0: Any no progress. > > I tested it on next-20150729 on board with Hardkernel bootloader. Maybe > the bootloader sets 12-hour mode which cannot be switched to 24-hour? > My bootloader doesn't touch any registers of s5m-rtc. Thanks. -- 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/