Regards
Shashank
On 7/12/2017 10:47 PM, Ville Syrjälä wrote:
On Mon, Jul 10, 2017 at 04:48:39PM +0530, Shashank Sharma wrote:
To get a YCBCR420 output from intel platforms, we need one
scaler to scale down YCBCR444 samples to YCBCR420 samples.
This patch:
- Does scaler allocation for HDMI yc
Regards
Shashank
On 7/12/2017 10:47 PM, Ville Syrjälä wrote:
On Mon, Jul 10, 2017 at 04:48:38PM +0530, Shashank Sharma wrote:
This patch checks encoder level support for YCBCR420 outputs.
The logic goes as simple as this:
If the input mode is YCBCR420-only mode: prepare HDMI for
YCBCR420 outp
Regards
Shashank
On 7/12/2017 10:47 PM, Ville Syrjälä wrote:
On Mon, Jul 10, 2017 at 04:48:37PM +0530, Shashank Sharma wrote:
This patch adds helper functions for YCBCR 420 handling.
These functions do:
- check if a given video mode is YCBCR 420 only mode.
- check if a given video mode is YCB
Regards
Shashank
On 7/12/2017 10:48 PM, Ville Syrjälä wrote:
On Mon, Jul 10, 2017 at 04:48:34PM +0530, Shashank Sharma wrote:
YCBCR420 modes are supported only on HDMI 2.0 capable sources.
This patch adds:
- A drm helper to validate YCBCR420-only mode on a particular
connector. This functi
Regards
Shashank
On 7/12/2017 10:48 PM, Ville Syrjälä wrote:
On Mon, Jul 10, 2017 at 04:48:35PM +0530, Shashank Sharma wrote:
CEA-861-F spec adds ycbcr420 deep color support information
in hf-vsdb block. This patch extends the existing hf-vsdb parsing
function by adding parsing of ycbcr420 de
Regards
Shashank
On 7/12/2017 10:48 PM, Ville Syrjälä wrote:
On Mon, Jul 10, 2017 at 04:48:30PM +0530, Shashank Sharma wrote:
CEA-861-F specs defines new video modes to be used with
HDMI 2.0 EDIDs. The VIC range has been extended from 1-64 to
1-107.
Our existing CEA modedb contains only 64 m
Regards
Shashank
On 7/12/2017 10:54 PM, Ville Syrjälä wrote:
On Mon, Jul 10, 2017 at 04:48:48PM +0530, Shashank Sharma wrote:
LSPCON chips can't pick the HDMI AVI infoframes from direct link.
In order to pass AVI infoframes from display controller to LSPCON,
we have to write infoframe packets
On Wed, Jul 12, 2017 at 11:44 PM, Felix Kuehling wrote:
>
> --- a/drivers/gpu/drm/drm_prime.c
> +++ b/drivers/gpu/drm/drm_prime.c
> @@ -634,16 +634,14 @@ struct drm_gem_object *drm_gem_prime_import(struct
> drm_device *dev,
> struct drm_gem_object *obj;
> int ret;
>
> - if (
On Wed, Jul 12, 2017 at 9:10 PM, Sean Paul wrote:
>> > Why all these intermediate steps and different failure modes? Either hdcp
>> > works, or it doesnt (and we can split up with the type 0 or type 1 if
>> > needed), but I don't know what userspace would do with all the other
>> > stuff?
>> enum
On Thursday 13 July 2017 12:40 AM, Sean Paul wrote:
On Wed, Jul 12, 2017 at 08:26:02PM +0530, Ramalingam C wrote:
Daniel,
Thank you for reviewing the patch in short time. My views are below.
On Wednesday 12 July 2017 03:24 PM, Daniel Vetter wrote:
On Wed, Jul 12, 2017 at 01:58:45PM +0530,
On Thursday 13 July 2017 11:39 AM, Daniel Vetter wrote:
On Wed, Jul 12, 2017 at 9:10 PM, Sean Paul wrote:
Why all these intermediate steps and different failure modes? Either hdcp
works, or it doesnt (and we can split up with the type 0 or type 1 if
needed), but I don't know what userspace wo
201 - 211 of 211 matches
Mail list logo