Re: [Intel-gfx] [PATCH v12 21/38] mei: me: add ice lake point device id.

2019-02-08 Thread Greg KH
On Sat, Feb 09, 2019 at 12:42:50PM +0530, Ramalingam C wrote: > From: Tomas Winkler > > Add icelake mei device id. > > Cc: > Signed-off-by: Tomas Winkler > Signed-off-by: Greg Kroah-Hartman > Cherry-picked from > git://git.kernel.org/pub/scm/linux/kernel/git/gregkh/char-misc.git > char-mis

[Intel-gfx] ✗ Fi.CI.SPARSE: warning for drm/i915: Implement HDCP2.2

2019-02-08 Thread Patchwork
== Series Details == Series: drm/i915: Implement HDCP2.2 URL : https://patchwork.freedesktop.org/series/56453/ State : warning == Summary == $ dim sparse origin/drm-tip Sparse version: v0.5.2 Commit: drm/doc: document recommended component helper usage Okay! Commit: drm/i915: Gathering the HD

[Intel-gfx] ✗ Fi.CI.CHECKPATCH: warning for drm/i915: Implement HDCP2.2

2019-02-08 Thread Patchwork
== Series Details == Series: drm/i915: Implement HDCP2.2 URL : https://patchwork.freedesktop.org/series/56453/ State : warning == Summary == $ dim checkpatch origin/drm-tip d6c858444861 drm/doc: document recommended component helper usage -:17: WARNING:SPDX_LICENSE_TAG: Missing or malformed SP

[Intel-gfx] [PATCH v12 32/38] misc/mei/hdcp: Verify M_prime

2019-02-08 Thread Ramalingam C
Request to ME to verify the M_Prime received from the HDCP sink. ME FW will calculate the M and compare with M_prime received as part of RepeaterAuth_Stream_Ready, which is HDCP2.2 protocol msg. On successful completion of this stage, downstream propagation of the stream management info is comple

[Intel-gfx] [PATCH v12 38/38] FOR_TESTING_ONLY: ICL: Limit clk to <= 340MHz

2019-02-08 Thread Ramalingam C
Pruning 4k60 modes. Signed-off-by: Ramalingam C --- drivers/gpu/drm/i915/intel_hdmi.c | 3 +++ 1 file changed, 3 insertions(+) diff --git a/drivers/gpu/drm/i915/intel_hdmi.c b/drivers/gpu/drm/i915/intel_hdmi.c index c2c91e6645a5..d60713cd658c 100644 --- a/drivers/gpu/drm/i915/intel_hdmi.c +++

[Intel-gfx] [PATCH v12 34/38] misc/mei/hdcp: Closing wired HDCP2.2 Tx Session

2019-02-08 Thread Ramalingam C
Request the ME to terminate the HDCP2.2 session for a port. On Success, ME FW will mark the intel port as Deauthenticated and terminate the wired HDCP2.2 Tx session started due to the cmd WIRED_INITIATE_HDCP2_SESSION. v2: Rebased. v3: cldev is passed as first parameter [Tomas] Redundant comme

[Intel-gfx] [PATCH v12 33/38] misc/mei/hdcp: Enabling the HDCP authentication

2019-02-08 Thread Ramalingam C
Request to ME to configure a port as authenticated. On Success, ME FW will mark the port as authenticated and provides HDCP cipher with the encryption keys. Enabling the Authentication can be requested once all stages of HDCP2.2 authentication is completed by interacting with ME FW. Only after t

[Intel-gfx] [PATCH v12 36/38] FOR_TEST_ONLY: i915/Kconfig: Select mei_hdcp by I915

2019-02-08 Thread Ramalingam C
FOR TESTING PURPOSE ONLY. By default INTEL_MEI_HDCP is set to y. This patch is created to test the interface between I915 and MEI_HDCP. Signed-off-by: Ramalingam C --- drivers/misc/mei/Kconfig | 1 + 1 file changed, 1 insertion(+) diff --git a/drivers/misc/mei/Kconfig b/drivers/misc/mei/Kconfi

[Intel-gfx] [PATCH v12 35/38] misc/mei/hdcp: Component framework for I915 Interface

2019-02-08 Thread Ramalingam C
Mei hdcp driver is designed as component slave for the I915 component master. v2: Rebased. v3: Notifier chain is adopted for cldev state update [Tomas] v4: Made static dummy functions as inline in mei_hdcp.h API for polling client device status IS_ENABLED used in header, for config status

[Intel-gfx] [PATCH v12 37/38] FOR_TESTING_ONLY: debugfs: Excluding the LSPCon for HDCP1.4

2019-02-08 Thread Ramalingam C
Just excluding the LSPCon HDMI ports from the HDCP1.4 testing. Signed-off-by: Ramalingam C --- drivers/gpu/drm/i915/i915_debugfs.c | 10 -- 1 file changed, 8 insertions(+), 2 deletions(-) diff --git a/drivers/gpu/drm/i915/i915_debugfs.c b/drivers/gpu/drm/i915/i915_debugfs.c index 20a49

[Intel-gfx] [PATCH v12 15/38] drm/i915: Implement the HDCP2.2 support for DP

2019-02-08 Thread Ramalingam C
Implements the DP adaptation specific HDCP2.2 functions. These functions perform the DPCD read and write for communicating the HDCP2.2 auth message back and forth. v2: wait for cp_irq is merged with this patch. Rebased. v3: wait_queue is used for wait for cp_irq [Chris Wilson] v4: Style fix

[Intel-gfx] [PATCH v12 29/38] misc/mei/hdcp: Verify L_prime

2019-02-08 Thread Ramalingam C
Request to ME to verify the LPrime received from HDCP sink. On Success, ME FW will verify the received Lprime by calculating and comparing with L. This represents the completion of Locality Check. v2: Rebased. v3: cldev is passed as first parameter [Tomas] Redundant comments and cast are rem

