[Intel-gfx] [PATCH 2/2] drm/i915: Show PCI power state under debugfs/i915_runtime_pm_status

2016-03-30 Thread Chris Wilson
As the current PCI power state is an essential feature of runtime pm, include it in the debugfs/i915_runtime_pm_status. Signed-off-by: Chris Wilson Cc: Imre Deak --- drivers/gpu/drm/i915/i915_debugfs.c | 9 + 1 file changed, 5 insertions(+), 4 deletions(-) diff --git a/drivers/gpu/drm/

[Intel-gfx] [PATCH 1/2] drm/i915: Add struct_mutex locking for debugs/i915_gem_framebuffer

2016-03-30 Thread Chris Wilson
Since describe_obj() looks at state guarded by the struct_mutex, we need to be holding it. [ 580.201054] drv_suspend: starting subtest debugfs-reader [ 580.239652] [ cut here ] [ 580.239696] WARNING: CPU: 0 PID: 920 at include/linux/list_check.h:25 describe_obj+0x419/0x

Re: [Intel-gfx] [PATCH v4 RESEND 5/5] drm/i915: Get rid of intel_dp_dpcd_read_wake()

2016-03-30 Thread Jani Nikula
On Mon, 28 Mar 2016, Lyude wrote: > Since we've fixed up drm_dp_dpcd_read() to allow for retries when things > timeout, there's no use for having this function anymore. Good riddens. > > Signed-off-by: Lyude > --- > drivers/gpu/drm/i915/intel_dp.c | 79 >

[Intel-gfx] [PATCH 3/3] drm/i915: Add backlight Control using DPCD registers for DP connectors

2016-03-30 Thread Yetunde Adebisi
This patch enables support for DPCD backlight control for DP connectors. The VESA spec defines DPCD backlight control only for eDP but some add-on cards like the Chrontel CH7511B DP-LVDS cards have the display control DPCD registers enabled. This patch registers a backlight device exposed via sysfs

[Intel-gfx] [PATCH 2/3] drm/i915: Add Backlight Control using DPCD for eDP connectors (v8)

2016-03-30 Thread Yetunde Adebisi
This patch adds support for eDP backlight control using DPCD registers to backlight hooks in intel_panel. It checks for backlight control over AUX channel capability and sets up function pointers to get and set the backlight brightness level if supported. v2: Moved backlight functions from intel_

[Intel-gfx] [PATCH 1/3] drm/dp: Add definition for Display Control DPCD Registers capability size

2016-03-30 Thread Yetunde Adebisi
This is used when reading Display Control capability Registers on the sink device. cc: Jani Nikula cc: dri-de...@lists.freedesktop.org Signed-off-by: Yetunde Adebisi --- include/drm/drm_dp_helper.h | 1 + 1 file changed, 1 insertion(+) diff --git a/include/drm/drm_dp_helper.h b/include/drm/drm

[Intel-gfx] [PATCH 0/3] DPCD Backlight Control

2016-03-30 Thread Yetunde Adebisi
These patches add support for Backlight Control using DPCD registers on eDP displays. - Patch 1 adds macro for DPCD registers capability size to drm_dp_helper.h A copy of this patch has also been sent to dri-devel list. - Patch 2 Implements functionaly for DPCD Backlight Control - Patch 3 Impl

Re: [Intel-gfx] [PATCH 2/2] drm/i915/BXT: Tolerance at BXT DSI pipe_config comparison

2016-03-30 Thread Ramalingam C
On Wednesday 30 March 2016 05:02 PM, Daniel Vetter wrote: On Tue, Mar 29, 2016 at 11:04:51PM +0530, Ramalingam C wrote: At BXT DSI, PIPE registers are inactive. So we can't get the PIPE's mode parameters from them. The possible option is retriving them from the PORT registers. But mode timing p

Re: [Intel-gfx] [PATCH 1/2] drm/i915: Update VBT fields for child devices

2016-03-30 Thread Jani Nikula
On Fri, 25 Mar 2016, Shubhangi Shrivastava wrote: > This patch adds new fields that are not yet added in drm code > in child devices struct > > Signed-off-by: Sivakumar Thulasimani > Signed-off-by: Durgadoss R > Signed-off-by: Shubhangi Shrivastava > Reviewed-by: Ville Syrjälä > --- > driver

[Intel-gfx] [PATCH] drm/i915/kbl: Remove preliminary_hw_support protection from KBL.

2016-03-30 Thread Rodrigo Vivi
We now have KBL machines running in our CI systems and with no blocking issues that could cause a full hangs or blank screens. Signed-off-by: Rodrigo Vivi --- drivers/gpu/drm/i915/i915_drv.c | 2 -- 1 file changed, 2 deletions(-) diff --git a/drivers/gpu/drm/i915/i915_drv.c b/drivers/gpu/drm/i9

Re: [Intel-gfx] [PATCH 1/2] drm/i915: Cache elsp submit register

2016-03-30 Thread Dave Gordon
On 22/03/16 17:39, Tvrtko Ursulin wrote: On 22/03/16 17:29, Ville Syrjälä wrote: On Tue, Mar 22, 2016 at 05:16:52PM +, Tvrtko Ursulin wrote: From: Tvrtko Ursulin Since we write four times to the same register, caching the mmio register saves a tiny amount of generated code. The compile

[Intel-gfx] [PATCH 1/3] drm/i915: Pass crtc_state to color management functions.

2016-03-30 Thread Maarten Lankhorst
Signed-off-by: Maarten Lankhorst --- drivers/gpu/drm/i915/i915_drv.h | 4 ++-- drivers/gpu/drm/i915/intel_color.c | 43 ++-- drivers/gpu/drm/i915/intel_display.c | 22 +++--- drivers/gpu/drm/i915/intel_drv.h | 4 ++-- 4 files changed, 40 in

