[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <5630CE44.7070204@samsung.com>
Date: Wed, 28 Oct 2015 22:31:48 +0900
From: Krzysztof Kozlowski <k.kozlowski@...sung.com>
To: Alexandre Belloni <alexandre.belloni@...e-electrons.com>
Cc: k.kozlowski.k@...il.com, Alim Akhtar <alim.akhtar@...sung.com>,
Mark Brown <broonie@...nel.org>, lee.jones@...aro.org,
mturquette@...libre.com, linux-samsung-soc@...r.kernel.org,
linux-clk@...r.kernel.org, rtc-linux@...glegroups.com,
linux-kernel@...r.kernel.org
Subject: Re: [rtc-linux] Re: [PATCH v3 5/5] drivers/rtc/rtc-s5m.c: add support
for S2MPS15 RTC
W dniu 28.10.2015 o 18:48, Alexandre Belloni pisze:
> 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.
Nope, DTB does not contain the name for RTC driver (s2mps15-rtc). It
will be exactly the same.
>
> 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 ;)
In case of RTC driver there is no chance of DT ABI issues here.
The clock driver is different because it contain a compatible.
Best regards,
Krzysztof
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists