Re: [Intel-gfx] [PATCH 00/31] IPS/DRRS/PSR rework with PSR enabled by default

Hi Rodrigo, On 10 November 2015 at 15:57, Vivi, Rodrigo wrote: > On Mon, 2015-11-09 at 11:47 +, Daniel Stone wrote: >> I've been looking at pulling this on top of Maarten's tree, and > > I'm afraid I didn't followed completely your idea and maybe because I > don't

Re: [Intel-gfx] HDMI hotplug fails when using VT or boot on text mode

An update about this issue: I requested the customer to perform the command udevadmin monitor on text mode to check if the driver is issuing uevents, the command shows activity when there the hdmi is unplugged but it doesn't show any activity when the hdmi is plugged again. On graphic mode

Re: [Intel-gfx] [PATCH 06/31] drm/i915: Fix IPS disable sequence.

Hi, On 5 November 2015 at 18:49, Rodrigo Vivi wrote: > /** > + * intel_ips_disable_if_alone - Disable IPS if alone in the pipe. > + * @crtc: intel crtc > + * > + * This function should be called when primary plane is being disabled. > + * It checks if there is any other

Re: [Intel-gfx] HDMI hotplug fails when using VT or boot on text mode

Hello Jani Thanks for your clarification. On graphic mode what userspace application handles this? Is the X server? And in this case if the customer wants to enable hotpluging he should write an udev script to handle the situation? Best Regards, Adolfo. -Original Message- From: Jani

Re: [Intel-gfx] [PATCH 24/31] drm/i915: PSR: Don't Skip aux handshake on DP_PSR_NO_TRAIN_ON_EXIT.

On Mon, 2015-11-09 at 12:38 +0200, Jani Nikula wrote: > On Thu, 05 Nov 2015, Rodrigo Vivi wrote: > > Since the beginning there is a confusion on the meaning of this > > bit. > > > > A previous patch had identified this already and fixed it > > partially: > > 'commit

Re: [Intel-gfx] [PATCH 3/3] drm/i915: Move the fbdev async_schedule() into intel_fbdev.c

Hi Ville, On Mon, Nov 09, 2015 at 01:00:50PM +0200, Ville Syrjälä wrote: > On Sun, Nov 08, 2015 at 05:44:37PM +0100, Lukas Wunner wrote: > > Hi Ville, > > > > On Fri, Nov 06, 2015 at 03:08:33PM +0200, ville.syrj...@linux.intel.com > > wrote: > > > From: Ville Syrjälä

Re: [Intel-gfx] [PATCH] drm/i915/skl: implement DP Aux Mutex framework

When PSR is enablabled the Hardware takes control on AUX and use it to control panel exit/entry states. When validating PSR with automated tests grabbing CRC from sink we were facing strange aux communication issues where aux were returning message size read equal 0. And 0 is a forbidden message.

Re: [Intel-gfx] [PATCH 25/31] drm/i915: Send TP1 TP2/3 even when panel claims no NO_TRAIN_ON_EXIT.

On Mon, 2015-11-09 at 12:39 +0200, Jani Nikula wrote: > On Thu, 05 Nov 2015, Rodrigo Vivi wrote: > > On the commit 3301d4092106 ("drm/i915: PSR: Fix > > DP_PSR_NO_TRAIN_ON_EXIT logic")' > > we already had identified that DP_PSR_NO_TRAIN_ON_EXIT > > doesn't mean we

Re: [Intel-gfx] [PATCH 00/31] IPS/DRRS/PSR rework with PSR enabled by default

On Mon, 2015-11-09 at 11:47 +, Daniel Stone wrote: > Hi Rodrigo, > > On 5 November 2015 at 18:49, Rodrigo Vivi > wrote: > > So I'm confident we can enable PSR back by default now. > > > > All comments, ideas, suggestions and even bikesheddings are pretty > >

Re: [Intel-gfx] [PATCH v2] drm/i915: Respect the brightness range from VBT.

On Tue, Nov 10, 2015 at 02:57:39PM +0200, Jani Nikula wrote: > On Tue, 10 Nov 2015, "Shih-Yuan Lee (FourDollars)" > wrote: > > Apparently you are not aware of GNOME has used 1 as the minimum brightness > > level because of > > > > commit

Re: [Intel-gfx] [PATCH 00/14] drm/i915: FIFO underrun elimination for PCH platforms

On Thu, Oct 29, 2015 at 09:25:49PM +0200, ville.syrj...@linux.intel.com wrote: > From: Ville Syrjälä > > This series eliminates all spurious PCH FIFO underrun reports on my > machines during a BAT run ('-t basic -x reload -x suspend' actually). > It also eliminates

Re: [Intel-gfx] [PATCH 1/3] drm/i915: Kill intel_runtime_pm_disable()

On 11/06/2015 05:08 AM, ville.syrj...@linux.intel.com wrote: > From: Ville Syrjälä > > intel_runtime_pm_disable() takes an extra rpm reference which combined > with the one we leak from intel_display_set_init_power() leaves the > usage count at +1 after the driver

Re: [Intel-gfx] [PATCH 28/31] drm/i915: Make Sink crc calculation waiting for counter to reset.

2015-11-05 16:50 GMT-02:00 Rodrigo Vivi : > According to VESA DP spec TEST_CRC_COUNT (Bits 3:0) at > TEST_SINK_MISC (00246h) is "Reset to 0 when TEST_SINK bit 0 = 0; > > So let's give few vblanks so we are really sure that this counter > is really zeroed on the next

Re: [Intel-gfx] [PATCH 29/31] drm/i915: Stop tracking last calculated Sink CRC.

2015-11-05 16:50 GMT-02:00 Rodrigo Vivi : > It was created at 'commit aabc95dcf20 (drm/i915: Dont -ETIMEDOUT > on identical new and previous (count, crc).")' becase the counter > wasn't reliable. > > Now that we properly wait for the counter to be reset we can rely > a bit

Re: [Intel-gfx] [PATCH 28/31] drm/i915: Make Sink crc calculation waiting for counter to reset.

2015-11-10 18:31 GMT-02:00 Paulo Zanoni : > 2015-11-05 16:50 GMT-02:00 Rodrigo Vivi : >> According to VESA DP spec TEST_CRC_COUNT (Bits 3:0) at >> TEST_SINK_MISC (00246h) is "Reset to 0 when TEST_SINK bit 0 = 0; >> >> So let's give few vblanks so we are

Re: [Intel-gfx] [PATCH] drm/i915: Try to fix MST for SKL

On 08/17/2015 08:46 AM, ville.syrj...@linux.intel.com wrote: > From: Ville Syrjälä > > Set up the DDI->PLL mapping on SKL also for MST links. Might help make > MST operational on SKL. > > Cc: Maarten Lankhorst > Signed-off-by:

Re: [Intel-gfx] [PATCH] drm/i915: Try to fix MST for SKL

On Tue, Nov 10, 2015 at 12:15:40PM -0800, Jesse Barnes wrote: > On 08/17/2015 08:46 AM, ville.syrj...@linux.intel.com wrote: > > From: Ville Syrjälä > > > > Set up the DDI->PLL mapping on SKL also for MST links. Might help make > > MST operational on SKL. > > > >

Re: [Intel-gfx] [PATCH 30/31] drm/i915: Rely on TEST_SINK_START instead of tracking Sink CRC state on dev_priv.

2015-11-05 16:50 GMT-02:00 Rodrigo Vivi : > Signed-off-by: Rodrigo Vivi Another patch I was going to request in the review of the previous ones. Reviewed-by: Paulo Zanoni > --- > drivers/gpu/drm/i915/intel_dp.c | 14

Re: [Intel-gfx] [PATCH 27/31] drm/i915: Allow 1 vblank to let Sink CRC calculation to start or stop.

2015-11-05 16:50 GMT-02:00 Rodrigo Vivi : > According to VESA DP Spec, setting TEST_SINK_START (bit 0) > of TEST_SINK (00270h) "Stop/Start calculating CRC on the next frame" > > So let's wait at least 1 vblank to really say the calculation > stopped or started. I'm hoping

Re: [Intel-gfx] [PATCH] drm/i915/guc: Fix a fw content lost issue after it is evicted

On 11/09/2015 02:15 AM, Chris Wilson wrote: On Fri, Nov 06, 2015 at 03:18:37PM -0800, Yu Dai wrote: > > > On 11/06/2015 02:07 PM, Chris Wilson wrote: > >On Fri, Nov 06, 2015 at 01:55:27PM -0800, yu@intel.com wrote: > >> From: Alex Dai > >> > >> We keep a copy of GuC fw

[Intel-gfx] [PATCH v1] drm/i915/guc: Fix a fw content lost issue after it is evicted

From: Alex Dai We keep a copy of GuC fw in a GEM obj. However its content is lost if the GEM obj is swapped (igt/gem_evict_*). Therefore, the later fw loading during GPU reset will fail. Mark the obj dirty after copying data into the pages. So its content will be kept during

Re: [Intel-gfx] [PATCH 1/3] drm/i915: Kill intel_runtime_pm_disable()

On Tuesday, November 10, 2015 09:20:56 AM Jesse Barnes wrote: > On 11/06/2015 05:08 AM, ville.syrj...@linux.intel.com wrote: > > From: Ville Syrjälä > > > > intel_runtime_pm_disable() takes an extra rpm reference which combined > > with the one we leak from

[Intel-gfx] [PATCH i-g-t] tests/gem_buffered_svm_test: New tests for buffered SVM feature

v1: These tests exercise the userptr ioctl to create shared buffers between CPU and GPU. They contain error and normal usage scenarios. They also contain a couple of stress tests which copy buffers between CPU and GPU. These tests rely on the softpin patch in order to pin buffers to a certain VA.

[Intel-gfx] [PATCH i-g-t] tests/gem_buffered_svm_test: New tests for buffered SVM feature

v1: These tests exercise the userptr ioctl to create shared buffers between CPU and GPU. They contain error and normal usage scenarios. They also contain a couple of stress tests which copy buffers between CPU and GPU. These tests rely on the softpin patch in order to pin buffers to a certain VA.

[Intel-gfx] [PATCH v2] drm/i915: Respect the brightness range from VBT.

Taking Dell XPS 13 (2015) as an example. The lowest PWM brightness is 10 and the highest PWM brightness is 937. Before this change, we can only use from 37 to 937, and 37 is used to turn off the backlight because it is mapped to 0 of sysfs brightness however the maximum sysfs brightness is still

Re: [Intel-gfx] [PATCH 3/3] drm/i915: Use insert_page for pwrite_fast

On Tue, 2015-11-10 at 09:55 +0200, Mika Kuoppala wrote: > ankitprasad.r.sha...@intel.com writes: > > > From: Ankitprasad Sharma > > > > In pwrite_fast, map an object page by page if obj_ggtt_pin fails. First, > > we try a nonblocking pin for the whole object

Re: [Intel-gfx] [PATCH 3/3] drm/i915: Use insert_page for pwrite_fast

On Tue, Nov 10, 2015 at 09:55:18AM +0200, Mika Kuoppala wrote: > ankitprasad.r.sha...@intel.com writes: > > > From: Ankitprasad Sharma > > > > In pwrite_fast, map an object page by page if obj_ggtt_pin fails. First, > > we try a nonblocking pin for the whole

Re: [Intel-gfx] [PATCH] drm/i915: Change context lifecycle

On Mon, Nov 09, 2015 at 04:18:20PM +, Nick Hoath wrote: > Use the first retired request on a new context to unpin > the old context. This ensures that the hw context remains > bound until it has been saved. > Now that the context is pinned until later in the request/context > lifecycle, it no

Re: [Intel-gfx] [PATCH] drm/i915/bxt: Broxton doesn't use gen9 scaling for rps frequencies.

Bob Paauwe writes: > Signed-off-by: Bob Paauwe > Bugzilla: https://bugs.freedesktop.org/show_bug.cgi?id=92768 > --- > drivers/gpu/drm/i915/intel_pm.c | 4 ++-- > 1 file changed, 2 insertions(+), 2 deletions(-) > > diff --git

Re: [Intel-gfx] [PATCH v2 3/4] drm/i915: make assert_device_not_suspended more precise

On ma, 2015-11-09 at 21:44 +, Chris Wilson wrote: > On Mon, Nov 09, 2015 at 09:13:45PM +0200, Imre Deak wrote: > > Atm, we assert that the device is not suspended after the point > > when the > > HW is truly put to a suspended state. This is fine, but we can > > catch > > more problems if we

Re: [Intel-gfx] [PATCH v2] drm/i915: Respect the brightness range from VBT.

On Tue, 10 Nov 2015, "Shih-Yuan Lee (FourDollars)" wrote: > Taking Dell XPS 13 (2015) as an example. The lowest PWM brightness is 10 > and the highest PWM brightness is 937. Before this change, we can only > use from 37 to 937, and 37 is used to turn off the backlight because

Re: [Intel-gfx] [PATCH 10/13] drm/i915: fix the CFB size check

Op 04-11-15 om 20:10 schreef Paulo Zanoni: > In function find_compression_threshold() we try to over-allocate CFB > space in order to reudce reallocations and fragmentation, and we're > not considering that at the CFB size check. Consider it. > > There is also a longer-term plan to kill >

Re: [Intel-gfx] [RFC 0/5] LRC irq handler cleanups

On 10/11/15 11:36, Chris Wilson wrote: On Tue, Nov 10, 2015 at 10:59:40AM +, Tvrtko Ursulin wrote: From: Tvrtko Ursulin Some random bits to make the LRC irq handler do fewer branching, locking and VMA lookups per interrupt handled. I failed to measure a

Re: [Intel-gfx] [PATCH 10/13] drm/i915: fix the CFB size check

Em Ter, 2015-11-10 às 11:22 +0100, Maarten Lankhorst escreveu: > Op 04-11-15 om 20:10 schreef Paulo Zanoni: > > In function find_compression_threshold() we try to over-allocate > > CFB > > space in order to reudce reallocations and fragmentation, and we're > > not considering that at the CFB size

Re: [Intel-gfx] [PATCH v2 11/14] drm/i915: Remove some post-commit members from intel_crtc->atomic.

On Tue, 2015-11-03 at 08:31 +0100, Maarten Lankhorst wrote: > fb_bits is useful to have in the crtc_state for cs flips later on, Why? When is later on? > so keep it alive there. The other stuff can be calculated in > post_plane_update, and aren't useful elsewhere. > > Currently there's a loop

Re: [Intel-gfx] [PATCH v2] drm/i915: Respect the brightness range from VBT.

On Tue, 10 Nov 2015, "Shih-Yuan Lee (FourDollars)" wrote: > Apparently you are not aware of GNOME has used 1 as the minimum brightness > level because of > > commit e6755fb78e8f20ecadf2a4080084121336624ad9 > Author: Jani Nikula > Date: Tue Aug 12

[Intel-gfx] [PATCH] drm/i915/skl: implement DP Aux Mutex framework

Beginning with SKL the DP Aux channel communication can be protected using a built in HW mutex. When PSR is enablabled the HW takes control on AUX and uses it to control panel exit/entry states. When validating PSR with automated tests, grabbing CRC from sink revealed strange aux communication

[Intel-gfx] [RFC 0/5] LRC irq handler cleanups

From: Tvrtko Ursulin Some random bits to make the LRC irq handler do fewer branching, locking and VMA lookups per interrupt handled. I failed to measure a significant gain on a powerful chip but it definitely results in fewer instructions and branches in the hot path.

[Intel-gfx] [PATCH 2/5] drm/i915: Move LRCA check out of the hot path

From: Tvrtko Ursulin There is no need to check the LRCA for non-aligment or range several times per interrupt handled when the VMA address in question is explicitly pinned and unpinned with a wider lifetime. So move the check to the place which does the pinning.

[Intel-gfx] [PATCH 5/5] drm/i915: Only grab and calculate timestamps when needed

From: Tvrtko Ursulin Tiny cleanup to avoid grabbing a timestamp and calculating the timeout when it is not going to be used. If anything makes the profile correctly show busy wait spends time in get seqno and not in ktime_get. Signed-off-by: Tvrtko Ursulin

[Intel-gfx] [PATCH 1/5] drm/i915: Avoid invariant conditionals in lrc interrupt handler

From: Tvrtko Ursulin There is no point in doing several gen and static feature dependant branches multiple times per interrupt handled. Do them once on ring setup and use the cached values. Signed-off-by: Tvrtko Ursulin ---

[Intel-gfx] [PATCH 3/5] drm/i915: Cache LRCA in the context

From: Tvrtko Ursulin LRCA is static while the context is pinned so we can avoid looking up the VMA in question several times per interrupt handled. Signed-off-by: Tvrtko Ursulin --- drivers/gpu/drm/i915/i915_debugfs.c | 15 ++-

[Intel-gfx] [PATCH 4/5] drm/i915: Grab one forcewake across the whole LRC irq handler

From: Tvrtko Ursulin This is to replace multiple branch and spinlock heavy mmio operations per LRC interrupt with a single forcewake grab. Signed-off-by: Tvrtko Ursulin --- drivers/gpu/drm/i915/intel_lrc.c | 60

Re: [Intel-gfx] [PATCH v2] drm/i915: Respect the brightness range from VBT.

On Tue, Nov 10, 2015 at 12:15:48PM +0200, Jani Nikula wrote: > On Tue, 10 Nov 2015, "Shih-Yuan Lee (FourDollars)" > wrote: > > Taking Dell XPS 13 (2015) as an example. The lowest PWM brightness is 10 > > and the highest PWM brightness is 937. Before this change, we can only

Re: [Intel-gfx] [PATCH v2 09/14] drm/i915: Remove atomic.pre_disable_primary.

On Tue, 2015-11-03 at 08:31 +0100, Maarten Lankhorst wrote: > This can be derived from the atomic state in pre_plane_update, > which makes it more clear when it's supposed to be called. > > Signed-off-by: Maarten Lankhorst > --- >

Re: [Intel-gfx] [PATCH i-g-t] lib: add a environment variable to control output

On 9 November 2015 at 20:58, Chris Wilson wrote: > On Mon, Nov 09, 2015 at 05:17:13PM +, Thomas Wood wrote: >> Disable output of terminal control characters and progress meters when >> IGT_PLAIN_OUTPUT is set in the environment. >> >> Cc: Derek Morton

Re: [Intel-gfx] [RFC 0/5] LRC irq handler cleanups

On Tue, Nov 10, 2015 at 10:59:40AM +, Tvrtko Ursulin wrote: > From: Tvrtko Ursulin > > Some random bits to make the LRC irq handler do fewer branching, > locking and VMA lookups per interrupt handled. > > I failed to measure a significant gain on a powerful chip

Re: [Intel-gfx] [PATCH 3/3] drm/i915: Use insert_page for pwrite_fast

On Tue, Nov 10, 2015 at 08:44:59AM +, Chris Wilson wrote: > On Tue, Nov 10, 2015 at 09:55:18AM +0200, Mika Kuoppala wrote: > > > + while (remain) { > > > /* Operation in this page > > >* > > >* page_base = page offset within aperture > > >*

Re: [Intel-gfx] [PATCH] drm/i915/skl: implement DP Aux Mutex framework

On Tue, 10 Nov 2015, Wayne Boyer wrote: > Beginning with SKL the DP Aux channel communication can be protected > using a built in H/W mutex. > > This patch provides an initial implementation for using that mutex. > The use is currently limited to protecting the sink crc

Re: [Intel-gfx] [PATCH] drm/i915/skl: implement DP Aux Mutex framework

On 10 November 2015 at 20:51, Jani Nikula wrote: > On Tue, 10 Nov 2015, Wayne Boyer wrote: >> Beginning with SKL the DP Aux channel communication can be protected >> using a built in H/W mutex. >> >> This patch provides an initial

[Intel-gfx] [PATCH v4] drm/i915: Set brightness maximum to a fixed value 100.

Take Dell XPS 13 (2015) as an example. The vbt min 10 out of [0..255]. The PWM max is 937 so the corresponding PWM min is 37 (10*937/256). This commit makes the sysfs brightness 1 map to the PWM brightness 37 and 100 map to the PWM brightness 937. Signed-off-by: Shih-Yuan Lee (FourDollars)

Re: [Intel-gfx] [PATCH 13/14] drm/i915: Use intel_dp->DP in eDP PLL setup

On Fri, 30 Oct 2015, Ville Syrjälä wrote: > On Fri, Oct 30, 2015 at 05:00:42PM +0100, Daniel Vetter wrote: >> On Thu, Oct 29, 2015 at 09:26:02PM +0200, ville.syrj...@linux.intel.com >> wrote: >> > From: Ville Syrjälä >> > >> > Use

Re: [Intel-gfx] [PATCH v2 13/14] drm/i915: Use intel_dp->DP in eDP PLL setup

On Tue, 10 Nov 2015, ville.syrj...@linux.intel.com wrote: > From: Ville Syrjälä > > Use intel_dp->DP in the eDP PLL setup, instead of doing RMWs. > > To do this we need to move DP_AUDIO_OUTPUT_ENABLE setup to happen later, > so that we don't enable audio

[Intel-gfx] [PATCH i-g-t 2/2] tests/kms_force_connector: reset connectors and edid on exit

Signed-off-by: Thomas Wood --- tests/kms_force_connector.c | 8 +--- 1 file changed, 5 insertions(+), 3 deletions(-) diff --git a/tests/kms_force_connector.c b/tests/kms_force_connector.c index a79c974..cf918a7 100644 --- a/tests/kms_force_connector.c +++

[Intel-gfx] [PATCH i-g-t 1/2] tests/kms_force_connector: clear forced edid in reset

Signed-off-by: Thomas Wood --- tests/kms_force_connector.c | 4 +++- 1 file changed, 3 insertions(+), 1 deletion(-) diff --git a/tests/kms_force_connector.c b/tests/kms_force_connector.c index f34f21a..a79c974 100644 --- a/tests/kms_force_connector.c +++

Re: [Intel-gfx] [PATCH] drm/i915: Reset dpll_hw_state when selecting a new pll on hsw

On Wed, 14 Oct 2015, Daniel Vetter wrote: > On Wed, Oct 14, 2015 at 04:58:55PM +0300, Ander Conselvan De Oliveira wrote: >> On Wed, 2015-10-14 at 14:44 +0200, Daniel Vetter wrote: >> > On Wed, Oct 14, 2015 at 11:21:46AM +0300, Ander Conselvan De Oliveira >> > wrote: >> > > On

[Intel-gfx] [PATCH v2 13/14] drm/i915: Use intel_dp->DP in eDP PLL setup

From: Ville Syrjälä Use intel_dp->DP in the eDP PLL setup, instead of doing RMWs. To do this we need to move DP_AUDIO_OUTPUT_ENABLE setup to happen later, so that we don't enable audio accidentally while configuring the PLL. Note that actually we already enabled

Re: [Intel-gfx] [PATCH v3] drm/i915: Set brightness maximum to a fixed value 100.

Hi Shih-Yuan, [auto build test ERROR on drm-intel/for-linux-next] [also build test ERROR on v4.3 next-2015] url: https://github.com/0day-ci/linux/commits/Shih-Yuan-Lee-FourDollars/drm-i915-Set-brightness-maximum-to-a-fixed-value-100/2015-121325 base:

[Intel-gfx] [V2 PATCH 1/2] dp/mst: add SDP stream support

From: Libin Yang This adds code to initialise the SDP streams for a sink in the simplest ordering. I've no idea how you'd want to control the ordering at this level, so don't bother until someone comes up with a use case. Signed-off-by: Libin Yang

[Intel-gfx] [V2 PATCH 2/2] drm/i915: start adding dp mst audio

From: Libin Yang This patch adds support for DP MST audio in i915. Enable audio codec when DP MST is enabled if has_audio flag is set. Disable audio codec when DP MST is disabled if has_audio flag is set. Signed-off-by: Libin Yang

Re: [Intel-gfx] [PATCH 10/13] drm/i915: fix the CFB size check

Op 10-11-15 om 13:20 schreef Zanoni, Paulo R: > Em Ter, 2015-11-10 às 11:22 +0100, Maarten Lankhorst escreveu: >> Op 04-11-15 om 20:10 schreef Paulo Zanoni: >>> In function find_compression_threshold() we try to over-allocate >>> CFB >>> space in order to reudce reallocations and fragmentation,

Re: [Intel-gfx] [PATCH v2 12/14] drm/i915: Nuke fbc members from intel_crtc->atomic.

On Tue, 2015-11-03 at 08:31 +0100, Maarten Lankhorst wrote: > This leaves intel_crtc->atomic empty, so zap it as well. > > Signed-off-by: Maarten Lankhorst > --- > drivers/gpu/drm/i915/intel_display.c | 84 ++- > - >

Re: [Intel-gfx] HDMI hotplug fails when using VT or boot on text mode

On Tue, 10 Nov 2015, "Sanchez, AdolfoX" wrote: > When using i915 > O.S. Ubuntu 15.10 > Pltaform: Bay Trail I > > Issue: When the O.S. is on Virtual Terminal or Text Mode it doesn't > detect when connecting HDMI display, the issue is not present on > graphic mode. > > Is

[Intel-gfx] [PATCH v3] drm/i915: Set brightness maximum to a fixed value 100.

Take Dell XPS 13 (2015) as an example. The vbt min 10 out of [0..255]. The PWM max is 937 so the corresponding PWM min is 37 (10*937/256). This commit makes the sysfs brightness 1 map to the PWM brightness 37 and 100 map to the PWM brightness 937. Signed-off-by: Shih-Yuan Lee (FourDollars)