All of lore.kernel.org
 help / color / mirror / Atom feed
From: Miquel Raynal <miquel.raynal@bootlin.com>
To: Alexander Usyskin <alexander.usyskin@intel.com>
Cc: Vignesh Raghavendra <vigneshr@ti.com>,
	Richard Weinberger <richard@nod.at>,
	intel-gfx@lists.freedesktop.org,
	Lucas De Marchi <lucas.demarchi@intel.com>,
	linux-mtd@lists.infradead.org,
	Rodrigo Vivi <rodrigo.vivi@intel.com>,
	Tomas Winkler <tomas.winkler@intel.com>,
	Vitaly Lubart <vitaly.lubart@intel.com>
Subject: Re: [Intel-gfx] [PATCH 06/10] drm/i915/spi: spi register with mtd
Date: Mon, 16 Oct 2023 10:39:39 +0200	[thread overview]
Message-ID: <20231016103939.67445bee@xps-13> (raw)
In-Reply-To: <20230910123949.1251964-7-alexander.usyskin@intel.com>

Hi Alexander,

> +static int i915_spi_init_mtd(struct i915_spi *spi, struct device *device,
> +			     unsigned int nparts)
> +{
> +	unsigned int i;
> +	unsigned int n;
> +	struct mtd_partition *parts = NULL;
> +	int ret;
> +
> +	dev_dbg(device, "registering with mtd\n");
> +
> +	spi->mtd.owner = THIS_MODULE;
> +	spi->mtd.dev.parent = device;
> +	spi->mtd.flags = MTD_CAP_NORFLASH | MTD_WRITEABLE;
> +	spi->mtd.type = MTD_DATAFLASH;
> +	spi->mtd.priv = spi;
> +	spi->mtd._write = i915_spi_write;
> +	spi->mtd._read = i915_spi_read;
> +	spi->mtd._erase = i915_spi_erase;
> +	spi->mtd._get_device = i915_spi_get_device;
> +	spi->mtd._put_device = i915_spi_put_device;
> +	spi->mtd.writesize = SZ_1; /* 1 byte granularity */

You say writesize should be aligned with 4 in your next patch?

> +	spi->mtd.erasesize = SZ_4K; /* 4K bytes granularity */
> +	spi->mtd.size = spi->size;
> +
> +	parts = kcalloc(spi->nregions, sizeof(*parts), GFP_KERNEL);
> +	if (!parts)
> +		return -ENOMEM;
> +
> +	for (i = 0, n = 0; i < spi->nregions && n < nparts; i++) {
> +		if (!spi->regions[i].is_readable)
> +			continue;
> +		parts[n].name = spi->regions[i].name;
> +		parts[n].offset  = spi->regions[i].offset;
> +		parts[n].size = spi->regions[i].size;
> +		if (!spi->regions[i].is_writable)
> +			parts[n].mask_flags = MTD_WRITEABLE;
> +		n++;
> +	}
> +
> +	ret = mtd_device_register(&spi->mtd, parts, n);
> +
> +	kfree(parts);
> +
> +	return ret;
> +}
> +

Thanks,
Miquèl

WARNING: multiple messages have this Message-ID (diff)
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>,
	Jani Nikula <jani.nikula@linux.intel.com>,
	Joonas Lahtinen <joonas.lahtinen@linux.intel.com>,
	Rodrigo Vivi <rodrigo.vivi@intel.com>,
	Vitaly Lubart <vitaly.lubart@intel.com>,
	linux-mtd@lists.infradead.org, intel-gfx@lists.freedesktop.org,
	Tomas Winkler <tomas.winkler@intel.com>,
	Lucas De Marchi <lucas.demarchi@intel.com>
Subject: Re: [PATCH 06/10] drm/i915/spi: spi register with mtd
Date: Mon, 16 Oct 2023 10:39:39 +0200	[thread overview]
Message-ID: <20231016103939.67445bee@xps-13> (raw)
In-Reply-To: <20230910123949.1251964-7-alexander.usyskin@intel.com>

Hi Alexander,

> +static int i915_spi_init_mtd(struct i915_spi *spi, struct device *device,
> +			     unsigned int nparts)
> +{
> +	unsigned int i;
> +	unsigned int n;
> +	struct mtd_partition *parts = NULL;
> +	int ret;
> +
> +	dev_dbg(device, "registering with mtd\n");
> +
> +	spi->mtd.owner = THIS_MODULE;
> +	spi->mtd.dev.parent = device;
> +	spi->mtd.flags = MTD_CAP_NORFLASH | MTD_WRITEABLE;
> +	spi->mtd.type = MTD_DATAFLASH;
> +	spi->mtd.priv = spi;
> +	spi->mtd._write = i915_spi_write;
> +	spi->mtd._read = i915_spi_read;
> +	spi->mtd._erase = i915_spi_erase;
> +	spi->mtd._get_device = i915_spi_get_device;
> +	spi->mtd._put_device = i915_spi_put_device;
> +	spi->mtd.writesize = SZ_1; /* 1 byte granularity */

You say writesize should be aligned with 4 in your next patch?

> +	spi->mtd.erasesize = SZ_4K; /* 4K bytes granularity */
> +	spi->mtd.size = spi->size;
> +
> +	parts = kcalloc(spi->nregions, sizeof(*parts), GFP_KERNEL);
> +	if (!parts)
> +		return -ENOMEM;
> +
> +	for (i = 0, n = 0; i < spi->nregions && n < nparts; i++) {
> +		if (!spi->regions[i].is_readable)
> +			continue;
> +		parts[n].name = spi->regions[i].name;
> +		parts[n].offset  = spi->regions[i].offset;
> +		parts[n].size = spi->regions[i].size;
> +		if (!spi->regions[i].is_writable)
> +			parts[n].mask_flags = MTD_WRITEABLE;
> +		n++;
> +	}
> +
> +	ret = mtd_device_register(&spi->mtd, parts, n);
> +
> +	kfree(parts);
> +
> +	return ret;
> +}
> +

Thanks,
Miquèl

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

  reply	other threads:[~2023-10-16  8:39 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   ` Miquel Raynal [this message]
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         ` [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=20231016103939.67445bee@xps-13 \
    --to=miquel.raynal@bootlin.com \
    --cc=alexander.usyskin@intel.com \
    --cc=intel-gfx@lists.freedesktop.org \
    --cc=linux-mtd@lists.infradead.org \
    --cc=lucas.demarchi@intel.com \
    --cc=richard@nod.at \
    --cc=rodrigo.vivi@intel.com \
    --cc=tomas.winkler@intel.com \
    --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.