[Intel-gfx] [PATCH 0/3] drm/i915: color management atomic fixes

2016-03-30 Thread Maarten Lankhorst
Some small fixes to color management. crtc_state should be passed, a redundant check removed, and color management updated during vblank evasion. Maarten Lankhorst (3): drm/i915: Pass crtc_state to color management functions. drm/i915: Do not check crtc_state->active in intel_color_load_luts.

[Intel-gfx] [PATCH 2/3] drm/i915: Do not check crtc_state->active in intel_color_load_luts.

2016-03-30 Thread Maarten Lankhorst
This is already tested by its callers. Signed-off-by: Maarten Lankhorst --- drivers/gpu/drm/i915/intel_color.c | 4 1 file changed, 4 deletions(-) diff --git a/drivers/gpu/drm/i915/intel_color.c b/drivers/gpu/drm/i915/intel_color.c index 9cffa638c351..1b3f97449395 100644 --- a/drivers/gpu

[Intel-gfx] [PATCH 3/3] drm/i915: Update color management during vblank evasion.

2016-03-30 Thread Maarten Lankhorst
Without this a vblank may occur between updating color management and planes, which should be prevented. intel_color_set_csc was called in update pipe config because the handover from hardware may not have any csc set, which resulted in a black screen. Because of this also update color management

Re: [Intel-gfx] [PATCH] drm/ttm: Remove TTM_HAS_AGP

2016-03-30 Thread Daniel Vetter
On Wed, Mar 30, 2016 at 01:53:38PM +0100, Emil Velikov wrote: > On 30 March 2016 at 12:24, Daniel Vetter wrote: > > It tries to do fancy things with excluding agp support if ttm is > > built-in, but agp isn't. Instead just express this depency like drm > > does and use CONFIG_AGP everywhere. > > >

Re: [Intel-gfx] [PATCH 03/10] drm/armada: Drop fb gamma_set/get functions

2016-03-30 Thread Daniel Vetter
On Wed, Mar 30, 2016 at 01:56:06PM +0100, Russell King - ARM Linux wrote: > On Wed, Mar 30, 2016 at 01:19:21PM +0200, Daniel Vetter wrote: > > On Wed, Mar 30, 2016 at 1:09 PM, Russell King - ARM Linux > > wrote: > > > On Wed, Mar 30, 2016 at 11:51:18AM +0200, Daniel Vetter wrote: > > >> The fb hel

Re: [Intel-gfx] [PATCH 04/10] drm/sysfs: Nuke TV/DVI property files

2016-03-30 Thread Daniel Vetter
On Wed, Mar 30, 2016 at 09:49:26AM -0400, Alex Deucher wrote: > On Wed, Mar 30, 2016 at 5:45 AM, Daniel Vetter wrote: > > This goes all the way back to the original KMS commit aeons ago > > > > commit f453ba0460742ad027ae0c4c7d61e62817b3e7ef > > Author: Dave Airlie > > Date: Fri Nov 7 14:05:41

Re: [Intel-gfx] [PATCH 10/10] drm/tegra: Don't set a gamma table size

2016-03-30 Thread Daniel Vetter
On Wed, Mar 30, 2016 at 02:39:22PM +0200, Thierry Reding wrote: > On Wed, Mar 30, 2016 at 11:51:25AM +0200, Daniel Vetter wrote: > > tegra doesn't have any functions to set gamma tables, so this is > > completely defunct. > > > > Not nice to lie to userspace, so let's stop! > > > > Cc: Thierry Re

Re: [Intel-gfx] [PATCH] vgacon: dummy implementation for vgacon_text_force

2016-03-30 Thread Daniel Vetter
On Wed, Mar 30, 2016 at 09:52:28AM -0400, Alex Deucher wrote: > On Wed, Mar 30, 2016 at 5:26 AM, Daniel Vetter wrote: > > This allows us to ditch a ton of ugly #ifdefs from a bunch of drm modeset > > drivers. > > > > v2: Make the dummy function actually return a sane value, spotted by > > Ville. >

[Intel-gfx] ✗ Fi.CI.BAT: failure for Another shot at cruft removal

2016-03-30 Thread Patchwork
== Series Details == Series: Another shot at cruft removal URL : https://patchwork.freedesktop.org/series/5033/ State : failure == Summary == Series 5033v1 Another shot at cruft removal 2016-03-30T09:23:14.874392 http://patchwork.freedesktop.org/api/1.0/series/5033/revisions/1/mbox/ Applying:

Re: [Intel-gfx] [PATCH 3/3] drm/i915: Update color management during vblank evasion.

2016-03-30 Thread Lionel Landwerlin
On 30/03/16 16:16, Maarten Lankhorst wrote: Without this a vblank may occur between updating color management and planes, which should be prevented. intel_color_set_csc was called in update pipe config because the handover from hardware may not have any csc set, which resulted in a black screen.

Re: [Intel-gfx] [PATCH 2/3] drm/i915: Do not check crtc_state->active in intel_color_load_luts.

2016-03-30 Thread Lionel Landwerlin
On 30/03/16 16:16, Maarten Lankhorst wrote: This is already tested by its callers. Signed-off-by: Maarten Lankhorst Reviewed-by: Lionel Landwerlin --- drivers/gpu/drm/i915/intel_color.c | 4 1 file changed, 4 deletions(-) diff --git a/drivers/gpu/drm/i915/intel_color.c b/drivers/gp

Re: [Intel-gfx] [PATCH 1/3] drm/i915: Pass crtc_state to color management functions.

2016-03-30 Thread Lionel Landwerlin
On 30/03/16 16:16, Maarten Lankhorst wrote: Signed-off-by: Maarten Lankhorst Reviewed-by: Lionel Landwerlin --- drivers/gpu/drm/i915/i915_drv.h | 4 ++-- drivers/gpu/drm/i915/intel_color.c | 43 ++-- drivers/gpu/drm/i915/intel_display.c | 22 +++

[Intel-gfx] [REGRESSION] system hang on ILK/SNB/IVB

2016-03-30 Thread Gabriel Feceoru
This commit causes a hang while running kms suspend tests (kms_pipe_crc_basic@suspend-read-crc-pipe-*) on ILK/SNB/IVB, affecting CI. Probably the same problem with the one in v2, but on older HW. commit a7442b93cf32c1e1ddb721a26cd1f92302e2a222 Author: Lukas Wunner Date: Wed Mar 9 12:52:53 2

[Intel-gfx] [PATCH] drm/i915: Protect fbdev across slow or failed initialisation

2016-03-30 Thread Chris Wilson
If the initialisation fails, we may be left with a dangling pointer with an incomplete fbdev structure. Here we want to disable internal calls into fbdev. Similarly, the initialisation may be slow and we haven't yet enabled the fbdev (e.g. quick suspend or last-close before the async init completes

Re: [Intel-gfx] [PATCH] drm/i915: Protect fbdev across slow or failed initialisation

2016-03-30 Thread kbuild test robot
Hi Chris, [auto build test ERROR on drm-intel/for-linux-next] [cannot apply to v4.6-rc1 next-20160330] [if your patch is applied to the wrong git tree, please drop us a note to help improving the system] url: https://github.com/0day-ci/linux/commits/Chris-Wilson/drm-i915-Protect-fbdev

Re: [Intel-gfx] [PATCH] drm/i915: Protect fbdev across slow or failed initialisation

2016-03-30 Thread kbuild test robot
Hi Chris, [auto build test WARNING on drm-intel/for-linux-next] [cannot apply to v4.6-rc1 next-20160330] [if your patch is applied to the wrong git tree, please drop us a note to help improving the system] url: https://github.com/0day-ci/linux/commits/Chris-Wilson/drm-i915-Protect-fbdev

Re: [Intel-gfx] [PATCH] drm/i915: Protect fbdev across slow or failed initialisation

2016-03-30 Thread kbuild test robot
Hi Chris, [auto build test ERROR on drm-intel/for-linux-next] [cannot apply to v4.6-rc1 next-20160330] [if your patch is applied to the wrong git tree, please drop us a note to help improving the system] url: https://github.com/0day-ci/linux/commits/Chris-Wilson/drm-i915-Protect-fbdev

Re: [Intel-gfx] [PATCH] drm/i915: Protect fbdev across slow or failed initialisation

2016-03-30 Thread Chris Wilson
On Wed, Mar 30, 2016 at 06:57:14PM +0100, Chris Wilson wrote: > If the initialisation fails, we may be left with a dangling pointer with > an incomplete fbdev structure. Here we want to disable internal calls > into fbdev. Similarly, the initialisation may be slow and we haven't yet > enabled the f

Re: [Intel-gfx] [REGRESSION] system hang on ILK/SNB/IVB

2016-03-30 Thread Daniel Vetter
On Wed, Mar 30, 2016 at 08:20:26PM +0300, Gabriel Feceoru wrote: > This commit causes a hang while running kms suspend tests > (kms_pipe_crc_basic@suspend-read-crc-pipe-*) on ILK/SNB/IVB, affecting CI. > > Probably the same problem with the one in v2, but on older HW. I did check the patchwork/BA

Re: [Intel-gfx] [PATCH 1/2] drm/i915: Add struct_mutex locking for debugs/i915_gem_framebuffer

2016-03-30 Thread Daniel Vetter
On Wed, Mar 30, 2016 at 03:18:40PM +0100, Chris Wilson wrote: > Since describe_obj() looks at state guarded by the struct_mutex, we need > to be holding it. > > [ 580.201054] drv_suspend: starting subtest debugfs-reader > [ 580.239652] [ cut here ] > [ 580.239696] WARNIN

Re: [Intel-gfx] [PATCH 2/2] drm/i915: Show PCI power state under debugfs/i915_runtime_pm_status

2016-03-30 Thread Daniel Vetter
On Wed, Mar 30, 2016 at 03:18:41PM +0100, Chris Wilson wrote: > As the current PCI power state is an essential feature of runtime pm, > include it in the debugfs/i915_runtime_pm_status. > > Signed-off-by: Chris Wilson > Cc: Imre Deak > --- > drivers/gpu/drm/i915/i915_debugfs.c | 9 + >

[Intel-gfx] [PATCH v3] drm/i915: Protect fbdev across slow or failed initialisation

2016-03-30 Thread Chris Wilson
If the initialisation fails, we may be left with a dangling pointer with an incomplete fbdev structure. Here we want to disable internal calls into fbdev. Similarly, the initialisation may be slow and we haven't yet enabled the fbdev (e.g. quick suspend or last-close before the async init completes

Re: [Intel-gfx] [PATCH 2/2] drm/i915/BXT: Tolerance at BXT DSI pipe_config comparison

2016-03-30 Thread Daniel Vetter
On Wed, Mar 30, 2016 at 07:49:40PM +0530, Ramalingam C wrote: > > On Wednesday 30 March 2016 05:02 PM, Daniel Vetter wrote: > >On Tue, Mar 29, 2016 at 11:04:51PM +0530, Ramalingam C wrote: > >>At BXT DSI, PIPE registers are inactive. So we can't get the > >>PIPE's mode parameters from them. The po

Re: [Intel-gfx] [PATCH 2/2] drm/i915: Show PCI power state under debugfs/i915_runtime_pm_status

2016-03-30 Thread Chris Wilson
On Wed, Mar 30, 2016 at 08:55:51PM +0200, Daniel Vetter wrote: > On Wed, Mar 30, 2016 at 03:18:41PM +0100, Chris Wilson wrote: > > As the current PCI power state is an essential feature of runtime pm, > > include it in the debugfs/i915_runtime_pm_status. > > > > Signed-off-by: Chris Wilson > > Cc

[Intel-gfx] [PATCH v5 02/46] backlight: pwm_bl: remove useless call to pwm_set_period()

2016-03-30 Thread Boris Brezillon
The PWM period will be set when calling pwm_config. Remove this useless call to pwm_set_period(), which might mess up with the internal PWM state. Signed-off-by: Boris Brezillon Acked-by: Lee Jones --- drivers/video/backlight/pwm_bl.c | 4 +--- 1 file changed, 1 insertion(+), 3 deletions(-) di

[Intel-gfx] [PATCH v5 03/46] backlight: lm3630a_bl: stop messing with the pwm->period field

2016-03-30 Thread Boris Brezillon
pwm->period field is not supposed to be changed by PWM users. The only ones authorized to change it are the PWM core and PWM drivers. Signed-off-by: Boris Brezillon --- drivers/video/backlight/lm3630a_bl.c | 3 +-- 1 file changed, 1 insertion(+), 2 deletions(-) diff --git a/drivers/video/backli

[Intel-gfx] [PATCH v5 06/46] pwm: use pwm_get/set_xxx() helpers where appropriate

2016-03-30 Thread Boris Brezillon
Use pwm_get/set_xxx() helpers instead of directly accessing the pwm->xxx field. Doing that will ease adaptation of the PWM framework to support atomic update. Signed-off-by: Boris Brezillon --- Patch generated with the following coccinelle script: --->8--- virtual patch @@ struct pwm_device *p;

[Intel-gfx] [PATCH v5 01/46] pwm: rcar: make use of pwm_is_enabled()

2016-03-30 Thread Boris Brezillon
Commit 5c31252c4a86 ("pwm: Add the pwm_is_enabled() helper") introduced a new function to test whether a PWM device is enabled or not without manipulating PWM internal fields. Hiding this is necessary if we want to smoothly move to the atomic PWM config approach without impacting PWM drivers. Fix t

[Intel-gfx] [PATCH v5 00/46] pwm: add support for atomic update

2016-03-30 Thread Boris Brezillon
Hello, This series adds support for atomic PWM update, or IOW, the capability to update all the parameters of a PWM device (enabled/disabled, period, duty and polarity) in one go. It also adds support for initial PWM state retrieval (or hardware readout), which should allow smooth handover betwee

[Intel-gfx] [PATCH v5 04/46] pwm: get rid of pwm->lock

2016-03-30 Thread Boris Brezillon
PWM devices are not protected against concurrent accesses. The lock in pwm_device might let PWM users think it is, but it's actually only protecting the enabled state. Removing this lock should be fine as long as all PWM users are aware that accesses to the PWM device have to be serialized, which

[Intel-gfx] [PATCH v5 15/46] pwm: introduce the pwm_state concept

2016-03-30 Thread Boris Brezillon
The PWM state, represented by its period, duty_cycle and polarity, is currently directly stored in the PWM device. Declare a pwm_state structure embedding those field so that we can later use this struct to atomically update all the PWM parameters at once. All pwm_get_xxx() helpers are now impleme

[Intel-gfx] [PATCH v5 14/46] pwm: keep PWM state in sync with hardware state

2016-03-30 Thread Boris Brezillon
Before the introduction of pwm_args, the core and some drivers were resetting the PWM period and polarity states to the reference values (those provided through the DT, a PWM lookup table or hardcoded in the driver). Now that all PWM users are correctly using pwm_args to configure their PWM device

[Intel-gfx] [PATCH v5 30/46] regulator: pwm: retrieve correct voltage

2016-03-30 Thread Boris Brezillon
The continuous PWM voltage regulator is caching the voltage value in the ->volt_uV field. While most of the time this value should reflect the real voltage, sometime it can be sightly different if the PWM device rounded the set_duty_cycle request. Moreover, this value is not valid until someone has

[Intel-gfx] [PATCH v5 36/46] input: misc: max77693: switch to the atomic API

2016-03-30 Thread Boris Brezillon
pwm_config/enable/disable() have been deprecated and should be replaced by pwm_apply_state(). Signed-off-by: Boris Brezillon --- drivers/input/misc/max77693-haptic.c | 23 +-- 1 file changed, 17 insertions(+), 6 deletions(-) diff --git a/drivers/input/misc/max77693-haptic.c

[Intel-gfx] [PATCH v5 07/46] clk: pwm: use pwm_get_args() where appropriate

2016-03-30 Thread Boris Brezillon
The PWM framework has clarified the concept of reference PWM config (the platform dependent config retrieved from the DT or the PWM lookup table) and real PWM state. Use pwm_get_args() when the PWM user wants to retrieve this reference config and not the current state. This is part of the rework

[Intel-gfx] [PATCH v5 08/46] hwmon: pwm-fan: use pwm_get_args() where appropriate

2016-03-30 Thread Boris Brezillon
The PWM framework has clarified the concept of reference PWM config (the platform dependent config retrieved from the DT or the PWM lookup table) and real PWM state. Use pwm_get_args() when the PWM user wants to retrieve this reference config and not the current state. This is part of the rework

