Simon Glass
4aa5053da5
timer: Tidy up use of notrace ...
Tracing is typically enabled by the time driver model starts up, so there
is no point in adding a 'notrace' to the timer-init function. However,
once the driver model timer is enabled, we do need to be able to access
the timer's private data when reading the timer, so add it to the core
function needed for that.
Update the function's documentation while we are here.
Signed-off-by: Simon Glass <sjg@chromium.org>
2023-02-11 12:22:34 -05:00
2023-01-12 16:25:51 +01:00
2023-01-23 18:11:40 -05:00
2023-01-23 18:11:41 -05:00
2022-12-05 16:06:08 -05:00
2022-12-02 08:39:00 -05:00
2023-02-10 12:50:01 -05:00
2023-02-10 07:41:40 -05:00
2023-02-11 12:22:34 -05:00
2023-01-18 12:46:13 -05:00
2023-02-10 07:41:39 -05:00
2023-01-30 21:02:27 +01:00
2022-12-22 10:31:48 -05:00
2023-02-10 07:41:41 -05:00
2023-01-18 13:11:13 -05:00
2023-02-07 14:33:48 -05:00
2022-10-31 14:47:32 -04:00
2023-02-10 12:50:00 -05:00
2023-02-10 12:50:00 -05:00
2023-02-10 13:41:06 -05:00
2023-01-27 14:47:58 -05:00
2022-11-02 13:58:17 -04:00
2022-12-08 18:06:27 +02:00
2022-12-08 18:06:27 +02:00
2023-02-09 16:32:25 -05:00
2023-02-10 07:41:40 -05:00
2023-02-07 14:33:49 -05:00
2023-02-10 13:41:07 -05:00
2023-01-23 18:11:41 -05:00
2023-02-07 14:33:49 -05:00
2023-02-10 07:41:40 -05:00
2023-02-10 08:22:52 -05:00
2023-02-07 14:33:49 -05:00
2022-12-23 10:10:40 -05:00
2023-01-20 12:27:24 -05:00
2023-01-20 12:27:24 -05:00
2023-01-11 11:54:50 -05:00
2023-01-05 10:06:35 +02:00
2023-02-07 14:33:49 -05:00
2023-01-23 18:11:41 -05:00
2023-02-10 07:41:41 -05:00
2023-01-24 13:55:05 +01:00
2022-12-05 17:43:21 +01:00
2023-02-10 07:41:41 -05:00
2022-10-29 07:36:33 -06:00
2023-02-10 07:41:41 -05:00
2023-01-20 10:04:56 +02:00
2023-02-11 12:22:34 -05:00
2023-02-10 07:41:40 -05:00
2023-01-20 12:27:24 -05:00
2023-02-11 09:25:44 -05:00
2023-02-10 07:41:41 -05:00
2023-02-06 13:04:53 -05:00
2022-10-29 07:36:33 -06:00
2023-01-20 12:27:23 -05:00
2023-02-10 07:41:41 -05:00
2022-12-08 18:06:27 +02:00
2023-02-07 14:33:49 -05:00
4aa5053da5