linux-mtd.lists.infradead.org archive mirror
 help / color / mirror / Atom feed
From: Miquel Raynal <miquel.raynal@bootlin.com>
To: Alexander Usyskin <alexander.usyskin@intel.com>
Cc: "Richard Weinberger" <richard@nod.at>,
	"Vignesh Raghavendra" <vigneshr@ti.com>,
	"Lucas De Marchi" <lucas.demarchi@intel.com>,
	"Thomas Hellström" <thomas.hellstrom@linux.intel.com>,
	"Rodrigo Vivi" <rodrigo.vivi@intel.com>,
	"Maarten Lankhorst" <maarten.lankhorst@linux.intel.com>,
	"Maxime Ripard" <mripard@kernel.org>,
	"Thomas Zimmermann" <tzimmermann@suse.de>,
	"David Airlie" <airlied@gmail.com>,
	"Simona Vetter" <simona@ffwll.ch>,
	"Jani Nikula" <jani.nikula@linux.intel.com>,
	"Joonas Lahtinen" <joonas.lahtinen@linux.intel.com>,
	"Tvrtko Ursulin" <tursulin@ursulin.net>,
	"Karthik Poosa" <karthik.poosa@intel.com>,
	"Reuven Abliyev" <reuven.abliyev@intel.com>,
	"Oren Weil" <oren.jer.weil@intel.com>,
	linux-mtd@lists.infradead.org, dri-devel@lists.freedesktop.org,
	intel-gfx@lists.freedesktop.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH v7 01/12] mtd: core: always create master device
Date: Tue, 01 Apr 2025 17:00:43 +0200	[thread overview]
Message-ID: <87ecycrko4.fsf@bootlin.com> (raw)
In-Reply-To: <20250326152623.3897204-2-alexander.usyskin@intel.com> (Alexander Usyskin's message of "Wed, 26 Mar 2025 17:26:12 +0200")

Hello Alexander,

On 26/03/2025 at 17:26:12 +02, Alexander Usyskin <alexander.usyskin@intel.com> wrote:

> Create master device without partition when
> CONFIG_MTD_PARTITIONED_MASTER flag is unset.
>
> This streamlines device tree and allows to anchor
> runtime power management on master device in all cases.
>
> Signed-off-by: Alexander Usyskin <alexander.usyskin@intel.com>

I successfully tested it, this patch will be applied at -rc1 to the
mtd/next tree.

I was wondering, do you think it would be possible to keep the creation
of mtd_master and make it a symbolic link to mtdx when
MTD_PARTITIONED_MASTER=y or when there is no partition? In short, always
having mtd_masterx, because I fear at some point we'll have problems
otherwise :-)

Right now we have:

- Without partition:
mtd0 (mtd0ro mtdblock0)
- With partition and MTD_PARTITIONED_MASTER=n
mtd0 (mtd0ro mtdblock0)
mtd_master0
- With partition and MTD_PARTITIONED_MASTER=y
mtd0 (mtd0ro mtdblock0) [this is the master]
mtd1 (mtd1ro mtdblock1)

I am suggesting:
- Without partition:
mtd0 (mtd0ro mtdblock0)
mtd_master0 -> link to mtd0
- With partition and MTD_PARTITIONED_MASTER=n
mtd0 (mtd0ro mtdblock0)
mtd_master0
- With partition and MTD_PARTITIONED_MASTER=y
mtd0 (mtd0ro mtdblock0) [this is the master]
mtd1 (mtd1ro mtdblock1)
mtd_master0 -> link to mtd0

What do you think? Or maybe even always mtd_master in the first place.

Richard, your point of view on this?

Thanks,
Miquèl

______________________________________________________
Linux MTD discussion mailing list
http://lists.infradead.org/mailman/listinfo/linux-mtd/

  reply	other threads:[~2025-04-01 15:02 UTC|newest]

Thread overview: 22+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-03-26 15:26 [PATCH v7 00/12] mtd: add driver for Intel discrete graphics Alexander Usyskin
2025-03-26 15:26 ` [PATCH v7 01/12] mtd: core: always create master device Alexander Usyskin
2025-04-01 15:00   ` Miquel Raynal [this message]
2025-04-07 12:47     ` Usyskin, Alexander
2025-04-09  9:59       ` Miquel Raynal
2025-04-10  9:44         ` Usyskin, Alexander
2025-04-10 14:12           ` Usyskin, Alexander
2025-04-29  9:23   ` Miquel Raynal
2025-05-06 11:07     ` Usyskin, Alexander
2025-05-12  8:25       ` Miquel Raynal
2025-03-26 15:26 ` [PATCH v7 02/12] mtd: add driver for intel graphics non-volatile memory device Alexander Usyskin
2025-03-26 15:26 ` [PATCH v7 03/12] mtd: intel-dg: implement region enumeration Alexander Usyskin
2025-03-26 15:26 ` [PATCH v7 04/12] mtd: intel-dg: implement access functions Alexander Usyskin
2025-03-26 15:26 ` [PATCH v7 05/12] mtd: intel-dg: register with mtd Alexander Usyskin
2025-03-26 15:26 ` [PATCH v7 06/12] mtd: intel-dg: align 64bit read and write Alexander Usyskin
2025-03-26 15:26 ` [PATCH v7 07/12] mtd: intel-dg: wake card on operations Alexander Usyskin
2025-03-26 15:26 ` [PATCH v7 08/12] drm/i915/nvm: add nvm device for discrete graphics Alexander Usyskin
2025-03-26 15:26 ` [PATCH v7 09/12] drm/i915/nvm: add support for access mode Alexander Usyskin
2025-03-26 15:26 ` [PATCH v7 10/12] drm/xe/nvm: add on-die non-volatile memory device Alexander Usyskin
2025-03-26 15:26 ` [PATCH v7 11/12] drm/xe/nvm: add support for access mode Alexander Usyskin
2025-03-26 19:22 ` [PATCH v7 00/12] mtd: add driver for Intel discrete graphics Rodrigo Vivi
2025-04-09  9:33   ` Usyskin, Alexander

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=87ecycrko4.fsf@bootlin.com \
    --to=miquel.raynal@bootlin.com \
    --cc=airlied@gmail.com \
    --cc=alexander.usyskin@intel.com \
    --cc=dri-devel@lists.freedesktop.org \
    --cc=intel-gfx@lists.freedesktop.org \
    --cc=jani.nikula@linux.intel.com \
    --cc=joonas.lahtinen@linux.intel.com \
    --cc=karthik.poosa@intel.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-mtd@lists.infradead.org \
    --cc=lucas.demarchi@intel.com \
    --cc=maarten.lankhorst@linux.intel.com \
    --cc=mripard@kernel.org \
    --cc=oren.jer.weil@intel.com \
    --cc=reuven.abliyev@intel.com \
    --cc=richard@nod.at \
    --cc=rodrigo.vivi@intel.com \
    --cc=simona@ffwll.ch \
    --cc=thomas.hellstrom@linux.intel.com \
    --cc=tursulin@ursulin.net \
    --cc=tzimmermann@suse.de \
    --cc=vigneshr@ti.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).