All of lore.kernel.org
 help / color / mirror / Atom feed
From: Thierry Reding <thierry.reding@gmail.com>
To: Sean Paul <seanpaul@chromium.org>
Cc: devicetree-discuss@lists.ozlabs.org, linux-doc@vger.kernel.org,
	dri-devel@lists.freedesktop.org, robdclark@gmail.com,
	daniel@ffwll.ch, airlied@linux.ie, marcheu@chromium.org
Subject: Re: [PATCH v2 2/2] drm/bridge: Add PTN3460 bridge driver
Date: Thu, 15 Aug 2013 17:28:13 +0200	[thread overview]
Message-ID: <20130815152812.GF16951@ulmo> (raw)
In-Reply-To: <1376513258-25703-3-git-send-email-seanpaul@chromium.org>

[-- Attachment #1: Type: text/plain, Size: 999 bytes --]

On Wed, Aug 14, 2013 at 04:47:38PM -0400, Sean Paul wrote:
[...]
> +int ptn3460_init(struct drm_device *dev, struct drm_encoder *encoder,
> +		struct i2c_client *client, struct device_node *node)
[...]
> +	ptn_bridge->gpio_pd_n = of_get_named_gpio(node, "powerdown-gpio", 0);

of_get_named_gpio() can return -EPROBE_DEFER and I wonder how you handle
that in the driver that uses ptn3460_init(). Since you pass in an
initialized drm_device, you'd need to undo all of that in case of
-EPROBE_DEFER. Well I guess you'd have to do that in case of any error,
but it makes things difficult to handle for drivers.

For instance on Tegra we pretty much delay DRM initialization until all
required subdevices (there are quite a few) have been probed, so if we
wanted to use this function we'd have to call it after all drivers have
been probed because only then do we have access to a struct drm_device.
That will cause other problems, however, because at that point we can't
defer probing anymore.

Thierry

[-- Attachment #2: Type: application/pgp-signature, Size: 836 bytes --]

  reply	other threads:[~2013-08-15 15:28 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-08-14 20:47 [PATCH v2 0/2] drm: Add drm_bridge and PTN3460 bridge driver Sean Paul
2013-08-14 20:47 ` [PATCH v2 1/2] drm: Add drm_bridge Sean Paul
2013-08-29 15:59   ` Sean Paul
2013-08-29 16:13     ` Rob Clark
2013-08-29 19:44       ` Daniel Vetter
2013-08-30 16:58   ` Rob Clark
2013-08-14 20:47 ` [PATCH v2 2/2] drm/bridge: Add PTN3460 bridge driver Sean Paul
2013-08-15 15:28   ` Thierry Reding [this message]
2013-08-15 19:32     ` Sean Paul
2013-08-15 20:42       ` Thierry Reding
2013-08-15 20:51         ` 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=20130815152812.GF16951@ulmo \
    --to=thierry.reding@gmail.com \
    --cc=airlied@linux.ie \
    --cc=daniel@ffwll.ch \
    --cc=devicetree-discuss@lists.ozlabs.org \
    --cc=dri-devel@lists.freedesktop.org \
    --cc=linux-doc@vger.kernel.org \
    --cc=marcheu@chromium.org \
    --cc=robdclark@gmail.com \
    --cc=seanpaul@chromium.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 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.