[Intel-gfx] [PATCH v5 39/46] leds: pwm: switch to the atomic PWM API

2016-03-30 Thread Boris Brezillon
pwm_config/enable/disable() have been deprecated and should be replaced by pwm_apply_state(). Signed-off-by: Boris Brezillon --- drivers/leds/leds-pwm.c | 11 --- 1 file changed, 8 insertions(+), 3 deletions(-) diff --git a/drivers/leds/leds-pwm.c b/drivers/leds/leds-pwm.c index b48231c

[Intel-gfx] [PATCH v5 27/46] regulator: pwm: adjust PWM config at probe time

2016-03-30 Thread Boris Brezillon
The PWM attached to a PWM regulator device might have been previously configured by the bootloader. Make sure the bootloader and linux config are in sync, and adjust the PWM config if that's not the case. Signed-off-by: Boris Brezillon --- drivers/regulator/pwm-regulator.c | 50 +

[Intel-gfx] [PATCH v5 10/46] leds: pwm: use pwm_get_args() where appropriate

2016-03-30 Thread Boris Brezillon
The PWM framework has clarified the concept of reference PWM config (the platform dependent config retrieved from the DT or the PWM lookup table) and real PWM state. Use pwm_get_args() when the PWM user wants to retrieve this reference config and not the current state. This is part of the rework

[Intel-gfx] [PATCH v5 05/46] pwm: introduce the pwm_args concept

2016-03-30 Thread Boris Brezillon
Currently the PWM core mixes the current PWM state with the per-platform reference config (specified through the PWM lookup table, DT definition or directly hardcoded in PWM drivers). Create a pwm_args struct to store this reference config, so that PWM users can differentiate the current config fr

[Intel-gfx] [PATCH v5 34/46] clk: pwm: switch to the atomic API

2016-03-30 Thread Boris Brezillon
pwm_config/enable/disable() have been deprecated and should be replaced by pwm_apply_state(). Signed-off-by: Boris Brezillon --- drivers/clk/clk-pwm.c | 26 +++--- 1 file changed, 23 insertions(+), 3 deletions(-) diff --git a/drivers/clk/clk-pwm.c b/drivers/clk/clk-pwm.c ind

[Intel-gfx] [PATCH v5 32/46] pwm: deprecate pwm_config(), pwm_enable() and pwm_disable()

2016-03-30 Thread Boris Brezillon
Prefix those function as deprecated to encourage all existing users to switch to pwm_apply_state(). Signed-off-by: Boris Brezillon --- include/linux/pwm.h | 24 1 file changed, 12 insertions(+), 12 deletions(-) diff --git a/include/linux/pwm.h b/include/linux/pwm.h inde

[Intel-gfx] [PATCH v5 24/46] pwm: sti: add support for initial state retrieval

2016-03-30 Thread Boris Brezillon
Implement ->get_state() to provide support for initial state retrieval. Signed-off-by: Boris Brezillon --- drivers/pwm/pwm-sti.c | 41 + 1 file changed, 41 insertions(+) diff --git a/drivers/pwm/pwm-sti.c b/drivers/pwm/pwm-sti.c index 92abbd5..0fbca94 100

[Intel-gfx] [PATCH v5 28/46] regulator: pwm: swith to the atomic PWM API

2016-03-30 Thread Boris Brezillon
pwm_config/enable/disable() have been deprecated in favor of pwm_apply_state(). Replace all those calls with the equivalent pwm_get/apply_state(). Signed-off-by: Boris Brezillon --- drivers/regulator/pwm-regulator.c | 54 --- 1 file changed, 34 insertions(+),

[Intel-gfx] [PATCH v5 11/46] regulator: pwm: use pwm_get_args() where appropriate

2016-03-30 Thread Boris Brezillon
The PWM framework has clarified the concept of reference PWM config (the platform dependent config retrieved from the DT or the PWM lookup table) and real PWM state. Use pwm_get_args() when the PWM user wants to retrieve this reference config and not the current state. This is part of the rework

[Intel-gfx] [PATCH v5 20/46] pwm: add information about polarity, duty cycle and period to debugfs

2016-03-30 Thread Boris Brezillon
From: Heiko Stübner The pwm-states make it possible to also output the polarity, duty cycle and period information in the debugfs pwm summary-outout. This makes it easier to gather overview information about pwms without needing to walk through the sysfs attributes of every pwm. Signed-off-by: H

[Intel-gfx] [PATCH v5 17/46] pwm: add the PWM initial state retrieval infra

2016-03-30 Thread Boris Brezillon
Add a ->get_state() function to the pwm_ops struct to let PWM drivers initialize the PWM state attached to a PWM device. Signed-off-by: Boris Brezillon --- drivers/pwm/core.c | 3 +++ include/linux/pwm.h | 5 + 2 files changed, 8 insertions(+) diff --git a/drivers/pwm/core.c b/drivers/pwm/

[Intel-gfx] [PATCH v5 40/46] backlight: lm3630a: switch to the atomic PWM API

2016-03-30 Thread Boris Brezillon
pwm_config/enable/disable() have been deprecated and should be replaced by pwm_apply_state(). Signed-off-by: Boris Brezillon --- drivers/video/backlight/lm3630a_bl.c | 14 -- 1 file changed, 8 insertions(+), 6 deletions(-) diff --git a/drivers/video/backlight/lm3630a_bl.c b/drivers

[Intel-gfx] [PATCH v5 41/46] backlight: lp855x: switch to the atomic PWM API

