[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20180108211322.ilzzgde4vh2eozsf@valkosipuli.retiisi.org.uk>
Date: Mon, 8 Jan 2018 23:13:23 +0200
From: Sakari Ailus <sakari.ailus@....fi>
To: Kieran Bingham <kieran.bingham@...asonboard.com>
Cc: linux-media@...r.kernel.org, linux-renesas-soc@...r.kernel.org,
niklas.soderlund@...natech.se, Hans Verkuil <hverkuil@...all.nl>,
Kieran Bingham <kieran.bingham+renesas@...asonboard.com>,
Mauro Carvalho Chehab <mchehab@...nel.org>,
Jonathan Corbet <corbet@....net>,
Archit Taneja <architt@...eaurora.org>,
Neil Armstrong <narmstrong@...libre.com>,
open list <linux-kernel@...r.kernel.org>
Subject: Re: [PATCH v2] v4l: doc: Clarify v4l2_mbus_fmt height definition
Hi Kieran,
Thanks for the update.
On Mon, Jan 08, 2018 at 05:55:24PM +0000, Kieran Bingham wrote:
> The v4l2_mbus_fmt width and height corresponds directly with the
> v4l2_pix_format definitions, yet the differences in documentation make
> it ambiguous what to do in the event of field heights.
>
> Clarify this using the same text as is provided for the v4l2_pix_format
> which is explicit on the matter, and by matching the terminology of
> 'image height' rather than the misleading 'frame height'.
>
> Signed-off-by: Kieran Bingham <kieran.bingham+renesas@...asonboard.com>
Acked-by: Sakari Ailus <sakari.ailus@...ux.intel.com>
--
Sakari Ailus
e-mail: sakari.ailus@....fi
Powered by blists - more mailing lists