linux-toradex.git/drivers/rtc, branch colibri Linux kernel for Apalis and Colibri modules rtc: max77663: fix alarm reading bug 2012-09-06T21:33:42+00:00 Daniel Fu danifu@nvidia.com 2012-09-05T03:45:04+00:00 e81b06d36a924dcdf8bb0456e7a50d1634d0365f When reading alarm of RTC-max77663, it didn't set alrm->enabled correctly, if irq is masked, means disable alarm, alrm->enabled should be set to 0, else it should be 1. Change-Id: Id0b1ffd9a816643712f33624d7d52cbe7b66b3c3 Signed-off-by: Daniel Fu <danifu@nvidia.com> Reviewed-on: http://git-master/r/129593 Reviewed-by: Simone Willett <swillett@nvidia.com> Tested-by: Simone Willett <swillett@nvidia.com> 
When reading alarm of RTC-max77663, it didn't set alrm->enabled correctly,
if irq is masked, means disable alarm, alrm->enabled should be set to 0,
else it should be 1.

Change-Id: Id0b1ffd9a816643712f33624d7d52cbe7b66b3c3
Signed-off-by: Daniel Fu <danifu@nvidia.com>
Reviewed-on: http://git-master/r/129593
Reviewed-by: Simone Willett <swillett@nvidia.com>
Tested-by: Simone Willett <swillett@nvidia.com>
rtc: max77663: Set Alarm wday to its reset value 2012-09-05T10:46:39+00:00 Daniel Fu danifu@nvidia.com 2012-08-23T11:40:08+00:00 1a61c310b66245a73e021d786eea45c31cd9f6e9 The wday is configured only when disabled alarm. When enable alarm, set it to its default reset value 0x01, and not enable it, to prevent an error happened when re-read the alarm value into the virtualized generic layer at boot up in reading alarm setting of RTC. Bug 1034871 Change-Id: I8bfa997653edaaa286cf768c1827b5ab986f52cc Signed-off-by: Daniel Fu <danifu@nvidia.com> Reviewed-on: http://git-master/r/129398 Reviewed-by: Automatic_Commit_Validation_User GVS: Gerrit_Virtual_Submit Reviewed-by: Bharat Nihalani <bnihalani@nvidia.com> Reviewed-by: Jinyoung Park <jinyoungp@nvidia.com> 
The wday is configured only when disabled alarm.
When enable alarm, set it to its default reset value 0x01,
and not enable it, to prevent an error happened when re-read the
alarm value into the virtualized generic layer at boot up in
reading alarm setting of RTC.

Bug 1034871

Change-Id: I8bfa997653edaaa286cf768c1827b5ab986f52cc
Signed-off-by: Daniel Fu <danifu@nvidia.com>
Reviewed-on: http://git-master/r/129398
Reviewed-by: Automatic_Commit_Validation_User
GVS: Gerrit_Virtual_Submit
Reviewed-by: Bharat Nihalani <bnihalani@nvidia.com>
Reviewed-by: Jinyoung Park <jinyoungp@nvidia.com>
rtc: tps80031: register as mfd sub device 2012-08-07T15:44:53+00:00 Laxman Dewangan ldewangan@nvidia.com 2012-08-01T10:55:25+00:00 0bf836b37cef4345629ecd8efb1a3e7f30628525 register RTC driver of TPS80031 as mfd sub driver in place of adding it as a sub devices. This is inline with the mfd driver policy. Change-Id: I2f9c13478a1e85c9670dd7bc576ec761f2e24733 Signed-off-by: Laxman Dewangan <ldewangan@nvidia.com> Reviewed-on: http://git-master/r/121133 Reviewed-by: Automatic_Commit_Validation_User 
register RTC driver of TPS80031 as mfd sub
driver in place of adding it as a sub devices.
This is inline with the mfd driver policy.

Change-Id: I2f9c13478a1e85c9670dd7bc576ec761f2e24733
Signed-off-by: Laxman Dewangan <ldewangan@nvidia.com>
Reviewed-on: http://git-master/r/121133
Reviewed-by: Automatic_Commit_Validation_User
rtc/tegra: treat compilation warning as error 2012-07-31T21:58:23+00:00 schowdary schowdary@nvidia.com 2012-07-25T07:00:01+00:00 0069bc53613779f858fb190fca1e6f5562efa49a - Add compilation flag to treat warning as error bug 949219 Change-Id: Ic52b13519b817ab3861bd56692ec6b6da60edc48 Signed-off-by: schowdary <schowdary@nvidia.com> 
- Add compilation flag to treat warning as error

bug 949219

