[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <CAJe_Zhc5jCBcfvTcs=Xi_QXLU+t_Erck-3pxV5co1xAsjj8kkA@mail.gmail.com>
Date: Tue, 25 Sep 2012 17:59:52 +0530
From: Jassi Brar <jaswinder.singh@...aro.org>
To: balbi@...com
Cc: Grazvydas Ignotas <notasas@...il.com>,
Sourav Poddar <sourav.poddar@...com>,
gregkh@...uxfoundation.org, alan@...ux.intel.com, tony@...mide.com,
khilman@...com, linux-omap@...r.kernel.org,
linux-arm-kernel@...ts.infradead.org, linux-serial@...r.kernel.org,
linux-kernel@...r.kernel.org, santosh.shilimkar@...com,
paul@...an.com
Subject: Re: [RFT/PATCH] serial: omap: prevent resume if device is not suspended.
On 19 September 2012 17:29, Felipe Balbi <balbi@...com> wrote:
> this is what I mean, actually. If we remove pm_runtime_get_sync() in
> exchange for pm_runtime_set_active() before pm_runtime_enable(), it
> works on PandaBoard, but breaks BeagleBoard.
>
Perhaps it suggests that OMAP4 (PandaBoard) serial port is already
activated but OMAP3 (BeagleBoard) isn't. So we need to reflect that
either by doing pm_runtime_set_active() only on OMAP4 or by bringing
up the OMAP3 too before the pm_runtime_set_active() call.
BTW I understand get_sync(), set_active() and enable() are for
different purposes, they can't be traded for one another.
--
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