[Intel-gfx] [PATCH v12 20/38] mei: bus: export to_mei_cl_device for mei client device drivers

2019-02-08 Thread Ramalingam C
From: Tomas Winkler Export to_mei_cl_device macro, it is needed also in mei client drivers. Signed-off-by: Tomas Winkler --- drivers/misc/mei/bus.c | 1 - include/linux/mei_cl_bus.h | 2 ++ 2 files changed, 2 insertions(+), 1 deletion(-) diff --git a/drivers/misc/mei/bus.c b/drivers/misc/

[Intel-gfx] [PATCH v12 17/38] drm/i915: CP_IRQ handling for DP HDCP2.2 msgs

2019-02-08 Thread Ramalingam C
Implements the Waitqueue is created to wait for CP_IRQ Signaling the CP_IRQ arrival through atomic variable. For applicable DP HDCP2.2 msgs read wait for CP_IRQ. As per HDCP2.2 spec "HDCP Transmitters must process CP_IRQ interrupts when they are received from HDCP Receivers

[Intel-gfx] [PATCH v12 25/38] misc/mei/hdcp: Verify Receiver Cert and prepare km

2019-02-08 Thread Ramalingam C
Requests for verification for receiver certification and also the preparation for next AKE auth message with km. On Success ME FW validate the HDCP2.2 receivers certificate and do the revocation check on the receiver ID. AKE_Stored_Km will be prepared if the receiver is already paired, else AKE_No

[Intel-gfx] [PATCH v12 28/38] misc/mei/hdcp: Initiate Locality check

