From: Raag Jadav <raag.jadav@intel.com>
To: Alexander Usyskin <alexander.usyskin@intel.com>
Cc: "Miquel Raynal" <miquel.raynal@bootlin.com>,
"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, intel-xe@lists.freedesktop.org,
dri-devel@lists.freedesktop.org, intel-gfx@lists.freedesktop.org,
linux-kernel@vger.kernel.org, "Tomas Winkler" <tomasw@gmail.com>
Subject: Re: [PATCH v10 02/10] mtd: intel-dg: implement region enumeration
Date: Sat, 17 May 2025 01:21:58 +0300 [thread overview]
Message-ID: <aCe6hlGFG3v0cav9@black.fi.intel.com> (raw)
In-Reply-To: <20250515133345.2805031-3-alexander.usyskin@intel.com>
On Thu, May 15, 2025 at 04:33:37PM +0300, Alexander Usyskin wrote:
> In intel-dg, there is no access to the spi controller,
> the information is extracted from the descriptor region.
...
> +static int intel_dg_nvm_init(struct intel_dg_nvm *nvm, struct device *device)
> +{
> + int ret;
> + unsigned int i, n;
> + u32 access_map = 0;
Reverse xmas order (along with all other places) and
Reviewed-by: Raag Jadav <raag.jadav@intel.com>
> + /* clean error register, previous errors are ignored */
> + idg_nvm_error(nvm);
> +
> + ret = idg_nvm_is_valid(nvm);
> + if (ret) {
> + dev_err(device, "The MEM is not valid %d\n", ret);
> + return ret;
> + }
> +
> + if (idg_nvm_get_access_map(nvm, &access_map))
> + return -EIO;
> +
> + for (i = 0, n = 0; i < nvm->nregions; i++) {
> + u32 address, base, limit, region;
> + u8 id = nvm->regions[i].id;
> +
> + address = NVM_FLREG(id);
> + region = idg_nvm_read32(nvm, address);
> +
> + base = FIELD_GET(NVM_FREG_BASE_MASK, region) << NVM_FREG_ADDR_SHIFT;
> + limit = (FIELD_GET(NVM_FREG_ADDR_MASK, region) << NVM_FREG_ADDR_SHIFT) |
> + NVM_FREG_MIN_REGION_SIZE;
> +
> + dev_dbg(device, "[%d] %s: region: 0x%08X base: 0x%08x limit: 0x%08x\n",
> + id, nvm->regions[i].name, region, base, limit);
> +
> + if (base >= limit || (i > 0 && limit == 0)) {
> + dev_dbg(device, "[%d] %s: disabled\n",
> + id, nvm->regions[i].name);
> + nvm->regions[i].is_readable = 0;
> + continue;
> + }
> +
> + if (nvm->size < limit)
> + nvm->size = limit;
> +
> + nvm->regions[i].offset = base;
> + nvm->regions[i].size = limit - base + 1;
> + /* No write access to descriptor; mask it out*/
> + nvm->regions[i].is_writable = idg_nvm_region_writable(access_map, id);
> +
> + nvm->regions[i].is_readable = idg_nvm_region_readable(access_map, id);
> + dev_dbg(device, "Registered, %s id=%d offset=%lld size=%lld rd=%d wr=%d\n",
> + nvm->regions[i].name,
> + nvm->regions[i].id,
> + nvm->regions[i].offset,
> + nvm->regions[i].size,
> + nvm->regions[i].is_readable,
> + nvm->regions[i].is_writable);
> +
> + if (nvm->regions[i].is_readable)
> + n++;
> + }
> +
> + dev_dbg(device, "Registered %d regions\n", n);
> +
> + /* Need to add 1 to the amount of memory
> + * so it is reported as an even block
> + */
> + nvm->size += 1;
> +
> + return n;
> +}
> +
> static void intel_dg_nvm_release(struct kref *kref)
> {
> struct intel_dg_nvm *nvm = container_of(kref, struct intel_dg_nvm, refcnt);
> @@ -85,6 +285,12 @@ static int intel_dg_mtd_probe(struct auxiliary_device *aux_dev,
> goto err;
> }
>
> + ret = intel_dg_nvm_init(nvm, device);
> + if (ret < 0) {
> + dev_err(device, "cannot initialize nvm %d\n", ret);
> + goto err;
> + }
> +
> dev_set_drvdata(&aux_dev->dev, nvm);
>
> return 0;
> --
> 2.43.0
>
WARNING: multiple messages have this Message-ID (diff)
From: Raag Jadav <raag.jadav@intel.com>
To: Alexander Usyskin <alexander.usyskin@intel.com>
Cc: "Miquel Raynal" <miquel.raynal@bootlin.com>,
"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, intel-xe@lists.freedesktop.org,
dri-devel@lists.freedesktop.org, intel-gfx@lists.freedesktop.org,
linux-kernel@vger.kernel.org, "Tomas Winkler" <tomasw@gmail.com>
Subject: Re: [PATCH v10 02/10] mtd: intel-dg: implement region enumeration
Date: Sat, 17 May 2025 01:21:58 +0300 [thread overview]
Message-ID: <aCe6hlGFG3v0cav9@black.fi.intel.com> (raw)
In-Reply-To: <20250515133345.2805031-3-alexander.usyskin@intel.com>
On Thu, May 15, 2025 at 04:33:37PM +0300, Alexander Usyskin wrote:
> In intel-dg, there is no access to the spi controller,
> the information is extracted from the descriptor region.
...
> +static int intel_dg_nvm_init(struct intel_dg_nvm *nvm, struct device *device)
> +{
> + int ret;
> + unsigned int i, n;
> + u32 access_map = 0;
Reverse xmas order (along with all other places) and
Reviewed-by: Raag Jadav <raag.jadav@intel.com>
> + /* clean error register, previous errors are ignored */
> + idg_nvm_error(nvm);
> +
> + ret = idg_nvm_is_valid(nvm);
> + if (ret) {
> + dev_err(device, "The MEM is not valid %d\n", ret);
> + return ret;
> + }
> +
> + if (idg_nvm_get_access_map(nvm, &access_map))
> + return -EIO;
> +
> + for (i = 0, n = 0; i < nvm->nregions; i++) {
> + u32 address, base, limit, region;
> + u8 id = nvm->regions[i].id;
> +
> + address = NVM_FLREG(id);
> + region = idg_nvm_read32(nvm, address);
> +
> + base = FIELD_GET(NVM_FREG_BASE_MASK, region) << NVM_FREG_ADDR_SHIFT;
> + limit = (FIELD_GET(NVM_FREG_ADDR_MASK, region) << NVM_FREG_ADDR_SHIFT) |
> + NVM_FREG_MIN_REGION_SIZE;
> +
> + dev_dbg(device, "[%d] %s: region: 0x%08X base: 0x%08x limit: 0x%08x\n",
> + id, nvm->regions[i].name, region, base, limit);
> +
> + if (base >= limit || (i > 0 && limit == 0)) {
> + dev_dbg(device, "[%d] %s: disabled\n",
> + id, nvm->regions[i].name);
> + nvm->regions[i].is_readable = 0;
> + continue;
> + }
> +
> + if (nvm->size < limit)
> + nvm->size = limit;
> +
> + nvm->regions[i].offset = base;
> + nvm->regions[i].size = limit - base + 1;
> + /* No write access to descriptor; mask it out*/
> + nvm->regions[i].is_writable = idg_nvm_region_writable(access_map, id);
> +
> + nvm->regions[i].is_readable = idg_nvm_region_readable(access_map, id);
> + dev_dbg(device, "Registered, %s id=%d offset=%lld size=%lld rd=%d wr=%d\n",
> + nvm->regions[i].name,
> + nvm->regions[i].id,
> + nvm->regions[i].offset,
> + nvm->regions[i].size,
> + nvm->regions[i].is_readable,
> + nvm->regions[i].is_writable);
> +
> + if (nvm->regions[i].is_readable)
> + n++;
> + }
> +
> + dev_dbg(device, "Registered %d regions\n", n);
> +
> + /* Need to add 1 to the amount of memory
> + * so it is reported as an even block
> + */
> + nvm->size += 1;
> +
> + return n;
> +}
> +
> static void intel_dg_nvm_release(struct kref *kref)
> {
> struct intel_dg_nvm *nvm = container_of(kref, struct intel_dg_nvm, refcnt);
> @@ -85,6 +285,12 @@ static int intel_dg_mtd_probe(struct auxiliary_device *aux_dev,
> goto err;
> }
>
> + ret = intel_dg_nvm_init(nvm, device);
> + if (ret < 0) {
> + dev_err(device, "cannot initialize nvm %d\n", ret);
> + goto err;
> + }
> +
> dev_set_drvdata(&aux_dev->dev, nvm);
>
> return 0;
> --
> 2.43.0
>
______________________________________________________
Linux MTD discussion mailing list
http://lists.infradead.org/mailman/listinfo/linux-mtd/
next prev parent reply other threads:[~2025-05-16 22:22 UTC|newest]
Thread overview: 76+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-05-15 13:33 [PATCH v10 00/10] mtd: add driver for Intel discrete graphics Alexander Usyskin
2025-05-15 13:33 ` Alexander Usyskin
2025-05-15 13:33 ` [PATCH v10 01/10] mtd: add driver for intel graphics non-volatile memory device Alexander Usyskin
2025-05-15 13:33 ` Alexander Usyskin
2025-05-16 22:19 ` Raag Jadav
2025-05-16 22:19 ` Raag Jadav
2025-05-15 13:33 ` [PATCH v10 02/10] mtd: intel-dg: implement region enumeration Alexander Usyskin
2025-05-15 13:33 ` Alexander Usyskin
2025-05-16 22:21 ` Raag Jadav [this message]
2025-05-16 22:21 ` Raag Jadav
2025-05-15 13:33 ` [PATCH v10 03/10] mtd: intel-dg: implement access functions Alexander Usyskin
2025-05-15 13:33 ` Alexander Usyskin
2025-05-20 17:31 ` Raag Jadav
2025-05-20 17:31 ` Raag Jadav
2025-05-21 9:19 ` Usyskin, Alexander
2025-05-21 9:19 ` Usyskin, Alexander
2025-05-21 20:26 ` Raag Jadav
2025-05-21 20:26 ` Raag Jadav
2025-05-22 10:26 ` Usyskin, Alexander
2025-05-22 10:26 ` Usyskin, Alexander
2025-05-15 13:33 ` [PATCH v10 04/10] mtd: intel-dg: register with mtd Alexander Usyskin
2025-05-15 13:33 ` Alexander Usyskin
2025-05-21 21:37 ` Raag Jadav
2025-05-21 21:37 ` Raag Jadav
2025-05-22 12:14 ` Usyskin, Alexander
2025-05-22 12:14 ` Usyskin, Alexander
2025-05-15 13:33 ` [PATCH v10 05/10] mtd: intel-dg: align 64bit read and write Alexander Usyskin
2025-05-15 13:33 ` Alexander Usyskin
2025-05-24 10:01 ` Raag Jadav
2025-05-24 10:01 ` Raag Jadav
2025-05-27 6:03 ` Usyskin, Alexander
2025-05-27 6:03 ` Usyskin, Alexander
2025-05-27 18:49 ` Raag Jadav
2025-05-27 18:49 ` Raag Jadav
2025-05-15 13:33 ` [PATCH v10 06/10] drm/i915/nvm: add nvm device for discrete graphics Alexander Usyskin
2025-05-15 13:33 ` Alexander Usyskin
2025-05-24 10:20 ` Raag Jadav
2025-05-24 10:20 ` Raag Jadav
2025-05-27 6:00 ` Usyskin, Alexander
2025-05-27 6:00 ` Usyskin, Alexander
2025-05-27 18:35 ` Raag Jadav
2025-05-27 18:35 ` Raag Jadav
2025-05-28 6:29 ` Usyskin, Alexander
2025-05-28 6:29 ` Usyskin, Alexander
2025-05-15 13:33 ` [PATCH v10 07/10] drm/i915/nvm: add support for access mode Alexander Usyskin
2025-05-15 13:33 ` Alexander Usyskin
2025-05-15 13:33 ` [PATCH v10 08/10] drm/xe/nvm: add on-die non-volatile memory device Alexander Usyskin
2025-05-15 13:33 ` Alexander Usyskin
2025-05-24 10:29 ` Raag Jadav
2025-05-24 10:29 ` Raag Jadav
2025-05-27 6:25 ` Usyskin, Alexander
2025-05-27 6:25 ` Usyskin, Alexander
2025-05-27 18:37 ` Raag Jadav
2025-05-27 18:37 ` Raag Jadav
2025-05-28 6:30 ` Usyskin, Alexander
2025-05-28 6:30 ` Usyskin, Alexander
2025-05-15 13:33 ` [PATCH v10 09/10] drm/xe/nvm: add support for access mode Alexander Usyskin
2025-05-15 13:33 ` Alexander Usyskin
2025-05-15 13:33 ` [PATCH v10 10/10] drm/xe/nvm: add support for non-posted erase Alexander Usyskin
2025-05-15 13:33 ` Alexander Usyskin
2025-05-15 13:56 ` ✓ CI.Patch_applied: success for mtd: add driver for Intel discrete graphics (rev3) Patchwork
2025-05-15 13:57 ` ✗ CI.checkpatch: warning " Patchwork
2025-05-15 13:58 ` ✓ CI.KUnit: success " Patchwork
2025-05-15 14:08 ` ✓ CI.Build: " Patchwork
2025-05-15 14:11 ` ✓ CI.Hooks: " Patchwork
2025-05-15 14:12 ` ✗ CI.checksparse: warning " Patchwork
2025-05-15 14:18 ` ✗ Fi.CI.CHECKPATCH: warning for mtd: add driver for Intel discrete graphics (rev11) Patchwork
2025-05-15 14:18 ` ✗ Fi.CI.SPARSE: " Patchwork
2025-05-15 14:36 ` ✓ Xe.CI.BAT: success for mtd: add driver for Intel discrete graphics (rev3) Patchwork
2025-05-15 14:47 ` ✓ i915.CI.BAT: success for mtd: add driver for Intel discrete graphics (rev11) Patchwork
2025-05-15 16:57 ` ✗ i915.CI.Full: failure " Patchwork
2025-05-16 3:00 ` ✗ Xe.CI.Full: failure for mtd: add driver for Intel discrete graphics (rev3) Patchwork
2025-05-27 2:06 ` ✓ CI.Patch_applied: success " Patchwork
2025-05-27 2:07 ` ✗ CI.checkpatch: warning " Patchwork
2025-05-27 2:08 ` ✓ CI.KUnit: success " Patchwork
2025-05-27 2:18 ` ✓ CI.Build: " Patchwork
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=aCe6hlGFG3v0cav9@black.fi.intel.com \
--to=raag.jadav@intel.com \
--cc=airlied@gmail.com \
--cc=alexander.usyskin@intel.com \
--cc=dri-devel@lists.freedesktop.org \
--cc=intel-gfx@lists.freedesktop.org \
--cc=intel-xe@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=miquel.raynal@bootlin.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=tomasw@gmail.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 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.