Mainline:Broadcom Kona/BCM590xx/RTC - Revision history

Knuxify at 17:41, 15 August 2025

2025-08-15T17:41:04Z

← Older revision		Revision as of 19:41, 15 August 2025
Line 57:		Line 57:
	There are interrupts for updates of each of the time values.		There are interrupts for updates of each of the time values.

	The default reset value is <code>0 0 0 0 0 1 7</code> (2007-01-00 00:00:00, weekday 0). Notably, the day of month is invalid (0)~~. In this state, the RTCADJ interrupt will be raised~~.		The default reset value is <code>0 0 0 0 0 1 7</code> (2007-01-00 00:00:00, weekday 0). Notably, the day of month is invalid (0).

	If the date overflows (1 second after 2255-12-31 23:59:59), the clock returns to 2255-12-01 00:00:00.		If the date overflows (1 second after 2255-12-31 23:59:59), the clock returns to 2255-12-01 00:00:00.

Knuxify at 12:57, 15 August 2025

2025-08-15T12:57:56Z

← Older revision		Revision as of 14:57, 15 August 2025
Line 49:		Line 49:
	\|}		\|}

	This exact format is used for both the time and alarm registers. ~~In the time registers, the~~ masks are enforced by hardware - any bit written outside of the mask gets ignored.		This exact format is used for both the time and alarm registers. The masks are enforced by hardware - any bit written outside of the mask gets ignored.

	== Getting the time ==		== Getting the time ==

Knuxify at 12:47, 15 August 2025

2025-08-15T12:47:29Z

← Older revision		Revision as of 14:47, 15 August 2025
Line 60:		Line 60:

	If the date overflows (1 second after 2255-12-31 23:59:59), the clock returns to 2255-12-01 00:00:00.		If the date overflows (1 second after 2255-12-31 23:59:59), the clock returns to 2255-12-01 00:00:00.

			=== Adjustment IRQ ===

			There is an RTCADJ IRQ that is supposed to fire when the RTC value is invalid (at least according to the comments of the downstream driver, and the downstream BCM59055 RTC driver). However, I haven't been able to get it to fire in my testing.

	== Alarm ==		== Alarm ==

Knuxify: /* Getting the time */

2025-08-15T12:45:20Z

Getting the time

← Older revision		Revision as of 14:45, 15 August 2025
Line 58:		Line 58:

	The default reset value is <code>0 0 0 0 0 1 7</code> (2007-01-00 00:00:00, weekday 0). Notably, the day of month is invalid (0). In this state, the RTCADJ interrupt will be raised.		The default reset value is <code>0 0 0 0 0 1 7</code> (2007-01-00 00:00:00, weekday 0). Notably, the day of month is invalid (0). In this state, the RTCADJ interrupt will be raised.

			If the date overflows (1 second after 2255-12-31 23:59:59), the clock returns to 2255-12-01 00:00:00.

	== Alarm ==		== Alarm ==

Knuxify: /* Time data */

2025-08-15T12:44:06Z

Time data

← Older revision		Revision as of 14:44, 15 August 2025
Line 30:		Line 30:
	\|3		\|3
	\|Weekday (<code>WD</code>)		\|Weekday (<code>WD</code>)
	\|~~0x0F~~		\|0x07
	\|Day of week, from 0 to 6. Appears to roll over whenever the day changes; {{speculation\|the hardware does not enforce a specific start.}} Sets itself to 0 on reset. '''Not used in downstream.'''<br>{{speculation\|The day of month sets itself to 0 on reset, which should be an invalid value, but would suggest that the range is 0 -> Sunday, 6 -> Monday, but there is no downstream code to confirm this.}}		\|Day of week, from 0 to 6. Appears to roll over whenever the day changes; {{speculation\|the hardware does not enforce a specific start.}} Sets itself to 0 on reset. '''Not used in downstream.'''<br>{{speculation\|The day of month sets itself to 0 on reset, which should be an invalid value, but would suggest that the range is 0 -> Sunday, 6 -> Monday, but there is no downstream code to confirm this.}}
	\|-		\|-
Line 50:		Line 50:

	This exact format is used for both the time and alarm registers. In the time registers, the masks are enforced by hardware - any bit written outside of the mask gets ignored.		This exact format is used for both the time and alarm registers. In the time registers, the masks are enforced by hardware - any bit written outside of the mask gets ignored.

	~~TODO: What happens on year overflow? Is there a reason as to why the downstream driver limits the values it gets?~~

	== Getting the time ==		== Getting the time ==

Knuxify: /* Time data */

2025-08-15T12:38:57Z

Time data

← Older revision		Revision as of 14:38, 15 August 2025
Line 30:		Line 30:
	\|3		\|3
	\|Weekday (<code>WD</code>)		\|Weekday (<code>WD</code>)
	~~\|{{speculation~~\|0x0F}}		\|0x0F
	\|Day of week, from 0 to 6. Appears to roll over whenever the day changes; {{speculation\|the hardware does not enforce a specific start.}} Sets itself to 0 on reset. '''Not used in downstream.'''<br>{{speculation\|The day of month sets itself to 0 on reset, which should be an invalid value, but would suggest that the range is 0 -> Sunday, 6 -> Monday, but there is no downstream code to confirm this.}}		\|Day of week, from 0 to 6. Appears to roll over whenever the day changes; {{speculation\|the hardware does not enforce a specific start.}} Sets itself to 0 on reset. '''Not used in downstream.'''<br>{{speculation\|The day of month sets itself to 0 on reset, which should be an invalid value, but would suggest that the range is 0 -> Sunday, 6 -> Monday, but there is no downstream code to confirm this.}}
	\|-		\|-
