From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from lithops.sigma-star.at (mailout.nod.at [116.203.167.152]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by smtp.subspace.kernel.org (Postfix) with ESMTPS id 3CBDEB67F for ; Fri, 17 Jan 2025 22:27:24 +0000 (UTC) Authentication-Results: smtp.subspace.kernel.org; arc=none smtp.client-ip=116.203.167.152 ARC-Seal:i=1; a=rsa-sha256; d=subspace.kernel.org; s=arc-20240116; t=1737152848; cv=none; b=fNvXEeoLtxRywk15m/C5R//fVxeyfrskh7a1EQHpISBLj7x3mt/y6DPWUy2aUgGv2H4SMj5e83Bb3ePJ4aOhocpi4p4gymh/yt7ryuoOBY+7CjEelQbKp9/9+FNrr4LFuLhz2GeK01Xv+R0nPi6iEbLQ/pFdwYAPv7mH7zfeTd0= ARC-Message-Signature:i=1; a=rsa-sha256; d=subspace.kernel.org; s=arc-20240116; t=1737152848; c=relaxed/simple; bh=rpx5ChtNtP/tklvZH9O2c+LiwMLiTIyqljaGMaWTeyk=; h=Date:From:To:Cc:Message-ID:In-Reply-To:References:Subject: MIME-Version:Content-Type; b=TdVvTl6Wrn5sn12gzSWTWQ1gXuYoxT3CIGWpPg6yoBznlEObD4F/L1ykR6KpEvGDOO0uGDerfiSqPwRfnDTpA7Y6tbLlbPNwtFOt4zhByvyVPVHwzFulCgd+FmmsGhdpLdBLD3wV0I8F2WfZ1TtFAiUVBYgssPda/2ULZyhfC9U= ARC-Authentication-Results:i=1; smtp.subspace.kernel.org; dmarc=none (p=none dis=none) header.from=nod.at; spf=fail smtp.mailfrom=nod.at; arc=none smtp.client-ip=116.203.167.152 Authentication-Results: smtp.subspace.kernel.org; dmarc=none (p=none dis=none) header.from=nod.at Authentication-Results: smtp.subspace.kernel.org; spf=fail smtp.mailfrom=nod.at Received: from localhost (localhost [127.0.0.1]) by lithops.sigma-star.at (Postfix) with ESMTP id 0DFA02BA969; Fri, 17 Jan 2025 23:27:17 +0100 (CET) Received: from lithops.sigma-star.at ([127.0.0.1]) by localhost (lithops.sigma-star.at [127.0.0.1]) (amavisd-new, port 10032) with ESMTP id PKRyMU3k07_p; Fri, 17 Jan 2025 23:27:16 +0100 (CET) Received: from localhost (localhost [127.0.0.1]) by lithops.sigma-star.at (Postfix) with ESMTP id 9F2942BA97A; Fri, 17 Jan 2025 23:27:16 +0100 (CET) Received: from lithops.sigma-star.at ([127.0.0.1]) by localhost (lithops.sigma-star.at [127.0.0.1]) (amavisd-new, port 10026) with ESMTP id w4ahg7LEgjAo; Fri, 17 Jan 2025 23:27:16 +0100 (CET) Received: from lithops.sigma-star.at (lithops.sigma-star.at [195.201.40.130]) by lithops.sigma-star.at (Postfix) with ESMTP id 67B8E2BA969; Fri, 17 Jan 2025 23:27:16 +0100 (CET) Date: Fri, 17 Jan 2025 23:27:16 +0100 (CET) From: Richard Weinberger To: Alexander Usyskin Cc: Miquel Raynal , Vignesh Raghavendra , Lucas De Marchi , Thomas =?utf-8?Q?Hellstr=C3=B6m?= , Rodrigo Vivi , Maarten Lankhorst , Maxime Ripard , Thomas Zimmermann , David Airlie , Simona Vetter , Jani Nikula , Joonas Lahtinen , Tvrtko Ursulin , Karthik Poosa , Reuven Abliyev , Oren Weil , linux-mtd , DRI mailing list , intel-gfx , linux-kernel Message-ID: <677101004.241399779.1737152836282.JavaMail.zimbra@nod.at> In-Reply-To: References: <20250101153925.865703-1-alexander.usyskin@intel.com> <20250101153925.865703-2-alexander.usyskin@intel.com> <78709125.231818577.1736980238251.JavaMail.zimbra@nod.at> Subject: Re: [PATCH v4 01/11] mtd: core: always create master device Precedence: bulk X-Mailing-List: linux-kernel@vger.kernel.org List-Id: List-Subscribe: List-Unsubscribe: MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable X-Mailer: Zimbra 8.8.12_GA_3807 (ZimbraWebClient - FF133 (Linux)/8.8.12_GA_3809) Thread-Topic: core: always create master device Thread-Index: AQHbXGTq3Ynz/rfH2UqisY27+I2b+LMYgWoAgACDNgDMz5OtTg== ----- Urspr=C3=BCngliche Mail ----- >> > This streamlines device tree and allows to anchor >> > runtime power management on master device in all cases. >>=20 >> Please explain in more detail why this is needed. >> If this change makes the overall situation better and breaks >> no userspace, I'm happy. :-) >>=20 >=20 > 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 hac= k, > not a solution. So, the problem is that mtd partitions don't have a common parent/master li= ke we have for generic disks? Please give more details. We have already a non-optimal situation in mtd and I want to fully understa= nd the requirements to get it this time right. Thanks, //richard