All of lore.kernel.org
 help / color / mirror / Atom feed
From: Clint Taylor <clinton.a.taylor@intel.com>
To: Hans Verkuil <hverkuil@xs4all.nl>,
	Jani Nikula <jani.nikula@intel.com>,
	Daniel Vetter <daniel@ffwll.ch>
Cc: linux-media@vger.kernel.org, dri-devel@lists.freedesktop.org,
	intel-gfx@lists.freedesktop.org,
	Hans Verkuil <hans.verkuil@cisco.com>
Subject: Re: [RFC PATCH 7/7] drm/i915: add DisplayPort CEC-Tunneling-over-AUX support
Date: Tue, 30 May 2017 13:31:40 -0700	[thread overview]
Message-ID: <8071df35-1bce-d537-693f-486478459f9c@intel.com> (raw)
In-Reply-To: <22961af9-5157-ae14-3000-f91cedc27958@xs4all.nl>



On 05/30/2017 09:49 AM, Hans Verkuil wrote:
> On 05/30/2017 04:19 PM, Clint Taylor wrote:
>>
>>
>> On 05/30/2017 12:11 AM, Jani Nikula wrote:
>>> On Tue, 30 May 2017, Hans Verkuil <hverkuil@xs4all.nl> wrote:
>>>> On 05/29/2017 09:00 PM, Daniel Vetter wrote:
>>>>> On Fri, May 26, 2017 at 12:20:48PM +0200, Hans Verkuil wrote:
>>>>>> On 05/26/2017 09:15 AM, Daniel Vetter wrote:
>>>>>>> Did you look into also wiring this up for dp mst chains?
>>>>>> Isn't this sufficient? I have no way of testing mst chains.
>>>>>>
>>>>>> I think I need some pointers from you, since I am a complete 
>>>>>> newbie when it
>>>>>> comes to mst.
>>>>> I don't really have more clue, but yeah if you don't have an mst 
>>>>> thing (a
>>>>> simple dp port multiplexer is what I use for testing here, then 
>>>>> plug in a
>>>>> converter dongle or cable into that) then probably better to not 
>>>>> wire up
>>>>> the code for it.
>>>> I think my NUC already uses mst internally. But I was planning on 
>>>> buying a
>>>> dp multiplexer to make sure there is nothing special I need to do 
>>>> for mst.
>>>>
>>>> The CEC Tunneling is all in the branch device, so if I understand 
>>>> things
>>>> correctly it is not affected by mst.
>>>>
>>>> BTW, I did a bit more testing on my NUC7i5BNK: for the HDMI output 
>>>> they
>>>> use a MegaChip MCDP2800 DP-to-HDMI converter which according to their
>>>> datasheet is supposed to implement CEC Tunneling, but if they do it 
>>>> is not
>>>> exposed as a capability. I'm not sure if it is a MegaChip firmware 
>>>> issue
>>>> or something else. The BIOS is able to do some CEC, but whether 
>>>> they hook
>>>> into the MegaChip or have the CEC pin connected to a GPIO or 
>>>> something and
>>>> have their own controller is something I do not know.
>>>>
>>>> If anyone can clarify what Intel did on the NUC, then that would be 
>>>> very
>>>> helpful.
>>> It's called LSPCON, see i915/intel_lspcon.c, basically to support HDMI
>>> 2.0. Currently we only use it in PCON mode, shows up as DP for us. It
>>> could be used in LS mode, showing up as HDMI 1.4, but we don't support
>>> that in i915.
>>>
>>> I don't know about the CEC on that.
>>
>> My NUC6i7KYK has the MCDP2850 LSPCON and it does support CEC over Aux.
>> The release notes for the NUC state that there is a BIOS configuration
>> option for enabling support. My doesn't have the option but the LSPCON
>> fully supports CEC.
>
> What is the output of:
>
> dd if=/dev/drm_dp_aux0 of=aux0 skip=12288 ibs=1 count=48
> od -t x1 aux0
>
> Assuming drm_dp_aux0 is the aux channel for the HDMI output on your NUC.
>
> If the first byte is != 0x00, then it advertises CEC over Aux.
>
> For me it says 0x00.
slightly different command, but it still dumps DPCD 0x3000 for 48 bytes.

