[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <X/vePMbD4fwsNb5Y@atomide.com>
Date: Mon, 11 Jan 2021 07:12:28 +0200
From: Tony Lindgren <tony@...mide.com>
To: Dmitry Torokhov <dmitry.torokhov@...il.com>
Cc: linux-input@...r.kernel.org, linux-kernel@...r.kernel.org,
linux-omap@...r.kernel.org,
Arthur Demchenkov <spinal.by@...il.com>,
Carl Philipp Klemm <philipp@...s.xyz>,
Merlijn Wajer <merlijn@...zup.org>,
Pavel Machek <pavel@....cz>, ruleh <ruleh@....de>,
Sebastian Reichel <sre@...nel.org>
Subject: Re: [PATCH 4/5] Input: omap4-keypad - use PM runtime autosuspend
* Dmitry Torokhov <dmitry.torokhov@...il.com> [210111 05:01]:
> Hi Tony,
>
> On Sun, Jan 10, 2021 at 09:05:28PM +0200, Tony Lindgren wrote:
> > @@ -350,15 +379,12 @@ static int omap4_keypad_probe(struct platform_device *pdev)
> >
> > error = omap4_keypad_check_revision(&pdev->dev,
> > keypad_data);
> > - if (!error) {
> > - /* Ensure device does not raise interrupts */
> > - omap4_keypad_stop(keypad_data);
> > - }
> > -
> > - pm_runtime_put_sync(&pdev->dev);
>
> Why are we moving this down? The idea was to make sure the power usage
> counters are correct even if we exit probe early.
Yes you are right, omap4_keypad_close() won't help with balancing the
get if we exit early.
> Can we call pm_runtime_mark_last_busy() and pm_runtime_put_autosuspend()
> here?
Yes that should work as there's no more register access during the probe.
Regards,
Tony
Powered by blists - more mailing lists