lists.openwall.net   lists  /  announce  owl-users  owl-dev  john-users  john-dev  passwdqc-users  yescrypt  popa3d-users  /  oss-security  kernel-hardening  musl  sabotage  tlsify  passwords  /  crypt-dev  xvendor  /  Bugtraq  Full-Disclosure  linux-kernel  linux-netdev  linux-ext4  linux-hardening  linux-cve-announce  PHC 
Open Source and information security mailing list archives
 
Hash Suite: Windows password security audit tool. GUI, reports in PDF.
[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Date:	Tue, 31 Mar 2015 10:56:15 +0200
From:	Krzysztof Kozlowski <k.kozlowski@...sung.com>
To:	rtc-linux@...glegroups.com
Cc:	Chanwoo Choi <cw00.choi@...sung.com>,
	Krzysztof Kozlowski <k.kozlowski@...sung.com>,
	Kukjin Kim <kgene@...nel.org>,
	Alessandro Zummo <a.zummo@...ertech.it>,
	devicetree@...r.kernel.org, linux-kernel@...r.kernel.org,
	linux-arm-kernel@...ts.infradead.org,
	linux-samsung-soc@...r.kernel.org,
	Kyungmin Park <kyungmin.park@...sung.com>
Subject: Re: [rtc-linux] Re: [PATCH 2/2] ARM: dts: s3c-rtc: Use s3c6410-rtc
 instead of exynos3250-rtc

2015-03-31 10:12 GMT+02:00 Alexandre Belloni
<alexandre.belloni@...e-electrons.com>:
> On 31/03/2015 at 09:47:15 +0900, Chanwoo Choi wrote :
>> > Are you absolutely sure that the exynos3250 IP is the same as the
>> > s3c6410 (I don't know much about the exynos family). The concern being
>> > that if at one point you have an errata on one or ther other, you will
>> > have to break the DT ABI by undoing this change.
>> >
>> > Note that I'm fine with it, I'm just asking.
>>
>> I'm sure about exynos3250 RTC is same with S3C6410 RTC.
>> There was little different about that pevious S3C6410 RTC
>> don't consider to control the 'rtc_src' clk.
>>
>>
>> But, Javier's patch[1] add the '.needs_src_clk' to control the
>> 'rtc_src' clk. After merged this patch, there is no different part between
>> Exynos3250 RTC and S3C6410 RTC.
>>
>> [1] 8792f7772f4f (drivers/rtc/rtc-s3c.c: add .needs_src_clk to s3c6410 RTC data)
>>
>
> Yes, I saw that the software was handling both the same way, I was
> asking about the hardware side.

The hardware is exactly the same. Or maybe I should say: I could not
find any differences.

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

Powered by Openwall GNU/*/Linux Powered by OpenVZ