From: Miquel Raynal <miquel.raynal@bootlin.com>
To: "Usyskin, Alexander" <alexander.usyskin@intel.com>
Cc: "Guenter Roeck" <linux@roeck-us.net>,
"Richard Weinberger" <richard@nod.at>,
"Vignesh Raghavendra" <vigneshr@ti.com>,
"De Marchi, Lucas" <lucas.demarchi@intel.com>,
"Thomas Hellström" <thomas.hellstrom@linux.intel.com>,
"Vivi, Rodrigo" <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>,
"Poosa, Karthik" <karthik.poosa@intel.com>,
"Abliyev, Reuven" <reuven.abliyev@intel.com>,
"Weil, Oren jer" <oren.jer.weil@intel.com>,
"linux-mtd@lists.infradead.org" <linux-mtd@lists.infradead.org>,
"dri-devel@lists.freedesktop.org"
<dri-devel@lists.freedesktop.org>,
"intel-gfx@lists.freedesktop.org"
<intel-gfx@lists.freedesktop.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH v6 01/11] mtd: core: always create master device
Date: Sun, 08 Jun 2025 21:37:47 +0200 [thread overview]
Message-ID: <87bjqyja7o.fsf@bootlin.com> (raw)
In-Reply-To: <CY5PR11MB63666AE267B9F1609213D93CED68A@CY5PR11MB6366.namprd11.prod.outlook.com> (Alexander Usyskin's message of "Sun, 8 Jun 2025 07:00:10 +0000")
Hi Guenter,
On 08/06/2025 at 07:00:10 GMT, "Usyskin, Alexander" <alexander.usyskin@intel.com> wrote:
>> Subject: Re: [PATCH v6 01/11] mtd: core: always create master device
>>
>> Hi,
>>
>> On Sun, Mar 02, 2025 at 04:09:11PM +0200, Alexander Usyskin 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>
>>
>> Several of my qemu boot tests fail to boot from mtd devices with this patch
>> in the mainline kernel. Reverting it fixes the problem. As far as I can
>> see this affects configurations with CONFIG_MTD_PARTITIONED_MASTER=y
>> when
>> trying to boot from an mtd partition other than mtdblock0, with the
>> mtd partition data in devicetree (.../aspeed/openbmc-flash-layout.dtsi).
>> Is there a guidance describing the changed behavior, by any chance,
>> and how the boot command line now needs to look like when using one of
>> the flash partitions as root file system ?
>>
>> Thanks,
>> Guenter
>
> I've tried to make is as transparent as possible for the existing users.
> Only change is that now every partition has master that is not partitioned.
> Is the CONFIG_MTD_PARTITIONED_MASTER=n fixed the problem for you?
No change is expected, can you please describe the devices that you
observe with and without the patch? Maybe there is something wrong in
the core logic.
Thanks,
Miquèl
next prev parent reply other threads:[~2025-06-08 19:55 UTC|newest]
Thread overview: 38+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-03-02 14:09 [PATCH v6 00/11] mtd: add driver for Intel discrete graphics Alexander Usyskin
2025-03-02 14:09 ` [PATCH v6 01/11] mtd: core: always create master device Alexander Usyskin
2025-06-08 1:37 ` Guenter Roeck
2025-06-08 7:00 ` Usyskin, Alexander
2025-06-08 19:37 ` Miquel Raynal [this message]
2025-06-09 0:59 ` Guenter Roeck
2025-06-09 9:43 ` Miquel Raynal
2025-06-09 12:23 ` Usyskin, Alexander
2025-06-09 13:08 ` Guenter Roeck
2025-06-09 15:16 ` Usyskin, Alexander
2025-06-09 15:53 ` Guenter Roeck
2025-06-09 21:27 ` Richard Weinberger
2025-06-10 11:02 ` Usyskin, Alexander
2025-06-10 12:54 ` Richard Weinberger
2025-06-10 16:15 ` Guenter Roeck
2025-06-11 9:34 ` Miquel Raynal
2025-06-11 10:26 ` Richard Weinberger
2025-06-11 10:52 ` Usyskin, Alexander
2025-06-11 14:53 ` Miquel Raynal
2025-06-12 10:01 ` Usyskin, Alexander
2025-06-12 10:25 ` Richard Weinberger
2025-06-12 12:37 ` Usyskin, Alexander
2025-03-02 14:09 ` [PATCH v6 02/11] mtd: add driver for intel graphics non-volatile memory device Alexander Usyskin
2025-03-02 14:09 ` [PATCH v6 03/11] mtd: intel-dg: implement region enumeration Alexander Usyskin
2025-03-02 14:09 ` [PATCH v6 04/11] mtd: intel-dg: implement access functions Alexander Usyskin
2025-03-02 14:09 ` [PATCH v6 05/11] mtd: intel-dg: register with mtd Alexander Usyskin
2025-03-02 14:09 ` [PATCH v6 06/11] mtd: intel-dg: align 64bit read and write Alexander Usyskin
2025-03-02 14:09 ` [PATCH v6 07/11] mtd: intel-dg: wake card on operations Alexander Usyskin
2025-03-02 14:09 ` [PATCH v6 08/11] drm/i915/nvm: add nvm device for discrete graphics Alexander Usyskin
2025-03-02 14:09 ` [PATCH v6 09/11] drm/i915/nvm: add support for access mode Alexander Usyskin
2025-03-02 14:09 ` [PATCH v6 10/11] drm/xe/nvm: add on-die non-volatile memory device Alexander Usyskin
2025-03-02 14:09 ` [PATCH v6 11/11] drm/xe/nvm: add support for access mode Alexander Usyskin
2025-03-02 15:02 ` ✗ Fi.CI.CHECKPATCH: warning for mtd: add driver for Intel discrete graphics (rev6) Patchwork
2025-03-02 15:02 ` ✗ Fi.CI.SPARSE: " Patchwork
2025-03-02 15:22 ` ✓ i915.CI.BAT: success " Patchwork
2025-03-02 17:04 ` ✗ i915.CI.Full: failure " Patchwork
2025-03-18 16:02 ` [PATCH v6 00/11] mtd: add driver for Intel discrete graphics Miquel Raynal
2025-03-26 15:22 ` 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=87bjqyja7o.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=linux@roeck-us.net \
--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).