Line 49:		Line 49:
	\|}		\|}

	This exact format is used for both the time and alarm registers.		This exact format is used for both the time and alarm registers. In the time registers, the masks are enforced by hardware - any bit written outside of the mask gets ignored.

	TODO: What happens on year overflow? Is there a reason as to why the downstream driver limits the values it gets?		TODO: What happens on year overflow? Is there a reason as to why the downstream driver limits the values it gets?

Knuxify at 12:21, 15 August 2025

2025-08-15T12:21:16Z

← Older revision		Revision as of 14:21, 15 August 2025
Line 59:		Line 59:
	There are interrupts for updates of each of the time values.		There are interrupts for updates of each of the time values.

	The default reset value is <code>0 0 0 0 0 1 7</code> (2007-01-00 00:00:00, weekday 0). Notably, the day of month is invalid (0).		The default reset value is <code>0 0 0 0 0 1 7</code> (2007-01-00 00:00:00, weekday 0). Notably, the day of month is invalid (0). In this state, the RTCADJ interrupt will be raised.

	== Alarm ==		== Alarm ==

Knuxify at 10:53, 15 August 2025

2025-08-15T10:53:41Z

← Older revision		Revision as of 12:53, 15 August 2025
Line 10:		Line 10:
	!Offset		!Offset
	!Purpose		!Purpose
			!Mask
	!Value		!Value
	\|-		\|-
	\|0		\|0
	\|Second (<code>SC</code>)		\|Second (<code>SC</code>)
			\|0x3F
	\|Current second, from 0 to 59.		\|Current second, from 0 to 59.
	\|-		\|-
	\|1		\|1
	\|Minute (<code>MN</code>)		\|Minute (<code>MN</code>)
			\|0x3F
	\|Current minute of the hour, from 0 to 59.		\|Current minute of the hour, from 0 to 59.
	\|-		\|-
	\|2		\|2
	\|Hour (<code>HR</code>)		\|Hour (<code>HR</code>)
			\|0x1F
	\|Current hour of the day, from 0 to 23.		\|Current hour of the day, from 0 to 23.
	\|-		\|-
	\|3		\|3
	\|Weekday (<code>WD</code>)		\|Weekday (<code>WD</code>)
	\|Day of week, from 0 to 6. ~~{{speculation\|~~Appears to roll over whenever the day changes; the hardware does not enforce a specific start.}} Sets itself to 0 on reset. {{speculation\|The day of month sets itself to 0 on reset, which should be an invalid value, but would suggest that the range is 0 -> Sunday, 6 -> Monday, but there is no downstream code to confirm this.}}		\|{{speculation\|0x0F}}
			\|Day of week, from 0 to 6. Appears to roll over whenever the day changes; {{speculation\|the hardware does not enforce a specific start.}} Sets itself to 0 on reset. '''Not used in downstream.'''<br>{{speculation\|The day of month sets itself to 0 on reset, which should be an invalid value, but would suggest that the range is 0 -> Sunday, 6 -> Monday, but there is no downstream code to confirm this.}}
	\|-		\|-
	\|4		\|4
	\|Day of month (<code>DT</code>)		\|Day of month (<code>DT</code>)
	\|Day of month, starting from 1. ~~{{speculation\|~~Sets itself to 0 on reset.}}		\|0x1F
			\|Day of month, starting from 1. Sets itself to 0 on reset.
	\|-		\|-
	\|5		\|5
	\|Month (<code>MT_WD</code>)		\|Month (<code>MT_WD</code>)
			\|0x0F
	\|Number of the month. 1 to 12 represent January-December.		\|Number of the month. 1 to 12 represent January-December.
	\|-		\|-
	\|6		\|6
	\|Year (<code>YR</code>)		\|Year (<code>YR</code>)
			\|0xFF
	\|Amount of years since 2000 (0 = 2000, 1 = 2001, etc.)		\|Amount of years since 2000 (0 = 2000, 1 = 2001, etc.)
	\|}		\|}

Knuxify: /* Getting the time */

2025-08-14T06:43:41Z

Getting the time

← Older revision		Revision as of 08:43, 14 August 2025
Line 51:		Line 51:
	There are interrupts for updates of each of the time values.		There are interrupts for updates of each of the time values.

	The default reset value is 2007-01-~~01 at~~ 00:00:00.		The default reset value is <code>0 0 0 0 0 1 7</code> (2007-01-00 00:00:00, weekday 0). Notably, the day of month is invalid (0).

	== Alarm ==		== Alarm ==

Knuxify at 06:03, 14 August 2025

2025-08-14T06:03:50Z

← Older revision		Revision as of 08:03, 14 August 2025
Line 26:		Line 26:
	\|3		\|3
	\|Weekday (<code>WD</code>)		\|Weekday (<code>WD</code>)
	\|Day of week; 0 ~~is Monday, 6 is Sunday~~. {{speculation\|~~todo~~, ~~verify~~}}		\|Day of week, from 0 to 6. {{speculation\|Appears to roll over whenever the day changes; the hardware does not enforce a specific start.}} Sets itself to 0 on reset. {{speculation\|The day of month sets itself to 0 on reset, which should be an invalid value, but would suggest that the range is 0 -> Sunday, 6 -> Monday, but there is no downstream code to confirm this.}}
	\|-		\|-
	\|4		\|4
	\|Day of month (<code>DT</code>)		\|Day of month (<code>DT</code>)
	\|Day of month, starting from 0.		\|Day of month, starting from 1. {{speculation\|Sets itself to 0 on reset.}}
	\|-		\|-
	\|5		\|5