From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S965350AbbJ1Kkb (ORCPT ); Wed, 28 Oct 2015 06:40:31 -0400 Received: from mailout1.samsung.com ([203.254.224.24]:37942 "EHLO mailout1.samsung.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1755647AbbJ1Kjx (ORCPT ); Wed, 28 Oct 2015 06:39:53 -0400 X-AuditID: cbfee690-f794e6d0000014de-5f-5630a5f7d054 Message-id: <5630A3E2.9010207@samsung.com> Date: Wed, 28 Oct 2015 16:00:58 +0530 From: Alim Akhtar User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:24.0) Gecko/20100101 Thunderbird/24.5.0 MIME-version: 1.0 To: Alexandre Belloni , Krzysztof Kozlowski Cc: Mark Brown , lee.jones@linaro.org, mturquette@baylibre.com, linux-samsung-soc@vger.kernel.org, linux-clk@vger.kernel.org, rtc-linux@googlegroups.com, linux-kernel@vger.kernel.org Subject: Re: [rtc-linux] Re: [PATCH v3 5/5] drivers/rtc/rtc-s5m.c: add support for S2MPS15 RTC References: <1445863883-5187-1-git-send-email-alim.akhtar@samsung.com> <1445863883-5187-6-git-send-email-alim.akhtar@samsung.com> <56302514.4090407@samsung.com> <20151028015323.GZ28319@sirena.org.uk> <56303054.8060804@samsung.com> <56303DA3.5020306@samsung.com> <5630419F.1000300@samsung.com> <20151028094853.GM22331@piout.net> In-reply-to: <20151028094853.GM22331@piout.net> Content-type: text/plain; charset=ISO-8859-1; format=flowed Content-transfer-encoding: 7bit X-Brightmail-Tracker: H4sIAAAAAAAAA+NgFtrKIsWRmVeSWpSXmKPExsWyRsSkVvf7UoMwgwM7lCw6ri1mspj68Amb xesXhhb3vx5ltPjYc4/V4vKuOWwWM87vY7K4eMrVYn9nB6MDp8f7G63sHk82XWT02DPxJJvH plWdbB53ru1h8+jbsorR4/MmuQD2KC6blNSczLLUIn27BK6MFS/PMBZM46z4cbOLtYFxBnsX IweHhICJxN136l2MnECmmMSFe+vZuhi5OIQEVjBKrHl4lRkiYSIxrfsmK0RiFqPE6qdLGCGc B4wS/6ZNZAKp4hXQklh6/hYriM0ioCpx6fYDNhCbTUBb4u70LUwg20QFIiQeXxCCKBeU+DH5 HguILSKQK/H19E92kJnMAhcYJe7PnwuWEBZIkHiyphVsppDAeSaJbd/MQGxOAX2Jrl+vGEFs ZgFriZWTtkHZ8hKb17xlBhkkIfCVXeL6+dvsEAcJSHybfIgF4mVZiU0HoD6TlDi44gbLBEax WUhumoVk7CwkYxcwMq9iFE0tSC4oTkovMtErTswtLs1L10vOz93ECIzN0/+eTdjBeO+A9SFG AQ5GJR5egwq9MCHWxLLiytxDjKZAV0xklhJNzgcmgLySeENjMyMLUxNTYyNzSzMlcd7XUj+D hQTSE0tSs1NTC1KL4otKc1KLDzEycXBKNTDyfY9b6/bE8FnLEj4b7bpC/lKeW1yTVZzVWVra H8zbOrXOqfLhdc4ZtxvYv52rSIyedHtNc4C5IOfcjCc3JZhPr10X/+rvAYkE7fn5y3kW3dHQ 7pMRb8zljQhSlWvWu39M5au8wfvtSzLq9lfPYS3rWTb7Z2yLdEXLMvaa9cuUls3k9N7rr6/E UpyRaKjFXFScCACzixyoyAIAAA== X-Brightmail-Tracker: H4sIAAAAAAAAA+NgFmpmleLIzCtJLcpLzFFi42I5/e+xoO73pQZhBhf3SFt0XFvMZDH14RM2 i9cvDC3ufz3KaPGx5x6rxeVdc9gsZpzfx2Rx8ZSrxf7ODkYHTo/3N1rZPZ5susjosWfiSTaP Tas62TzuXNvD5tG3ZRWjx+dNcgHsUQ2MNhmpiSmpRQqpecn5KZl56bZK3sHxzvGmZgaGuoaW FuZKCnmJuam2Si4+AbpumTlAlykplCXmlAKFAhKLi5X07TBNCA1x07WAaYzQ9Q0JgusxMkAD CWsYM1a8PMNYMI2z4sfNLtYGxhnsXYycHBICJhLTum+yQthiEhfurWfrYuTiEBKYxSix+ukS RgjnAaPEv2kTmUCqeAW0JJaevwXWwSKgKnHp9gM2EJtNQFvi7vQtQDUcHKICERKPLwhBlAtK /Jh8jwXEFhHIlfh6+ic7yExmgQuMEvfnzwVLCAskSDxZ0wo2U0jgPJPEtm9mIDangL5E169X jCA2s4C1xMpJ26BseYnNa94yT2AEOhNhxywkZbOQlC1gZF7FKJFakFxQnJSea5iXWq5XnJhb XJqXrpecn7uJEZwAnkntYDy4y/0QowAHoxIP788i/TAh1sSy4srcQ4wSHMxKIrzfWgzChHhT EiurUovy44tKc1KLDzGaAgNhIrOUaHI+MDnllcQbGpuYmxqbWppYmJhZKonzXsjQCBMSSE8s Sc1OTS1ILYLpY+LglGpgvMiX7dvqXS3NOGXFn18NyVn3ue4/nr7+a/JxN8lnFzdb5Z984fbn akDCRwtbqVVefS98dwWsOGyxWcfBzo17QlT77JNKAVuu1y6a5rVlbwKf7We1XTO+zE2RWXwk 6LiXcqsm04dD5x6eyvm8uEhBO3Tb93PbIvdlcB6NvLT20PPNlUsOGs5zWqTEUpyRaKjFXFSc CABsrnHQFgMAAA== 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 Hi Alexandre, On 10/28/2015 03:18 PM, Alexandre Belloni wrote: > On 28/10/2015 at 12:31:43 +0900, Krzysztof Kozlowski wrote : >> The s2mps13 clock driver added new name and compatible... which was >> probably totally unneeded (I missed that during review). We don't have >> to make this as a rule... >> >> Since we do not have any data about future workarounds and the >> differences then just follow Ockham's razor - use the same name and >> compatible. >> > > So you don't care about DT backward compatibility because when a > workaround will be needed for one of the IPs, then you will have to > update the old dtb to use it. > > Unless you are sure that the IP is the same, doing > > { "s2mps15-rtc", S2MPS14X }, > > is probably the best way to handle that. Note that I personally don't > care about the DT ABI, I'm just pointing out what may happen ;) > Thats what my point is, anyway I am still looking into the fine prints of the s2mps15 and s2mps14 user manual, now I have found at least one difference in their one of the register bit, which might be a good reason to keep s2mps15-rtc device. Will update the same in v4. Thanks,