On 10/16, Viresh Kumar wrote:
> On 15-10-15, 12:04, Stephen Boyd wrote:
> > On 10/15, Viresh Kumar wrote:
> > > With debug options on, it is difficult to locate OPP core's debug
> > > prints. Fix this by prefixing OPP debug prints with KBUILD_MODNAME.
> > >
> > > Signed-off-by: Viresh Kumar
> >
On 15-10-15, 12:04, Stephen Boyd wrote:
> On 10/15, Viresh Kumar wrote:
> > With debug options on, it is difficult to locate OPP core's debug
> > prints. Fix this by prefixing OPP debug prints with KBUILD_MODNAME.
> >
> > Signed-off-by: Viresh Kumar
>
> Why not use dynamic debug's m flag to turn
On 10/15, Viresh Kumar wrote:
> With debug options on, it is difficult to locate OPP core's debug
> prints. Fix this by prefixing OPP debug prints with KBUILD_MODNAME.
>
> Signed-off-by: Viresh Kumar
Why not use dynamic debug's m flag to turn on KBUILD_MODNAME when
debugging?
>From Documentatio
With debug options on, it is difficult to locate OPP core's debug
prints. Fix this by prefixing OPP debug prints with KBUILD_MODNAME.
Signed-off-by: Viresh Kumar
---
drivers/base/power/opp/core.c | 2 ++
drivers/base/power/opp/cpu.c | 3 +++
2 files changed, 5 insertions(+)
diff --git a/driver
4 matches
Mail list logo