Re: [PATCH v1] PM: runtime: add tracepoint for runtime_status changes

2024-02-21 Thread Vilas Bhat
On Wed, Feb 21, 2024 at 10:33 AM Steven Rostedt wrote: > > On Wed, 21 Feb 2024 09:57:03 -0800 > Vilas Bhat wrote: > > > > You could do what everyone else does: > > > > > > #define RPM_STATUS_STRINGS \ > > > EM( RPM_INVALID, "RPM_INVALID" )\ > > > EM(

Re: [PATCH v1] PM: runtime: add tracepoint for runtime_status changes

2024-02-21 Thread Steven Rostedt
On Wed, 21 Feb 2024 09:57:03 -0800 Vilas Bhat wrote: > > You could do what everyone else does: > > > > #define RPM_STATUS_STRINGS \ > > EM( RPM_INVALID, "RPM_INVALID" )\ > > EM( RPM_ACTIVE, "RPM_ACTIVE" ) \ > > EM( RPM_RESUMING,

Re: [PATCH v1] PM: runtime: add tracepoint for runtime_status changes

2024-02-21 Thread Vilas Bhat
On Wed, Feb 21, 2024 at 9:12 AM Steven Rostedt wrote: > > On Wed, 21 Feb 2024 16:41:10 + > Vilas Bhat wrote: > > > > diff --git a/include/trace/events/rpm.h b/include/trace/events/rpm.h > > index 3c716214dab1..f1dc4e95dbce 100644 > > --- a/include/trace/events/rpm.h > > +++

Re: [PATCH v1] PM: runtime: add tracepoint for runtime_status changes

2024-02-21 Thread Steven Rostedt
On Wed, 21 Feb 2024 16:41:10 + Vilas Bhat wrote: > diff --git a/include/trace/events/rpm.h b/include/trace/events/rpm.h > index 3c716214dab1..f1dc4e95dbce 100644 > --- a/include/trace/events/rpm.h > +++ b/include/trace/events/rpm.h > @@ -101,6 +101,42 @@ TRACE_EVENT(rpm_return_int, >

[PATCH v1] PM: runtime: add tracepoint for runtime_status changes

2024-02-21 Thread Vilas Bhat
Existing runtime PM ftrace events (`rpm_suspend`, `rpm_resume`, `rpm_return_int`) offer limited visibility into the exact timing of device runtime power state transitions, particularly when asynchronous operations are involved. When the `rpm_suspend` or `rpm_resume` functions are invoked with the