All of lore.kernel.org
 help / color / mirror / Atom feed
From: Jani Nikula <jani.nikula@linux.intel.com>
To: Badal Nilawar <badal.nilawar@intel.com>,
	intel-xe@lists.freedesktop.org, dri-devel@lists.freedesktop.org
Cc: anshuman.gupta@intel.com, rodrigo.vivi@intel.com,
	alexander.usyskin@intel.com, gregkh@linuxfoundation.org,
	daniele.ceraolospurio@intel.com
Subject: Re: [RFC 0/9] Introducing firmware late binding
Date: Wed, 30 Apr 2025 14:47:55 +0300	[thread overview]
Message-ID: <87jz71vpjo.fsf@intel.com> (raw)
In-Reply-To: <20250429160956.1014376-1-badal.nilawar@intel.com>

On Tue, 29 Apr 2025, Badal Nilawar <badal.nilawar@intel.com> wrote:
> Introducing firmware late binding feature to enable firmware loading
> for the devices, such as the fan controller and voltage regulator,
> during the driver probe.
> Typically, firmware for these devices are part of IFWI flash image but
> can be replaced at probe after OEM tuning.

I replied to the previous version [1], the comment has been ignored, and
there's no version information in this series on what changed.

Please don't do that.

BR,
Jani.


[1] https://lore.kernel.org/r/87v7qnwdm3.fsf@intel.com


>
> Alexander Usyskin (2):
>   mei: bus: add mei_cldev_mtu interface
>   mei: late_bind: add late binding component driver
>
> Badal Nilawar (6):
>   drm/xe/late_bind_fw: Introducing late_bind_fw
>   drm/xe/xe_late_bind_fw: Initialize late binding firmware
>   drm/xe/xe_late_bind_fw: Load late binding firmware
>   drm/xe/xe_late_bind_fw: Reload late binding fw in rpm resume
>   drm/xe/xe_late_bind_fw: Reload late binding fw in S2Idle/S3 resume
>   drm/xe/xe_late_bind_fw: Introduce debug fs node to disable late
>     binding
>
> Rodrigo Vivi (1):
>   {fwctl,drm}/xe/pcode: Introduce xe_pcode_fwctl
>
>  Documentation/userspace-api/fwctl/index.rst   |   1 +
>  drivers/gpu/drm/xe/Kconfig                    |   2 +
>  drivers/gpu/drm/xe/Makefile                   |   2 +
>  drivers/gpu/drm/xe/xe_debugfs.c               |  42 +++
>  drivers/gpu/drm/xe/xe_device.c                |   7 +
>  drivers/gpu/drm/xe/xe_device_types.h          |   4 +
>  drivers/gpu/drm/xe/xe_late_bind_fw.c          | 289 ++++++++++++++++++
>  drivers/gpu/drm/xe/xe_late_bind_fw.h          |  18 ++
>  drivers/gpu/drm/xe/xe_late_bind_fw_types.h    |  97 ++++++
>  drivers/gpu/drm/xe/xe_pci.c                   |   5 +
>  drivers/gpu/drm/xe/xe_pcode_fwctl.c           | 218 +++++++++++++
>  drivers/gpu/drm/xe/xe_pcode_fwctl.h           |  13 +
>  drivers/gpu/drm/xe/xe_pm.c                    |   7 +
>  drivers/misc/mei/Kconfig                      |   1 +
>  drivers/misc/mei/Makefile                     |   1 +
>  drivers/misc/mei/bus.c                        |  13 +
>  drivers/misc/mei/late_bind/Kconfig            |  12 +
>  drivers/misc/mei/late_bind/Makefile           |   9 +
>  drivers/misc/mei/late_bind/mei_late_bind.c    | 261 ++++++++++++++++
>  include/drm/intel/i915_component.h            |   1 +
>  .../drm/intel/xe_late_bind_mei_interface.h    |  49 +++
>  include/linux/mei_cl_bus.h                    |   1 +
>  include/uapi/fwctl/fwctl.h                    |   1 +
>  include/uapi/fwctl/xe_pcode.h                 |  80 +++++
>  24 files changed, 1134 insertions(+)
>  create mode 100644 drivers/gpu/drm/xe/xe_late_bind_fw.c
>  create mode 100644 drivers/gpu/drm/xe/xe_late_bind_fw.h
>  create mode 100644 drivers/gpu/drm/xe/xe_late_bind_fw_types.h
>  create mode 100644 drivers/gpu/drm/xe/xe_pcode_fwctl.c
>  create mode 100644 drivers/gpu/drm/xe/xe_pcode_fwctl.h
>  create mode 100644 drivers/misc/mei/late_bind/Kconfig
>  create mode 100644 drivers/misc/mei/late_bind/Makefile
>  create mode 100644 drivers/misc/mei/late_bind/mei_late_bind.c
>  create mode 100644 include/drm/intel/xe_late_bind_mei_interface.h
>  create mode 100644 include/uapi/fwctl/xe_pcode.h

