From: "Lee, Shawn C" <shawn.c.lee@intel.com>
To: "Kulkarni, Vandita" <vandita.kulkarni@intel.com>,
"intel-gfx@lists.freedesktop.org"
<intel-gfx@lists.freedesktop.org>
Cc: "Nikula, Jani" <jani.nikula@intel.com>,
"ville.syrjala@linux.intel.com" <ville.syrjala@linux.intel.com>,
"Chiou, Cooper" <cooper.chiou@intel.com>,
"Tseng, William" <william.tseng@intel.com>,
Jani Nikula <jani.nikula@linux.intel.com>
Subject: Re: [Intel-gfx] [v4 6/7] drm/i915/dsi: Retrieve max brightness level from VBT.
Date: Mon, 23 Aug 2021 09:03:53 +0000 [thread overview]
Message-ID: <CO6PR11MB56518647521412FDCBA955A4A3C49@CO6PR11MB5651.namprd11.prod.outlook.com> (raw)
In-Reply-To: <c9f59c701b334f5fb70555c6d7fbd413@intel.com>
On Mon, 23 Aug 2021, Kulkarni, Vandita <vandita.kulkarni@intel.com> wrote:
>>
>> So far, DCS backlight driver hardcode (0xFF) for max brightness level.
>> MIPI DCS spec allow max 0xFFFF for set_display_brightness (51h) command.
>> And VBT brightness precision bits can support 8 ~ 16 bits.
>>
>> We should set correct precision bits in VBT that meet panel's request.
>> Driver can refer to this setting then configure max brightness level
>> in DCS backlight driver properly.
>>
>> Cc: Ville Syrjala <ville.syrjala@linux.intel.com>
>> Cc: Jani Nikula <jani.nikula@linux.intel.com>
>> Cc: Vandita Kulkarni <vandita.kulkarni@intel.com>
>> Cc: Cooper Chiou <cooper.chiou@intel.com>
>> Cc: William Tseng <william.tseng@intel.com>
>> Signed-off-by: Lee Shawn C <shawn.c.lee@intel.com>
>> ---
>> drivers/gpu/drm/i915/display/intel_bios.c | 3 +++
>> .../gpu/drm/i915/display/intel_dsi_dcs_backlight.c | 12 +++++++++---
>> drivers/gpu/drm/i915/i915_drv.h | 1 +
>> 3 files changed, 13 insertions(+), 3 deletions(-)
>>
>> diff --git a/drivers/gpu/drm/i915/display/intel_bios.c
>> b/drivers/gpu/drm/i915/display/intel_bios.c
>> index e86e6ed2d3bf..1affd679d1d1 100644
>> --- a/drivers/gpu/drm/i915/display/intel_bios.c
>> +++ b/drivers/gpu/drm/i915/display/intel_bios.c
>> @@ -483,6 +483,9 @@ parse_lfp_backlight(struct drm_i915_private *i915,
>> level = 255; } i915->vbt.backlight.min_brightness = min_level;
>> +
>> +i915->vbt.backlight.max_brightness_level =
>> +(1 << backlight_data-
>> >brightness_precision_bits[panel_type]) - 1;
>> } else {
>> level = backlight_data->level[panel_type];
>> i915->vbt.backlight.min_brightness = entry->min_brightness; diff
>> --git a/drivers/gpu/drm/i915/display/intel_dsi_dcs_backlight.c
>> b/drivers/gpu/drm/i915/display/intel_dsi_dcs_backlight.c
>> index 584c14c4cbd0..cd85520d36e2 100644
>> --- a/drivers/gpu/drm/i915/display/intel_dsi_dcs_backlight.c
>> +++ b/drivers/gpu/drm/i915/display/intel_dsi_dcs_backlight.c
>> @@ -41,7 +41,7 @@
>> #define POWER_SAVE_HIGH(3 << 0)
>> #define POWER_SAVE_OUTDOOR_MODE(4 << 0)
>>
>> -#define PANEL_PWM_MAX_VALUE0xFF
>
>Shouldn't this be panel dependant too?
If driver did not retrieve proper precision bits, we will use PANEL_PWM_MAX_VALUE as default max backlight.
Do you recommend to keep 0xFF here?
>> +#define PANEL_PWM_MAX_VALUE0xFFFF
>>
>> static u32 dcs_get_backlight(struct intel_connector *connector, enum
>> pipe
>> unused) { @@ -147,10 +147,16 @@ static void
>> dcs_enable_backlight(const struct intel_crtc_state *crtc_state,
>> static int dcs_setup_backlight(struct intel_connector *connector,
>> enum pipe unused)
>> {
>> +struct drm_device *dev = connector->base.dev; struct drm_i915_private
>> +*dev_priv = to_i915(dev);
>> struct intel_panel *panel = &connector->panel;
>>
>> -panel->backlight.max = PANEL_PWM_MAX_VALUE; backlight.level =
>> -panel->PANEL_PWM_MAX_VALUE;
>> +panel->backlight.max = dev_priv-
>> >vbt.backlight.max_brightness_level \
>> + ? dev_priv->vbt.backlight.max_brightness_level \
>> + : PANEL_PWM_MAX_VALUE;
>> +panel->backlight.level = dev_priv-
>> >vbt.backlight.max_brightness_level \
>> + ? dev_priv-
>> >vbt.backlight.max_brightness_level \
>> + : PANEL_PWM_MAX_VALUE;
>>
>> return 0;
>> }
>> diff --git a/drivers/gpu/drm/i915/i915_drv.h
>> b/drivers/gpu/drm/i915/i915_drv.h index 005b1cec7007..fbb3f18e7b8e
>> 100644
>> --- a/drivers/gpu/drm/i915/i915_drv.h
>> +++ b/drivers/gpu/drm/i915/i915_drv.h
>> @@ -706,6 +706,7 @@ struct intel_vbt_data {
>>
>> struct {
>> u16 pwm_freq_hz;
>
>VBT doesn't provide max_brightness_level, instead it gives us Brightness Precision bits from version 236 onwards.
I will modify this variable name to "brightness_precision_bits". And move the max brightness calculation
into dcs_setup_backlight().
Best regards,
Shawn
>> +u16 max_brightness_level;
>> bool present;
>> bool active_low_pwm;
>> u8 min_brightness;/* min_brightness/255 of max */
>> --
>> 2.17.1
next prev parent reply other threads:[~2021-08-23 9:04 UTC|newest]
Thread overview: 39+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-08-12 15:42 [Intel-gfx] [v4 0/7] MIPI DSI driver enhancements Lee Shawn C
2021-08-12 15:42 ` [Intel-gfx] [v4 1/7] drm/i915/dsi: send correct gpio_number on gen11 platform Lee Shawn C
2021-08-12 15:42 ` [Intel-gfx] [v4 2/7] drm/i915/jsl: program DSI panel GPIOs Lee Shawn C
2021-08-23 12:06 ` Jani Nikula
2021-08-12 15:42 ` [Intel-gfx] [v4 3/7] drm/i915/dsi: wait for header and payload credit available Lee Shawn C
2021-08-26 5:54 ` Kulkarni, Vandita
2021-08-12 15:42 ` [Intel-gfx] [v4 4/7] drm/i915/dsi: refine send MIPI DCS command sequence Lee Shawn C
2021-08-23 9:45 ` Kulkarni, Vandita
2021-08-12 15:42 ` [Intel-gfx] [v4 5/7] drm/i915: Get proper min cdclk if vDSC enabled Lee Shawn C
2021-08-23 12:19 ` Kulkarni, Vandita
2021-08-12 15:42 ` [Intel-gfx] [v4 6/7] drm/i915/dsi: Retrieve max brightness level from VBT Lee Shawn C
2021-08-23 8:46 ` Kulkarni, Vandita
2021-08-23 9:03 ` Lee, Shawn C [this message]
2021-08-23 12:10 ` Kulkarni, Vandita
2021-08-24 14:00 ` [Intel-gfx] [PATCH] " Lee Shawn C
2021-08-24 14:33 ` Jani Nikula
2021-08-24 15:53 ` Lee, Shawn C
2021-08-12 15:42 ` [Intel-gfx] [v4 7/7] drm/i915/dsi: Send proper brightness value via MIPI DCS command Lee Shawn C
2021-08-12 23:22 ` kernel test robot
2021-08-13 2:46 ` [Intel-gfx] [v4] " Lee Shawn C
2021-08-18 11:10 ` Jani Nikula
2021-08-18 14:58 ` Lee, Shawn C
2021-08-19 11:16 ` [Intel-gfx] [v4] drm/i915/dsi: Read/write " Lee Shawn C
2021-08-12 20:56 ` [Intel-gfx] ✗ Fi.CI.CHECKPATCH: warning for MIPI DSI driver enhancements (rev5) Patchwork
2021-08-12 20:57 ` [Intel-gfx] ✗ Fi.CI.SPARSE: " Patchwork
2021-08-12 21:26 ` [Intel-gfx] ✓ Fi.CI.BAT: success " Patchwork
2021-08-13 2:29 ` [Intel-gfx] ✓ Fi.CI.IGT: " Patchwork
2021-08-13 2:56 ` [Intel-gfx] ✗ Fi.CI.CHECKPATCH: warning for MIPI DSI driver enhancements (rev6) Patchwork
2021-08-13 2:58 ` [Intel-gfx] ✗ Fi.CI.SPARSE: " Patchwork
2021-08-13 3:24 ` [Intel-gfx] ✓ Fi.CI.BAT: success " Patchwork
2021-08-13 7:56 ` [Intel-gfx] ✓ Fi.CI.IGT: " Patchwork
2021-08-19 11:45 ` [Intel-gfx] ✗ Fi.CI.CHECKPATCH: warning for MIPI DSI driver enhancements (rev7) Patchwork
2021-08-19 11:46 ` [Intel-gfx] ✗ Fi.CI.SPARSE: " Patchwork
2021-08-19 12:09 ` [Intel-gfx] ✓ Fi.CI.BAT: success " Patchwork
2021-08-19 13:41 ` [Intel-gfx] ✗ Fi.CI.IGT: failure " Patchwork
2021-08-24 19:11 ` [Intel-gfx] ✗ Fi.CI.CHECKPATCH: warning for MIPI DSI driver enhancements (rev8) Patchwork
2021-08-24 19:12 ` [Intel-gfx] ✗ Fi.CI.SPARSE: " Patchwork
2021-08-24 19:41 ` [Intel-gfx] ✓ Fi.CI.BAT: success " Patchwork
2021-08-25 1:22 ` [Intel-gfx] ✓ Fi.CI.IGT: " Patchwork
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=CO6PR11MB56518647521412FDCBA955A4A3C49@CO6PR11MB5651.namprd11.prod.outlook.com \
--to=shawn.c.lee@intel.com \
--cc=20210812154237.13911-7-shawn.c.lee@intel.com \
--cc=cooper.chiou@intel.com \
--cc=intel-gfx@lists.freedesktop.org \
--cc=jani.nikula@intel.com \
--cc=jani.nikula@linux.intel.com \
--cc=vandita.kulkarni@intel.com \
--cc=ville.syrjala@linux.intel.com \
--cc=william.tseng@intel.com \
/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).