Skip to contentSkip to conversation

drm/radeon/kms: fix up LVDS handling on macs (v2)

DISCUSSION Benjamin Herrenschmidt 3 participants 4 messages Jan 14, 2010 – Jan 15, 2010 1 message not in the archive

lore
Share & tools
lore

A message that is not in the archive (sent off-list or not yet received): [email protected]

#1 lore raw
Quoted 10 lines · Linux Kernel Mailing List
Gitweb:     http://git.kernel.org/linus/3890ddf56dbc0f804953198e65a7e406ed654576
Commit:     3890ddf56dbc0f804953198e65a7e406ed654576
Parent:     804c7559e9376c3ba78ae15a30337b1e24f8ae80
Author:     Alex Deucher <[email protected]>
AuthorDate: Tue Jan 12 11:16:57 2010 -0500
Committer:  Dave Airlie <[email protected]>
CommitDate: Wed Jan 13 13:25:08 2010 +1000

drm/radeon/kms: fix up LVDS handling on macs (v2)

Quoted 8 lines

Based on radeonfb code and recent ddx fix.

v2: minor formatting fix from Michel Dänzer

I have to dbl check that ... but I think the "Real" issue is that some panel have inverted polarity on the PWM signal. Thus if BLON is turned off the panels goes full backlight instead among other things :-)

However, not all macs are the same. If you look at the radeonfb code, we do things differently depending on the mac model...

I don't know if there's a "proper" way to figure out how the panel is really wired on these. Here, the ATI "mac" guys might be able to help by telling us how the Mac driver figures it out :-)

Cheers,
Ben.

Quoted 61 lines
---
 drivers/gpu/drm/radeon/radeon_legacy_encoders.c |   21 ++++++++++++++++++++-
 1 files changed, 20 insertions(+), 1 deletions(-)
drivers/gpu/drm/radeon/radeon_legacy_encoders.c +20 -2
index 981508f..38e45e2 100644
@@ -46,6 +46,7 @@ static void radeon_legacy_lvds_dpms(struct drm_encoder *encoder, int mode)
 	struct radeon_encoder *radeon_encoder = to_radeon_encoder(encoder);
 	uint32_t lvds_gen_cntl, lvds_pll_cntl, pixclks_cntl, disp_pwr_man;
 	int panel_pwr_delay = 2000;
+	bool is_mac = false;
 	DRM_DEBUG("\n");
 
 	if (radeon_encoder->enc_priv) {
@@ -58,6 +59,15 @@ static void radeon_legacy_lvds_dpms(struct drm_encoder *encoder, int mode)
 		}
 	}
 
+	/* macs (and possibly some x86 oem systems?) wire up LVDS strangely
+	 * Taken from radeonfb.
+	 */
+	if ((rdev->mode_info.connector_table == CT_IBOOK) ||
+	    (rdev->mode_info.connector_table == CT_POWERBOOK_EXTERNAL) ||
+	    (rdev->mode_info.connector_table == CT_POWERBOOK_INTERNAL) ||
+	    (rdev->mode_info.connector_table == CT_POWERBOOK_VGA))
+		is_mac = true;
+
 	switch (mode) {
 	case DRM_MODE_DPMS_ON:
 		disp_pwr_man = RREG32(RADEON_DISP_PWR_MAN);
@@ -74,6 +84,8 @@ static void radeon_legacy_lvds_dpms(struct drm_encoder *encoder, int mode)
 
 		lvds_gen_cntl = RREG32(RADEON_LVDS_GEN_CNTL);
 		lvds_gen_cntl |= (RADEON_LVDS_ON | RADEON_LVDS_EN | RADEON_LVDS_DIGON | RADEON_LVDS_BLON);
+		if (is_mac)
+			lvds_gen_cntl |= RADEON_LVDS_BL_MOD_EN;
 		lvds_gen_cntl &= ~(RADEON_LVDS_DISPLAY_DIS);
 		udelay(panel_pwr_delay * 1000);
 		WREG32(RADEON_LVDS_GEN_CNTL, lvds_gen_cntl);
@@ -85,7 +97,14 @@ static void radeon_legacy_lvds_dpms(struct drm_encoder *encoder, int mode)
 		WREG32_PLL_P(RADEON_PIXCLKS_CNTL, 0, ~RADEON_PIXCLK_LVDS_ALWAYS_ONb);
 		lvds_gen_cntl = RREG32(RADEON_LVDS_GEN_CNTL);
 		lvds_gen_cntl |= RADEON_LVDS_DISPLAY_DIS;
-		lvds_gen_cntl &= ~(RADEON_LVDS_ON | RADEON_LVDS_BLON | RADEON_LVDS_EN | RADEON_LVDS_DIGON);
+		if (is_mac) {
+			lvds_gen_cntl &= ~RADEON_LVDS_BL_MOD_EN;
+			WREG32(RADEON_LVDS_GEN_CNTL, lvds_gen_cntl);
+			lvds_gen_cntl &= ~(RADEON_LVDS_ON | RADEON_LVDS_EN);
+		} else {
+			WREG32(RADEON_LVDS_GEN_CNTL, lvds_gen_cntl);
+			lvds_gen_cntl &= ~(RADEON_LVDS_ON | RADEON_LVDS_BLON | RADEON_LVDS_EN | RADEON_LVDS_DIGON);
+		}
 		udelay(panel_pwr_delay * 1000);
 		WREG32(RADEON_LVDS_GEN_CNTL, lvds_gen_cntl);
 		WREG32_PLL(RADEON_PIXCLKS_CNTL, pixclks_cntl);
--

To unsubscribe from this list: send the line "unsubscribe git-commits-head" in the body of a message to [email protected]
More majordomo info at http://vger.kernel.org/majordomo-info.html

#2 lore raw
Quoted 20 lines · Benjamin Herrenschmidt
Quoted 10 lines · Linux Kernel Mailing List
Gitweb:     http://git.kernel.org/linus/3890ddf56dbc0f804953198e65a7e406ed654576
Commit:     3890ddf56dbc0f804953198e65a7e406ed654576
Parent:     804c7559e9376c3ba78ae15a30337b1e24f8ae80
Author:     Alex Deucher <[email protected]>
AuthorDate: Tue Jan 12 11:16:57 2010 -0500
Committer:  Dave Airlie <[email protected]>
CommitDate: Wed Jan 13 13:25:08 2010 +1000

drm/radeon/kms: fix up LVDS handling on macs (v2)

Quoted 8 lines

Based on radeonfb code and recent ddx fix.

v2: minor formatting fix from Michel Dänzer

Quoted 6 lines

I have to dbl check that ... but I think the "Real" issue is that some panel have inverted polarity on the PWM signal. Thus if BLON is turned off the panels goes full backlight instead among other things :-)

