This is a note to let you know that I've just added the patch titled
staging: sm750fb: Correctly set CLOCK_PHASE bit of display controller.
to the 4.8-stable tree which can be found at:
http://www.kernel.org/git/?p=linux/kernel/git/stable/stable-queue.git;a=summary
The filename of the patch is:
staging-sm750fb-correctly-set-clock_phase-bit-of-display-controller.patch
and it can be found in the queue-4.8 subdirectory.
If you, or anyone else, feels it should not be added to the stable tree,
please let <stable@xxxxxxxxxxxxxxx> know about it.
>From 992f961480d23e9ef9e686e512a419efef723523 Mon Sep 17 00:00:00 2001
From: Phil Turnbull <phil.turnbull@xxxxxxxxxx>
Date: Fri, 2 Sep 2016 15:35:31 -0400
Subject: staging: sm750fb: Correctly set CLOCK_PHASE bit of display controller.
From: Phil Turnbull <phil.turnbull@xxxxxxxxxx>
commit 992f961480d23e9ef9e686e512a419efef723523 upstream.
Commit 6fba39cf32a3 ("staging: sm750fb: use BIT macro for
PANEL_DISPLAY_CTRL single-bit fields") accidentally changed the
CLOCK_PHASE logic from '|=' to '=' which clears all the previously set
bits.
Fixes: 6fba39cf32a3 ("staging: sm750fb: use BIT macro for PANEL_DISPLAY_CTRL single-bit fields")
Signed-off-by: Phil Turnbull <phil.turnbull@xxxxxxxxxx>
Signed-off-by: Greg Kroah-Hartman <gregkh@xxxxxxxxxxxxxxxxxxx>
---
drivers/staging/sm750fb/ddk750_mode.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
--- a/drivers/staging/sm750fb/ddk750_mode.c
+++ b/drivers/staging/sm750fb/ddk750_mode.c
@@ -63,7 +63,7 @@ static unsigned long displayControlAdjus
dispControl |= (CRT_DISPLAY_CTRL_CRTSELECT | CRT_DISPLAY_CTRL_RGBBIT);
/* Set bit 14 of display controller */
- dispControl = DISPLAY_CTRL_CLOCK_PHASE;
+ dispControl |= DISPLAY_CTRL_CLOCK_PHASE;
POKE32(CRT_DISPLAY_CTRL, dispControl);
Patches currently in stable-queue which might be from phil.turnbull@xxxxxxxxxx are
queue-4.8/staging-sm750fb-correctly-set-clock_phase-bit-of-display-controller.patch
--
To unsubscribe from this list: send the line "unsubscribe stable" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html