From: Miquel Raynal <miquel.raynal@bootlin.com>
To: "Usyskin, Alexander" <alexander.usyskin@intel.com>
Cc: Richard Weinberger <richard@nod.at>,
Vignesh Raghavendra <vigneshr@ti.com>,
Jani Nikula <jani.nikula@linux.intel.com>,
Joonas Lahtinen <joonas.lahtinen@linux.intel.com>,
"Vivi, Rodrigo" <rodrigo.vivi@intel.com>,
"Lubart, Vitaly" <vitaly.lubart@intel.com>,
"linux-mtd@lists.infradead.org" <linux-mtd@lists.infradead.org>,
"intel-gfx@lists.freedesktop.org"
<intel-gfx@lists.freedesktop.org>,
"Winkler, Tomas" <tomas.winkler@intel.com>,
"De Marchi, Lucas" <lucas.demarchi@intel.com>,
Michael Walle <michael@walle.cc>,
Tudor Ambarus <tudor.ambarus@linaro.org>
Subject: Re: [PATCH 06/10] drm/i915/spi: spi register with mtd
Date: Mon, 19 Feb 2024 10:09:15 +0100 [thread overview]
Message-ID: <20240219100915.5a778fb9@xps-13> (raw)
In-Reply-To: <CY5PR11MB63660FF7942CA400439B76D8ED4E2@CY5PR11MB6366.namprd11.prod.outlook.com>
Hi Alexander,
alexander.usyskin@intel.com wrote on Wed, 14 Feb 2024 12:16:00 +0000:
> Hi Miquel
>
> Intel Gfx in infinite wisdom decided to create another driver - Xe and
> the spi driver part of this series should be moved to some common location.
> Should it be drivers/mtd or drivers/spi, or some other place?
It probably depends on the framework they decided to register into. I'm
sorry but I interacted in this thread more than 3 months ago, I no
longer remember most of the details.
If this is a driver for a spi controller (even a limited one) then it
should be drivers/spi/ I guess.
Thanks,
Miquèl
WARNING: multiple messages have this Message-ID (diff)
From: Miquel Raynal <miquel.raynal@bootlin.com>
To: "Usyskin, Alexander" <alexander.usyskin@intel.com>
Cc: Richard Weinberger <richard@nod.at>,
Vignesh Raghavendra <vigneshr@ti.com>,
Jani Nikula <jani.nikula@linux.intel.com>,
Joonas Lahtinen <joonas.lahtinen@linux.intel.com>,
"Vivi, Rodrigo" <rodrigo.vivi@intel.com>,
"Lubart, Vitaly" <vitaly.lubart@intel.com>,
"linux-mtd@lists.infradead.org" <linux-mtd@lists.infradead.org>,
"intel-gfx@lists.freedesktop.org"
<intel-gfx@lists.freedesktop.org>,
"Winkler, Tomas" <tomas.winkler@intel.com>,
"De Marchi, Lucas" <lucas.demarchi@intel.com>,
Michael Walle <michael@walle.cc>,
Tudor Ambarus <tudor.ambarus@linaro.org>
Subject: Re: [PATCH 06/10] drm/i915/spi: spi register with mtd
Date: Mon, 19 Feb 2024 10:09:15 +0100 [thread overview]
Message-ID: <20240219100915.5a778fb9@xps-13> (raw)
In-Reply-To: <CY5PR11MB63660FF7942CA400439B76D8ED4E2@CY5PR11MB6366.namprd11.prod.outlook.com>
Hi Alexander,
alexander.usyskin@intel.com wrote on Wed, 14 Feb 2024 12:16:00 +0000:
> Hi Miquel
>
> Intel Gfx in infinite wisdom decided to create another driver - Xe and
> the spi driver part of this series should be moved to some common location.
> Should it be drivers/mtd or drivers/spi, or some other place?
It probably depends on the framework they decided to register into. I'm
sorry but I interacted in this thread more than 3 months ago, I no
longer remember most of the details.
If this is a driver for a spi controller (even a limited one) then it
should be drivers/spi/ I guess.
Thanks,
Miquèl
______________________________________________________
Linux MTD discussion mailing list
http://lists.infradead.org/mailman/listinfo/linux-mtd/
next prev parent reply other threads:[~2024-02-19 9:09 UTC|newest]
Thread overview: 88+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-09-10 12:39 [Intel-gfx] [PATCH 00/10] drm/i915/spi: spi access for discrete graphics Alexander Usyskin
2023-09-10 12:39 ` Alexander Usyskin
2023-09-10 12:39 ` [Intel-gfx] [PATCH 01/10] drm/i915/spi: add spi device " Alexander Usyskin
2023-09-10 12:39 ` Alexander Usyskin
2023-09-11 15:41 ` [Intel-gfx] " Jani Nikula
2023-09-11 15:41 ` Jani Nikula
2023-09-12 10:47 ` [Intel-gfx] " Usyskin, Alexander
2023-09-12 10:47 ` Usyskin, Alexander
2023-09-10 12:39 ` [Intel-gfx] [PATCH 02/10] drm/i915/spi: add intel_spi_region map Alexander Usyskin
2023-09-10 12:39 ` Alexander Usyskin
2023-09-10 12:39 ` [Intel-gfx] [PATCH 03/10] drm/i915/spi: add driver for on-die spi device Alexander Usyskin
2023-09-10 12:39 ` Alexander Usyskin
2023-09-10 12:39 ` [Intel-gfx] [PATCH 04/10] drm/i915/spi: implement region enumeration Alexander Usyskin
2023-09-10 12:39 ` Alexander Usyskin
2023-09-10 12:39 ` [Intel-gfx] [PATCH 05/10] drm/i915/spi: implement spi access functions Alexander Usyskin
2023-09-10 12:39 ` Alexander Usyskin
2023-09-10 12:39 ` [Intel-gfx] [PATCH 06/10] drm/i915/spi: spi register with mtd Alexander Usyskin
2023-09-10 12:39 ` Alexander Usyskin
2023-10-16 8:39 ` [Intel-gfx] " Miquel Raynal
2023-10-16 8:39 ` Miquel Raynal
2023-10-17 11:54 ` [Intel-gfx] " Usyskin, Alexander
2023-10-17 11:54 ` Usyskin, Alexander
2023-10-17 13:55 ` [Intel-gfx] " Miquel Raynal
2023-10-17 13:55 ` Miquel Raynal
2023-10-17 14:20 ` [Intel-gfx] " Usyskin, Alexander
2023-10-17 14:20 ` Usyskin, Alexander
2023-10-17 14:46 ` [Intel-gfx] " Miquel Raynal
2023-10-17 14:46 ` Miquel Raynal
2023-11-14 8:47 ` [Intel-gfx] " Usyskin, Alexander
2023-11-14 8:47 ` Usyskin, Alexander
2023-11-14 9:13 ` [Intel-gfx] " Miquel Raynal
2023-11-14 9:13 ` Miquel Raynal
2024-02-14 12:16 ` Usyskin, Alexander
2024-02-14 12:16 ` Usyskin, Alexander
2024-02-19 9:09 ` Miquel Raynal [this message]
2024-02-19 9:09 ` Miquel Raynal
2023-09-10 12:39 ` [Intel-gfx] [PATCH 07/10] drm/i915/spi: mtd: implement access handlers Alexander Usyskin
2023-09-10 12:39 ` Alexander Usyskin
2023-09-10 12:39 ` [Intel-gfx] [PATCH 08/10] drm/i915/spi: align 64bit read and write Alexander Usyskin
2023-09-10 12:39 ` Alexander Usyskin
2023-09-10 12:39 ` [Intel-gfx] [PATCH 09/10] drm/i915/spi: wake card on operations Alexander Usyskin
2023-09-10 12:39 ` Alexander Usyskin
2023-09-10 12:39 ` [Intel-gfx] [PATCH 10/10] drm/i915/spi: add support for access mode Alexander Usyskin
2023-09-10 12:39 ` Alexander Usyskin
2023-09-10 13:11 ` [Intel-gfx] ✗ Fi.CI.CHECKPATCH: warning for drm/i915/spi: spi access for discrete graphics Patchwork
2023-09-10 13:11 ` [Intel-gfx] ✗ Fi.CI.SPARSE: " Patchwork
2023-09-11 7:42 ` [Intel-gfx] [PATCH 00/10] " Miquel Raynal
2023-09-11 7:42 ` Miquel Raynal
2023-09-11 7:42 ` Miquel Raynal
2023-09-12 10:50 ` [Intel-gfx] " Usyskin, Alexander
2023-09-12 10:50 ` Usyskin, Alexander
2023-09-12 10:50 ` Usyskin, Alexander
2023-09-12 12:14 ` [Intel-gfx] " Mark Brown
2023-09-12 12:14 ` Mark Brown
2023-09-12 12:14 ` Mark Brown
2023-09-12 13:15 ` [Intel-gfx] " Usyskin, Alexander
2023-09-12 13:15 ` Usyskin, Alexander
2023-09-12 13:15 ` Usyskin, Alexander
2023-09-12 13:21 ` [Intel-gfx] " Miquel Raynal
2023-09-12 13:21 ` Miquel Raynal
2023-09-12 13:21 ` Miquel Raynal
2023-09-12 13:36 ` [Intel-gfx] " Mark Brown
2023-09-12 13:36 ` Mark Brown
2023-09-12 13:36 ` Mark Brown
2023-09-20 13:52 ` [Intel-gfx] " Usyskin, Alexander
2023-09-20 13:52 ` Usyskin, Alexander
2023-09-20 13:52 ` Usyskin, Alexander
2023-09-20 15:54 ` [Intel-gfx] " Mark Brown
2023-09-20 15:54 ` Mark Brown
2023-09-20 15:54 ` Mark Brown
2023-09-20 21:00 ` [Intel-gfx] " Winkler, Tomas
2023-09-20 21:00 ` Winkler, Tomas
2023-09-20 21:00 ` Winkler, Tomas
2023-09-21 11:29 ` [Intel-gfx] " Mark Brown
2023-09-21 11:29 ` Mark Brown
2023-09-21 11:29 ` Mark Brown
2023-09-27 14:11 ` [Intel-gfx] " Usyskin, Alexander
2023-09-27 14:11 ` Usyskin, Alexander
2023-09-27 14:11 ` Usyskin, Alexander
2023-09-27 14:37 ` [Intel-gfx] " Mark Brown
2023-09-27 14:37 ` Mark Brown
2023-09-27 14:37 ` Mark Brown
2023-09-27 14:54 ` [Intel-gfx] " Miquel Raynal
2023-09-27 14:54 ` Miquel Raynal
2023-09-27 14:54 ` Miquel Raynal
2023-09-28 6:33 ` [Intel-gfx] " Usyskin, Alexander
2023-09-28 6:33 ` Usyskin, Alexander
2023-09-28 6: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=20240219100915.5a778fb9@xps-13 \
--to=miquel.raynal@bootlin.com \
--cc=alexander.usyskin@intel.com \
--cc=intel-gfx@lists.freedesktop.org \
--cc=jani.nikula@linux.intel.com \
--cc=joonas.lahtinen@linux.intel.com \
--cc=linux-mtd@lists.infradead.org \
--cc=lucas.demarchi@intel.com \
--cc=michael@walle.cc \
--cc=richard@nod.at \
--cc=rodrigo.vivi@intel.com \
--cc=tomas.winkler@intel.com \
--cc=tudor.ambarus@linaro.org \
--cc=vigneshr@ti.com \
--cc=vitaly.lubart@intel.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.