From: Thierry Reding <thierry.reding@gmail.com>
To: Boris Brezillon <boris.brezillon@free-electrons.com>
Cc: David Airlie <airlied@linux.ie>,
dri-devel@lists.freedesktop.org,
Laurent Pinchart <laurent.pinchart@ideasonboard.com>,
linux-kernel@vger.kernel.org,
Nicolas Ferre <nicolas.ferre@atmel.com>,
Jean-Christophe Plagniol-Villard <plagnioj@jcrosoft.com>,
Alexandre Belloni <alexandre.belloni@free-electrons.com>,
Andrew Victor <linux@maxim.org.za>
Subject: Re: [PATCH v4 1/3] drm: add bus_formats and num_bus_formats fields to drm_display_info
Date: Mon, 1 Dec 2014 16:42:58 +0100 [thread overview]
Message-ID: <20141201154257.GD11943@ulmo.nvidia.com> (raw)
In-Reply-To: <1417422061-10384-6-git-send-email-boris.brezillon@free-electrons.com>
[-- Attachment #1: Type: text/plain, Size: 2653 bytes --]
On Mon, Dec 01, 2014 at 09:20:59AM +0100, Boris Brezillon wrote:
> Add bus_formats and num_bus_formats fields and
> drm_display_info_set_bus_formats helper function to specify the bus
> formats supported by a given display.
>
> This information can be used by display controller drivers to configure
> the output interface appropriately (i.e. RGB565, RGB666 or RGB888 on raw
> RGB or LVDS busses).
>
> Signed-off-by: Boris Brezillon <boris.brezillon@free-electrons.com>
> ---
> drivers/gpu/drm/drm_crtc.c | 32 ++++++++++++++++++++++++++++++++
> include/drm/drm_crtc.h | 7 +++++++
> 2 files changed, 39 insertions(+)
>
> diff --git a/drivers/gpu/drm/drm_crtc.c b/drivers/gpu/drm/drm_crtc.c
> index e79c8d3..d3b7ed0 100644
> --- a/drivers/gpu/drm/drm_crtc.c
> +++ b/drivers/gpu/drm/drm_crtc.c
> @@ -763,6 +763,38 @@ static void drm_mode_remove(struct drm_connector *connector,
> drm_mode_destroy(connector->dev, mode);
> }
>
> +/*
This needs a /** marker to make it a valid kerneldoc comment.
> + * drm_display_info_set_bus_formats - set the supported bus formats
> + * @info: display info to store bus formats in
> + * @fmts: array containing the supported bus formats
> + * @nfmts: the number of entries in the fmts array
> + *
> + * Store the suppported bus formats in display info structure.
> + * See MEDIA_BUS_FMT_* definitions in include/uapi/linux/media-bus-format.h for
> + * a full list of available formats.
> + */
> +int drm_display_info_set_bus_formats(struct drm_display_info *info, const u32 *fmts,
This one still exceeds 80-characters per line, but perhaps I'm reviewing
the wrong patch? Also I think fmts should be formats here.
> + unsigned int num_fmts)
And this should be num_formats, for consistency. Also make sure to keep
this consistent with the kerneldoc.
> +{
> + u32 *formats = NULL;
If you name the parameter formats, maybe bus_formats would be a good
alternative for this local variable. Or fmts here. I think it's most
important that the public API gets the more idiomatic name.
> +
> + if (!fmts && num_fmts)
> + return -EINVAL;
> +
> + if (fmts && num_fmts) {
> + formats = kmemdup(fmts, sizeof(*fmts) * num_fmts, GFP_KERNEL);
> + if (!formats)
> + return -ENOMEM;
> + }
> +
> + kfree(info->bus_formats);
> + info->bus_formats = formats;
> + info->num_bus_formats = num_fmts;
> +
> + return 0;
> +}
> +EXPORT_SYMBOL(drm_display_info_set_bus_formats);
I think you'll want to call kfree() on the bus_formats array from
drm_connector_cleanup() as well to make sure you don't leak this on
driver unload.
Thierry
[-- Attachment #2: Type: application/pgp-signature, Size: 819 bytes --]
next prev parent reply other threads:[~2014-12-01 15:43 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-12-01 8:20 [PATCH v4 0/3] drm: describe display bus format Boris Brezillon
2014-12-01 8:20 ` [PATCH v4 1/3] drm: add bus_formats and num_bus_formats fields to drm_display_info Boris Brezillon
2014-12-01 15:06 ` Philipp Zabel
2014-12-01 15:13 ` Boris Brezillon
2014-12-01 8:20 ` [PATCH v4 2/3] drm: panel: simple-panel: add support for bus_format retrieval Boris Brezillon
2014-12-01 8:20 ` [PATCH v4 3/3] drm: panel: simple-panel: add bus format information for foxlink panel Boris Brezillon
2014-12-01 8:20 ` [PATCH v4 0/3] drm: describe display bus format Boris Brezillon
2014-12-01 8:20 ` [PATCH v4 1/3] drm: add bus_formats and num_bus_formats fields to drm_display_info Boris Brezillon
2014-12-01 15:42 ` Thierry Reding [this message]
2014-12-01 21:22 ` Boris Brezillon
2014-12-01 8:21 ` [PATCH v4 2/3] drm: panel: simple-panel: add support for bus_format retrieval Boris Brezillon
2014-12-01 8:21 ` [PATCH v4 3/3] drm: panel: simple-panel: add bus format information for foxlink panel Boris Brezillon
2014-12-01 8:42 ` [PATCH RESEND v4 1/3] drm: add bus_formats and num_bus_formats fields to drm_display_info Boris Brezillon
2014-12-01 13:00 ` Laurent Pinchart
2014-12-01 13:06 ` Boris Brezillon
2014-12-01 15:18 ` Philipp Zabel
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=20141201154257.GD11943@ulmo.nvidia.com \
--to=thierry.reding@gmail.com \
--cc=airlied@linux.ie \
--cc=alexandre.belloni@free-electrons.com \
--cc=boris.brezillon@free-electrons.com \
--cc=dri-devel@lists.freedesktop.org \
--cc=laurent.pinchart@ideasonboard.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux@maxim.org.za \
--cc=nicolas.ferre@atmel.com \
--cc=plagnioj@jcrosoft.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;
as well as URLs for NNTP newsgroup(s).