linux-fbdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Laurent Pinchart <laurent.pinchart@ideasonboard.com>
To: linux-fbdev@vger.kernel.org
Subject: Re: [PATCH] videomode: provide dummy of_get_display_timing helper
Date: Mon, 29 Sep 2014 20:43:19 +0000	[thread overview]
Message-ID: <1509068.h69CH2ppLS@avalon> (raw)
In-Reply-To: <1957575.to7BPgiTer@wuerfel>

Hi Arnd,

Thank you for the patch.

On Monday 29 September 2014 18:00:33 Arnd Bergmann wrote:
> If CONFIG_OF is disabled but we build any driver that tries to
> use of_get_display_timing, we get this link error:
> 
> ERROR: "of_get_display_timing" [drivers/gpu/drm/rcar-du/rcar-du-drm.ko]
> undefined!
> 
> This adds an empty inline function as an alternative, to avoid changing
> each driver using this function when we want to build them without
> CONFIG_OF.
> 
> Signed-off-by: Arnd Bergmann <arnd@arndb.de>

Shouldn't empty functions also be defined for of_get_display_timings and 
of_display_timings_exist ?

> diff --git a/include/video/of_display_timing.h
> b/include/video/of_display_timing.h index 79e6697af6cf..02b6eb7c3ded 100644
> --- a/include/video/of_display_timing.h
> +++ b/include/video/of_display_timing.h
> @@ -15,8 +15,17 @@ struct display_timings;
> 
>  #define OF_USE_NATIVE_MODE -1
> 
> +#ifdef CONFIG_OF
>  int of_get_display_timing(struct device_node *np, const char *name,
>  		struct display_timing *dt);
> +#else
> +static inline int of_get_display_timing(struct device_node *np, const char
> *name,
> +		struct display_timing *dt)
> +{
> +	return -ENOSYS;
> +}
> +
> +#endif
>  struct display_timings *of_get_display_timings(struct device_node *np);
>  int of_display_timings_exist(struct device_node *np);

-- 
Regards,

Laurent Pinchart


  reply	other threads:[~2014-09-29 20:43 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-09-29 16:00 [PATCH] videomode: provide dummy of_get_display_timing helper Arnd Bergmann
2014-09-29 20:43 ` Laurent Pinchart [this message]
2014-10-06 12:18 ` Tomi Valkeinen

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=1509068.h69CH2ppLS@avalon \
    --to=laurent.pinchart@ideasonboard.com \
    --cc=linux-fbdev@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).