sudo dd if=/dev/drm_dp_aux0 bs=1 skip=12288 count=48 | hexdump -C
00000000  07 00 00 00 00 00 00 00  00 00 00 00 00 00 00 80 
|................|
00000010  f8 23 c4 8f 06 d8 59 7b  37 bb 1e 14 9c cb cd 88 
|.#....Y{7.......|
00000020  4e 84 10 00 04 00 f7 f5  e2 fa a3 30 ad 42 ed 19 
|N..........0.B..|


>
> When you say "it does support CEC over Aux", does that mean you have 
> actually
> tested it somehow? The only working solution I have seen mentioned for 
> the
> NUC6i7KYK is a Pulse-Eight adapter.
>
> With the NUC7i Intel made BIOS support for CEC, but it is not at all
> clear to me if they used CEC tunneling or just hooked up the CEC pin to
> some microcontroller.
>
> The only working chipset I have seen is the Parade PS176.
I have a couple PS176 based devices that I purchased from Amazon that do 
not work even though they advertise support at DPCD 0x3000.

Club 3D USB-C->HDMI 2.0 UHD
Uptab    USB-C->HDMI 2.0

-Clint


>
> Regards,
>
>     Hans
>
>>
>> -Clint
>>
>>>
>>>
>>> BR,
>>> Jani.
>>>
>>>> It would be so nice to get MegaChip CEC Tunneling working on the 
>>>> NUC, because
>>>> then you have native CEC support without requiring any Pulse Eight 
>>>> adapter.
>>>>
>>>> And add a CEC-capable USB-C to HDMI adapter and you have it on the 
>>>> USB-C
>>>> output as well.
>>>>
>>>> Regards,
>>>>
>>>>     Hans
>>
>

WARNING: multiple messages have this Message-ID (diff)
From: Clint Taylor <clinton.a.taylor@intel.com>
To: Hans Verkuil <hverkuil@xs4all.nl>,
	Jani Nikula <jani.nikula@intel.com>,
	Daniel Vetter <daniel@ffwll.ch>
Cc: intel-gfx@lists.freedesktop.org,
	Hans Verkuil <hans.verkuil@cisco.com>,
	dri-devel@lists.freedesktop.org, linux-media@vger.kernel.org
Subject: Re: [RFC PATCH 7/7] drm/i915: add DisplayPort CEC-Tunneling-over-AUX support
Date: Tue, 30 May 2017 13:31:40 -0700	[thread overview]
Message-ID: <8071df35-1bce-d537-693f-486478459f9c@intel.com> (raw)
In-Reply-To: <22961af9-5157-ae14-3000-f91cedc27958@xs4all.nl>



