[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <YWP1jX1DA/bgDyIn@hovoldconsulting.com>
Date: Mon, 11 Oct 2021 10:27:57 +0200
From: Johan Hovold <johan@...nel.org>
To: Hector Martin <marcan@...can.st>
Cc: Krzysztof Kozlowski <krzysztof.kozlowski@...onical.com>,
linux-arm-kernel@...ts.infradead.org,
Marc Zyngier <maz@...nel.org>,
Rob Herring <robh+dt@...nel.org>,
Arnd Bergmann <arnd@...nel.org>,
Linus Walleij <linus.walleij@...aro.org>,
Alyssa Rosenzweig <alyssa@...enzweig.io>,
Greg Kroah-Hartman <gregkh@...uxfoundation.org>,
Mark Kettenis <mark.kettenis@...all.nl>,
Philipp Zabel <p.zabel@...gutronix.de>,
"Rafael J. Wysocki" <rafael@...nel.org>,
devicetree@...r.kernel.org, linux-pm@...r.kernel.org,
linux-kernel@...r.kernel.org, linux-samsung-soc@...r.kernel.org,
linux-serial@...r.kernel.org
Subject: Re: [PATCH 6/7] tty: serial: samsung_tty: Support runtime PM
On Mon, Oct 11, 2021 at 02:32:29PM +0900, Hector Martin wrote:
> On 06/10/2021 16.43, Krzysztof Kozlowski wrote:
> > On 05/10/2021 17:59, Hector Martin wrote:
> >> if (port) {
> >> + pm_runtime_get_sync(&dev->dev);
> >
> > 1. You need to check return status.
> > 2. Why do you need to resume the device here?
>
> As Rafael mentioned, this is basically disabling PM so the device is
> enabled when not bound (which seems to be expected behavior). Not sure
> what I'd do if the resume fails... this is the remove path after all,
> it's not like we're doing anything else with the device at this point.
You still need to disable the clocks before returning from remove().
Consider what happens when the driver is rebound otherwise.
Johan
Powered by blists - more mailing lists