2016-03-30 Thread Boris Brezillon
pwm_config/enable/disable() have been deprecated and should be replaced by pwm_apply_state(). Signed-off-by: Boris Brezillon --- drivers/video/backlight/lp855x_bl.c | 15 +-- 1 file changed, 9 insertions(+), 6 deletions(-) diff --git a/drivers/video/backlight/lp855x_bl.c b/drivers/

[Intel-gfx] [PATCH v5 37/46] input: misc: max8997: switch to the atomic PWM API

2016-03-30 Thread Boris Brezillon
pwm_config/enable/disable() have been deprecated and should be replaced by pwm_apply_state(). Signed-off-by: Boris Brezillon --- drivers/input/misc/max8997_haptic.c | 23 ++- 1 file changed, 18 insertions(+), 5 deletions(-) diff --git a/drivers/input/misc/max8997_haptic.c b

[Intel-gfx] [PATCH v5 38/46] input: misc: pwm-beeper: switch to the atomic PWM API

2016-03-30 Thread Boris Brezillon
pwm_config/enable/disable() have been deprecated and should be replaced by pwm_apply_state(). Signed-off-by: Boris Brezillon --- drivers/input/misc/pwm-beeper.c | 46 +++-- 1 file changed, 31 insertions(+), 15 deletions(-) diff --git a/drivers/input/misc/pwm-

[Intel-gfx] [PATCH v5 26/46] pwm: sun4i: implement hardware readout

2016-03-30 Thread Boris Brezillon
Implement ->get_state() instead of only initializing the polarity in the probe function. This implementation also takes care of keeping the PWM clk enabled if at least one of the PWM exported by the PWM chip is already enabled, which should prevent glitches. Signed-off-by: Boris Brezillon --- d

[Intel-gfx] [PATCH v5 44/46] video: ssd1307fb: switch to the atomic PWM API

2016-03-30 Thread Boris Brezillon
pwm_config/enable/disable() have been deprecated and should be replaced by pwm_apply_state(). Signed-off-by: Boris Brezillon --- drivers/video/fbdev/ssd1307fb.c | 24 +++- 1 file changed, 19 insertions(+), 5 deletions(-) diff --git a/drivers/video/fbdev/ssd1307fb.c b/drivers

[Intel-gfx] [PATCH v5 22/46] pwm: rockchip: avoid glitches on already running PWMs

