Intel-XE Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Matthew Brost <matthew.brost@intel.com>
To: Michal Wajdeczko <michal.wajdeczko@intel.com>
Cc: intel-xe@lists.freedesktop.org
Subject: Re: [PATCH 2/2] drm/xe/guc: Add kernel-doc for xe_guc_ct_send_recv()
Date: Thu, 18 Jan 2024 18:38:14 +0000	[thread overview]
Message-ID: <ZalwFtTe+5fb7H3A@DUT025-TGLU.fm.intel.com> (raw)
In-Reply-To: <932f978f-0016-4393-93c0-aac32007e3f5@intel.com>

On Sat, Jan 13, 2024 at 02:01:05PM +0100, Michal Wajdeczko wrote:
> 
> 
> On 13.01.2024 00:12, Matthew Brost wrote:
> > On Fri, Jan 12, 2024 at 11:25:54AM +0100, Michal Wajdeczko wrote:
> >> The communication with the GuC firmware is crucial for the driver
> >> but unfortunately it has limited documentation.  Add initial
> > 
> > The first sentence doesn't seem necessary.
> 
> can drop while pushing
> 

With that:
Reviewed-by: Matthew Brost <matthew.brost@intel.com>

> > 
> >> documentation for recently updated xe_guc_ct_send_recv().
> >>
> >> Signed-off-by: Michal Wajdeczko <michal.wajdeczko@intel.com>
> >> Cc: Matthew Brost <matthew.brost@intel.com>
> >> ---
> >>  drivers/gpu/drm/xe/xe_guc_ct.c | 18 ++++++++++++++++++
> >>  1 file changed, 18 insertions(+)
> >>
> >> diff --git a/drivers/gpu/drm/xe/xe_guc_ct.c b/drivers/gpu/drm/xe/xe_guc_ct.c
> >> index 4ae1a0cd9537..ee5d99456aeb 100644
> >> --- a/drivers/gpu/drm/xe/xe_guc_ct.c
> >> +++ b/drivers/gpu/drm/xe/xe_guc_ct.c
> >> @@ -785,6 +785,24 @@ static int guc_ct_send_recv(struct xe_guc_ct *ct, const u32 *action, u32 len,
> >>  	return ret > 0 ? response_buffer ? g2h_fence.response_len : g2h_fence.response_data : ret;
> >>  }
> >>  
> >> +/**
> >> + * xe_guc_ct_send_recv - Send and receive HXG to the GuC
> >> + * @ct: the &xe_guc_ct
> >> + * @action: the dword array with `HXG Request`_ message (can't be NULL)
> > 
> > What's the deal with the _ trailing everwhere? Is this kernel doc link thing?
> 
> yes, see [1]
> 
> [1]
> https://docutils.sourceforge.io/docs/ref/rst/restructuredtext.html#hyperlink-references
> 
> 
> > 
> > Matt
> > 
> >> + * @len: length of the `HXG Request`_ message (in dwords, can't be 0)
> >> + * @response_buffer: placeholder for the `HXG Response`_ message (can be NULL)
> >> + *
> >> + * Send a `HXG Request`_ message to the GuC over CT communication channel and
> >> + * blocks until GuC replies with a `HXG Response`_ message.
> >> + *
> >> + * For non-blocking communication with GuC use xe_guc_ct_send().
> >> + *
> >> + * Note: The size of &response_buffer must be at least GUC_CTB_MAX_DWORDS_.
> >> + *
> >> + * Return: response length (in dwords) if &response_buffer was not NULL, or
> >> + *         DATA0 from `HXG Response`_ if &response_buffer was NULL, or
> >> + *         a negative error code on failure.
> >> + */
> >>  int xe_guc_ct_send_recv(struct xe_guc_ct *ct, const u32 *action, u32 len,
> >>  			u32 *response_buffer)
> >>  {
> >> -- 
> >> 2.25.1
> >>

  reply	other threads:[~2024-01-18 18:40 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-01-12 10:25 [PATCH 1/2] drm/xe/guc: Return CTB HXG response DATA0 if no buffer provided Michal Wajdeczko
2024-01-12 10:25 ` [PATCH 2/2] drm/xe/guc: Add kernel-doc for xe_guc_ct_send_recv() Michal Wajdeczko
2024-01-12 23:12   ` Matthew Brost
2024-01-13 13:01     ` Michal Wajdeczko
2024-01-18 18:38       ` Matthew Brost [this message]
2024-01-12 10:44 ` ✓ CI.Patch_applied: success for series starting with [1/2] drm/xe/guc: Return CTB HXG response DATA0 if no buffer provided Patchwork
2024-01-12 10:45 ` ✓ CI.checkpatch: " Patchwork
2024-01-12 10:45 ` ✓ CI.KUnit: " Patchwork
2024-01-12 10:53 ` ✓ CI.Build: " Patchwork
2024-01-12 10:53 ` ✓ CI.Hooks: " Patchwork
2024-01-12 10:54 ` ✓ CI.checksparse: " Patchwork
2024-01-12 11:17 ` ✓ CI.BAT: " Patchwork
2024-01-12 23:10 ` [PATCH 1/2] " Matthew Brost

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=ZalwFtTe+5fb7H3A@DUT025-TGLU.fm.intel.com \
    --to=matthew.brost@intel.com \
    --cc=intel-xe@lists.freedesktop.org \
    --cc=michal.wajdeczko@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox