All of lore.kernel.org
 help / color / mirror / Atom feed
From: Kevin Hilman <khilman@deeprootsystems.com>
To: "G, Manjunath Kondaiah" <manjugk@ti.com>
Cc: "felipe.balbi@nokia.com" <felipe.balbi@nokia.com>,
	"dedekind1@gmail.com" <dedekind1@gmail.com>,
	"linux-omap@vger.kernel.org" <linux-omap@vger.kernel.org>
Subject: Re: [PATCH] [OMAP3_PM] Fix zoom2 defconfig build
Date: Mon, 02 Nov 2009 09:10:52 -0800	[thread overview]
Message-ID: <87bpjklun7.fsf@deeprootsystems.com> (raw)
In-Reply-To: <E0D41E29EB0DAC4E9F3FF173962E9E940254037B8F@dbde02.ent.ti.com> (Manjunath Kondaiah G.'s message of "Mon\, 2 Nov 2009 22\:00\:35 +0530")

"G, Manjunath Kondaiah" <manjugk@ti.com> writes:

>> > diff --git a/arch/arm/mach-omap2/pm-debug.c 
>> b/arch/arm/mach-omap2/pm-debug.c
>> > index 767ebbc..3a42615 100644
>> > --- a/arch/arm/mach-omap2/pm-debug.c
>> > +++ b/arch/arm/mach-omap2/pm-debug.c
>> > @@ -625,4 +625,6 @@ arch_initcall(pm_dbg_init);
>> >
>> >  #else
>> >  void pm_dbg_update_time(struct powerdomain *pwrdm, int prev) {}
>> > +int pm_dbg_regset_init(int reg_set) {}
>> > +int pm_dbg_regset_save(int reg_set) {}
>> 
>> you'll get compiler warnings from these.
>
> Can be changed to return with value zero for these API's.
>
>> 
>> >  #endif
>> 
>> but even there, this should be fixed in pm.h.  The current PM branch
>> has these defines already:
>> 
>> #define pm_dbg_regset_save(reg_set) do {} while (0);
>> #define pm_dbg_regset_init(reg_set) do {} while (0);
>> 
>> It would be cleaner to fix the #ifdef there to handle the
>> !CONFIG_DEBUG_FS case.
>
> pm branch has else condition for CONFIG_PM_DEBUG. But, CONFIG_DEBUG_FS
> is not handled. 

I know, my proposal is to handle the DEBUG_FS case there also.

> As there is already similar API - pm_dbg_update_time in pm_debug.c,
> these API's can also fit there. More over, using !CONFIG_DEBUG_FS
> will add some #ifdef's in header.

So handle the pm_dbg_update_time() in the header as well.

Handling them in the header will also eliminate the runtime overhead
of an empty function call when DEBUG_FS is not included.

Kevin
<

  reply	other threads:[~2009-11-02 17:10 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-11-02  7:56 [PATCH] [OMAP3_PM] Fix zoom2 defconfig build manjugk
2009-11-02  7:59 ` G, Manjunath Kondaiah
2009-11-02  8:26 ` Artem Bityutskiy
2009-11-02  9:00   ` G, Manjunath Kondaiah
2009-11-02  9:14     ` Felipe Balbi
2009-11-02 10:00       ` G, Manjunath Kondaiah
2009-11-02 16:09         ` Kevin Hilman
2009-11-02 16:30           ` G, Manjunath Kondaiah
2009-11-02 17:10             ` Kevin Hilman [this message]
2009-11-02  9:17     ` Artem Bityutskiy

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=87bpjklun7.fsf@deeprootsystems.com \
    --to=khilman@deeprootsystems.com \
    --cc=dedekind1@gmail.com \
    --cc=felipe.balbi@nokia.com \
    --cc=linux-omap@vger.kernel.org \
    --cc=manjugk@ti.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.