Change-Id: Ic52b13519b817ab3861bd56692ec6b6da60edc48
Signed-off-by: schowdary <schowdary@nvidia.com>
rtc: tps6591x: Prevent wrong date setting 2012-07-26T11:46:03+00:00 Preetham Chandru pchandru@nvidia.com 2012-07-20T05:31:26+00:00 9b30c9e8b7c3ec08f56a610644491125690e9ef2 This CL handles the following: 1. Prevents setting of wrong date in tps6591x_rtc_set_time(). For example the following case was not handled in rtc driver: if hwclock command wanted to set 31/Dec/1999 then our RTC driver was setting the date to 31/Dec/2099 and later on when hwclock read the date back it was getting a invalid date. Also, the hwclock command can only handle date upto the year 2038. 2. Sets STOP_RTC bit to one when the driver is initialized Bug 1012914 Bug 1017647 Signed-off-by: Preetham Chandru R <pchandru@nvidia.com> Change-Id: If8abfebe3ee6da05498deb38d7247ab265729c0c Reviewed-on: http://git-master/r/117298 Reviewed-by: Automatic_Commit_Validation_User Reviewed-by: Venu Byravarasu <vbyravarasu@nvidia.com> Reviewed-by: Kiran Adduri <kadduri@nvidia.com> Reviewed-by: Laxman Dewangan <ldewangan@nvidia.com> 
This CL handles the following:

	1. Prevents setting of wrong date in tps6591x_rtc_set_time().

For example the following case was not handled in rtc driver:
if hwclock command wanted to set 31/Dec/1999 then our RTC driver was
setting the date to 31/Dec/2099 and later on when hwclock read the
date back it was getting a invalid date.
Also, the hwclock command can only handle date upto the year 2038.

	2. Sets STOP_RTC bit to one when the driver is initialized

Bug 1012914
Bug 1017647
Signed-off-by: Preetham Chandru R <pchandru@nvidia.com>
Change-Id: If8abfebe3ee6da05498deb38d7247ab265729c0c
Reviewed-on: http://git-master/r/117298
Reviewed-by: Automatic_Commit_Validation_User
Reviewed-by: Venu Byravarasu <vbyravarasu@nvidia.com>
Reviewed-by: Kiran Adduri <kadduri@nvidia.com>
Reviewed-by: Laxman Dewangan <ldewangan@nvidia.com>
rtc: set alarm logging enable 2012-07-21T00:34:03+00:00 Bitan Biswas bbiswas@nvidia.com 2012-07-18T12:58:20+00:00 afe7f3c35b4d8b8b3bed8453bf64141aafdf26ad Set alarm logs enabled to help understand suspend stress failures Change-Id: I60644ff0e3fea813ae1140be1b71fc2694d95709 Signed-off-by: Bitan Biswas <bbiswas@nvidia.com> Reviewed-on: http://git-master/r/115361 Reviewed-by: Venu Byravarasu <vbyravarasu@nvidia.com> Reviewed-by: Automatic_Commit_Validation_User Reviewed-by: Jinyoung Park <jinyoungp@nvidia.com> Tested-by: Jinyoung Park <jinyoungp@nvidia.com> Reviewed-by: Laxman Dewangan <ldewangan@nvidia.com> 
Set alarm logs enabled to help understand suspend stress failures

Change-Id: I60644ff0e3fea813ae1140be1b71fc2694d95709
Signed-off-by: Bitan Biswas <bbiswas@nvidia.com>
Reviewed-on: http://git-master/r/115361
Reviewed-by: Venu Byravarasu <vbyravarasu@nvidia.com>
Reviewed-by: Automatic_Commit_Validation_User
Reviewed-by: Jinyoung Park <jinyoungp@nvidia.com>
Tested-by: Jinyoung Park <jinyoungp@nvidia.com>
Reviewed-by: Laxman Dewangan <ldewangan@nvidia.com>
rtc: max77663: avoid powering on system by RTC alarm. 2012-06-27T14:09:34+00:00 Jinyoung Park jinyoungp@nvidia.com 2012-05-15T08:42:32+00:00 781ed854b9aa91ebf3180dd5c1a258969f5a556a Clean RTC alarm and don't set new alarm during shutdown process. After powering off, we do not want Maxim PMIC automaticly boots caused by RTC alarm. Bug 985193 Signed-off-by: Haley Teng <hteng@nvidia.com> Reviewed-on: http://git-master/r/104773 (cherry picked from commit 0bd7f3163f73ba3cf87dadd6bc6fa35a538ac153) Change-Id: I7209407503b9f51dfb5b8f59d05c6fa8f04c6069 Signed-off-by: Jinyoung Park <jinyoungp@nvidia.com> Reviewed-on: http://git-master/r/110858 Reviewed-by: Automatic_Commit_Validation_User GVS: Gerrit_Virtual_Submit Reviewed-by: Bharat Nihalani <bnihalani@nvidia.com> 
Clean RTC alarm and don't set new alarm during shutdown process.
After powering off, we do not want Maxim PMIC automaticly boots caused
by RTC alarm.

Bug 985193

