linux-clk.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Alim Akhtar <alim.akhtar@samsung.com>
To: Krzysztof Kozlowski <k.kozlowski@samsung.com>,
	Mark Brown <broonie@kernel.org>
Cc: 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: [PATCH v3 5/5] drivers/rtc/rtc-s5m.c: add support for S2MPS15 RTC
Date: Wed, 28 Oct 2015 09:03:47 +0530	[thread overview]
Message-ID: <5630421B.5010803@samsung.com> (raw)
In-Reply-To: <5630419F.1000300@samsung.com>



On 10/28/2015 09:01 AM, Krzysztof Kozlowski wrote:
> On 28.10.2015 12:14, Alim Akhtar wrote:
>> Hello,
>>
>> On 10/28/2015 07:47 AM, Krzysztof Kozlowski wrote:
>>> On 28.10.2015 10:53, Mark Brown wrote:
>>>> On Wed, Oct 28, 2015 at 10:29:56AM +0900, Krzysztof Kozlowski wrote:
>>>>
>>>>> If that's true, then don't add new compatibles, new names etc. Re-use.
>>>>> No new code needed, no changes needed. Keep it simple.
>>>>
>>>> Well, it depends - it can be useful to get the information about it
>>>> being a different part into DT so that if in future we realise that
>>>> there is some difference (perhaps a bug workaround even if the IP is
>>>> intended to be the same).  Though in the case of a MFD that information
>>>> can be obtained from the MFD for the device.
>>>
>>> We can always differentiate later and introduce new compatible.
>>> Declaring a compatible right now would be useful only if we really cared
>>> about using the workaround on older DTBs.
>>>
>>> Since I cannot judge the difference (I don't have the datasheet of
>>> S2MPS15) then I don't see the need of adding new compatible/name for the
>>> "same device".
>>>
>>> Of course maybe there is such need? Alim?
>>>
>> Well I did think of keeping the changes as minimal as possible, like
>> just have "{ "s2mps15-rtc",        S2MPS14X }", since I don't have
>> access to s2mps14 UM, I could not confirm that s2mps14 and s2mps15 are
>> exactly the same w.r.t rtc block. So I proposed the current changes.
>>
>> Well I do agree with Mark here, a name/compatible matching with the pmic
>> is good to at least avoid confusion while looking at the sysfs.
>
> What kind of confusion in sysfs? I don't see any... and already the
> s2mps14-rtc name is used for S2MPS11 and S2MPS14.
>
> 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.
>
ok, have request s2smp14 UM, will cross check and update accordingly.
Thanks.
> Best regards,
> Krzysztof
>

  reply	other threads:[~2015-10-28  3:33 UTC|newest]

Thread overview: 33+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-10-26 12:51 [PATCH v3 0/5] mfd: sec: add S2MPS15 PMIC support Alim Akhtar
2015-10-26 12:51 ` [PATCH v3 1/5] dt-bindings: mfd: s2mps11: add documentation for s2mps15 PMIC Alim Akhtar
2015-10-26 12:51 ` [PATCH v3 2/5] mfd: sec: Add support for S2MPS15 PMIC Alim Akhtar
2015-10-26 14:34   ` Lee Jones
2015-10-28  1:15     ` Krzysztof Kozlowski
2015-10-28  8:46       ` Lee Jones
2015-10-28 11:21         ` Alim Akhtar
2015-10-28 13:47           ` Krzysztof Kozlowski
2015-10-28 13:44         ` Krzysztof Kozlowski
2015-10-28 13:51           ` Lee Jones
2015-10-29  4:19             ` Alim Akhtar
2015-10-28  1:28   ` Krzysztof Kozlowski
2015-10-26 12:51 ` [PATCH v3 3/5] regulator: s2mps11: add support for S2MPS15 regulators Alim Akhtar
2015-10-26 12:51 ` [PATCH v3 4/5] clk: s2mps15: Add support for S2MPS15 clocks Alim Akhtar
2015-10-28  1:22   ` Krzysztof Kozlowski
2015-10-28  3:36     ` Alim Akhtar
2015-10-28  1:26   ` Krzysztof Kozlowski
2015-10-28  4:34     ` Krzysztof Kozlowski
2015-10-28  4:55       ` Alim Akhtar
2015-10-28  5:36         ` Krzysztof Kozlowski
2015-10-26 12:51 ` [PATCH v3 5/5] drivers/rtc/rtc-s5m.c: add support for S2MPS15 RTC Alim Akhtar
2015-10-27 22:59   ` [rtc-linux] " Alexandre Belloni
2015-10-28  1:29   ` Krzysztof Kozlowski
2015-10-28  1:53     ` Mark Brown
2015-10-28  2:17       ` Krzysztof Kozlowski
2015-10-28  3:14         ` Alim Akhtar
2015-10-28  3:31           ` Krzysztof Kozlowski
2015-10-28  3:33             ` Alim Akhtar [this message]
2015-10-28  9:48             ` [rtc-linux] " Alexandre Belloni
2015-10-28 10:30               ` Alim Akhtar
2015-10-28 13:35                 ` Krzysztof Kozlowski
2015-10-28 13:31               ` Krzysztof Kozlowski
2015-10-28 13:43                 ` Alexandre Belloni

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=5630421B.5010803@samsung.com \
    --to=alim.akhtar@samsung.com \
    --cc=broonie@kernel.org \
    --cc=k.kozlowski@samsung.com \
    --cc=lee.jones@linaro.org \
    --cc=linux-clk@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-samsung-soc@vger.kernel.org \
    --cc=mturquette@baylibre.com \
    --cc=rtc-linux@googlegroups.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).