On 05/30/2017 09:49 AM, Hans Verkuil wrote:
> On 05/30/2017 04:19 PM, Clint Taylor wrote:
>>
>>
>> On 05/30/2017 12:11 AM, Jani Nikula wrote:
>>> On Tue, 30 May 2017, Hans Verkuil <hverkuil@xs4all.nl> wrote:
>>>> On 05/29/2017 09:00 PM, Daniel Vetter wrote:
>>>>> On Fri, May 26, 2017 at 12:20:48PM +0200, Hans Verkuil wrote:
>>>>>> On 05/26/2017 09:15 AM, Daniel Vetter wrote:
>>>>>>> Did you look into also wiring this up for dp mst chains?
>>>>>> Isn't this sufficient? I have no way of testing mst chains.
>>>>>>
>>>>>> I think I need some pointers from you, since I am a complete 
>>>>>> newbie when it
>>>>>> comes to mst.
>>>>> I don't really have more clue, but yeah if you don't have an mst 
>>>>> thing (a
>>>>> simple dp port multiplexer is what I use for testing here, then 
>>>>> plug in a
>>>>> converter dongle or cable into that) then probably better to not 
>>>>> wire up
>>>>> the code for it.
>>>> I think my NUC already uses mst internally. But I was planning on 
>>>> buying a
>>>> dp multiplexer to make sure there is nothing special I need to do 
>>>> for mst.
>>>>
>>>> The CEC Tunneling is all in the branch device, so if I understand 
>>>> things
>>>> correctly it is not affected by mst.
>>>>
>>>> BTW, I did a bit more testing on my NUC7i5BNK: for the HDMI output 
>>>> they
>>>> use a MegaChip MCDP2800 DP-to-HDMI converter which according to their
>>>> datasheet is supposed to implement CEC Tunneling, but if they do it 
>>>> is not
>>>> exposed as a capability. I'm not sure if it is a MegaChip firmware 
>>>> issue
>>>> or something else. The BIOS is able to do some CEC, but whether 
>>>> they hook
>>>> into the MegaChip or have the CEC pin connected to a GPIO or 
>>>> something and
>>>> have their own controller is something I do not know.
>>>>
>>>> If anyone can clarify what Intel did on the NUC, then that would be 
>>>> very
>>>> helpful.
>>> It's called LSPCON, see i915/intel_lspcon.c, basically to support HDMI
>>> 2.0. Currently we only use it in PCON mode, shows up as DP for us. It
>>> could be used in LS mode, showing up as HDMI 1.4, but we don't support
>>> that in i915.
>>>
>>> I don't know about the CEC on that.
>>
>> My NUC6i7KYK has the MCDP2850 LSPCON and it does support CEC over Aux.
>> The release notes for the NUC state that there is a BIOS configuration
>> option for enabling support. My doesn't have the option but the LSPCON
>> fully supports CEC.
>
> What is the output of:
>
> dd if=/dev/drm_dp_aux0 of=aux0 skip=12288 ibs=1 count=48
> od -t x1 aux0
>
> Assuming drm_dp_aux0 is the aux channel for the HDMI output on your NUC.
>
> If the first byte is != 0x00, then it advertises CEC over Aux.
>
> For me it says 0x00.
slightly different command, but it still dumps DPCD 0x3000 for 48 bytes.

sudo dd if=/dev/drm_dp_aux0 bs=1 skip=12288 count=48 | hexdump -C
00000000  07 00 00 00 00 00 00 00  00 00 00 00 00 00 00 80 
|................|
00000010  f8 23 c4 8f 06 d8 59 7b  37 bb 1e 14 9c cb cd 88 
|.#....Y{7.......|
00000020  4e 84 10 00 04 00 f7 f5  e2 fa a3 30 ad 42 ed 19 
|N..........0.B..|


>
> When you say "it does support CEC over Aux", does that mean you have 
> actually
> tested it somehow? The only working solution I have seen mentioned for 
> the
> NUC6i7KYK is a Pulse-Eight adapter.
>
> With the NUC7i Intel made BIOS support for CEC, but it is not at all
> clear to me if they used CEC tunneling or just hooked up the CEC pin to
> some microcontroller.
>
> The only working chipset I have seen is the Parade PS176.
I have a couple PS176 based devices that I purchased from Amazon that do 
not work even though they advertise support at DPCD 0x3000.

Club 3D USB-C->HDMI 2.0 UHD
Uptab    USB-C->HDMI 2.0

-Clint


>
> Regards,
>
>     Hans
>
>>
>> -Clint
>>
>>>
>>>
>>> BR,
>>> Jani.
>>>
>>>> It would be so nice to get MegaChip CEC Tunneling working on the 
>>>> NUC, because
>>>> then you have native CEC support without requiring any Pulse Eight 
>>>> adapter.
>>>>
>>>> And add a CEC-capable USB-C to HDMI adapter and you have it on the 
>>>> USB-C
>>>> output as well.
>>>>
>>>> Regards,
>>>>
>>>>     Hans
>>
>

_______________________________________________
dri-devel mailing list
dri-devel@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/dri-devel

  parent reply	other threads:[~2017-05-30 20:31 UTC|newest]

