All of lore.kernel.org
 help / color / mirror / Atom feed
From: Miquel Raynal <miquel.raynal@bootlin.com>
To: "Usyskin, Alexander" <alexander.usyskin@intel.com>
Cc: Vignesh Raghavendra <vigneshr@ti.com>,
	Richard Weinberger <richard@nod.at>,
	"intel-gfx@lists.freedesktop.org"
	<intel-gfx@lists.freedesktop.org>,
	Michael Walle <michael@walle.cc>,
	"linux-spi@vger.kernel.org" <linux-spi@vger.kernel.org>,
	Tudor Ambarus <tudor.ambarus@linaro.org>,
	Mark Brown <broonie@kernel.org>,
	"linux-mtd@lists.infradead.org" <linux-mtd@lists.infradead.org>,
	"Vivi, Rodrigo" <rodrigo.vivi@intel.com>,
	"Lubart, Vitaly" <vitaly.lubart@intel.com>,
	Pratyush Yadav <pratyush@kernel.org>
Subject: Re: [Intel-gfx] [PATCH 00/10] drm/i915/spi: spi access for discrete graphics
Date: Tue, 12 Sep 2023 15:21:02 +0200	[thread overview]
Message-ID: <20230912152102.0dfe7558@xps-13> (raw)
In-Reply-To: <CY5PR11MB63667AB9958A23970B4B0D3EEDF1A@CY5PR11MB6366.namprd11.prod.outlook.com>

Hi,

alexander.usyskin@intel.com wrote on Tue, 12 Sep 2023 13:15:58 +0000:

> >   
> > > The spi controller on discreet graphics card is not visible to user-space.
> > > Spi access flows are supported by another hardware module and relevant  
> > registers are  
> > > available on graphics device memory bar.  
> > 
> > No SPI controllers are directly visible to userspace, some SPI devices
> > are selectively exposed but that needs to be explicitly requested and is
> > generally discouraged.  
> 
> What are the options here? Explicitly request exception is the one.
> Any other way to add access to flash memory connected in such way?

Register a spi controller with at least spi-mem ops, as suggested
previously, is the standard way I guess. If you're not willing to do
so, it must be justified, 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: Mark Brown <broonie@kernel.org>,
	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>,
	Tudor Ambarus <tudor.ambarus@linaro.org>,
	Pratyush Yadav <pratyush@kernel.org>,
	Michael Walle <michael@walle.cc>,
	"linux-spi@vger.kernel.org" <linux-spi@vger.kernel.org>
Subject: Re: [PATCH 00/10] drm/i915/spi: spi access for discrete graphics
Date: Tue, 12 Sep 2023 15:21:02 +0200	[thread overview]
Message-ID: <20230912152102.0dfe7558@xps-13> (raw)
In-Reply-To: <CY5PR11MB63667AB9958A23970B4B0D3EEDF1A@CY5PR11MB6366.namprd11.prod.outlook.com>

Hi,

alexander.usyskin@intel.com wrote on Tue, 12 Sep 2023 13:15:58 +0000:

> >   
> > > The spi controller on discreet graphics card is not visible to user-space.
> > > Spi access flows are supported by another hardware module and relevant  
> > registers are  
> > > available on graphics device memory bar.  
> > 
> > No SPI controllers are directly visible to userspace, some SPI devices
> > are selectively exposed but that needs to be explicitly requested and is
> > generally discouraged.  
> 
> What are the options here? Explicitly request exception is the one.
> Any other way to add access to flash memory connected in such way?

Register a spi controller with at least spi-mem ops, as suggested
previously, is the standard way I guess. If you're not willing to do
so, it must be justified, I guess?

Thanks,
Miquèl

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

WARNING: multiple messages have this Message-ID (diff)
From: Miquel Raynal <miquel.raynal@bootlin.com>
To: "Usyskin, Alexander" <alexander.usyskin@intel.com>
Cc: Mark Brown <broonie@kernel.org>,
	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>,
	Tudor Ambarus <tudor.ambarus@linaro.org>,
	Pratyush Yadav <pratyush@kernel.org>,
	Michael Walle <michael@walle.cc>,
	"linux-spi@vger.kernel.org" <linux-spi@vger.kernel.org>
Subject: Re: [PATCH 00/10] drm/i915/spi: spi access for discrete graphics
Date: Tue, 12 Sep 2023 15:21:02 +0200	[thread overview]
Message-ID: <20230912152102.0dfe7558@xps-13> (raw)
In-Reply-To: <CY5PR11MB63667AB9958A23970B4B0D3EEDF1A@CY5PR11MB6366.namprd11.prod.outlook.com>

Hi,

alexander.usyskin@intel.com wrote on Tue, 12 Sep 2023 13:15:58 +0000:

> >   
> > > The spi controller on discreet graphics card is not visible to user-space.
> > > Spi access flows are supported by another hardware module and relevant  
> > registers are  
> > > available on graphics device memory bar.  
> > 
> > No SPI controllers are directly visible to userspace, some SPI devices
> > are selectively exposed but that needs to be explicitly requested and is
> > generally discouraged.  
> 
> What are the options here? Explicitly request exception is the one.
> Any other way to add access to flash memory connected in such way?

Register a spi controller with at least spi-mem ops, as suggested
previously, is the standard way I guess. If you're not willing to do
so, it must be justified, I guess?

Thanks,
Miquèl

  reply	other threads:[~2023-09-18 12:24 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
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         ` Miquel Raynal [this message]
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=20230912152102.0dfe7558@xps-13 \
    --to=miquel.raynal@bootlin.com \
    --cc=alexander.usyskin@intel.com \
    --cc=broonie@kernel.org \
    --cc=intel-gfx@lists.freedesktop.org \
    --cc=linux-mtd@lists.infradead.org \
    --cc=linux-spi@vger.kernel.org \
    --cc=michael@walle.cc \
    --cc=pratyush@kernel.org \
    --cc=richard@nod.at \
    --cc=rodrigo.vivi@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.