All of lore.kernel.org
 help / color / mirror / Atom feed
From: Greg KH <greg@kroah.com>
To: linux-arm-kernel@lists.infradead.org
Subject: Re: [PATCH] ARM: video: mxs: Fix mxsfb misconfiguring VDCTRL0
Date: Mon, 18 Mar 2013 18:58:10 +0000	[thread overview]
Message-ID: <20130318185810.GA11040@kroah.com> (raw)
In-Reply-To: <1363630997-5254-1-git-send-email-marex@denx.de>

On Mon, Mar 18, 2013 at 07:23:17PM +0100, Marek Vasut wrote:
> The issue fixed by this patch manifests only then using X11
> with mxsfb driver. The X11 will display either shifted image
> or otherwise distorted image on the LCD.
> 
> The problem is that the X11 tries to reconfigure the framebuffer
> and along the way calls fb_ops.fb_set_par() with X11's desired
> configuration values. The field of particular interest is
> fb_info->var.sync which contains non-standard values if
> configured by kernel. These are either FB_SYNC_DATA_ENABLE_HIGH_ACT,
> FB_SYNC_DOTCLK_FAILING_ACT or both, depending on the platform
> configuration. Both of these values are defined in the
> include/linux/mxsfb.h file.
> 
> The driver interprets these values and configures the LCD controller
> accordingly. Yet X11 only has access to the standard values for this
> field defined in include/uapi/linux/fb.h and thus, unlike kernel,
> omits these special values. This results in distorted image on the
> LCD.
> 
> This patch moves these non-standard values into new field of the
> mxsfb_platform_data structure so the driver can in turn check this
> field instead of the video mode field for these specific portions.
> 
> Moreover, this patch prefixes these values with MXSFB_SYNC_ prefix
> instead of FB_SYNC_ prefix to prevent confusion of subsequent users.
> 
> Signed-off-by: Marek Vasut <marex@denx.de>
> Cc: Fabio Estevam <fabio.estevam@freescale.com>
> Cc: Linux ARM <linux-arm-kernel@lists.infradead.org>
> Cc: Linux FBDEV <linux-fbdev@vger.kernel.org>
> Cc: Lothar Waßmann <LW@karo-electronics.de>
> Cc: Sascha Hauer <kernel@pengutronix.de>
> Cc: Shawn Guo <shawn.guo@linaro.org>
> Tested-by: Fabio Estevam <fabio.estevam@freescale.com>
> ---
>  arch/arm/mach-mxs/mach-mxs.c |   22 +++++++++++-----------
>  drivers/video/mxsfb.c        |    7 +++++--
>  include/linux/mxsfb.h        |    7 +++++--
>  3 files changed, 21 insertions(+), 15 deletions(-)
> 
> NOTE: This is the version for stable v3.8.3, so I'm sending it to -stable.
>       I will send adjusted version for mainline 3.9-rc , since there is
>       one more board in mainline and therefore the versions of the patch
>       must differ.


<formletter>

This is not the correct way to submit patches for inclusion in the
stable kernel tree.  Please read Documentation/stable_kernel_rules.txt
for how to do this properly.

</formletter>

WARNING: multiple messages have this Message-ID (diff)
From: greg@kroah.com (Greg KH)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH] ARM: video: mxs: Fix mxsfb misconfiguring VDCTRL0
Date: Mon, 18 Mar 2013 11:58:10 -0700	[thread overview]
Message-ID: <20130318185810.GA11040@kroah.com> (raw)
In-Reply-To: <1363630997-5254-1-git-send-email-marex@denx.de>