Signed-off-by: Haley Teng <hteng@nvidia.com>
Reviewed-on: http://git-master/r/104773
(cherry picked from commit 0bd7f3163f73ba3cf87dadd6bc6fa35a538ac153)

Change-Id: I7209407503b9f51dfb5b8f59d05c6fa8f04c6069
Signed-off-by: Jinyoung Park <jinyoungp@nvidia.com>
Reviewed-on: http://git-master/r/110858
Reviewed-by: Automatic_Commit_Validation_User
GVS: Gerrit_Virtual_Submit
Reviewed-by: Bharat Nihalani <bnihalani@nvidia.com>
rtc: tps80031: add msecure support 2012-06-01T20:01:56+00:00 Tom Cherry tcherry@nvidia.com 2012-05-22T01:38:13+00:00 31884ed13df71599102f8fff9fab30a89e07dd9f Bug 986402 Change-Id: Id12540e31f8d7d9a04d764ed012310a685eafb8d Signed-off-by: Tom Cherry <tcherry@nvidia.com> Reviewed-on: http://git-master/r/104269 Reviewed-by: Automatic_Commit_Validation_User GVS: Gerrit_Virtual_Submit Reviewed-by: Laxman Dewangan <ldewangan@nvidia.com> 
Bug 986402

Change-Id: Id12540e31f8d7d9a04d764ed012310a685eafb8d
Signed-off-by: Tom Cherry <tcherry@nvidia.com>
Reviewed-on: http://git-master/r/104269
Reviewed-by: Automatic_Commit_Validation_User
GVS: Gerrit_Virtual_Submit
Reviewed-by: Laxman Dewangan <ldewangan@nvidia.com>
rtc: tps6591x: Limiting years in the 0 - 99 range 2012-05-23T06:52:12+00:00 Venu Byravarasu vbyravarasu@nvidia.com 2012-05-16T10:15:45+00:00 3910362a2873687a41a9dd4c186e28b1451db7d0 As RTC can store year in the 0 - 99 range only, handling it accordingly bug 985890 Change-Id: Idcfb29028f482283ae2658579a3283c7d4f230f1 Signed-off-by: Venu Byravarasu <vbyravarasu@nvidia.com> Reviewed-on: http://git-master/r/102798 Reviewed-by: Automatic_Commit_Validation_User GVS: Gerrit_Virtual_Submit Reviewed-by: Bitan Biswas <bbiswas@nvidia.com> 
As RTC can store year in the 0 - 99 range only,
handling it accordingly

bug 985890

Change-Id: Idcfb29028f482283ae2658579a3283c7d4f230f1
Signed-off-by: Venu Byravarasu <vbyravarasu@nvidia.com>
Reviewed-on: http://git-master/r/102798
Reviewed-by: Automatic_Commit_Validation_User
GVS: Gerrit_Virtual_Submit
Reviewed-by: Bitan Biswas <bbiswas@nvidia.com>
rtc: tps6591x: Enable alarm interrupt for RTC_WKALM_SET ioctl 2012-05-15T22:12:19+00:00 Preetham Chandru pchandru@nvidia.com 2012-05-08T14:26:27+00:00 d03e84c4d981d65d7b7e68322ce02157c7e7a6c7 RTC_WKALM_SET ioctl should do two things: 1. Set alarm value 2. Enable alarm irq In the current implementation for RTC_WKALM_SET ioctl we are only setting the alarm value but not enabling the alarm irq and hence the system is not waking from lp0 state once the set alarm value expiries. For RTC_WKALM_SET ioctl, alarm->enabled will be set to one from userspace. So based on this condition we can differentiate between RTC_WKALM_SET & RTC_ALM_SET and accordingly enable alarm irq. Bug 978205 Signed-off-by: Preetham Chandru R <pchandru@nvidia.com> Change-Id: Ia35192e691ca116b13093f52873020f67c5c2f8d Reviewed-on: http://git-master/r/101447 Reviewed-by: Automatic_Commit_Validation_User Reviewed-by: Varun Wadekar <vwadekar@nvidia.com> 
RTC_WKALM_SET ioctl should do two things:
	1. Set alarm value
	2. Enable alarm irq
In the current implementation for RTC_WKALM_SET ioctl we are only setting
the alarm value but not enabling the alarm irq and hence the system
is not waking from lp0 state once the set alarm value expiries.
For RTC_WKALM_SET ioctl, alarm->enabled will be set to one from userspace.
So based on this condition we can differentiate between RTC_WKALM_SET &
RTC_ALM_SET and accordingly enable alarm irq.

Bug 978205
Signed-off-by: Preetham Chandru R <pchandru@nvidia.com>
Change-Id: Ia35192e691ca116b13093f52873020f67c5c2f8d
Reviewed-on: http://git-master/r/101447
Reviewed-by: Automatic_Commit_Validation_User
Reviewed-by: Varun Wadekar <vwadekar@nvidia.com>