Thread overview: 46+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-05-25 15:06 [RFC PATCH 0/7] drm/i915: add support for DisplayPort CEC-Tunneling-over-AUX Hans Verkuil
2017-05-25 15:06 ` [RFC PATCH 1/7] cec: add CEC_CAP_NEEDS_HPD Hans Verkuil
2017-05-25 15:06 ` [RFC PATCH 2/7] cec-ioc-adap-g-caps.rst: document CEC_CAP_NEEDS_HPD Hans Verkuil
2017-05-25 15:06 ` [RFC PATCH 3/7] cec: add cec_s_phys_addr_from_edid helper function Hans Verkuil
2017-05-25 15:06 ` [RFC PATCH 4/7] cec: add cec_phys_addr_invalidate() " Hans Verkuil
2017-05-25 15:06 ` [RFC PATCH 5/7] drm/cec: Add CEC over Aux register definitions Hans Verkuil
2017-05-25 15:06   ` Hans Verkuil
2017-05-26  8:39   ` Jani Nikula
2017-05-26  8:39     ` Jani Nikula
2017-05-25 15:06 ` [RFC PATCH 6/7] drm: add support for DisplayPort CEC-Tunneling-over-AUX Hans Verkuil
2017-05-25 15:06   ` Hans Verkuil
2017-05-26  7:18   ` Daniel Vetter
2017-05-26  7:18     ` Daniel Vetter
2017-05-26 10:34     ` Hans Verkuil
2017-05-26 10:34       ` Hans Verkuil
2017-05-26 11:33       ` Daniel Vetter
2017-05-26 11:33         ` Daniel Vetter
2017-05-30 23:57     ` Clint Taylor
2017-05-31  6:40       ` Hans Verkuil
2017-05-25 15:06 ` [RFC PATCH 7/7] drm/i915: add DisplayPort CEC-Tunneling-over-AUX support Hans Verkuil
2017-05-25 15:06   ` Hans Verkuil
2017-05-26  7:15   ` Daniel Vetter
2017-05-26 10:20     ` Hans Verkuil
2017-05-26 10:20       ` Hans Verkuil
2017-05-29 19:00       ` Daniel Vetter
2017-05-30  7:02         ` Hans Verkuil
2017-05-30  7:02           ` Hans Verkuil
2017-05-30  7:11           ` Jani Nikula
2017-05-30 14:19             ` Clint Taylor
2017-05-30 16:49               ` Hans Verkuil
2017-05-30 16:54                 ` Hans Verkuil
2017-05-30 20:32                   ` Clint Taylor
2017-05-30 20:32                     ` Clint Taylor
2017-05-30 21:29                     ` Hans Verkuil
2017-05-30 23:25                       ` Clint Taylor
2017-05-30 23:25                         ` Clint Taylor
2017-05-31  6:37                         ` Hans Verkuil
2017-05-30 20:31                 ` Clint Taylor [this message]
2017-05-30 20:31                   ` Clint Taylor
2017-05-26 10:13   ` Jani Nikula
2017-05-26 10:13     ` Jani Nikula
2017-05-26 10:13     ` Hans Verkuil
2017-05-26 10:13       ` Hans Verkuil
2017-05-25 15:30 ` [RFC PATCH 0/7] drm/i915: add support for DisplayPort CEC-Tunneling-over-AUX Mike Lothian
2017-05-25 15:56   ` Hans Verkuil
2017-05-25 15:34 ` ✓ Fi.CI.BAT: success for " Patchwork

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=8071df35-1bce-d537-693f-486478459f9c@intel.com \
    --to=clinton.a.taylor@intel.com \
    --cc=daniel@ffwll.ch \
    --cc=dri-devel@lists.freedesktop.org \
    --cc=hans.verkuil@cisco.com \
    --cc=hverkuil@xs4all.nl \
    --cc=intel-gfx@lists.freedesktop.org \
    --cc=jani.nikula@intel.com \
    --cc=linux-media@vger.kernel.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.