[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <aPYKRvCenwnrFXcb@ashevche-desk.local>
Date: Mon, 20 Oct 2025 13:09:10 +0300
From: Andy Shevchenko <andriy.shevchenko@...ux.intel.com>
To: Alexander Usyskin <alexander.usyskin@...el.com>
Cc: Miquel Raynal <miquel.raynal@...tlin.com>,
Richard Weinberger <richard@....at>,
Vignesh Raghavendra <vigneshr@...com>,
linux-mtd@...ts.infradead.org, linux-kernel@...r.kernel.org,
Reuven Abliyev <reuven.abliyev@...el.com>,
Lucas De Marchi <lucas.demarchi@...el.com>
Subject: Re: [PATCH] mtd: intel-dg: wake card on operations
On Sun, Oct 19, 2025 at 06:01:45PM +0300, Alexander Usyskin wrote:
> Enable runtime PM in mtd driver to notify parent graphics driver
> that whole card should be kept awake while nvm operations are
> performed through this driver.
...
> + pm_runtime_mark_last_busy(nvm->dev);
> + pm_runtime_put_autosuspend(nvm->dev);
Please, drop the second (duplicate) call.
...
> + devm_pm_runtime_enable(device);
Please, justify why this code is good without error checking. Before doing that
think for a moment for the cases when devm_*() might be developed in the future
and return something interesting (if not yet).
...
> err:
> + pm_runtime_put(device);
> +err_norpm:
> kref_put(&nvm->refcnt, intel_dg_nvm_release);
> return ret;
Mixing devm with non-devm usually lead to hard to catch bugs in the error paths
/ remove stages with ordering of cleaning resources up.
--
With Best Regards,
Andy Shevchenko
Powered by blists - more mailing lists