From: Laurent Pinchart <laurent.pinchart@ideasonboard.com>
To: Tomi Valkeinen <tomi.valkeinen@ti.com>
Cc: linux-fbdev@vger.kernel.org,
"H. Nikolaus Schaller" <hns@goldelico.com>,
linux-kernel@vger.kernel.org, dri-devel@lists.freedesktop.org,
gta04-owner@goldelico.com, linux-omap@vger.kernel.org,
Jean-Christophe Plagniol-Villard <plagnioj@jcrosoft.com>
Subject: Re: [PATCH 2/2] video:omapdrm: make omapdrm assume the tv-out cable is always connected
Date: Fri, 13 Nov 2015 14:01:04 +0200 [thread overview]
Message-ID: <3973104.FPbEEICOqe@avalon> (raw)
In-Reply-To: <5645CD79.5040107@ti.com>
On Friday 13 November 2015 13:46:01 Tomi Valkeinen wrote:
> On 13/11/15 12:29, H. Nikolaus Schaller wrote:
> > Include VENC in the set of drivers where it is assimed that the cable
> > is always connected. Like DPI, DSI, DBI and SDI do.
> >
> > Otherwise, the VENC will return cable status "unknown" and is not enabled
> > by the X-server. So there is no video output signal.
> >
> > Tested on: BeagleBoard XM, GTA04 and OpenPandora
> >
> > Signed-off-by: H. Nikolaus Schaller <hns@goldelico.com>
> > ---
> >
> > drivers/gpu/drm/omapdrm/omap_connector.c | 1 +
> > 1 file changed, 1 insertion(+)
> >
> > diff --git a/drivers/gpu/drm/omapdrm/omap_connector.c
> > b/drivers/gpu/drm/omapdrm/omap_connector.c index 83f2a91..98ddb5d 100644
> > --- a/drivers/gpu/drm/omapdrm/omap_connector.c
> > +++ b/drivers/gpu/drm/omapdrm/omap_connector.c
> > @@ -120,6 +120,7 @@ static enum drm_connector_status
> > omap_connector_detect(
> > else
> > ret = connector_status_disconnected;
> > } else if (dssdev->type == OMAP_DISPLAY_TYPE_DPI ||
> > + dssdev->type == OMAP_DISPLAY_TYPE_VENC ||
> > dssdev->type == OMAP_DISPLAY_TYPE_DBI ||
> > dssdev->type == OMAP_DISPLAY_TYPE_SDI ||
> > dssdev->type == OMAP_DISPLAY_TYPE_DSI) {
>
> I have no idea why VENC is not working for you when using
> connector_status_unknown, but I just tested DPI with
> connector_status_unknown (i.e. changed the above func to return unknown
> for DPI), and it works fine with X and X omap driver. And xrandr
> confirms that the connection status is unknown:
>
> # xrandr
> Screen 0: minimum 320 x 200, current 1920 x 1200, maximum 2048 x 2048
> HDMI-1 disconnected (normal left inverted right x axis y axis)
> None-1 unknown connection 1920x1200+0+0 (normal left inverted right x
> axis y axis) 0mm x 0mm
> 1920x1200 60.00*+ 60.00 +
>
> Grep also shows that there are many drivers using
> connector_status_unknown, so I'm guessing it should work fine...
And beside it's not right to consider VENC as always connected, as it isn't.
The unknown status is there for a reason, to describe connectors for which we
can't get any status information. The situation is different for DPI, DBI, SDI
and DSI as those are on-board busses that connect to a non-removable panel, so
we can say with a good confidence that the panel is connected (the situation
could be changed with a hammer and a chisel, but that's unlikely to happen,
hence the confidence).
--
Regards,
Laurent Pinchart
_______________________________________________
dri-devel mailing list
dri-devel@lists.freedesktop.org
http://lists.freedesktop.org/mailman/listinfo/dri-devel
next prev parent reply other threads:[~2015-11-13 12:01 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-11-13 10:29 [PATCH 0/2] Fix omap VENC (PAL/NTSC TV out) operation with omapdrm driver H. Nikolaus Schaller
2015-11-13 10:29 ` [PATCH 1/2] video:omap2:dss: fix timings for VENC to match what omapdrm expects H. Nikolaus Schaller
2015-12-09 8:18 ` Tomi Valkeinen
2015-12-13 18:41 ` H. Nikolaus Schaller
2015-12-15 12:53 ` Tomi Valkeinen
2015-11-13 10:29 ` [PATCH 2/2] video:omapdrm: make omapdrm assume the tv-out cable is always connected H. Nikolaus Schaller
2015-11-13 11:46 ` Tomi Valkeinen
2015-11-13 12:01 ` Laurent Pinchart [this message]
2015-11-13 13:31 ` H. Nikolaus Schaller
2015-11-13 16:45 ` H. Nikolaus Schaller
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=3973104.FPbEEICOqe@avalon \
--to=laurent.pinchart@ideasonboard.com \
--cc=dri-devel@lists.freedesktop.org \
--cc=gta04-owner@goldelico.com \
--cc=hns@goldelico.com \
--cc=linux-fbdev@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-omap@vger.kernel.org \
--cc=plagnioj@jcrosoft.com \
--cc=tomi.valkeinen@ti.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).