[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20110511111732.2f75713a@bike.lwn.net>
Date: Wed, 11 May 2011 11:17:32 -0600
From: Jonathan Corbet <corbet@....net>
To: "Rafael J. Wysocki" <rjw@...k.pl>
Cc: Linux PM mailing list <linux-pm@...ts.linux-foundation.org>,
Greg KH <gregkh@...e.de>, LKML <linux-kernel@...r.kernel.org>,
Kevin Hilman <khilman@...com>,
Grant Likely <grant.likely@...retlab.ca>,
Magnus Damm <magnus.damm@...il.com>, linux-sh@...r.kernel.org,
MyungJoo Ham <myungjoo.ham@...il.com>,
Guennadi Liakhovetski <g.liakhovetski@....de>
Subject: Re: [PATCH 3/5] PM: Support for system-wide power transitions in
generic power domains
Hi, Rafael,
One small question that came to mind as I was looking at this patch:
> +/**
> + * pm_genpd_powered_down - Check if power has been removed from a power domain.
> + * @genpd: Power domain to check.
> + */
> +static bool pm_genpd_powered_down(struct generic_power_domain *genpd)
> +{
> + bool ret;
> +
> + mutex_lock(&genpd->lock);
> + ret = genpd->power_is_off;
> + mutex_unlock(&genpd->lock);
> +
> + return ret;
I'm not quite sure why this function exists? The lock doesn't really
change anything, since the power state can change before or after this
check regardless. If you need the power state to be stable, it seems like
the lock needs to be taken further up the stack; otherwise simply checking
genpd->power_is_off directly would seem to be sufficient. Am I missing
something?
Thanks,
jon
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists