All of lore.kernel.org
 help / color / mirror / Atom feed
From: Gabriel Krisman Bertazi <krisman@collabora.co.uk>
To: Tomeu Vizoso <tomeu.vizoso@collabora.com>
Cc: dri-devel@lists.freedesktop.org
Subject: Re: [PATCH v6 2/4] drm/dp: add helpers for capture of frame CRCs
Date: Tue, 07 Mar 2017 15:26:36 -0300	[thread overview]
Message-ID: <877f413pur.fsf@dilma.collabora.co.uk> (raw)
In-Reply-To: <20170303133936.14964-3-tomeu.vizoso@collabora.com> (Tomeu Vizoso's message of "Fri, 3 Mar 2017 14:39:34 +0100")

Tomeu Vizoso <tomeu.vizoso@collabora.com> writes:

> +
> +/**
> + * drm_dp_start_crc() - start capture of frame CRCs
> + * @aux: DisplayPort AUX channel
> + *
> + * Returns 0 on success or a negative error code on failure.
> + */
> +int drm_dp_start_crc(struct drm_dp_aux *aux, struct drm_crtc *crtc)
> +{
> +	u8 buf;
> +	int ret;
> +
> +	ret = drm_dp_dpcd_readb(aux, DP_TEST_SINK, &buf);
> +	if (ret < 0)
> +		return ret;
> +
> +	ret = drm_dp_dpcd_writeb(aux, DP_TEST_SINK, buf | DP_TEST_SINK_START);
> +	if (ret < 0)
> +		return ret;
> +
> +	aux->crc_count = 0;
> +	aux->crtc = crtc;
> +	schedule_work(&aux->crc_work);
> +
> +	return 0;
> +}
> +EXPORT_SYMBOL(drm_dp_start_crc);
> +

Hi Tomeu,

This triggers a new warning when building documentation:

./drivers/gpu/drm/drm_dp_helper.c:1165: warning: No description found
for parameter 'crtc'
./drivers/gpu/drm/drm_dp_helper.c:1166: warning: No description found
for parameter 'crtc'

-- 
Gabriel Krisman Bertazi
_______________________________________________
dri-devel mailing list
dri-devel@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/dri-devel

  reply	other threads:[~2017-03-07 18:26 UTC|newest]

Thread overview: 30+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-03-03 13:39 [PATCH v6 0/4] drm/dp: Implement CRC debugfs API Tomeu Vizoso
2017-03-03 13:39 ` Tomeu Vizoso
2017-03-03 13:39 ` Tomeu Vizoso
2017-03-03 13:39 ` [PATCH v6 1/4] drm/dp: add crtc backpointer to drm_dp_aux Tomeu Vizoso
2017-03-03 13:39   ` Tomeu Vizoso
2017-03-03 13:39 ` [PATCH v6 2/4] drm/dp: add helpers for capture of frame CRCs Tomeu Vizoso
2017-03-03 13:39   ` Tomeu Vizoso
2017-03-07 18:26   ` Gabriel Krisman Bertazi [this message]
2017-03-07 20:35     ` [PATCH] drm/dp: Add missing description to parameter Tomeu Vizoso
2017-03-07 20:35       ` Tomeu Vizoso
2017-03-07 22:03       ` Sean Paul
2017-03-07 22:03         ` Sean Paul
2017-03-08  8:39         ` 0day 'make htmldocs' testing (was: Re: [PATCH] drm/dp: Add missing description to parameter) Jani Nikula
2017-03-08  8:41           ` Jani Nikula
2017-03-08  9:20             ` [kbuild-all] " Philip Li
2017-03-08  9:24             ` Fengguang Wu
2017-03-03 13:39 ` [PATCH v6 3/4] drm/bridge: analogix_dp: add helpers for capture of frame CRCs Tomeu Vizoso
2017-03-03 13:39   ` Tomeu Vizoso
2017-03-03 13:39 ` [PATCH v6 4/4] drm/rockchip: Implement CRC debugfs API Tomeu Vizoso
2017-03-03 13:39   ` Tomeu Vizoso
2017-03-03 13:39   ` Tomeu Vizoso
2017-03-06  0:55   ` Mark yao
2017-03-06  0:55     ` Mark yao
2017-03-06  0:55     ` Mark yao
2017-03-06 17:58   ` Emil Velikov
2017-03-06 17:58     ` Emil Velikov
2017-03-06 17:58     ` Emil Velikov
2017-03-06 17:19 ` [PATCH v6 0/4] drm/dp: " Sean Paul
2017-03-06 17:19   ` Sean Paul
2017-03-06 17:19   ` Sean Paul

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=877f413pur.fsf@dilma.collabora.co.uk \
    --to=krisman@collabora.co.uk \
    --cc=dri-devel@lists.freedesktop.org \
    --cc=tomeu.vizoso@collabora.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.