Bug 101445

Summary:	[KBL] NUC Gen 7 HDMI CEC features
Product:	DRI	Reporter:	raik.zimmermann
Component:	DRM/Intel	Assignee:	raik.zimmermann
Status:	CLOSED FIXED	QA Contact:	Intel GFX Bugs mailing list <intel-gfx-bugs>
Severity:	enhancement
Priority:	medium	CC:	clinton.a.taylor, intel-gfx-bugs
Version:	XOrg git
Hardware:	x86-64 (AMD64)
OS:	Linux (All)
Whiteboard:
i915 platform:	KBL	i915 features:	display/HDMI

Description raik.zimmermann 2017-06-15 11:44:52 UTC

Hello dear devs,

recently I've purchased a brand new NUC7i5BNK. One of the reasons I've bought it is the included HDMI CEC support.

However I've found out very quickly that it doesn't do what I've expected (at least not out of the box): Allow TV remote control interaction via CEC with a media center software (Kodi). So I thought: ok - the hardware is probably not yet supported by libcec. That's why I've opened this request over at github: https://github.com/Pulse-Eight/libcec/issues/345

As of the moment it is only possible to automatically turn on / off connected devices according to the official product specification. So I'm beginning to get the feeling that it will never be possible because the hardware isn't designed for that.

Can anyone shed some light on this topic please? At Intel communities I'm not getting a clear answer: https://communities.intel.com/thread/114554

At Kodi Wiki I've just found this information: http://kodi.wiki/view/CEC#Intel_NUC "Updated list of CEC commands: Intel graphics do not support this feature." Is this true even for the latest NUC generation? And is this by hardware or software currently?

Perhaps someone here can even help to make a solution.

Otherwise I will likely need an additional Pulse-Eight product. :-(

Comment 1 Joseph Yasi 2017-06-15 13:13:39 UTC

You need one of these internal adapters: https://www.pulse-eight.com/p/154/intel-nuc-hdmi-cec-adapter

Comment 2 Jani Nikula 2017-07-04 12:08:44 UTC

I don't think buying an adapter will help alone. There are some patches floating around, but needs work. Enhancement.

Clint, please share the status if you know more about CEC.

Comment 3 Ricardo 2017-07-04 15:42:30 UTC

Moving bug to NEEDINFO. Clint can you help me with an update if possible, once adding your comment please change the bug to REOPEN and reset the ASSIGNEE.

Comment 4 Clinton Taylor 2017-07-05 16:51:46 UTC

First, The KBL processor does not have native support for HDMI CEC. 

According to https://www.intel.com/content/dam/support/us/en/documents/boardsandkits/custom-solutions-header-whitepaper.pdf some models of the NUC include an internal header for an internal Pulse8 controller as mentioned in comment 1.

There is also a patch series that has been posted to the upstream mailing list currently in RFC form that would implement HDMI CEC using a DP->HDMI converter and the CEC_CORE functionality in the kernel. However, At this time very few existing DP->HDMI converters actually support HDMI CEC though many advertise support.

I really can't give more advise as I have never used the NUC and a 3rd party HDMI CEC controller. I'm sure there are forums with further information. I would suggest starting at www.pulse-eight.com

Comment 5 Elizabeth 2017-07-20 15:57:26 UTC

Hello Raik, 
I think the information provided by Clinton Taylor is the answer for this question. I'll close the bug as fixed, if you have more doubts you can try in the community forums: https://01.org/linuxgraphics/community to get more info about kernel.
BR, Elizabeth.

Comment 6 michaelwitten82 2017-07-28 02:37:47 UTC

Just a bit more information for people in future. The 7th (and I believe some of the 6th gen) NUCs DO have CEC support built into them (as well as the headers like in the old ones).

However, I have found (after talking to Intel - very painfully for the past few weeks), the CEC controller on the NUC (built in one) ONLY supports the power options.

For further info: https://askubuntu.com/questions/935445/how-to-get-hdmi-cec-working-on-a-7th-gen-intel-nuc/935649#935649

Use of freedesktop.org services, including Bugzilla, is subject to our Code of Conduct. How we collect and use information is described in our Privacy Policy.