-- 
Jani Nikula, Intel

  parent reply	other threads:[~2025-04-30 11:48 UTC|newest]

Thread overview: 41+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-04-29 16:09 [RFC 0/9] Introducing firmware late binding Badal Nilawar
2025-04-29 16:09 ` [RFC 1/9] mei: bus: add mei_cldev_mtu interface Badal Nilawar
2025-04-29 16:09 ` [RFC 2/9] mei: late_bind: add late binding component driver Badal Nilawar
2025-05-07 22:42   ` Daniele Ceraolo Spurio
2025-05-08  5:41     ` Usyskin, Alexander
2025-06-03 12:01       ` Nilawar, Badal
2025-04-29 16:09 ` [RFC 3/9] drm/xe/late_bind_fw: Introducing late_bind_fw Badal Nilawar
2025-05-02 13:02   ` kernel test robot
2025-05-07 21:38   ` Daniele Ceraolo Spurio
2025-06-03 13:52     ` Nilawar, Badal
2025-04-29 16:09 ` [RFC 4/9] drm/xe/xe_late_bind_fw: Initialize late binding firmware Badal Nilawar
2025-05-07 23:11   ` Daniele Ceraolo Spurio
2025-06-03 13:57     ` Nilawar, Badal
2025-04-29 16:09 ` [RFC 5/9] drm/xe/xe_late_bind_fw: Load " Badal Nilawar
2025-05-07 23:44   ` Daniele Ceraolo Spurio
2025-06-04  5:36     ` Nilawar, Badal
2025-04-29 16:09 ` [RFC 6/9] drm/xe/xe_late_bind_fw: Reload late binding fw in rpm resume Badal Nilawar
2025-04-29 16:09 ` [RFC 7/9] drm/xe/xe_late_bind_fw: Reload late binding fw in S2Idle/S3 resume Badal Nilawar
2025-04-29 16:09 ` [RFC 8/9] drm/xe/xe_late_bind_fw: Introduce debug fs node to disable late binding Badal Nilawar
2025-04-29 16:09 ` [RFC 9/9] {fwctl,drm}/xe/pcode: Introduce xe_pcode_fwctl Badal Nilawar
2025-05-01 15:44   ` Rodrigo Vivi
2025-05-06 18:13   ` Jason Gunthorpe
2025-05-07 19:49     ` Rodrigo Vivi
2025-05-07 22:04       ` Jason Gunthorpe
2025-08-22 19:33         ` Rodrigo Vivi
2025-08-28 12:48           ` Jason Gunthorpe
2025-06-06 13:47       ` Nilawar, Badal
2025-06-06 13:45     ` Nilawar, Badal
2025-06-30 22:01     ` Rodrigo Vivi
2025-06-30 22:45       ` Jason Gunthorpe
2025-04-29 16:13 ` ✓ CI.Patch_applied: success for Introducing firmware late binding (rev2) Patchwork
2025-04-29 16:14 ` ✗ CI.checkpatch: warning " Patchwork
2025-04-29 16:15 ` ✓ CI.KUnit: success " Patchwork
2025-04-29 16:23 ` ✓ CI.Build: " Patchwork
2025-04-29 16:26 ` ✗ CI.Hooks: failure " Patchwork
2025-04-29 16:27 ` ✗ CI.checksparse: warning " Patchwork
2025-04-29 19:02 ` ✗ Xe.CI.Full: failure " Patchwork
2025-04-30 11:47 ` Jani Nikula [this message]
2025-05-06  7:53 ` ✗ Xe.CI.BAT: " Patchwork
  -- strict thread matches above, loose matches on Subject: below --
2025-04-29  7:37 [RFC 0/9] Introducing firmware late binding Badal Nilawar
2025-04-29 15:58 ` Nilawar, Badal

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=87jz71vpjo.fsf@intel.com \
    --to=jani.nikula@linux.intel.com \
    --cc=alexander.usyskin@intel.com \
    --cc=anshuman.gupta@intel.com \
    --cc=badal.nilawar@intel.com \
    --cc=daniele.ceraolospurio@intel.com \
    --cc=dri-devel@lists.freedesktop.org \
    --cc=gregkh@linuxfoundation.org \
    --cc=intel-xe@lists.freedesktop.org \
    --cc=rodrigo.vivi@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.