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.freedeskop.org
Cc: anshuman.gupta@intel.com, rodrigo.vivi@intel.com,
	alexander.usyskin@intel.com, gregkh@linuxfoundation.org
Subject: Re: [RFC 1/9] mei: late_bind: add late binding component driver
Date: Tue, 29 Apr 2025 11:55:48 +0300	[thread overview]
Message-ID: <87v7qnwdm3.fsf@intel.com> (raw)
In-Reply-To: <20250429073804.972137-2-badal.nilawar@intel.com>

On Tue, 29 Apr 2025, Badal Nilawar <badal.nilawar@intel.com> wrote:
> diff --git a/include/drm/intel/xe_late_bind_mei_interface.h b/include/drm/intel/xe_late_bind_mei_interface.h
> new file mode 100644
> index 000000000000..4005c4c6184f
> --- /dev/null
> +++ b/include/drm/intel/xe_late_bind_mei_interface.h
> @@ -0,0 +1,49 @@
> +/* SPDX-License-Identifier: MIT */
> +/*
> + * Copyright (c) 2025 Intel Corporation
> + */
> +
> +#ifndef _XE_LATE_BIND_MEI_INTERFACE_H_
> +#define _XE_LATE_BIND_MEI_INTERFACE_H_
> +
> +#include <linux/types.h>
> +
> +struct device;
> +struct module;
> +
> +/**
> + * struct xe_late_bind_component_ops - ops for Late Binding services.
> + * @owner: Module providing the ops
> + * @push_config: Sends a config to FW.
> + */
> +struct xe_late_bind_component_ops {

Please don't name the file after xe, please don't name the structs after
xe. The whole directory include/drm/intel/ is supposed to be agnostic to
i915 or xe, even if the current naming has i915 for historical
reasons.

Aim for generic interfaces and solutions and naming instead of doing
something specific for xe, even if the first user is xe.

BR,
Jani.


> +	struct module *owner;
> +
> +	/**
> +	 * @push_config: Sends a config to FW.
> +	 * @dev: device struct corresponding to the mei device
> +	 * @type: payload type
> +	 * @flags: payload flags
> +	 * @payload: payload buffer
> +	 * @payload_size: payload buffer size
> +	 *
> +	 * Return: 0 success, negative errno value on transport failure,
> +	 *         positive status returned by FW
> +	 */
> +	int (*push_config)(struct device *dev, u32 type, u32 flags,
> +			   const void *payload, size_t payload_size);
> +};
> +
> +/**
> + * struct xe_late_bind_component - Late Binding services component
> + * @mei_dev: device that provide Late Binding service.
> + * @ops: Ops implemented by Late Binding driver, used by Xe driver.
> + *
> + * Communication between Xe and MEI drivers for Late Binding services
> + */
> +struct xe_late_bind_component {
> +	struct device *mei_dev;
> +	const struct xe_late_bind_component_ops *ops;
> +};
> +
> +#endif /* _XE_LATE_BIND_MEI_INTERFACE_H_ */

-- 
Jani Nikula, Intel

  reply	other threads:[~2025-04-29  8:55 UTC|newest]

Thread overview: 22+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-04-29  7:37 [RFC 0/9] Introducing firmware late binding Badal Nilawar
2025-04-29  7:37 ` [RFC 1/9] mei: late_bind: add late binding component driver Badal Nilawar
2025-04-29  8:55   ` Jani Nikula [this message]
2025-04-30 12:23     ` Nilawar, Badal
2025-04-29  7:37 ` [RFC 2/9] mei: bus: add mei_cldev_mtu interface Badal Nilawar
2025-04-29  7:37 ` [RFC 3/9] drm/xe/late_bind_fw: Introducing late_bind_fw Badal Nilawar
2025-04-29  7:37 ` [RFC 4/9] drm/xe/xe_late_bind_fw: Initialize late binding firmware Badal Nilawar
2025-04-29  7:38 ` [RFC 5/9] drm/xe/xe_late_bind_fw: Load " Badal Nilawar
2025-04-29  7:38 ` [RFC 6/9] drm/xe/xe_late_bind_fw: Reload late binding fw in rpm resume Badal Nilawar
2025-04-29  7:38 ` [RFC 7/9] drm/xe/xe_late_bind_fw: Reload late binding fw in S2Idle/S3 resume Badal Nilawar
2025-04-29  7:38 ` [RFC 8/9] drm/xe/xe_late_bind_fw: Introduce debug fs node to disable late binding Badal Nilawar
2025-04-29  7:38 ` [RFC 9/9] {fwctl,drm}/xe/pcode: Introduce xe_pcode_fwctl Badal Nilawar
2025-04-29  9:15 ` ✓ CI.Patch_applied: success for Introducing firmware late binding Patchwork
2025-04-29  9:15 ` ✗ CI.checkpatch: warning " Patchwork
2025-04-29  9:17 ` ✓ CI.KUnit: success " Patchwork
2025-04-29  9:39 ` ✓ CI.Build: " Patchwork
2025-04-29  9:41 ` ✗ CI.Hooks: failure " Patchwork
2025-04-29  9:43 ` ✗ CI.checksparse: warning " Patchwork
2025-04-29 10:39 ` ✗ Xe.CI.Full: failure " Patchwork
2025-04-29 15:58 ` [RFC 0/9] " Nilawar, Badal
2025-05-06  7:14 ` ✗ Xe.CI.BAT: failure for " Patchwork
2025-05-06  7:51 ` 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=87v7qnwdm3.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=dri-devel@lists.freedeskop.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.