However, not all macs are the same. If you look at the radeonfb code, we do things differently depending on the mac model...

I have looked at radeonfb for a patch I posted a while ago to expose a backlight class device with KMS, and I can only see what you describe above affecting the LVDS_GEN_CNTL backlight level, not BLON or BL_MOD_EN. Am I missing something?

Without my patch, KMS doesn't change the backlight level at all, so assuming the firmware manages to enable the backlight, it should stay like that.

Signature · 2 lines
Earthling Michel Dänzer           |                http://www.vmware.com
Libre software enthusiast         |          Debian, X and DRI developer
#3 lore raw
Quoted 4 lines · Michel Dänzer

I have looked at radeonfb for a patch I posted a while ago to expose a backlight class device with KMS, and I can only see what you describe above affecting the LVDS_GEN_CNTL backlight level, not BLON or BL_MOD_EN. Am I missing something?

No, you aren't, it's radeonfb who is :-) I never quite got that part right. I was somewhat hoping several times that Hui and then Alex would manage to dig some info from ATI about what the right method is to drive those panels I think :-)

But my observation on those HW was definitely that when inverted, disabling the modulation was also turning the panel to full bright on, rather than turning it off.

Quoted 3 lines

Without my patch, KMS doesn't change the backlight level at all, so assuming the firmware manages to enable the backlight, it should stay like that.

Your patch might make things better than they are today, I'm not arguing there :-) I'm just saying that now might be a good time to try to sort out exactly what should be done in there :-)

Cheers,
Ben.

#4 lore raw

2010/1/14 Benjamin Herrenschmidt <[email protected]>:

Quoted 11 lines · Michel Dänzer
Quoted 4 lines

I have looked at radeonfb for a patch I posted a while ago to expose a backlight class device with KMS, and I can only see what you describe above affecting the LVDS_GEN_CNTL backlight level, not BLON or BL_MOD_EN. Am I missing something?

No, you aren't, it's radeonfb who is :-) I never quite got that part right. I was somewhat hoping several times that Hui and then Alex would manage to dig some info from ATI about what the right method is to drive those panels I think :-)

I've tried, but we are coming up on 10 years ago for some of these chips so they aren't exactly fresh in people's minds and most of the code is in long term storage at this point. The problem is the sequence is oem specific, even on the PC side there are cases were we probably aren't doing it quite right. The current non-mac code in kms is the generic code that the PC bios team gave me.

Alex

Quoted 16 lines

But my observation on those HW was definitely that when inverted, disabling the modulation was also turning the panel to full bright on, rather than turning it off.

Quoted 3 lines

Without my patch, KMS doesn't change the backlight level at all, so assuming the firmware manages to enable the backlight, it should stay like that.

Your patch might make things better than they are today, I'm not arguing there :-) I'm just saying that now might be a good time to try to sort out exactly what should be done in there :-)

Cheers,
Ben.