2016-03-30 Thread Boris Brezillon
The current logic will disable the PWM clk even if the PWM was left enabled by the bootloader (because it's controlling a critical device like a regulator for example). Keep the PWM clk enabled if the PWM is enabled to avoid any glitches. Signed-off-by: Boris Brezillon --- drivers/pwm/pwm-rockch

[Intel-gfx] [PATCH v5 23/46] pwm: rockchip: add support for atomic update

2016-03-30 Thread Boris Brezillon
Implement the ->apply() function to add support for atomic update. Signed-off-by: Boris Brezillon Tested-by: Heiko Stuebner --- drivers/pwm/pwm-rockchip.c | 63 -- 1 file changed, 39 insertions(+), 24 deletions(-) diff --git a/drivers/pwm/pwm-rockchi

[Intel-gfx] [PATCH v5 31/46] pwm: update documentation

2016-03-30 Thread Boris Brezillon
Update the PWM subsystem documentation to reflect the atomic PWM changes. Signed-off-by: Boris Brezillon --- Documentation/pwm.txt | 27 +-- 1 file changed, 25 insertions(+), 2 deletions(-) diff --git a/Documentation/pwm.txt b/Documentation/pwm.txt index ca895fd..cb25fca

[Intel-gfx] [PATCH v5 13/46] backlight: pwm_bl: use pwm_get_args() where appropriate

2016-03-30 Thread Boris Brezillon
The PWM framework has clarified the concept of reference PWM config (the platform dependent config retrieved from the DT or the PWM lookup table) and real PWM state. Use pwm_get_args() when the PWM user wants to retrieve this reference config and not the current state. This is part of the rework

[Intel-gfx] [PATCH v5 35/46] hwmon: pwm-fan: switch to the atomic API

2016-03-30 Thread Boris Brezillon
pwm_config/enable/disable() have been deprecated and should be replaced by pwm_apply_state(). Signed-off-by: Boris Brezillon --- drivers/hwmon/pwm-fan.c | 81 - 1 file changed, 46 insertions(+), 35 deletions(-) diff --git a/drivers/hwmon/pwm-fan.c

[Intel-gfx] [PATCH v5 25/46] pwm: sti: avoid glitches on already running PWMs

2016-03-30 Thread Boris Brezillon
The current logic will disable the PWM clk even if a PWM was left enabled by the bootloader (because it's controlling a critical device like a regulator for example). Keep the PWM clk enabled if at least one PWM is enabled to avoid any glitches. Signed-off-by: Boris Brezillon --- drivers/pwm/pwm

[Intel-gfx] [PATCH v5 21/46] pwm: rockchip: add initial state retrieval

2016-03-30 Thread Boris Brezillon
Implement the ->get_state() function to expose initial state. Signed-off-by: Boris Brezillon --- drivers/pwm/pwm-rockchip.c | 69 ++ 1 file changed, 69 insertions(+) diff --git a/drivers/pwm/pwm-rockchip.c b/drivers/pwm/pwm-rockchip.c index 7d9cc90..6

[Intel-gfx] [PATCH v5 12/46] fbdev: ssd1307fb: use pwm_get_args() where appropriate

2016-03-30 Thread Boris Brezillon
The PWM framework has clarified the concept of reference PWM config (the platform dependent config retrieved from the DT or the PWM lookup table) and real PWM state. Use pwm_get_args() when the PWM user wants to retrieve this reference config and not the current state. This is part of the rework

[Intel-gfx] [PATCH v5 19/46] pwm: switch to the atomic API

2016-03-30 Thread Boris Brezillon
Replace legacy pwm_get/set_xxx() and pwm_config/enable/disable() calls by pwm_get/apply_state(). Signed-off-by: Boris Brezillon --- drivers/pwm/core.c | 5 - drivers/pwm/sysfs.c | 61 +++-- 2 files changed, 40 insertions(+), 26 deletions(-)

[Intel-gfx] [PATCH v5 18/46] pwm: add the core infrastructure to allow atomic update

2016-03-30 Thread Boris Brezillon
Add an ->apply() method to the pwm_ops struct to allow PWM drivers to implement atomic update. This method will be preferred over the ->enable(), ->disable() and ->config() methods if available. Add the pwm_apply_state() function to the PWM user API. Note that the pwm_apply_state() does not guara

[Intel-gfx] [PATCH v5 46/46] ARM: s3c24xx: rx1950: switch to the atomic PWM API

2016-03-30 Thread Boris Brezillon
Replace pwm_disable/enable/config() by pwm_apply_state(). Signed-off-by: Boris Brezillon --- arch/arm/mach-s3c24xx/mach-rx1950.c | 17 ++--- 1 file changed, 14 insertions(+), 3 deletions(-) diff --git a/arch/arm/mach-s3c24xx/mach-rx1950.c b/arch/arm/mach-s3c24xx/mach-rx1950.c index

[Intel-gfx] [PATCH v5 42/46] backlight: lp8788: switch to the atomic PWM API

2016-03-30 Thread Boris Brezillon
pwm_config/enable/disable() have been deprecated and should be replaced by pwm_apply_state(). Signed-off-by: Boris Brezillon --- drivers/video/backlight/lp8788_bl.c | 17 + 1 file changed, 9 insertions(+), 8 deletions(-) diff --git a/drivers/video/backlight/lp8788_bl.c b/driver

[Intel-gfx] [PATCH v5 33/46] pwm: replace pwm_disable() by pwm_apply_state()

2016-03-30 Thread Boris Brezillon
Some PWM drivers are calling the deprecated pwm_disable() function in their pwm->free() or pdev->remove() function. Replace those calls by the pwm_apply_state(). Signed-off-by: Boris Brezillon --- drivers/pwm/pwm-lpc18xx-sct.c | 7 +-- drivers/pwm/pwm-lpc32xx.c | 9 +++-- drivers/pwm

[Intel-gfx] [PATCH v5 45/46] drm: i915: switch to the atomic PWM API

2016-03-30 Thread Boris Brezillon
pwm_config/enable/disable() have been deprecated and should be replaced by pwm_apply_state(). Signed-off-by: Boris Brezillon --- drivers/gpu/drm/i915/intel_panel.c | 39 +- 1 file changed, 26 insertions(+), 13 deletions(-) diff --git a/drivers/gpu/drm/i915/in

[Intel-gfx] [PATCH v5 09/46] misc: max77693-haptic: use pwm_get_args() where appropriate

2016-03-30 Thread Boris Brezillon
The PWM framework has clarified the concept of reference PWM config (the platform dependent config retrieved from the DT or the PWM lookup table) and real PWM state. Use pwm_get_args() when the PWM user wants to retrieve this reference config and not the current state. This is part of the rework

[Intel-gfx] [PATCH v5 43/46] backlight: pwm_bl: switch to the atomic PWM API

2016-03-30 Thread Boris Brezillon
pwm_config/enable/disable() have been deprecated and should be replaced by pwm_apply_state(). Signed-off-by: Boris Brezillon --- drivers/video/backlight/pwm_bl.c | 43 ++-- 1 file changed, 24 insertions(+), 19 deletions(-) diff --git a/drivers/video/backlight

[Intel-gfx] [PATCH v5 29/46] regulator: pwm: properly initialize the ->state field

2016-03-30 Thread Boris Brezillon
The ->state field is currently initialized to 0, thus referencing the voltage selector at index 0, which might not reflect the current voltage value. If possible, retrieve the current voltage selector from the PWM state, else return -EINVAL. Signed-off-by: Boris Brezillon Tested-by: Heiko Stuebne

[Intel-gfx] [PATCH v5 16/46] pwm: move the enabled/disabled info into pwm_state

2016-03-30 Thread Boris Brezillon
Prepare the transition to PWM atomic update by moving the enabled/disabled state into the pwm_state struct. This way we can easily update the whole PWM state by copying the new state in the ->state field. Signed-off-by: Boris Brezillon --- drivers/pwm/core.c | 13 + include/linux/pw

Re: [Intel-gfx] [PATCH v5 00/46] pwm: add support for atomic update

2016-03-30 Thread Boris Brezillon
+Doug (sorry, I forgot to add you in to the recipient list) On Wed, 30 Mar 2016 22:03:23 +0200 Boris Brezillon wrote: > Hello, > > This series adds support for atomic PWM update, or IOW, the capability > to update all the parameters of a PWM device (enabled/disabled, period, > duty and polarity

[Intel-gfx] [maintainer-tools PATCH] dim.rst: Point to drm-intel.rst in case of conflict.

2016-03-30 Thread Rodrigo Vivi
When searching for how to solve my first commit here I didn't noticed the right information was there already so I followed what was stated here and started bothering maintainers! :) Cc: Danie Vetter Signed-off-by: Rodrigo Vivi --- dim.rst | 8 +++- 1 file changed, 3 insertions(+), 5 deleti

Re: [Intel-gfx] [REGRESSION] system hang on ILK/SNB/IVB

2016-03-30 Thread Lukas Wunner
Hi Gabriel, On Wed, Mar 30, 2016 at 08:20:26PM +0300, Gabriel Feceoru wrote: > This commit causes a hang while running kms suspend tests > (kms_pipe_crc_basic@suspend-read-crc-pipe-*) on ILK/SNB/IVB, affecting CI. This happened with v1 but not with v2 of the patch. Please check if somehow v1 ende

Re: [Intel-gfx] [PATCH v5 30/46] regulator: pwm: retrieve correct voltage

2016-03-30 Thread Mark Brown
On Wed, Mar 30, 2016 at 10:03:53PM +0200, Boris Brezillon wrote: > The continuous PWM voltage regulator is caching the voltage value in > the ->volt_uV field. While most of the time this value should reflect the > real voltage, sometime it can be sightly different if the PWM device > rounded the se

Re: [Intel-gfx] [PATCH v5 28/46] regulator: pwm: swith to the atomic PWM API

2016-03-30 Thread Mark Brown
On Wed, Mar 30, 2016 at 10:03:51PM +0200, Boris Brezillon wrote: > pwm_config/enable/disable() have been deprecated in favor of > pwm_apply_state(). > Replace all those calls with the equivalent pwm_get/apply_state(). Acked-by: Mark Brown signature.asc Description: PGP signature ___

Re: [Intel-gfx] [PATCH v5 27/46] regulator: pwm: adjust PWM config at probe time

2016-03-30 Thread Mark Brown
On Wed, Mar 30, 2016 at 10:03:50PM +0200, Boris Brezillon wrote: > The PWM attached to a PWM regulator device might have been previously > configured by the bootloader. > Make sure the bootloader and linux config are in sync, and adjust the PWM > config if that's not the case. Acked-by: Mark Brown

Re: [Intel-gfx] [PATCH v5 08/46] hwmon: pwm-fan: use pwm_get_args() where appropriate

2016-03-30 Thread Guenter Roeck
On Wed, Mar 30, 2016 at 10:03:31PM +0200, Boris Brezillon wrote: > The PWM framework has clarified the concept of reference PWM config > (the platform dependent config retrieved from the DT or the PWM > lookup table) and real PWM state. > > Use pwm_get_args() when the PWM user wants to retrieve th

[Intel-gfx] i951 ERRORs and WARN_ON()s (was: blank screen on boot with i915/DRM_FBDEV_EMULATION)

2016-03-30 Thread Florian Zumbiehl
buffer device | [ 16.061856] [drm:intel_set_cpu_fifo_underrun_reporting [i915]] *ERROR* pipe A underrun | [ 16.725274] [drm] Initialized i915 1.6.0 20160330 for :00:02.0 on minor 0 | [ 16.805727] [drm:intel_cpu_fifo_underrun_irq_handler [i915]] *ERROR* CPU pipe A FIFO underrun > > | [ 2520.457732] WARNIN

[Intel-gfx] linux-next: manual merge of the drm-misc tree with Linus' tree

2016-03-30 Thread Stephen Rothwell
Hi all, Today's linux-next merge of the drm-misc tree got a conflict in: drivers/gpu/drm/amd/amdgpu/amdgpu_drv.c between commit: 257bf15a4b97 ("drm/amdgpu: add slap cache for sync objects as well") from Linus' tree and commit: 44debe7a123c ("vgacon: dummy implementation for vgacon_text_

Re: [Intel-gfx] [PATCH 1/5] drm: Add new DCS commands in the enum list

2016-03-30 Thread Andrzej Hajda
On 03/30/2016 04:03 PM, Jani Nikula wrote: > From: Deepak M > > Adding new DCS commands which are specified in the > DCS 1.3 spec related to CABC. > > v2: Sorted the Macro`s by value (Andrzej) > > v3 by Jani: sort all of enum, refer to MIPI DCS 1.3 > > Cc: Andrzej Hajda > Cc: Thierry Reding > Cc

Re: [Intel-gfx] [PATCH 1/5] drm: Add new DCS commands in the enum list

2016-03-30 Thread Daniel Vetter
On Thu, Mar 31, 2016 at 07:54:18AM +0200, Andrzej Hajda wrote: > On 03/30/2016 04:03 PM, Jani Nikula wrote: > > From: Deepak M > > > > Adding new DCS commands which are specified in the > > DCS 1.3 spec related to CABC. > > > > v2: Sorted the Macro`s by value (Andrzej) > > > > v3 by Jani: sort all

Re: [Intel-gfx] [PATCH v5 45/46] drm: i915: switch to the atomic PWM API

2016-03-30 Thread Jani Nikula
[aggressively trimmed the recipient list, can't seem to be able to send this otherwise] On Wed, 30 Mar 2016, Boris Brezillon wrote: > pwm_config/enable/disable() have been deprecated and should be replaced > by pwm_apply_state(). > > Signed-off-by: Boris Brezillon Reviewed-by: Jani Nikula Cc

Re: [Intel-gfx] [PATCH v5 34/46] clk: pwm: switch to the atomic API

2016-03-30 Thread Boris Brezillon
Hi Stephen, On Wed, 30 Mar 2016 15:01:49 -0700 Stephen Boyd wrote: > On 03/30, Boris Brezillon wrote: > > diff --git a/drivers/clk/clk-pwm.c b/drivers/clk/clk-pwm.c > > index ebcd738..49ec5b1 100644 > > --- a/drivers/clk/clk-pwm.c > > +++ b/drivers/clk/clk-pwm.c > > @@ -28,15 +28,29 @@ static in

<    1   2