On Mon, Mar 18, 2013 at 07:23:17PM +0100, Marek Vasut wrote:
> The issue fixed by this patch manifests only then using X11
> with mxsfb driver. The X11 will display either shifted image
> or otherwise distorted image on the LCD.
> 
> The problem is that the X11 tries to reconfigure the framebuffer
> and along the way calls fb_ops.fb_set_par() with X11's desired
> configuration values. The field of particular interest is
> fb_info->var.sync which contains non-standard values if
> configured by kernel. These are either FB_SYNC_DATA_ENABLE_HIGH_ACT,
> FB_SYNC_DOTCLK_FAILING_ACT or both, depending on the platform
> configuration. Both of these values are defined in the
> include/linux/mxsfb.h file.
> 
> The driver interprets these values and configures the LCD controller
> accordingly. Yet X11 only has access to the standard values for this
> field defined in include/uapi/linux/fb.h and thus, unlike kernel,
> omits these special values. This results in distorted image on the
> LCD.
> 
> This patch moves these non-standard values into new field of the
> mxsfb_platform_data structure so the driver can in turn check this
> field instead of the video mode field for these specific portions.
> 
> Moreover, this patch prefixes these values with MXSFB_SYNC_ prefix
> instead of FB_SYNC_ prefix to prevent confusion of subsequent users.
> 
> Signed-off-by: Marek Vasut <marex@denx.de>
> Cc: Fabio Estevam <fabio.estevam@freescale.com>
> Cc: Linux ARM <linux-arm-kernel@lists.infradead.org>
> Cc: Linux FBDEV <linux-fbdev@vger.kernel.org>
> Cc: Lothar Wa?mann <LW@karo-electronics.de>
> Cc: Sascha Hauer <kernel@pengutronix.de>
> Cc: Shawn Guo <shawn.guo@linaro.org>
> Tested-by: Fabio Estevam <fabio.estevam@freescale.com>
> ---
>  arch/arm/mach-mxs/mach-mxs.c |   22 +++++++++++-----------
>  drivers/video/mxsfb.c        |    7 +++++--
>  include/linux/mxsfb.h        |    7 +++++--
>  3 files changed, 21 insertions(+), 15 deletions(-)
> 
> NOTE: This is the version for stable v3.8.3, so I'm sending it to -stable.
>       I will send adjusted version for mainline 3.9-rc , since there is
>       one more board in mainline and therefore the versions of the patch
>       must differ.


<formletter>

This is not the correct way to submit patches for inclusion in the
stable kernel tree.  Please read Documentation/stable_kernel_rules.txt
for how to do this properly.

</formletter>

  reply	other threads:[~2013-03-18 18:58 UTC|newest]

Thread overview: 44+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-03-16 20:09 Shifted framebuffer after X11 starts on mx28 Fabio Estevam
2013-03-16 20:09 ` Fabio Estevam
2013-03-16 20:55 ` Marek Vasut
2013-03-16 20:55   ` Marek Vasut
2013-03-16 21:00   ` Marek Vasut
2013-03-16 21:00     ` Marek Vasut
2013-03-16 22:06 ` [PATCH] ARM: video: mxs: Fix mxsfb misconfiguring VDCTRL0 Marek Vasut
2013-03-16 22:06   ` Marek Vasut
2013-03-16 22:38   ` Fabio Estevam
2013-03-16 22:38     ` Fabio Estevam
2013-03-18 18:23     ` Marek Vasut
2013-03-18 18:23       ` Marek Vasut
2013-03-18 18:58       ` Greg KH [this message]
2013-03-18 18:58         ` Greg KH
2013-03-18 21:31         ` Marek Vasut
2013-03-18 21:31           ` Marek Vasut
2013-03-18 22:01           ` Jonathan Nieder
2013-03-18 22:01             ` Jonathan Nieder
2013-03-18 22:17             ` Marek Vasut
2013-03-18 22:17               ` Marek Vasut
2013-03-18 18:24     ` Marek Vasut
2013-03-18 18:24       ` Marek Vasut
2013-03-19  5:51       ` Shawn Guo
2013-03-19  5:51         ` Shawn Guo
2013-03-18 12:44   ` Shawn Guo
2013-03-18 12:44     ` Shawn Guo
2013-03-18 12:52     ` Fabio Estevam
2013-03-18 13:11       ` Fabio Estevam
2013-03-18 13:01       ` Shawn Guo
2013-03-18 13:01         ` Shawn Guo
2013-03-18 13:58         ` Marek Vasut
2013-03-18 13:58           ` Marek Vasut
2013-03-18 14:06           ` Shawn Guo
2013-03-18 14:06             ` Shawn Guo
2013-03-18 14:18             ` Marek Vasut
2013-03-18 14:18               ` Marek Vasut
2013-03-18 14:31               ` Shawn Guo
2013-03-18 14:31                 ` Shawn Guo
2013-03-18 15:19                 ` Marek Vasut
2013-03-18 15:19                   ` Marek Vasut
2013-03-19  5:48                   ` Shawn Guo
2013-03-19  5:48                     ` Shawn Guo
2013-03-19 10:33                     ` Marek Vasut
2013-03-19 10:33                       ` Marek Vasut

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=20130318185810.GA11040@kroah.com \
    --to=greg@kroah.com \
    --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 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.