From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from relay9-d.mail.gandi.net (relay9-d.mail.gandi.net [217.70.183.199]) (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 0DDC028DA1 for ; Mon, 23 Dec 2024 19:21:32 +0000 (UTC) Authentication-Results: smtp.subspace.kernel.org; arc=none smtp.client-ip=217.70.183.199 ARC-Seal:i=1; a=rsa-sha256; d=subspace.kernel.org; s=arc-20240116; t=1734981695; cv=none; b=GDkPilUs8lo3hiSYvWlDZvUVGcjg4QKLg46fxNE8FjO+Qw3QcFcPbXgzVu8TAKdjUJCImwRpiltBihicgJN6SUnoPJA/UpAvOfpdcHb5lxC1Y8lOOQ2XpyTqxEAi9VUHwY789H68Qsmy9aJlDvVodSu8mFJtsTXc+y8wRdQ+gCg= ARC-Message-Signature:i=1; a=rsa-sha256; d=subspace.kernel.org; s=arc-20240116; t=1734981695; c=relaxed/simple; bh=KWj1thEE3fEk4/JDoMlPzjIiOgvaovwBP/OLPmPxMTc=; h=From:To:Cc:Subject:In-Reply-To:References:Date:Message-ID: MIME-Version:Content-Type; b=WMVHQRXoPymLL3SjQcyzWshg8y4Zzg4np0Jj8kNqW857++nAai83isq8BCiqRKwkpSsFRqbW8UdBNehmLxlUCmMmlm62GfYjcVek0FGiRQJZnN3Lzr6O9edFNM65mZGR+DhwHbhQcJ0oHwox/bT48FAFiABJ14GK1Z8mmdZ/6ro= ARC-Authentication-Results:i=1; smtp.subspace.kernel.org; dmarc=pass (p=reject dis=none) header.from=bootlin.com; spf=pass smtp.mailfrom=bootlin.com; dkim=pass (2048-bit key) header.d=bootlin.com header.i=@bootlin.com header.b=XkL4HlxD; arc=none smtp.client-ip=217.70.183.199 Authentication-Results: smtp.subspace.kernel.org; dmarc=pass (p=reject dis=none) header.from=bootlin.com Authentication-Results: smtp.subspace.kernel.org; spf=pass smtp.mailfrom=bootlin.com Authentication-Results: smtp.subspace.kernel.org; dkim=pass (2048-bit key) header.d=bootlin.com header.i=@bootlin.com header.b="XkL4HlxD" Received: by mail.gandi.net (Postfix) with ESMTPSA id 4343AFF803; Mon, 23 Dec 2024 19:21:30 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=bootlin.com; s=gm1; t=1734981691; h=from:from:reply-to:subject:subject:date:date:message-id:message-id: to:to:cc:cc:mime-version:mime-version:content-type:content-type: content-transfer-encoding:content-transfer-encoding: in-reply-to:in-reply-to:references:references; bh=KWj1thEE3fEk4/JDoMlPzjIiOgvaovwBP/OLPmPxMTc=; b=XkL4HlxDTSTVu8Z3tpaDo0aUqQjDmb1EDtc/kb/3vkFvtvfjq5NCactwOYkt2DXR9/jgDL wrtpgjGDtx0hpkK9ZmSvEYv2EMZbYwv9arz0d3MZuxWiyvtWmfZHn7mwGrlqtaMv6I4+6Y 90hO51r6ps3MOp4l27g2VGiqP80/ZIJ9OvQmo2O7Bop199rK/KyLNYvqfNj8LseasjZkdO AnUXXqybWyvrrZqpZB6TGEVAFLXkpc7XQALLfRbrORYiVT31MnMNXB8uAD28QDMsCT1zp7 aZgUix8Gfs2nXqYN47SFUTEpGx6C7wxgo0RLtW2VnFI6M3Hae/LoYaQyEMzS9g== From: Miquel Raynal To: "Usyskin, Alexander" Cc: "Poosa, Karthik" , "Vivi, Rodrigo" , Richard Weinberger , Vignesh Raghavendra , "De Marchi, Lucas" , Thomas =?utf-8?Q?Hellstr=C3=B6m?= , Maarten Lankhorst , Maxime Ripard , Thomas Zimmermann , David Airlie , Simona Vetter , Jani Nikula , Joonas Lahtinen , Tvrtko Ursulin , "Weil, Oren jer" , "linux-mtd@lists.infradead.org" , "dri-devel@lists.freedesktop.org" , "intel-gfx@lists.freedesktop.org" , "linux-kernel@vger.kernel.org" Subject: Re: [PATCH v3 06/10] mtd: intel-dg: wake card on operations In-Reply-To: (Alexander Usyskin's message of "Wed, 18 Dec 2024 15:58:35 +0000") References: <20241119140112.790720-1-alexander.usyskin@intel.com> <20241119140112.790720-7-alexander.usyskin@intel.com> <24725a85-47c2-49c3-b2ae-443279b2bd13@intel.com> User-Agent: mu4e 1.12.7; emacs 29.4 Date: Mon, 23 Dec 2024 20:21:29 +0100 Message-ID: <87cyhiqk7a.fsf@bootlin.com> 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-GND-Sasl: miquel.raynal@bootlin.com Hello Alexander, >> If so, I have to add patch for mtd subsystem to always have device for m= aster >> initialized regardless of kernel flag. >> Only to initialize struct device, not to create full mtd node. >>=20 >> Miquel - are you agree to this? Conceptually yes, but please mind one thing: we do not break userspace. So if you want to keep the master mtd device, fine, but you need to do it in a consistent way so that people not enabling the kernel flag won't get a new device in their rootfs, shifting all indexes upwards. That being said, you are probably going in the right direction by doing that. Thanks, Miqu=C3=A8l