[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <CY5PR11MB6366CDF16D135064955D3842EDF3A@CY5PR11MB6366.namprd11.prod.outlook.com>
Date: Wed, 22 Oct 2025 14:26:22 +0000
From: "Usyskin, Alexander" <alexander.usyskin@...el.com>
To: Miquel Raynal <miquel.raynal@...tlin.com>
CC: Richard Weinberger <richard@....at>, Vignesh Raghavendra
<vigneshr@...com>, "linux-mtd@...ts.infradead.org"
<linux-mtd@...ts.infradead.org>, "linux-kernel@...r.kernel.org"
<linux-kernel@...r.kernel.org>, Andy Shevchenko
<andriy.shevchenko@...ux.intel.com>, "Abliyev, Reuven"
<reuven.abliyev@...el.com>, "De Marchi, Lucas" <lucas.demarchi@...el.com>
Subject: RE: [PATCH v2] mtd: intel-dg: wake card on operations
> Subject: Re: [PATCH v2] mtd: intel-dg: wake card on operations
>
> Hi Alexander,
>
> On 21/10/2025 at 15:32:46 +03, Alexander Usyskin
> <alexander.usyskin@...el.com> wrote:
>
> > The Intel DG cards do not have separate power control for
> > persistent memory.
> > The memory is available when the whole card is awake.
> >
> > 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.
> >
> > CC: Lucas De Marchi <lucas.demarchi@...el.com>
> > Signed-off-by: Alexander Usyskin <alexander.usyskin@...el.com>
> > ---
>
> I am curious to know why this now works, whereas in your previous
> attempt (which had to be reverted) we had to do a lot more.
>
The reverted attempt was to always create mtd master device and use
normal device hierarchy in power management.
Here the power management manipulated directly on the parent device
without involving mtd master that may not be initialized.
- -
Thanks,
Sasha
> Thanks,
> Miquèl
Powered by blists - more mailing lists