linux-kernel - Re: [PATCH v4 01/11] mtd: core: always create master device

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <677101004.241399779.1737152836282.JavaMail.zimbra@nod.at>
Date: Fri, 17 Jan 2025 23:27:16 +0100 (CET)
From: Richard Weinberger <richard@....at>
To: Alexander Usyskin <alexander.usyskin@...el.com>
Cc: Miquel Raynal <miquel.raynal@...tlin.com>, 
	Vignesh Raghavendra <vigneshr@...com>, 
	Lucas De Marchi <lucas.demarchi@...el.com>, 
	Thomas Hellström <thomas.hellstrom@...ux.intel.com>, 
	Rodrigo Vivi <rodrigo.vivi@...el.com>, 
	Maarten Lankhorst <maarten.lankhorst@...ux.intel.com>, 
	Maxime Ripard <mripard@...nel.org>, 
	Thomas Zimmermann <tzimmermann@...e.de>, 
	David Airlie <airlied@...il.com>, Simona Vetter <simona@...ll.ch>, 
	Jani Nikula <jani.nikula@...ux.intel.com>, 
	Joonas Lahtinen <joonas.lahtinen@...ux.intel.com>, 
	Tvrtko Ursulin <tursulin@...ulin.net>, 
	Karthik Poosa <karthik.poosa@...el.com>, 
	Reuven Abliyev <reuven.abliyev@...el.com>, 
	Oren Weil <oren.jer.weil@...el.com>, 
	linux-mtd <linux-mtd@...ts.infradead.org>, 
	DRI mailing list <dri-devel@...ts.freedesktop.org>, 
	intel-gfx <intel-gfx@...ts.freedesktop.org>, 
	linux-kernel <linux-kernel@...r.kernel.org>
Subject: Re: [PATCH v4 01/11] mtd: core: always create master device

----- Ursprüngliche Mail -----
>> > This streamlines device tree and allows to anchor
>> > runtime power management on master device in all cases.
>> 
>> Please explain in more detail why this is needed.
>> If this change makes the overall situation better and breaks
>> no userspace, I'm happy. :-)
>> 
> 
> The rest of the series is a driver that need runtime power management.
> Absence of the master device breaks power management logic,
> as kernel automatically propagates state from children to parent.
> I initially hooked runtime_pm on chip auxiliary device, but this is a hack,
> not a solution.

So, the problem is that mtd partitions don't have a common parent/master like
we have for generic disks?
Please give more details.
We have already a non-optimal situation in mtd and I want to fully understand
the requirements to get it this time right.

Thanks,
//richard