[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <CACRpkdb50speJbhRYO5=nNzeo4tY00eKmsJZnbz_wc35ng-0Cg@mail.gmail.com>
Date: Sun, 22 Nov 2015 13:15:00 +0100
From: Linus Walleij <linus.walleij@...aro.org>
To: Mathieu Poirier <mathieu.poirier@...aro.org>
Cc: Greg KH <gregkh@...uxfoundation.org>,
Peter Zijlstra <a.p.zijlstra@...llo.nl>,
Alexander Shishkin <alexander.shishkin@...ux.intel.com>,
Arnaldo Carvalho de Melo <acme@...nel.org>,
Ingo Molnar <mingo@...hat.com>, Jon Corbet <corbet@....net>,
Nicolas Pitre <nicolas.pitre@...aro.org>,
Adrian Hunter <adrian.hunter@...el.com>,
Chunyan Zhang <zhang.chunyan@...aro.org>, mike.leach@....com,
tor@...com, Al Grant <al.grant@....com>,
Paweł Moll <pawel.moll@....com>,
fainelli@...adcom.com,
"linux-arm-kernel@...ts.infradead.org"
<linux-arm-kernel@...ts.infradead.org>,
"linux-doc@...r.kernel.org" <linux-doc@...r.kernel.org>,
"linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>
Subject: Re: [PATCH V4 07/26] coresight: moving PM runtime operations to core framework
On Fri, Nov 13, 2015 at 7:44 PM, Mathieu Poirier
<mathieu.poirier@...aro.org> wrote:
> Moving PM runtime operations in Coresight devices enable() and
> disable() API to the framework core when a path is setup. That
> way the runtime core doesn't have to be involved everytime a
> path is enabled. It also avoids calling runtime PM operations
> in IRQ context.
>
> Signed-off-by: Mathieu Poirier <mathieu.poirier@...aro.org>
Looks reasonable. The PM runtime part of coresight is not very
aggressive anyways, and I think the most important thing it does
is assure it does not consume any power (clocks etc) when it's
not in use.
Reviewed-by: Linus Walleij <linus.walleij@...aro.org>
Linus Walleij
--
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