2019-02-08 Thread Ramalingam C
Requests ME to start the second stage of HDCP2.2 authentication, called Locality Check. On Success, ME FW will provide LC_Init message to send to hdcp sink. v2: Rebased. v3: cldev is passed as first parameter [Tomas] Redundant comments and cast are removed [Tomas] v4: %zd used for ssize_t [

[Intel-gfx] [PATCH v12 24/38] misc/mei/hdcp: Initiate Wired HDCP2.2 Tx Session

2019-02-08 Thread Ramalingam C
Request ME FW to start the HDCP2.2 session for an intel port. Prepares payloads for command WIRED_INITIATE_HDCP2_SESSION and sends to ME FW. On Success, ME FW will start a HDCP2.2 session for the port and provides the content for HDCP2.2 AKE_Init message. v2: Rebased. v3: cldev is add as a sepa

[Intel-gfx] [PATCH v12 26/38] misc/mei/hdcp: Verify H_prime

2019-02-08 Thread Ramalingam C
Requests for the verification of AKE_Send_H_prime. ME will calculate the H and comparing it with received H_Prime. The result will be returned as status. Here AKE_Send_H_prime is a HDCP2.2 Authentication msg. v2: Rebased. v3: cldev is passed as first parameter [Tomas] Redundant comments and

[Intel-gfx] [PATCH v12 22/38] misc/mei/hdcp: Client driver for HDCP application

2019-02-08 Thread Ramalingam C
ME FW contributes a vital role in HDCP2.2 authentication. HDCP2.2 driver needs to communicate to ME FW for each step of the HDCP2.2 authentication. ME FW prepare and HDCP2.2 authentication parameters and encrypt them as per spec. With such parameter Driver prepares HDCP2.2 auth messages and commu

[Intel-gfx] [PATCH v12 16/38] drm/i915: Implement the HDCP2.2 support for HDMI

2019-02-08 Thread Ramalingam C
Implements the HDMI adaptation specific HDCP2.2 operations. Basically these are DDC read and write for authenticating through HDCP2.2 messages. v2: Rebased. v3: No more special handling of Gmbus burst read for AKE_SEND_CERT. Style fixed with few naming. [Uma] %s/PARING/PAIRING v4: msg_sz

[Intel-gfx] [PATCH v12 31/38] misc/mei/hdcp: Repeater topology verification and ack

2019-02-08 Thread Ramalingam C
Request ME to verify the downstream topology information received. ME FW will validate the Repeaters receiver id list and downstream topology. On Success ME FW will provide the Least Significant 128bits of VPrime, which forms the repeater ack. v2: Rebased. v3: cldev is passed as first paramete

[Intel-gfx] [PATCH v12 18/38] drm/i915: Fix KBL HDCP2.2 encrypt status signalling

2019-02-08 Thread Ramalingam C
HDCP transmitter is supposed to indicate the HDCP encryption status of the link through enc_en signals in a window of time called "window of opportunity" defined by HDCP HDMI spec. But on KBL this timing of signalling has an issue. To fix the issue this WA of resetting the signalling is required.

[Intel-gfx] [PATCH v12 21/38] mei: me: add ice lake point device id.

2019-02-08 Thread Ramalingam C
From: Tomas Winkler Add icelake mei device id. Cc: Signed-off-by: Tomas Winkler Signed-off-by: Greg Kroah-Hartman Cherry-picked from git://git.kernel.org/pub/scm/linux/kernel/git/gregkh/char-misc.git char-misc-linus --- drivers/misc/mei/hw-me-regs.h | 2 ++ drivers/misc/mei/pci-me.c |

[Intel-gfx] [PATCH v12 30/38] misc/mei/hdcp: Prepare Session Key

2019-02-08 Thread Ramalingam C
Request to ME to prepare the encrypted session key. On Success, ME provides Encrypted session key. Function populates the HDCP2.2 authentication msg SKE_Send_Eks. v2: Rebased. v3: cldev is passed as first parameter [Tomas] Redundant comments and cast are removed [Tomas] v4: %zd for ssize_t

[Intel-gfx] [PATCH v12 23/38] misc/mei/hdcp: Define ME FW interface for HDCP2.2

2019-02-08 Thread Ramalingam C
Defines the HDCP specific ME FW interfaces such as Request CMDs, payload structure for CMDs and their response status codes. This patch defines payload size(Excluding the Header)for each WIRED HDCP2.2 CMDs. v2: Rebased. v3: Extra comments are removed. v4: %s/\/\*\*/\/\* v5: Extra lines are

[Intel-gfx] [PATCH v12 27/38] misc/mei/hdcp: Store the HDCP Pairing info

2019-02-08 Thread Ramalingam C
Provides Pairing info to ME to store. Pairing is a process to fast track the subsequent authentication with the same HDCP sink. On Success, received HDCP pairing info is stored in non-volatile memory of ME. v2: Rebased. v3: cldev is passed as first parameter [Tomas] Redundant comments and ca

[Intel-gfx] [PATCH v12 19/38] mei: bus: whitelist hdcp client

2019-02-08 Thread Ramalingam C
From: Tomas Winkler Whitelist HDCP client for in kernel drm use v2: Rebased. Signed-off-by: Tomas Winkler --- drivers/misc/mei/bus-fixup.c | 16 1 file changed, 16 insertions(+) diff --git a/drivers/misc/mei/bus-fixup.c b/drivers/misc/mei/bus-fixup.c index 80215c312f0e..5f

[Intel-gfx] [PATCH v12 09/38] drm: helper functions for hdcp2 seq_num to from u32

2019-02-08 Thread Ramalingam C
Library functions for endianness are aligned for 16/32/64 bits. But hdcp sequence numbers are 24bits(big endian). So for their conversion to and from u32 helper functions are developed. v2: Comment is updated. [Daniel] Reviewed-by Uma. Signed-off-by: Ramalingam C Reviewed-by: Daniel Vetter

[Intel-gfx] [PATCH v12 08/38] drm/i915: Implement HDCP2.2 receiver authentication

2019-02-08 Thread Ramalingam C
Implements HDCP2.2 authentication for hdcp2.2 receivers, with following steps: Authentication and Key exchange (AKE). Locality Check (LC). Session Key Exchange(SKE). DP Errata for stream type configuration for receivers. At AKE, the HDCP Receiver’s public key certif

[Intel-gfx] [PATCH v12 14/38] drm: removing the DP Errata msg and its msg id

2019-02-08 Thread Ramalingam C
Since DP ERRATA message is not defined at spec, those structure definition is removed from drm_hdcp.h Signed-off-by: Ramalingam C Suggested-by: Daniel Vetter Reviewed-by: Daniel Vetter Reviewed-by: Uma Shankar --- include/drm/drm_hdcp.h | 6 -- 1 file changed, 6 deletions(-) diff --git a

[Intel-gfx] [PATCH v12 05/38] drm/i915: MEI interface definition

2019-02-08 Thread Ramalingam C
Defining the mei-i915 interface functions and initialization of the interface. v2: Adjust to the new interface changes. [Tomas] Added further debug logs for the failures at MEI i/f. port in hdcp_port data is equipped to handle -ve values. v3: mei comp is matched for global i915 comp master

[Intel-gfx] [PATCH v12 11/38] drm: HDCP2.2 link check period

2019-02-08 Thread Ramalingam C
Time period for HDCP2.2 link check. Signed-off-by: Ramalingam C Reviewed-by: Daniel Vetter Reviewed-by: Uma Shankar --- include/drm/drm_hdcp.h | 1 + 1 file changed, 1 insertion(+) diff --git a/include/drm/drm_hdcp.h b/include/drm/drm_hdcp.h index 7260b31af276..d4e98b11b4aa 100644 --- a/inclu

[Intel-gfx] [PATCH v12 06/38] drm/i915: hdcp1.4 CP_IRQ handling and SW encryption tracking

2019-02-08 Thread Ramalingam C
"hdcp_encrypted" flag is defined to denote the HDCP1.4 encryption status. This SW tracking is used to determine the need for real hdcp1.4 disable and hdcp_check_link upon CP_IRQ. On CP_IRQ we filter the CP_IRQ related to the states like Link failure and reauthentication req etc and handle them in

[Intel-gfx] [PATCH v12 13/38] drm/i915: Handle HDCP2.2 downstream topology change

2019-02-08 Thread Ramalingam C
When repeater notifies a downstream topology change, this patch reauthenticate the repeater alone without disabling the hdcp encryption. If that fails then complete reauthentication is executed. v2: Rebased. v3: Typo in commit msg is fixed [Uma] v4: Rebased as part of patch reordering. Min

[Intel-gfx] [PATCH v12 07/38] drm/i915: Enable and Disable of HDCP2.2

2019-02-08 Thread Ramalingam C
Considering that HDCP2.2 is more secure than HDCP1.4, When a setup supports HDCP2.2 and HDCP1.4, HDCP2.2 will be enabled. When HDCP2.2 enabling fails and HDCP1.4 is supported, HDCP1.4 is enabled. This change implements a sequence of enabling and disabling of HDCP2.2 authentication and HDCP2.2 por

[Intel-gfx] [PATCH v12 12/38] drm/i915: Implement HDCP2.2 link integrity check

2019-02-08 Thread Ramalingam C
Implements the link integrity check once in 500mSec. Once encryption is enabled, an ongoing Link Integrity Check is performed by the HDCP Receiver to check that cipher synchronization is maintained between the HDCP Transmitter and the HDCP Receiver. On the detection of synchronization lost, the H

[Intel-gfx] [PATCH v12 01/38] drm/doc: document recommended component helper usage

2019-02-08 Thread Ramalingam C
From: Daniel Vetter Now that component has docs it's worth spending a few words and hyperlinks on recommended best practices in drm. Cc: Russell King - ARM Linux admin Signed-off-by: Daniel Vetter --- Documentation/driver-api/component.rst | 2 ++ Documentation/gpu/drm-internals.rst| 5

[Intel-gfx] [PATCH v12 10/38] drm/i915: Implement HDCP2.2 repeater authentication

2019-02-08 Thread Ramalingam C
Implements the HDCP2.2 repeaters authentication steps such as verifying the downstream topology and sending stream management information. v2: Rebased. v3: -EINVAL is returned for topology error and rollover scenario. Endianness conversion func from drm_hdcp.h is used [Uma] v4: Rebased as pa

[Intel-gfx] [PATCH v12 02/38] drm/i915: Gathering the HDCP1.4 routines together

2019-02-08 Thread Ramalingam C
All HDCP1.4 routines are gathered together, followed by the generic functions those can be extended for HDCP2.2 too. Signed-off-by: Ramalingam C Acked-by: Daniel Vetter Reviewed-by: Uma Shankar Reviewed-by: Tomas Winkler --- drivers/gpu/drm/i915/intel_hdcp.c | 118 +++-

[Intel-gfx] [PATCH v12 00/38] drm/i915: Implement HDCP2.2

2019-02-08 Thread Ramalingam C
This series enables the HDCP2.2 Type 0 for I915. The sequence for HDCP2.2 authentication and encryption is implemented as a generic flow between HDMI and DP. Encoder specific implementations are moved into hdcp_shim. Intel HWs supports HDCP2.2 through ME FW. Hence this series introduces a client d

[Intel-gfx] [PATCH v12 04/38] drm/i915: Initialize HDCP2.2

2019-02-08 Thread Ramalingam C
Add the HDCP2.2 initialization to the existing HDCP1.4 stack. v2: mei interface handle is protected with mutex. [Chris Wilson] v3: Notifiers are used for the mei interface state. v4: Poll for mei client device state Error msg for out of mem [Uma] Inline req for init function removed [Uma

[Intel-gfx] [PATCH v12 03/38] drm: header for i915 - MEI_HDCP interface

2019-02-08 Thread Ramalingam C
Header defines the interface for the I915 and MEI_HDCP drivers. This interface is specific to the usage of mei_hdcp from gen9+ platforms for ME FW based HDCP2.2 services. And Generic HDCP2.2 protocol specific definitions are added at drm/drm_hdcp.h. v2: Commit msg is enhanced [Daniel] v3: i91

[Intel-gfx] [PATCH v12 01/38] drm/doc: document recommended component helper usage

2019-02-08 Thread Ramalingam C
From: Daniel Vetter Now that component has docs it's worth spending a few words and hyperlinks on recommended best practices in drm. Cc: Russell King - ARM Linux admin Signed-off-by: Daniel Vetter --- Documentation/driver-api/component.rst | 2 ++ Documentation/gpu/drm-internals.rst| 5

[Intel-gfx] [PATCH v12 00/38] drm/i915: Implement HDCP2.2

2019-02-08 Thread Ramalingam C
This series enables the HDCP2.2 Type 0 for I915. The sequence for HDCP2.2 authentication and encryption is implemented as a generic flow between HDMI and DP. Encoder specific implementations are moved into hdcp_shim. Intel HWs supports HDCP2.2 through ME FW. Hence this series introduces a client d

[Intel-gfx] ✓ Fi.CI.IGT: success for drm/i915/execlists: Refactor out can_merge_rq()

2019-02-08 Thread Patchwork
== Series Details == Series: drm/i915/execlists: Refactor out can_merge_rq() URL : https://patchwork.freedesktop.org/series/56440/ State : success == Summary == CI Bug Log - changes from CI_DRM_5571_full -> Patchwork_12185_full Summary

[Intel-gfx] ✓ Fi.CI.IGT: success for Support 64 bpp half float formats (rev6)

2019-02-08 Thread Patchwork
== Series Details == Series: Support 64 bpp half float formats (rev6) URL : https://patchwork.freedesktop.org/series/53212/ State : success == Summary == CI Bug Log - changes from CI_DRM_5570_full -> Patchwork_12184_full Summary ---

[Intel-gfx] ✓ Fi.CI.IGT: success for drm/i915: Dump skl+ watermark changes (rev2)

2019-02-08 Thread Patchwork
== Series Details == Series: drm/i915: Dump skl+ watermark changes (rev2) URL : https://patchwork.freedesktop.org/series/56432/ State : success == Summary == CI Bug Log - changes from CI_DRM_5569_full -> Patchwork_12183_full Summary ---

[Intel-gfx] ✓ Fi.CI.BAT: success for series starting with [1/2] drm/i915/hotplug: Move iteration over connectors to other function

2019-02-08 Thread Patchwork
== Series Details == Series: series starting with [1/2] drm/i915/hotplug: Move iteration over connectors to other function URL : https://patchwork.freedesktop.org/series/56445/ State : success == Summary == CI Bug Log - changes from CI_DRM_5571 -> Patchwork_12186 =

[Intel-gfx] ✗ Fi.CI.CHECKPATCH: warning for series starting with [1/2] drm/i915/hotplug: Move iteration over connectors to other function

2019-02-08 Thread Patchwork
== Series Details == Series: series starting with [1/2] drm/i915/hotplug: Move iteration over connectors to other function URL : https://patchwork.freedesktop.org/series/56445/ State : warning == Summary == $ dim checkpatch origin/drm-tip 657dfb10e498 drm/i915/hotplug: Move iteration over con

[Intel-gfx] [PATCH 1/2] drm/i915/hotplug: Move iteration over connectors to other function

2019-02-08 Thread José Roberto de Souza
The next patch will need to a second iteration over connectors so moving it to a function, no behavior changes intended here. While at it moving intel_connector and intel_encoder to inside of the block that actually uses it. Cc: Imre Deak Signed-off-by: José Roberto de Souza --- drivers/gpu/dr

[Intel-gfx] [PATCH 2/2] drm/i915/icl: Probe again type-c connectors that failed

2019-02-08 Thread José Roberto de Souza
Unpowered type-c dongles can take some time to boot and be responsible, causing the probe to fail and sink never be detected without further actions from userspace. It was not a issue for older platforms because there was a hardware bridge between DDI/DP ports and type-c controller adding a implic

[Intel-gfx] [drm-tip:drm-tip 2/8] drivers/gpu/drm//arm/display/komeda/komeda_kms.c:33:2: error: unknown field 'driver_features' specified in initializer

2019-02-08 Thread kbuild test robot
tree: git://anongit.freedesktop.org/drm/drm-tip drm-tip head: d4794b009ccd1ef8816e15c833f07ab696911a8d commit: bd6ee5d2d2032416ba36ec6c24bf513f4ff0d338 [2/8] Merge remote-tracking branch 'drm-misc/drm-misc-next' into drm-tip config: i386-randconfig-h0-02082357 (attached as .config) compiler: g

[Intel-gfx] ✓ Fi.CI.BAT: success for drm/i915/execlists: Refactor out can_merge_rq()

2019-02-08 Thread Patchwork
== Series Details == Series: drm/i915/execlists: Refactor out can_merge_rq() URL : https://patchwork.freedesktop.org/series/56440/ State : success == Summary == CI Bug Log - changes from CI_DRM_5571 -> Patchwork_12185 Summary --- **S

[Intel-gfx] [CI] drm/i915/execlists: Refactor out can_merge_rq()

2019-02-08 Thread Chris Wilson
In the next patch, we add another user that wants to check whether requests can be merge into a single HW execution, and in the future we want to add more conditions under which requests from the same context cannot be merge. In preparation, extract out can_merge_rq(). v2: Reorder tests to decide

[Intel-gfx] ✓ Fi.CI.IGT: success for series starting with [v3,1/3] drm/i915/opregion: fix version check

2019-02-08 Thread Patchwork
== Series Details == Series: series starting with [v3,1/3] drm/i915/opregion: fix version check URL : https://patchwork.freedesktop.org/series/56429/ State : success == Summary == CI Bug Log - changes from CI_DRM_5568_full -> Patchwork_12181_full ===

[Intel-gfx] ✓ Fi.CI.BAT: success for Support 64 bpp half float formats (rev6)

2019-02-08 Thread Patchwork
== Series Details == Series: Support 64 bpp half float formats (rev6) URL : https://patchwork.freedesktop.org/series/53212/ State : success == Summary == CI Bug Log - changes from CI_DRM_5570 -> Patchwork_12184 Summary --- **SUCCESS*

[Intel-gfx] ✓ Fi.CI.IGT: success for Add Colorspace connector property interface (rev14)

2019-02-08 Thread Patchwork
== Series Details == Series: Add Colorspace connector property interface (rev14) URL : https://patchwork.freedesktop.org/series/47132/ State : success == Summary == CI Bug Log - changes from CI_DRM_5568_full -> Patchwork_12180_full Summary

[Intel-gfx] ✗ Fi.CI.CHECKPATCH: warning for Support 64 bpp half float formats (rev6)

2019-02-08 Thread Patchwork
== Series Details == Series: Support 64 bpp half float formats (rev6) URL : https://patchwork.freedesktop.org/series/53212/ State : warning == Summary == $ dim checkpatch origin/drm-tip adafd20058ef drm/fourcc: Add 64 bpp half float formats -:44: WARNING:LONG_LINE: line over 100 characters #44

Re: [Intel-gfx] linux-next: build failure after merge of the drm-misc tree

2019-02-08 Thread Sam Ravnborg
Hi Daniel/Stephen Thanks for the report and the hints how to move forward to fix it. > Sam, can you pls take a look at what komeda needs? you need to > manually merge together drm-misc-next and drm-next first I think. Merged the two tree and fixed build. Undid the merge and checked that the buil

[Intel-gfx] ✓ Fi.CI.BAT: success for drm/i915: Dump skl+ watermark changes (rev2)

2019-02-08 Thread Patchwork
== Series Details == Series: drm/i915: Dump skl+ watermark changes (rev2) URL : https://patchwork.freedesktop.org/series/56432/ State : success == Summary == CI Bug Log - changes from CI_DRM_5569 -> Patchwork_12183 Summary --- **SUCC

[Intel-gfx] [PATCH v5 3/3] drm/i915/icl: Implement half float formats

2019-02-08 Thread Kevin Strasser
64 bpp half float formats are supported on hdr planes only and are subject to the following restrictions: * 90/270 rotation not supported * Yf Tiling not supported * Frame Buffer Compression not supported * Color Keying not supported v2: - Drop handling pixel normalize register - Don't use

[Intel-gfx] [PATCH v5 2/3] drm/i915: Refactor icl_is_hdr_plane

2019-02-08 Thread Kevin Strasser
Change the api in order to enable callers that can't supply a valid intel_plane pointer, as would be the case prior to calling drm_universal_plane_init. v4: - Rename variables and move a declaration (Ville) Cc: Uma Shankar Cc: Shashank Sharma Cc: Ville Syrjälä Cc: David Airlie Cc: Daniel Vett

[Intel-gfx] [PATCH v5 1/3] drm/fourcc: Add 64 bpp half float formats

2019-02-08 Thread Kevin Strasser
Add 64 bpp 16:16:16:16 half float pixel formats. Each 16 bit component is formatted in IEEE-754 half-precision float (binary16) 1:5:10 MSb-sign:exponent:fraction form. This patch attempts to address the feedback provided when 2 of these formats were previosly proposed: https://patchwork.kernel.o

[Intel-gfx] [PATCH v5 0/3] Support 64 bpp half float formats

2019-02-08 Thread Kevin Strasser
This series defines new formats and adds implementation to the i915 driver. Since posting v1 I have removed the pixel normalize property, as it's not needed for basic functionality. Also, I have been working on adding support to userspace, but we can't land any patches until drm_fourcc.h has been u

Re: [Intel-gfx] [PATCH v3] drm/dsc: Add kernel documentation for DRM DP DSC helpers

2019-02-08 Thread Manasi Navare
Pushed to drm-misc thanks for the reviews. Regards Manasi On Wed, Feb 06, 2019 at 01:31:48PM -0800, Manasi Navare wrote: > This patch adds appropriate kernel documentation for DRM DP helpers > used for enabling Display Stream compression functionality in > drm_dp_helper.h and drm_dp_helper.c as w

[Intel-gfx] ✗ Fi.CI.BAT: failure for drm/i915: Dump skl+ watermark changes

2019-02-08 Thread Patchwork
== Series Details == Series: drm/i915: Dump skl+ watermark changes URL : https://patchwork.freedesktop.org/series/56432/ State : failure == Summary == CI Bug Log - changes from CI_DRM_5569 -> Patchwork_12182 Summary --- **FAILURE**

[Intel-gfx] [PATCH] drm/i915: Dump skl+ watermark changes

2019-02-08 Thread Ville Syrjala
From: Ville Syrjälä Currently we're only dumping out the ddb allocation changes, let's do the same for the watermarks. This should help with debugging underruns and whatnot. First I tried one line per plane per wm level, but that resulted in an obnoxious amount of lines printed. So as a compromi

[Intel-gfx] ✓ Fi.CI.IGT: success for series starting with [CI,1/7] drm/i915: Defer removing fence register tracking to rpm wakeup

2019-02-08 Thread Patchwork
== Series Details == Series: series starting with [CI,1/7] drm/i915: Defer removing fence register tracking to rpm wakeup URL : https://patchwork.freedesktop.org/series/56412/ State : success == Summary == CI Bug Log - changes from CI_DRM_5567_full -> Patchwork_12179_full

Re: [Intel-gfx] [PATCH v3 2/3] drm/i915/opregion: rvda is relative from opregion base in opregion 2.1+

2019-02-08 Thread Ville Syrjälä
On Fri, Feb 08, 2019 at 09:00:59PM +0200, Jani Nikula wrote: > On Fri, 08 Feb 2019, Ville Syrjälä wrote: > > On Fri, Feb 08, 2019 at 08:42:53PM +0200, Jani Nikula wrote: > >> Starting from opregion version 2.1 (roughly corresponding to ICL+) the > >> RVDA field is relative from the beginning of op

[Intel-gfx] ✓ Fi.CI.BAT: success for series starting with [v3,1/3] drm/i915/opregion: fix version check

2019-02-08 Thread Patchwork
== Series Details == Series: series starting with [v3,1/3] drm/i915/opregion: fix version check URL : https://patchwork.freedesktop.org/series/56429/ State : success == Summary == CI Bug Log - changes from CI_DRM_5568 -> Patchwork_12181 Sum

Re: [Intel-gfx] [PATCH v3 2/3] drm/i915/opregion: rvda is relative from opregion base in opregion 2.1+

2019-02-08 Thread Jani Nikula
On Fri, 08 Feb 2019, Ville Syrjälä wrote: > On Fri, Feb 08, 2019 at 08:42:53PM +0200, Jani Nikula wrote: >> Starting from opregion version 2.1 (roughly corresponding to ICL+) the >> RVDA field is relative from the beginning of opregion, not absolute >> address. >> >> Fix the error path while at i

Re: [Intel-gfx] [PATCH v3 2/3] drm/i915/opregion: rvda is relative from opregion base in opregion 2.1+

2019-02-08 Thread Ville Syrjälä
On Fri, Feb 08, 2019 at 08:42:53PM +0200, Jani Nikula wrote: > Starting from opregion version 2.1 (roughly corresponding to ICL+) the > RVDA field is relative from the beginning of opregion, not absolute > address. > > Fix the error path while at it. > > v2: Make relative vs. absolute conditional

Re: [Intel-gfx] [PATCH v4 0/3] Support 64 bpp half float formats

2019-02-08 Thread Strasser, Kevin
Maarten Lankhorst wrote: > It's nice that the igt parts are almost done. I think this might need rebasing > on top of > > I'm glad there are tests, but the internal accuracy of the CAIRO_FORMAT_RGB24 > is only 8 bits, so it wouldn't test this properly. > > Fortunately we will start using CAIRO_FORM

[Intel-gfx] ✗ Fi.CI.CHECKPATCH: warning for series starting with [v3,1/3] drm/i915/opregion: fix version check

2019-02-08 Thread Patchwork
== Series Details == Series: series starting with [v3,1/3] drm/i915/opregion: fix version check URL : https://patchwork.freedesktop.org/series/56429/ State : warning == Summary == $ dim checkpatch origin/drm-tip 1fd6ccae8d76 drm/i915/opregion: fix version check cb64272c9352 drm/i915/opregion:

[Intel-gfx] ✓ Fi.CI.IGT: success for drm/drv: Rework drm_dev_unplug() (was: Remove drm_dev_unplug())

2019-02-08 Thread Patchwork
== Series Details == Series: drm/drv: Rework drm_dev_unplug() (was: Remove drm_dev_unplug()) URL : https://patchwork.freedesktop.org/series/56404/ State : success == Summary == CI Bug Log - changes from CI_DRM_5567_full -> Patchwork_12178_full ==

[Intel-gfx] [PATCH v3 2/3] drm/i915/opregion: rvda is relative from opregion base in opregion 2.1+

2019-02-08 Thread Jani Nikula
Starting from opregion version 2.1 (roughly corresponding to ICL+) the RVDA field is relative from the beginning of opregion, not absolute address. Fix the error path while at it. v2: Make relative vs. absolute conditional on the opregion version, bumped for the purpose. Turned out there are

[Intel-gfx] [PATCH v3 3/3] HACK: drm/i915/opregion: ICL should have opregion 2.1+ and relative rvda

2019-02-08 Thread Jani Nikula
Temporary CI workaround before proper opregion version bump propagates to the machines. v2: Rebase Cc: Ville Syrjälä Cc: Imre Deak Signed-off-by: Jani Nikula --- drivers/gpu/drm/i915/intel_opregion.c | 3 ++- 1 file changed, 2 insertions(+), 1 deletion(-) diff --git a/drivers/gpu/drm/i915/in

[Intel-gfx] [PATCH v3 1/3] drm/i915/opregion: fix version check

2019-02-08 Thread Jani Nikula
The u32 version field encodes major, minor, revision and reserved. We've basically been checking for any non-zero version. Add opregion version logging while at it. v2: Fix the fix of the version check Fixes: 04ebaadb9f2d ("drm/i915/opregion: handle VBT sizes bigger than 6 KB") Cc: Ville Syrjälä

Re: [Intel-gfx] [PATCH v4 1/3] drm/fourcc: Add 64 bpp half float formats

2019-02-08 Thread Strasser, Kevin
Maarten Lankhorst wrote: > Hmmm, from include/drm/drm_fourcc.h > * @depth: > * > * Color depth (number of bits per pixel excluding padding bits), > * valid for a subset of RGB formats only. This is a legacy field, do > * not use in new code and set to 0

[Intel-gfx] ✓ Fi.CI.BAT: success for Add Colorspace connector property interface (rev14)

2019-02-08 Thread Patchwork
== Series Details == Series: Add Colorspace connector property interface (rev14) URL : https://patchwork.freedesktop.org/series/47132/ State : success == Summary == CI Bug Log - changes from CI_DRM_5568 -> Patchwork_12180 Summary ---

Re: [Intel-gfx] [PATCH 1/3] drm/i915/opregion: fix version check

2019-02-08 Thread Jani Nikula
On Fri, 08 Feb 2019, Jani Nikula wrote: > On Fri, 08 Feb 2019, Ville Syrjälä wrote: >> On Fri, Feb 08, 2019 at 05:57:53PM +0200, Ville Syrjälä wrote: >>> On Fri, Feb 08, 2019 at 05:09:51PM +0200, Jani Nikula wrote: >>> > On Fri, 08 Feb 2019, Jani Nikula wrote: >>> > > The u32 version field encod

[Intel-gfx] ✗ Fi.CI.CHECKPATCH: warning for Add Colorspace connector property interface (rev14)

2019-02-08 Thread Patchwork
== Series Details == Series: Add Colorspace connector property interface (rev14) URL : https://patchwork.freedesktop.org/series/47132/ State : warning == Summary == $ dim checkpatch origin/drm-tip 15e6383fc8d1 drm: Add HDMI colorspace property 8efb8eb9d670 drm: Add DP colorspace property 6e307

[Intel-gfx] ✓ Fi.CI.IGT: success for Enable P0xx (planar), Y2xx and Y4xx (packed) pixel formats

2019-02-08 Thread Patchwork
== Series Details == Series: Enable P0xx (planar), Y2xx and Y4xx (packed) pixel formats URL : https://patchwork.freedesktop.org/series/56402/ State : success == Summary == CI Bug Log - changes from CI_DRM_5567_full -> Patchwork_12177_full S

[Intel-gfx] [v15 2/4] drm: Add DP colorspace property

2019-02-08 Thread Uma Shankar
This patch adds a DP colorspace property, enabling userspace to switch to various supported colorspaces. This will help enable BT2020 along with other colorspaces. v2: Addressed Maarten and Ville's review comments. Enhanced the colorspace enum to incorporate both HDMI and DP supported colo

Re: [Intel-gfx] [PATCH 1/3] drm/i915/opregion: fix version check

2019-02-08 Thread Jani Nikula
On Fri, 08 Feb 2019, Ville Syrjälä wrote: > On Fri, Feb 08, 2019 at 05:57:53PM +0200, Ville Syrjälä wrote: >> On Fri, Feb 08, 2019 at 05:09:51PM +0200, Jani Nikula wrote: >> > On Fri, 08 Feb 2019, Jani Nikula wrote: >> > > The u32 version field encodes major version in the high word. We've been >

[Intel-gfx] [v15 4/4] drm/i915: Attach colorspace property and enable modeset

2019-02-08 Thread Uma Shankar
This patch attaches the colorspace connector property to the hdmi connector. Based on colorspace change, modeset will be triggered to switch to new colorspace. Based on colorspace property value create an infoframe with appropriate colorspace. This can be used to send an infoframe packet with prop

[Intel-gfx] [v15 0/4] Add Colorspace connector property interface

2019-02-08 Thread Uma Shankar
This patch series creates a new connector property to program colorspace to sink devices. Modern sink devices support more than 1 type of colorspace like 601, 709, BT2020 etc. This helps to switch based on content type which is to be displayed. The decision lies with compositors as to in which scen

[Intel-gfx] [v15 3/4] drm: Add colorspace info to AVI Infoframe

2019-02-08 Thread Uma Shankar
This adds colorspace information to HDMI AVI infoframe. A helper function is added to program the same. v2: Moved this to drm core instead of i915 driver. v3: Exported the helper function. v4: Added separate HDMI specific macro as per CTA spec. This is separate from user exposed enum values. Thi

[Intel-gfx] [v15 1/4] drm: Add HDMI colorspace property

2019-02-08 Thread Uma Shankar
Create a new connector property to program colorspace to sink devices. Modern sink devices support more than 1 type of colorspace like 601, 709, BT2020 etc. This helps to switch based on content type which is to be displayed. The decision lies with compositors as to in which scenarios, a particular

Re: [Intel-gfx] [PATCH 1/3] drm/i915/opregion: fix version check

2019-02-08 Thread Jani Nikula
On Fri, 08 Feb 2019, Ville Syrjälä wrote: > On Fri, Feb 08, 2019 at 02:43:30PM +0200, Jani Nikula wrote: >> The u32 version field encodes major version in the high word. We've been >> checking for version >= 0.2. >> >> Add opregion version logging while at it. >> >> Fixes: 04ebaadb9f2d ("drm/i91

Re: [Intel-gfx] Fixes that failed to apply to v5.0-rc5

2019-02-08 Thread Rodrigo Vivi
On Fri, Feb 08, 2019 at 05:07:52AM -0800, Aditya Swarup wrote: > On Tue, Feb 05, 2019 at 03:42:05PM +0200, Jani Nikula wrote: > > > > The following commits have been marked as Cc: stable or fixing something > > in v5.0-rc5 or earlier, but failed to cherry-pick to > > drm-intel-fixes. Please see if

Re: [Intel-gfx] [PATCH -fixes] drm/i915: Try to sanitize bogus DPLL state left over by broken SNB BIOSen

2019-02-08 Thread Sasha Levin
Hi, [This is an automated email] This commit has been processed because it contains a "Fixes:" tag, fixing commit: 516a49cc1946 drm/i915: Fix assert_plane() warning on bootup with external display. The bot has tested the following trees: v4.20.6. v4.20.6: Failed to apply! Possible dependencies

Re: [Intel-gfx] [PATCH 1/2] drm/i915: Prevent a race during I915_GEM_MMAP ioctl with WC set

2019-02-08 Thread Adam Zabrocki
Thanks for the patch for both issues! Best regards, Adam -Original Message- From: Joonas Lahtinen Sent: Thursday, February 7, 2019 5:39 AM To: Intel graphics driver community testing & development Cc: sta...@vger.kernel.org; Akash Goel ; Chris Wilson ; Tvrtko Ursulin ; Adam Zabrocki

Re: [Intel-gfx] [PATCH 1/7] drm: Add P010, P012, P016 format definitions and fourcc

2019-02-08 Thread Daniel Vetter
On Fri, Feb 8, 2019 at 2:51 PM wrote: > > From: Juha-Pekka Heikkila > > Add P010 definition, semi-planar yuv format where each component > is 16 bits 10 msb containing color value. First come Y plane [10:6] > followed by 2x2 subsampled Cr:Cb plane [10:6:10:6] > > Add P012 definition, semi-planar

[Intel-gfx] ✓ Fi.CI.IGT: success for drm/i915: Protect i915_active iterators from the shrinker

2019-02-08 Thread Patchwork
== Series Details == Series: drm/i915: Protect i915_active iterators from the shrinker URL : https://patchwork.freedesktop.org/series/56401/ State : success == Summary == CI Bug Log - changes from CI_DRM_5567_full -> Patchwork_12176_full Su

[Intel-gfx] [PULL] drm-intel-next

2019-02-08 Thread Rodrigo Vivi
Hi Dave and Daniel, This is the last batch from us targeting 5.1 Here goes drm-intel-next-2019-02-07: UAPI Changes: - Expose RPCS (SSEU) configuration to userspace for Ice Lake in order to allow userspace to reconfigure the subslice config per context basis. (Tvrtko, Lionel) Driver Changes: -

Re: [Intel-gfx] [PATCH i-g-t v4 5/5] tests/pm_dc: Added test for DC6 during DPMS

2019-02-08 Thread Anshuman Gupta
On Fri, Feb 08, 2019 at 04:53:18PM +0200, Imre Deak wrote: > On Fri, Feb 01, 2019 at 09:43:02PM +0530, Anshuman Gupta wrote: > > From: Jyoti Yadav > > > > Added new subtest for DC6 entry during DPMS on/off cycle. > > During DPMS on/off cycle DC6 counter is incremented. > > > > v2: Renamed the su

[Intel-gfx] ✓ Fi.CI.BAT: success for series starting with [CI,1/7] drm/i915: Defer removing fence register tracking to rpm wakeup

2019-02-08 Thread Patchwork
== Series Details == Series: series starting with [CI,1/7] drm/i915: Defer removing fence register tracking to rpm wakeup URL : https://patchwork.freedesktop.org/series/56412/ State : success == Summary == CI Bug Log - changes from CI_DRM_5567 -> Patchwork_12179 ==

Re: [Intel-gfx] [v11 1/4] drm: Add HDMI colorspace property

2019-02-08 Thread Shankar, Uma
>-Original Message- >From: Ville Syrjälä [mailto:ville.syrj...@linux.intel.com] >Sent: Friday, February 8, 2019 9:06 PM >To: Shankar, Uma >Cc: Sharma, Shashank ; intel- >g...@lists.freedesktop.org; Syrjala, Ville ; dri- >de...@lists.freedesktop.org; Lankhorst, Maarten >Subject: Re: [Int

Re: [Intel-gfx] [PATCH i-g-t v4 2/5] tests/pm_dc: Added new test to verify Display C States

2019-02-08 Thread Anshuman Gupta
On Fri, Feb 08, 2019 at 04:49:31PM +0200, Imre Deak wrote: > On Fri, Feb 01, 2019 at 09:42:59PM +0530, Anshuman Gupta wrote: > > From: Jyoti Yadav > > > > Currently this test validates DC5 upon PSR entry for supported platforms. > > Added new file for compilation inside Makefile and Meson. > > >

  1   2   3   >