Regards
Shashank
On 11/17/2017 6:19 PM, Ville Syrjälä wrote:
On Fri, Nov 17, 2017 at 05:50:11PM +0530, Sharma, Shashank wrote:
Regards
Shashank
On 11/17/2017 5:05 PM, Ville Syrjälä wrote:
On Fri, Nov 17, 2017 at 08:49:49AM +0530, Sharma, Shashank wrote:
Regards
Shashank
On 11/16/2017
Regards
Shashank
On 11/17/2017 5:08 PM, Ville Syrjälä wrote:
On Fri, Nov 17, 2017 at 08:53:54AM +0530, Sharma, Shashank wrote:
Regards
Shashank
On 11/16/2017 9:56 PM, Ville Syrjälä wrote:
On Thu, Nov 16, 2017 at 08:31:36PM +0530, Sharma, Shashank wrote:
Regards
Shashank
On 11/13/2017
Regards
Shashank
On 11/17/2017 5:05 PM, Ville Syrjälä wrote:
On Fri, Nov 17, 2017 at 08:49:49AM +0530, Sharma, Shashank wrote:
Regards
Shashank
On 11/16/2017 9:53 PM, Ville Syrjälä wrote:
On Thu, Nov 16, 2017 at 08:21:44PM +0530, Sharma, Shashank wrote:
Regards
Shashank
On 11/13/2017
Regards
Shashank
On 11/16/2017 9:56 PM, Ville Syrjälä wrote:
On Thu, Nov 16, 2017 at 08:31:36PM +0530, Sharma, Shashank wrote:
Regards
Shashank
On 11/13/2017 10:34 PM, Ville Syrjala wrote:
From: Ville Syrjälä <ville.syrj...@linux.intel.com>
If the user mode would specify an aspect
Regards
Shashank
On 11/16/2017 9:53 PM, Ville Syrjälä wrote:
On Thu, Nov 16, 2017 at 08:21:44PM +0530, Sharma, Shashank wrote:
Regards
Shashank
On 11/13/2017 10:34 PM, Ville Syrjala wrote:
From: Ville Syrjälä <ville.syrj...@linux.intel.com>
commit 6dffd431e229 ("drm: Add a
Regards
Shashank
On 11/16/2017 9:51 PM, Ville Syrjälä wrote:
On Thu, Nov 16, 2017 at 08:10:55PM +0530, Sharma, Shashank wrote:
Regards
Shashank
On 11/13/2017 10:34 PM, Ville Syrjala wrote:
From: Ville Syrjälä <ville.syrj...@linux.intel.com>
Appedix F of HDMI 2.0 says that some HDM
Regards
Shashank
On 11/16/2017 9:46 PM, Ville Syrjälä wrote:
On Thu, Nov 16, 2017 at 08:06:18PM +0530, Sharma, Shashank wrote:
Regards
Shashank
On 11/13/2017 10:34 PM, Ville Syrjala wrote:
From: Ville Syrjälä <ville.syrj...@linux.intel.com>
HDMI 2.0 Appendix F suggest that we
Regards
Shashank
On 11/13/2017 10:34 PM, Ville Syrjala wrote:
From: Ville Syrjälä
If the user mode would specify an aspect ratio other than 4:3 or 16:9
we now silently ignore it. Maybe a better apporoach is to return an
error? Let's try that.
Also we must be
Regards
Shashank
On 11/13/2017 10:34 PM, Ville Syrjala wrote:
From: Ville Syrjälä
commit 6dffd431e229 ("drm: Add aspect ratio parsing in DRM layer")
cause us to not send out any VICs in the AVI infoframes. That commit
was since reverted, but if and when we add
Regards
Shashank
On 11/13/2017 10:34 PM, Ville Syrjala wrote:
From: Ville Syrjälä
Appedix F of HDMI 2.0 says that some HDMI sink may fail to switch from
3D to 2D mode in a timely fashion if the source simply stops sending the
HDMI infoframe. The suggested
Regards
Shashank
On 11/13/2017 10:34 PM, Ville Syrjala wrote:
From: Ville Syrjälä
HDMI 2.0 Appendix F suggest that we should keep sending the infoframe
when switching from 3D to 2D mode, even if the infoframe isn't strictly
necessary (ie. not needed to
Reviewed-by: Shashank Sharma
Regards
Shashank
On 9/1/2017 8:14 PM, Thierry Reding wrote:
From: Thierry Reding
The file uses inconsistent capitalization for TMDS. Since it is an
abbreviation, all uppercase is correct.
Signed-off-by: Thierry
Regards
Shashank
On 9/1/2017 8:14 PM, Thierry Reding wrote:
From: Thierry Reding
The error messages generated by the SCDC helpers are somewhat
inconsistent with other DRM errors and even with other errors in the
same file. Fix them all up to use a common format.
Regards
Shashank
On 9/1/2017 8:14 PM, Thierry Reding wrote:
From: Thierry Reding
It's unusual to separate kerneldoc comments from the functions that they
describe by a blank line. Remove them.
Signed-off-by: Thierry Reding
---
Reviewed-by: Shashank Sharma
Regards
Shashank
-Original Message-
From: dri-devel [mailto:dri-devel-boun...@lists.freedesktop.org] On Behalf Of
Sean Paul
Sent: Thursday, July 20, 2017 11:18 PM
To: dri-devel@lists.freedesktop.org
Cc: Vetter, Daniel
Thanks for adding this fix , Sean, and sorry about missing this
alignment in doc.
Regards
Shashank
On 7/24/2017 9:01 PM, Sharma, Shashank wrote:
-Original Message-
From: dri-devel [mailto:dri-devel-boun...@lists.freedesktop.org] On Behalf Of
Sean Paul
Sent: Friday, July 21, 2017 1:39
Regards
Shashank
On 7/15/2017 12:32 AM, Ville Syrjälä wrote:
On Thu, Jul 13, 2017 at 09:03:06PM +0530, Shashank Sharma wrote:
Following YCBCR 4:4:4 and 4:2:2, YCBCR 4:2:0 is a new output format,
which is currently supported on HDMI 2.0 sources/sinks. Due to lower
chroma sub-sampling rate,
Regards
Shashank
On 7/15/2017 12:06 AM, Ville Syrjälä wrote:
On Thu, Jul 13, 2017 at 09:03:18PM +0530, Shashank Sharma wrote:
To support ycbcr output, we need a pipe CSC block to do
RGB->YCBCR conversion.
Current Intel platforms have only one pipe CSC unit, so
we can either do color
Regards
Shashank
On 7/15/2017 12:03 AM, Ville Syrjälä wrote:
On Thu, Jul 13, 2017 at 09:03:17PM +0530, Shashank Sharma wrote:
To get HDMI YCBCR420 output, the PIPEMISC register should be
programmed to:
- Generate YCBCR output (bit 11)
- In case of YCBCR420 outputs, it should be programmed in
Regards
Shahank
On 7/15/2017 12:00 AM, Ville Syrjälä wrote:
On Thu, Jul 13, 2017 at 09:03:16PM +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
Regards
Shashank
On 7/15/2017 12:00 AM, Ville Syrjälä wrote:
On Thu, Jul 13, 2017 at 09:03:15PM +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
Regards
Shashank
On 7/13/2017 9:51 PM, Ville Syrjälä wrote:
On Thu, Jul 13, 2017 at 09:03:12PM +0530, Shashank Sharma wrote:
HDMI 2.0 spec adds support for YCBCR420 sub-sampled output.
CEA-861-F adds two new blocks in EDID's CEA extension blocks,
to provide information about sink's YCBCR420
On 7/13/2017 7:40 PM, Ville Syrjälä wrote:
What I mean is
for_each() {
...
+ if (420) {
+ if (!420_dc)
+ return false;
+ } else {
if (!444_dc)
return false;
+ }
}
Got it, Thanks !
On 7/13/2017 6:56 PM, Ville Syrjälä wrote:
We don't want breaks in the loop. It's meant to go through all the
connectors for the crtc. Granted on modern platforms there can only be
one, but IMO assuming that just makes the whole thing look confusing.
It's much clearer IMO if we do
if (420) {
On 7/13/2017 6:49 PM, Ville Syrjälä wrote:
Yeah something like this perhaps:
"We send 4:4:4 data to LSPCON which performs the 4:4:4->4:2:0
downsampling or us, hence we don't need a pipe scaler."
Seems good ! Will add this.
- Shashank
___
dri-devel
On 7/13/2017 6:43 PM, Ville Syrjälä wrote:
We don't use those clocks with DP. You've just added them here because
the function call requires them as parameters.
Also the function call is actually doing the wrong thing for DP
by halving port_clock.
Ah, missed that part. Thanks for letting me
On 7/13/2017 6:33 PM, Ville Syrjälä wrote:
If the mode requires pixel repeat to meet the minimum clock requirement,
then we can't just not do pixel repeat. That would violate the spec in
other ways, and IIRC we couldn't even generate a low enough clock for
it.
The YCBCR420 modes I am seeing on
On 7/13/2017 6:30 PM, Ville Syrjälä wrote:
I guess then you just need to add the bitmap already in the validation
patch.
An alternative would be just squash the patches, but that seems a bit
drastic, and probably would mix up too many things in one patch.
Ok then, I will introduce this bitmap
Regards
Shashank
On 7/13/2017 6:25 PM, Ville Syrjälä wrote:
On Thu, Jul 13, 2017 at 06:09:53PM +0530, Sharma, Shashank wrote:
Regards
Shashank
On 7/13/2017 5:57 PM, Ville Syrjälä wrote:
On Thu, Jul 13, 2017 at 11:11:53AM +0530, Sharma, Shashank wrote:
Regards
Shashank
On 7/12/2017 10
Regards
Shashank
On 7/13/2017 6:23 PM, Ville Syrjälä wrote:
On Thu, Jul 13, 2017 at 10:56:06AM +0530, Sharma, Shashank wrote:
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
Regards
Shashank
On 7/13/2017 6:22 PM, Ville Syrjälä wrote:
On Thu, Jul 13, 2017 at 10:51:04AM +0530, Sharma, Shashank wrote:
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
Regards
Shashank
On 7/13/2017 6:20 PM, Ville Syrjälä wrote:
On Thu, Jul 13, 2017 at 10:44:51AM +0530, Sharma, Shashank wrote:
Regards
Shashank
On 7/12/2017 10:47 PM, Ville Syrjälä wrote:
On Mon, Jul 10, 2017 at 04:48:41PM +0530, Shashank Sharma wrote:
To support ycbcr output, we need
Regards
Shashank
On 7/13/2017 6:07 PM, Ville Syrjälä wrote:
On Thu, Jul 13, 2017 at 10:34:26AM +0530, Sharma, Shashank wrote:
Regads
Shashank
On 7/12/2017 10:45 PM, Ville Syrjälä wrote:
On Mon, Jul 10, 2017 at 04:48:44PM +0530, Shashank Sharma wrote:
This patch adds a helper function
Regards
Shashank
On 7/13/2017 6:05 PM, Ville Syrjälä wrote:
On Thu, Jul 13, 2017 at 10:37:53AM +0530, Sharma, Shashank wrote:
Regards
Shashank
On 7/12/2017 10:47 PM, Ville Syrjälä wrote:
On Mon, Jul 10, 2017 at 04:48:36PM +0530, Shashank Sharma wrote:
A source must set output colorspace
Regards
Shashank
On 7/13/2017 6:01 PM, Ville Syrjälä wrote:
On Thu, Jul 13, 2017 at 11:02:18AM +0530, Sharma, Shashank wrote:
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
Regards
Shashank
On 7/13/2017 5:57 PM, Ville Syrjälä wrote:
On Thu, Jul 13, 2017 at 11:11:53AM +0530, Sharma, Shashank wrote:
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
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
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
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
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
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
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
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
Regards
Shashank
On 7/12/2017 10:47 PM, Ville Syrjälä wrote:
On Mon, Jul 10, 2017 at 04:48:41PM +0530, Shashank Sharma wrote:
To support ycbcr output, we need a pipe CSC block to do
RGB->YCBCR conversion.
Current Intel platforms have only one pipe CSC unit, so
we can either do color
Regards
Shashank
On 7/12/2017 10:47 PM, Ville Syrjälä wrote:
On Mon, Jul 10, 2017 at 04:48:36PM +0530, Shashank Sharma wrote:
A source must set output colorspace information in AVI
infoframes, so that the sink can decode upcoming frames
accordingly.
This patch adds a function to add the
Regads
Shashank
On 7/12/2017 10:45 PM, Ville Syrjälä wrote:
On Mon, Jul 10, 2017 at 04:48:44PM +0530, Shashank Sharma wrote:
This patch adds a helper function in DP dual mode layer to
read the vendor's IEEE OUI signature from a Dual mode adapter.
This will be used to differentiate between
Regards
Shashank
On 7/12/2017 10:45 PM, Ville Syrjälä wrote:
On Mon, Jul 10, 2017 at 04:48:46PM +0530, Shashank Sharma wrote:
LSPCON chips support YCBCR420 outputs. To be able to get
YCBCR420 output from LSPCON chip, the source should:
- Generate YCBCR444 HDMI output
- Set AVI infoframes for
Thanks for the review, Ville.
My comments, inline.
Regards
Shashank
On 7/12/2017 10:45 PM, Ville Syrjälä wrote:
On Mon, Jul 10, 2017 at 04:48:47PM +0530, Shashank Sharma wrote:
We have an existing function to prepare AVI infoframes for HDMI,
this patch moves that function from HDMI layer, to
Regards
Shashank
On 7/5/2017 3:46 PM, Ville Syrjälä wrote:
On Wed, Jul 05, 2017 at 08:48:40AM +0530, Sharma, Shashank wrote:
Regards
Shashank
On 7/4/2017 9:26 PM, Ville Syrjälä wrote:
On Tue, Jul 04, 2017 at 07:41:51PM +0530, Shashank Sharma wrote:
YCBCR420 modes are supported only
Regards
Shashank
On 7/5/2017 12:01 PM, Daniel Vetter wrote:
On Wed, Jul 05, 2017 at 11:39:30AM +0530, Sharma, Shashank wrote:
Regards
Shashank
On 7/4/2017 9:06 PM, Daniel Vetter wrote:
On Tue, Jul 04, 2017 at 07:41:56PM +0530, Shashank Sharma wrote:
HDMI displays can support various
Regards
Shashank
On 7/4/2017 9:06 PM, Daniel Vetter wrote:
On Tue, Jul 04, 2017 at 07:41:56PM +0530, Shashank Sharma wrote:
HDMI displays can support various output types, based on
the color space and subsampling type. The possible
outputs from a HDMI 2.0 monitor could be:
- RGB
- YCBCR
Regards
Shashank
On 7/4/2017 9:26 PM, Ville Syrjälä wrote:
On Tue, Jul 04, 2017 at 07:41:51PM +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 function will
Regards
Shashank
On 7/4/2017 9:25 PM, Ville Syrjälä wrote:
On Tue, Jul 04, 2017 at 07:41:49PM +0530, Shashank Sharma wrote:
This patch adds a bool variable (ycbcr_420_allowed) in the drm connector
structure. While handling the EDID from HDMI 2.0 sinks, its important to
know if the source is
Regards
Shashank
On 7/3/2017 9:14 PM, David Weinehall wrote:
On Mon, Jul 03, 2017 at 08:41:53PM +0530, Shashank Sharma wrote:
CEA-861-F introduces extended tag codes for EDID extension blocks,
which indicates the actual type of the data block. The code for
using exteded tag is 0x7, whereas
Please ignore this version, sent premature. Actual one on the way.
-Original Message-
From: Sharma, Shashank
Sent: Monday, July 3, 2017 8:39 PM
To: dri-devel@lists.freedesktop.org; intel-...@lists.freedesktop.org
Cc: Sharma, Shashank <shashank.sha...@intel.com>; Ville S
Regards
Shashank
On 7/3/2017 3:27 PM, Ville Syrjälä wrote:
On Mon, Jul 03, 2017 at 02:36:58PM +0530, Sharma, Shashank wrote:
Regards
Shashank
On 6/30/2017 5:24 PM, Ville Syrjälä wrote:
On Wed, Jun 21, 2017 at 04:03:59PM +0530, Shashank Sharma wrote:
HDMI 1.4b support the CEA video modes
Regards
Shashank
On 6/30/2017 5:24 PM, Ville Syrjälä wrote:
On Wed, Jun 21, 2017 at 04:03:59PM +0530, Shashank Sharma wrote:
HDMI 1.4b support the CEA video modes as per range of CEA-861-D (VIC 1-64).
For any other mode, the VIC filed in AVI infoframes should be 0.
HDMI 2.0 sinks, support
Regards
Shashank
On 6/30/2017 7:45 PM, Ander Conselvan De Oliveira wrote:
On Fri, 2017-06-30 at 17:29 +0530, Sharma, Shashank wrote:
Regards
Shashank
On 6/30/2017 5:04 PM, Ander Conselvan De Oliveira wrote:
On Fri, 2017-06-30 at 11:20 +0530, Sharma, Shashank wrote:
Regards
Shashank
Regards
Shashank
On 6/30/2017 5:37 PM, Ander Conselvan De Oliveira wrote:
On Wed, 2017-06-21 at 16:04 +0530, Shashank Sharma wrote:
This patch sets the is_hdmi2_src identifier in drm connector
for GLK platform. GLK contains a native HDMI 2.0 controller.
This identifier will help the EDID
Regards
Shashank
On 6/30/2017 5:28 PM, Ville Syrjälä wrote:
On Fri, Jun 30, 2017 at 10:47:48AM +0530, Sharma, Shashank wrote:
Regards
Shashank
On 6/27/2017 5:22 PM, Ville Syrjälä wrote:
On Wed, Jun 21, 2017 at 04:04:02PM +0530, Shashank Sharma wrote:
HDMI 2.0 spec adds support
Regards
Shashank
On 6/30/2017 5:16 PM, Ville Syrjälä wrote:
On Fri, Jun 30, 2017 at 10:52:54AM +0530, Sharma, Shashank wrote:
Regards
Shashank
On 6/27/2017 5:25 PM, Ville Syrjälä wrote:
On Wed, Jun 21, 2017 at 04:04:04PM +0530, Shashank Sharma wrote:
CEA-861-F adds ycbcr capability map
Regards
Shashank
On 6/30/2017 5:04 PM, Ander Conselvan De Oliveira wrote:
On Fri, 2017-06-30 at 11:20 +0530, Sharma, Shashank wrote:
Regards
Shashank
On 6/27/2017 5:46 PM, Ander Conselvan De Oliveira wrote:
On Wed, 2017-06-21 at 16:04 +0530, Shashank Sharma wrote:
To get a YCBCR420
Regards
Shashank
On 6/29/2017 5:38 PM, Ander Conselvan De Oliveira wrote:
On Wed, 2017-06-21 at 16:04 +0530, Shashank Sharma wrote:
To support ycbcr HDMI output, we need a pipe CSC block to
do the RGB->YCBCR conversion, as the blender output is in RGB.
Current Intel platforms have only one
Regards
Shashank
On 6/27/2017 5:46 PM, Ander Conselvan De Oliveira wrote:
On Wed, 2017-06-21 at 16:04 +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
Regards
Shashank
On 6/27/2017 5:44 PM, Ville Syrjälä wrote:
On Wed, Jun 21, 2017 at 04:04:13PM +0530, Shashank Sharma wrote:
HDMI displays can support various output types, based on
the color space and subsampling type. The possible
outputs from a HDMI 2.0 monitor could be:
- RGB
- YCBCR
Regards
Shashank
On 6/27/2017 5:25 PM, Ville Syrjälä wrote:
On Wed, Jun 21, 2017 at 04:04:04PM +0530, Shashank Sharma wrote:
CEA-861-F adds ycbcr capability map block, for HDMI 2.0 sinks.
This block contains a map of indexes of CEA modes, which can
support YCBCR 420 output also. To avoid
Regards
Shashank
On 6/27/2017 5:23 PM, Ville Syrjälä wrote:
On Wed, Jun 21, 2017 at 04:04:03PM +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
Regards
Shashank
On 6/27/2017 5:22 PM, Ville Syrjälä wrote:
On Wed, Jun 21, 2017 at 04:04:02PM +0530, Shashank Sharma wrote:
HDMI 2.0 spec adds support for YCBCR420 sub-sampled output.
CEA-861-F adds two new blocks in EDID's CEA extension blocks,
to provide information about sink's YCBCR420
Regards
Shashank
On 6/27/2017 5:02 PM, Ville Syrjälä wrote:
On Wed, Jun 21, 2017 at 04:04:01PM +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
Regards
Shashank
On 6/23/2017 2:50 PM, Daniel Vetter wrote:
On Thu, Jun 22, 2017 at 10:33 AM, Sharma, Shashank
<shashank.sha...@intel.com> wrote:
- The property values should be limited to what the driver can support, I
guess that would mean limiting the available ycbcr modes? O
Regards
Shashank
On 6/23/2017 2:42 PM, Daniel Vetter wrote:
On Thu, Jun 22, 2017 at 11:42 AM, Sharma, Shashank
<shashank.sha...@intel.com> wrote:
You should explain in 1-2 sentences what exactly this function does, and
when a driver should use it. Just documenting the input/output
Regards
Shashank
On 6/22/2017 12:35 PM, Daniel Vetter wrote:
On Wed, Jun 21, 2017 at 04:04:06PM +0530, Shashank Sharma wrote:
This patch adds set of helper functions for YCBCR HDMI output
handling. These functions provide functionality like:
- check if a given video mode is YCBCR 420 only
Thanks for the review, Daniel.
My comments inline.
Regards
Shashank
On 6/22/2017 12:44 PM, Daniel Vetter wrote:
On Wed, Jun 21, 2017 at 04:04:13PM +0530, Shashank Sharma wrote:
HDMI displays can support various output types, based on
the color space and subsampling type. The possible
outputs
Regards
Shashank
On 6/20/2017 7:50 PM, Ander Conselvan De Oliveira wrote:
On Mon, 2017-06-19 at 21:38 +0530, Shashank Sharma wrote:
This patch checks encoder level support for HDMI YCBCR outputs.
HDMI output mode is a connector property, this patch checks if
source and sink can support the
typing these
examples :-).
Ok then, I will add a flag which sounds more like ycbcr_420_supported or
so.
Regards
Shashank
On 6/15/2017 10:29 PM, Ville Syrjälä wrote:
On Thu, Jun 15, 2017 at 10:18:40PM +0530, Sharma, Shashank wrote:
Regards
Shashank
On 6/15/2017 9:42 PM, Ville Syrjälä wrote
Regards
Shashank
On 6/15/2017 9:42 PM, Ville Syrjälä wrote:
On Thu, Jun 15, 2017 at 09:05:10PM +0530, Sharma, Shashank wrote:
Regards
Shashank
On 6/15/2017 8:13 PM, Ville Syrjälä wrote:
On Wed, Jun 14, 2017 at 11:17:35PM +0530, Shashank Sharma wrote:
HDMI 2.0 spec adds support
Regards
Shashank
On 6/15/2017 8:13 PM, Ville Syrjälä wrote:
On Wed, Jun 14, 2017 at 11:17:35PM +0530, Shashank Sharma wrote:
HDMI 2.0 spec adds support for YCBCR420 sub-sampled output.
CEA-861-F adds two new blocks in EDID's CEA extension blocks,
to provide information about sink's YCBCR420
Regards
Shashank
On 6/15/2017 6:59 PM, Ville Syrjälä wrote:
On Wed, Jun 14, 2017 at 11:17:33PM +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
Hello Thierry,
Thanks for the comments.
In fact, that was the plan earlier, but the problem is, this function is
being called from several drivers, and not all of them have
the drm_connector readily available with their caller function. For few
drivers, I might have to go up two to three
Regards
Shashank
On 5/31/2017 6:11 PM, Ville Syrjälä wrote:
On Tue, May 30, 2017 at 10:00:12PM +0530, Sharma, Shashank wrote:
Regards
Shashank
On 5/30/2017 9:43 PM, Ville Syrjälä wrote:
On Tue, May 30, 2017 at 05:43:40PM +0530, Shashank Sharma wrote:
HDMI 1.4b support the CEA video
Regards
Shashank
On 5/31/2017 6:09 PM, Ville Syrjälä wrote:
On Tue, May 30, 2017 at 09:56:56PM +0530, Sharma, Shashank wrote:
Regards
Shashank
On 5/30/2017 9:48 PM, Ville Syrjälä wrote:
On Tue, May 30, 2017 at 05:43:41PM +0530, Shashank Sharma wrote:
CEA-861-F specs defines new video
Regards
Shashank
On 5/31/2017 6:16 PM, Ville Syrjälä wrote:
On Tue, May 30, 2017 at 10:18:19PM +0530, Sharma, Shashank wrote:
Regards
Shashank
On 5/30/2017 10:06 PM, Ville Syrjälä wrote:
On Tue, May 30, 2017 at 05:43:44PM +0530, Shashank Sharma wrote:
HDMI displays can support various
Regards
Shashank
On 5/30/2017 10:06 PM, Ville Syrjälä wrote:
On Tue, May 30, 2017 at 05:43:44PM +0530, Shashank Sharma wrote:
HDMI displays can support various output types, based on
the color space and subsampling type. The possible
outputs from a HDMI 2.0 monitor could be:
- RGB
-
Regards
Shashank
On 5/30/2017 9:43 PM, Ville Syrjälä wrote:
On Tue, May 30, 2017 at 05:43:40PM +0530, Shashank Sharma wrote:
HDMI 1.4b support the CEA video modes as per range of CEA-861-D (VIC 1-64).
For any other mode, the VIC filed in AVI infoframes should be 0.
HDMI 2.0 sinks, support
Regards
Shashank
On 5/30/2017 9:48 PM, Ville Syrjälä wrote:
On Tue, May 30, 2017 at 05:43:41PM +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
Regards
Shashank
On 5/9/2017 8:58 PM, Ville Syrjälä wrote:
On Tue, May 09, 2017 at 02:04:55PM +0530, Sharma, Shashank wrote:
Regards
Shashank
On 5/8/2017 10:39 PM, Ville Syrjälä wrote:
On Mon, May 08, 2017 at 10:11:53PM +0530, Sharma, Shashank wrote:
Regards
Shashank
On 5/8/2017 9:54
Regards
Shashank
On 5/8/2017 10:39 PM, Ville Syrjälä wrote:
On Mon, May 08, 2017 at 10:11:53PM +0530, Sharma, Shashank wrote:
Regards
Shashank
On 5/8/2017 9:54 PM, Ville Syrjälä wrote:
On Fri, Apr 07, 2017 at 07:39:20PM +0300, Shashank Sharma wrote:
From: Jose Abreu <jose
Regards
Shashank
On 5/8/2017 10:28 PM, Ville Syrjälä wrote:
On Fri, Apr 07, 2017 at 07:39:21PM +0300, Shashank Sharma wrote:
HDMI 2.0 spec adds support for ycbcr420 subsampled output.
CEA-861-F adds two new blocks in EDID, to provide information about
sink's support for ycbcr420 output.
One
Regards
Shashank
On 5/8/2017 9:52 PM, Ville Syrjälä wrote:
On Fri, Apr 07, 2017 at 07:39:19PM +0300, 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
Regards
Shashank
On 5/8/2017 9:54 PM, Ville Syrjälä wrote:
On Fri, Apr 07, 2017 at 07:39:20PM +0300, Shashank Sharma wrote:
From: Jose Abreu
HDMI 2.0 spec adds support for ycbcr420 subsampled output.
CEA-861-F adds two new blocks in EDID, to provide information
Regards
Shashank
On 5/5/2017 12:43 PM, Daniel Vetter wrote:
On Fri, May 5, 2017 at 9:06 AM, Sharma, Shashank
<shashank.sha...@intel.com> wrote:
On 5/5/2017 12:28 PM, Daniel Vetter wrote:
On Thu, May 04, 2017 at 05:51:45PM +0300, Ville Syrjälä wrote:
On Thu, May 04, 2017 at 03:22:45PM
Regards
Shashank
On 5/5/2017 12:28 PM, Daniel Vetter wrote:
On Thu, May 04, 2017 at 05:51:45PM +0300, Ville Syrjälä wrote:
On Thu, May 04, 2017 at 03:22:45PM +0200, Daniel Vetter wrote:
On Thu, May 04, 2017 at 10:14:26AM +0300, Jyri Sarha wrote:
Add standard optinal property blobs for
Regards
Shashank
On 4/26/2017 6:26 PM, Jyri Sarha wrote:
On 04/24/17 19:55, Ville Syrjälä wrote:
In fact we have plane specific YCbCr to RGB CSC (only preoffset
possible), then (per crtc) gamma table, and finally a (per crtc) RGB to
YCbCr CSC with optional post offset (so it can be used
Regards
Shashank
On 4/21/2017 4:47 PM, Ville Syrjälä wrote:
On Fri, Apr 21, 2017 at 12:51:14PM +0300, Jyri Sarha wrote:
Add standard properties to control YCbCr to RGB conversion in DRM
planes. The created properties are stored to drm_plane object to allow
different set of supported
Regards
Shashank
On 4/21/2017 3:21 PM, Jyri Sarha wrote:
The series adds plane specific atomic properties to control YCbCr to
RGB conversions. My intention was to try to implement the plane
specific (before DEGAMMA) part of the suggestion in this dri-devel
post:
I would probably extend this
Regards
Shashank
On 4/8/2017 11:13 PM, Emil Velikov wrote:
Hi Shashank,
On 7 April 2017 at 17:39, Shashank Sharma wrote:
+ u64 hdmi_420_cap_map = connector->display_info.hdmi.ycbcr420_vcb_map;
for (i = 0; i < len; i++) {
struct
Regards
Shashank
On 4/10/2017 3:17 PM, Andrzej Hajda wrote:
On 07.04.2017 18:39, Shashank Sharma wrote:
HDMI 1.4b support the CEA video modes as per range of CEA-861-D (VIC 1-64).
For any other mode, the VIC filed in AVI infoframes should be 0.
HDMI 2.0 sinks, support video modes range as
Regards
Shashank
On 4/12/2017 3:19 PM, Jose Abreu wrote:
Hi Shashank,
On 07-04-2017 17:39, Shashank Sharma wrote:
HDMI source must set output colorspace information in AVI
infoframes, so that the sink can decode upcoming frames
accordingly.
As this patch series is adding support for HDMI
Hello Jose,
Sorry for delay in response, I was on vacation.
Please find my comments inline.
Regards
Shashank
On 4/12/2017 3:28 PM, Jose Abreu wrote:
Hi Shashank,
On 07-04-2017 17:39, Shashank Sharma wrote:
HDMI displays can support various output types, based on
the color space and
V6: https://patchwork.freedesktop.org/patch/146749/
Regards
Shashank
-Original Message-
From: Daniel Vetter [mailto:daniel.vet...@ffwll.ch] On Behalf Of Daniel Vetter
Sent: Tuesday, March 28, 2017 9:54 AM
To: Sharma, Shashank <shashank.sha...@intel.com>
Cc: dri
101 - 200 of 406 matches
Mail list logo