linux-fbdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Tomi Valkeinen <tomi.valkeinen@ti.com>
To: "H. Nikolaus Schaller" <hns@goldelico.com>
Cc: linux-fbdev@vger.kernel.org, linux-kernel@vger.kernel.org,
	dri-devel@lists.freedesktop.org, gta04-owner@goldelico.com,
	Laurent Pinchart <laurent.pinchart@ideasonboard.com>,
	linux-omap@vger.kernel.org,
	Jean-Christophe Plagniol-Villard <plagnioj@jcrosoft.com>
Subject: Re: [PATCH 1/2] video:omap2:dss: fix timings for VENC to match what omapdrm expects
Date: Tue, 15 Dec 2015 12:53:24 +0000	[thread overview]
Message-ID: <56700D44.9090100@ti.com> (raw)
In-Reply-To: <5BB301DB-5429-422E-B672-E7A508441C45@goldelico.com>

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


On 13/12/15 20:41, H. Nikolaus Schaller wrote:

> Great that you did find the real reason of the problem.
> 
> I have tested it on the GTA04 and it also works.
> 
> Will the patches arrive in 4.5?

4.4, I hope.

 Tomi


[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 819 bytes --]

  reply	other threads:[~2015-12-15 12:53 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 [this message]
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
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=56700D44.9090100@ti.com \
    --to=tomi.valkeinen@ti.com \
    --cc=dri-devel@lists.freedesktop.org \
    --cc=gta04-owner@goldelico.com \
    --cc=hns@goldelico.com \
    --cc=laurent.pinchart@ideasonboard.com \
    --cc=linux-fbdev@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-omap@vger.kernel.org \
    --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).