From: Sergei Shtylyov <sergei.shtylyov@cogentembedded.com>
To: Laurent Pinchart <laurent.pinchart+renesas@ideasonboard.com>,
linux-media@vger.kernel.org, dri-devel@lists.freedesktop.org
Cc: linux-renesas-soc@vger.kernel.org
Subject: Re: [PATCH 5/9] v4l: vsp1: Document the vsp1_du_atomic_config structure
Date: Mon, 4 Dec 2017 12:31:49 +0300 [thread overview]
Message-ID: <9703309e-d841-f8dc-b37a-be7a96ce91ae@cogentembedded.com> (raw)
In-Reply-To: <20171203105735.10529-6-laurent.pinchart+renesas@ideasonboard.com>
Hello!
On 12/3/2017 1:57 PM, Laurent Pinchart wrote:
> The structure is used in the API that the VSP1 driver exposes to the DU
> driver. Documenting it is thus important.
>
> Signed-off-by: Laurent Pinchart <laurent.pinchart+renesas@ideasonboard.com>
> ---
> include/media/vsp1.h | 10 ++++++++++
> 1 file changed, 10 insertions(+)
>
> diff --git a/include/media/vsp1.h b/include/media/vsp1.h
> index 68a8abe4fac5..7850f96fb708 100644
> --- a/include/media/vsp1.h
> +++ b/include/media/vsp1.h
> @@ -41,6 +41,16 @@ struct vsp1_du_lif_config {
> int vsp1_du_setup_lif(struct device *dev, unsigned int pipe_index,
> const struct vsp1_du_lif_config *cfg);
>
> +/**
> + * struct vsp1_du_atomic_config - VSP atomic configuration parameters
> + * @pixelformat: plan pixel format (V4L2 4CC)
s/plan/plane/?
[...]
MBR, Sergei
next prev parent reply other threads:[~2017-12-04 9:31 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-12-03 10:57 [PATCH 0/9] R-Car DU: Support CRC calculation Laurent Pinchart
2017-12-03 10:57 ` [PATCH 1/9] v4l: vsp1: Fix display stalls when requesting too many inputs Laurent Pinchart
2017-12-15 10:11 ` Kieran Bingham
2017-12-03 10:57 ` [PATCH 2/9] v4l: vsp1: Print the correct blending unit name in debug messages Laurent Pinchart
2017-12-15 10:13 ` Kieran Bingham
2017-12-03 10:57 ` [PATCH 3/9] v4l: vsp1: Share the CLU, LIF and LUT set_fmt pad operation code Laurent Pinchart
2017-12-03 10:57 ` [PATCH 4/9] v4l: vsp1: Reset the crop and compose rectangles in the set_fmt helper Laurent Pinchart
2017-12-03 10:57 ` [PATCH 5/9] v4l: vsp1: Document the vsp1_du_atomic_config structure Laurent Pinchart
2017-12-04 9:31 ` Sergei Shtylyov [this message]
2017-12-04 11:14 ` Laurent Pinchart
2017-12-03 10:57 ` [PATCH 6/9] v4l: vsp1: Extend the DU API to support CRC computation Laurent Pinchart
2017-12-03 10:57 ` [PATCH 7/9] v4l: vsp1: Add support for the DISCOM entity Laurent Pinchart
2017-12-03 10:57 ` [PATCH 8/9] v4l: vsp1: Integrate DISCOM in display pipeline Laurent Pinchart
2017-12-03 10:57 ` [PATCH 9/9] drm: rcar-du: Add support for CRC computation Laurent Pinchart
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=9703309e-d841-f8dc-b37a-be7a96ce91ae@cogentembedded.com \
--to=sergei.shtylyov@cogentembedded.com \
--cc=dri-devel@lists.freedesktop.org \
--cc=laurent.pinchart+renesas@ideasonboard.com \
--cc=linux-media@vger.kernel.org \
--cc=linux-renesas-soc@vger.kernel.org \
/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;
as well as URLs for NNTP newsgroup(s).