From: Guennadi Liakhovetski <g.liakhovetski@gmx.de>
To: linux-arm-kernel@lists.infradead.org
Subject: Re: [PATCH] mx3fb: Fix parameter to sdc_init_panel
Date: Thu, 10 Feb 2011 11:00:09 +0000 [thread overview]
Message-ID: <Pine.LNX.4.64.1102101158510.17898@axis700.grange> (raw)
In-Reply-To: <Pine.LNX.4.64.1102101136320.15087@axis700.grange>
On Thu, 10 Feb 2011, Guennadi Liakhovetski wrote:
> On Thu, 10 Feb 2011, Alexander Stein wrote:
>
> > h_end_width and v_end_width should only contain the front porches.
> > Otherwise, SCREEN_WIDTH (pixel clocks between HSYNC) in SDC_HOR_CONF
> > and SCREEN_HEIGHT (rows between VSYNC) in SDC_VER_CONF get false values.
>
> Hm, no, this corrupts image on my pcm990 test-board. What makes you think
> this patch is needed? How do you see, that current values are "false?"
>
> Thanks
> Guennadi
>
> >
> > Signed-off-by: Alexander Stein <alexander.stein@systec-electronic.com>
> > ---
> > drivers/video/mx3fb.c | 7 +++----
> > 1 files changed, 3 insertions(+), 4 deletions(-)
> >
> > diff --git a/drivers/video/mx3fb.c b/drivers/video/mx3fb.c
> > index ef71e56..9040833 100644
> > --- a/drivers/video/mx3fb.c
> > +++ b/drivers/video/mx3fb.c
> > @@ -881,12 +881,11 @@ static int __set_par(struct fb_info *fbi, bool lock)
Also just occurred to me - your offset of 881 lines is 100 lines below my
offset for the same code - against what tree is this patch, or do you have
some local changes there? Can it be, that that's the reason for your
problem?
Thanks
Guennadi
> > IPU_PIX_FMT_BGR666 : IPU_PIX_FMT_RGB666,
> > fbi->var.left_margin,
> > fbi->var.hsync_len,
> > - fbi->var.right_margin +
> > - fbi->var.hsync_len,
> > + fbi->var.right_margin,
> > fbi->var.upper_margin,
> > fbi->var.vsync_len,
> > - fbi->var.lower_margin +
> > - fbi->var.vsync_len, sig_cfg) != 0) {
> > + fbi->var.lower_margin,
> > + sig_cfg) != 0) {
> > dev_err(fbi->device,
> > "mx3fb: Error initializing panel.\n");
> > return -EINVAL;
> > --
> > 1.7.3.4
> >
> >
>
> ---
> Guennadi Liakhovetski, Ph.D.
> Freelance Open-Source Software Developer
> http://www.open-technology.de/
>
---
Guennadi Liakhovetski, Ph.D.
Freelance Open-Source Software Developer
http://www.open-technology.de/
next prev parent reply other threads:[~2011-02-10 11:00 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-02-10 10:05 [PATCH] mx3fb: Fix parameter to sdc_init_panel Alexander Stein
2011-02-10 10:44 ` Guennadi Liakhovetski
2011-02-10 11:00 ` Guennadi Liakhovetski [this message]
2011-02-10 11:27 ` Alexander Stein
2011-02-10 12:48 ` Guennadi Liakhovetski
2011-02-10 13:01 ` Alexander Stein
2011-02-14 7:46 ` Alexander Stein
2011-02-14 7:57 ` Guennadi Liakhovetski
2011-02-14 12:06 ` Alexander Stein
2011-02-16 13:47 ` Guennadi Liakhovetski
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=Pine.LNX.4.64.1102101158510.17898@axis700.grange \
--to=g.liakhovetski@gmx.de \
--cc=linux-arm-kernel@lists.infradead.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