[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <b4aa2023-238a-7929-fd1b-3a2aa0b49b6c@canonical.com>
Date: Mon, 11 Oct 2021 08:48:49 +0200
From: Krzysztof Kozlowski <krzysztof.kozlowski@...onical.com>
To: Hector Martin <marcan@...can.st>,
linux-arm-kernel@...ts.infradead.org
Cc: 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 11/10/2021 07:32, Hector Martin wrote:
>>> +
>>> s3c24xx_serial_cpufreq_deregister(to_ourport(port));
>>> uart_remove_one_port(&s3c24xx_uart_drv, port);
>>> +
>>> + pm_runtime_disable(&dev->dev);
>>
>> Why disabling it only if port!=NULL? Can remove() be called if
>> platform_set_drvdata() was not?
>
> Good question, I'm not entirely sure why these code paths have a check
> for NULL there. They were already there, do you happen to know why? To
> me it sounds like remove would only be called if probe succeeds, at
> which point drvdata should always be set.
>
Exactly, anyway it is not part of your patch, so no problem.
Best regards,
Krzysztof
Powered by blists - more mailing lists