linux-fbdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Fredrik Noring <noring@nocrew.org>
To: linux-fbdev@vger.kernel.org
Subject: Re: [PATCH] fbdev: Distinguish between interlaced and progressive modes
Date: Wed, 04 Jul 2018 19:08:48 +0000	[thread overview]
Message-ID: <20180704190846.GC2701@localhost.localdomain> (raw)
In-Reply-To: <20180622183754.GB17701@localhost.localdomain>

Hi Bartlomiej,

> > With this change fb_find_mode can match interlaced and progressive
> > modes equally well, and distinguish between for example 1920x1080i
> > and 1920x1080p.
> > 
> > Signed-off-by: Fredrik Noring <noring@nocrew.org>
> 
> Could you please give some examples of use cases that need this change
> (i.e. which fbdev drivers need it for which modes etc.)?

I discovered the problem when developing a frame buffer driver for the
PlayStation 2 (not yet merged), using the following video modes for the
PlayStation 3 in drivers/video/fbdev/ps3fb.c:

    }, {
	/* 1080if */
	"1080if", 50, 1920, 1080, 13468, 148, 484, 36, 4, 88, 5,
	FB_SYNC_BROADCAST, FB_VMODE_INTERLACED
    }, {
	/* 1080pf */
	"1080pf", 50, 1920, 1080, 6734, 148, 484, 36, 4, 88, 5,
	FB_SYNC_BROADCAST, FB_VMODE_NONINTERLACED
    },

In ps3fb_probe, the mode_option module parameter is used with fb_find_mode
but it can only select the interlaced variant of 1920x1080 since the loop
matching the modes does not take the difference between interlaced and
progressive modes into account.

In short, without the patch, progressive 1920x1080 cannot be chosen as a
mode_option parameter since fb_find_mode (falsely) thinks interlace is a
perfect match.

Fredrik

  parent reply	other threads:[~2018-07-04 19:08 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-06-22 18:37 [PATCH] fbdev: Distinguish between interlaced and progressive modes Fredrik Noring
2018-07-04 17:07 ` Bartlomiej Zolnierkiewicz
2018-07-04 19:08 ` Fredrik Noring [this message]
2018-07-24 14:38   ` Bartlomiej Zolnierkiewicz

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=20180704190846.GC2701@localhost.localdomain \
    --to=noring@nocrew.org \
    --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).