Hi, On 15/11/2017 at 15:30:21 +0800, Baolin Wang wrote: > It will be more helpful to add some tracepoints to track RTC actions when > debugging RTC driver. Below sample is that we set/read the RTC time, then > set 2 alarms, so we can see the trace logs: I'm not sure it is actually useful when debugging an RTC driver because you will be interested in the real values that are written to or read from the RTC, not what is returned by the driver to the RTC core as this information is already readily available to userspace. Is this really worth the added overhead? Maybe you have another use case? -- Alexandre Belloni, Free Electrons Embedded Linux and Kernel engineering http://free-electrons.com
