From: Krzysztof Kozlowski <k.kozlowski@samsung.com>
To: Hans Verkuil <hverkuil@xs4all.nl>, Hans Verkuil <hans.verkuil@cisco.com>
Cc: linux-media@vger.kernel.org, dri-devel@lists.freedesktop.org,
linux-samsung-soc@vger.kernel.org, linux-input@vger.kernel.org,
lars@opdenkamp.eu, linux@arm.linux.org.uk,
Kamil Debski <kamil@wypas.org>,
krzk@kernel.org
Subject: Re: [PATCHv13 01/17] dts: exynos4*: add HDMI CEC pin definition to pinctrl
Date: Mon, 21 Mar 2016 09:22:46 +0900 [thread overview]
Message-ID: <56EF3ED6.3010308@samsung.com> (raw)
In-Reply-To: <56ED0AA3.1000601@xs4all.nl>
On 19.03.2016 17:15, Hans Verkuil wrote:
> On 03/19/2016 03:50 AM, Krzysztof Kozlowski wrote:
>> On Fri, Mar 18, 2016 at 03:07:00PM +0100, Hans Verkuil wrote:
>>> From: Kamil Debski <kamil@wypas.org>
>>>
>>> Add pinctrl nodes for the HDMI CEC device to the Exynos4210 and
>>> Exynos4x12 SoCs. These are required by the HDMI CEC device.
>>>
>>> Signed-off-by: Kamil Debski <kamil@wypas.org>
>>> Signed-off-by: Hans Verkuil <hans.verkuil@cisco.com>
>>> Acked-by: Krzysztof Kozlowski <k.kozlowski@samsung.com>
>>> ---
>>> arch/arm/boot/dts/exynos4210-pinctrl.dtsi | 7 +++++++
>>> arch/arm/boot/dts/exynos4x12-pinctrl.dtsi | 7 +++++++
>>> 2 files changed, 14 insertions(+)
>>
>> Hi Hans,
>>
>> I see you have been carrying these three patches for a long time.
>> Initially I thought that there are some dependencies... but maybe there
>> are not?
>>
>> Can I take these Exynos DTS patches to samsung-soc?
>
> That would be very nice!
I'll apply them after merge window.
> BTW, it would be nice if someone from Samsung could try to improve the s5p
> CEC driver from this patch series.
>
> The problem is that it expects userspace to tell it the physical address,
> which is read from the EDID. But the HDMI driver in the kernel already knows
> this, so requiring userspace to handle this is not nice.
>
> Basically the CEC driver needs to know when a new EDID has been read and
> when the hotplug detect goes low (EDID has been lost).
>
> If someone who actually knows the HDMI code could provide me with a patch,
> then I can fix the CEC driver. I have an odroid to test with, so I can check
> the code.
Not quite my area of knowledge but I'll keep it in mind.
Best regards,
Krzysztof
next prev parent reply other threads:[~2016-03-21 0:22 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-03-18 14:06 [PATCHv13 00/17] HDMI CEC framework Hans Verkuil
2016-03-18 14:07 ` [PATCHv13 01/17] dts: exynos4*: add HDMI CEC pin definition to pinctrl Hans Verkuil
2016-03-19 2:50 ` Krzysztof Kozlowski
2016-03-19 2:50 ` Krzysztof Kozlowski
2016-03-19 8:15 ` Hans Verkuil
2016-03-21 0:22 ` Krzysztof Kozlowski [this message]
2016-03-18 14:07 ` [PATCHv13 02/17] dts: exynos4: add node for the HDMI CEC device Hans Verkuil
2016-03-18 14:07 ` [PATCHv13 03/17] dts: exynos4412-odroid*: enable " Hans Verkuil
2016-03-18 14:07 ` [PATCHv13 04/17] input.h: add BUS_CEC type Hans Verkuil
2016-03-18 14:07 ` [PATCHv13 05/17] HID: add HDMI CEC specific keycodes Hans Verkuil
2016-03-18 17:30 ` Hans Verkuil
2016-03-18 14:07 ` [PATCHv13 06/17] rc: Add HDMI CEC protocol handling Hans Verkuil
2016-03-18 14:07 ` [PATCHv13 07/17] cec: add HDMI CEC framework Hans Verkuil
2016-03-18 14:07 ` [PATCHv13 08/17] cec: add compat32 ioctl support Hans Verkuil
2016-03-18 14:07 ` [PATCHv13 09/17] cec.txt: add CEC framework documentation Hans Verkuil
2016-03-18 14:07 ` [PATCHv13 10/17] DocBook/media: add CEC documentation Hans Verkuil
2016-03-18 14:07 ` [PATCHv13 11/17] v4l2-subdev: add HDMI CEC ops Hans Verkuil
2016-03-18 14:07 ` [PATCHv13 12/17] cec: adv7604: add cec support Hans Verkuil
2016-03-18 14:07 ` [PATCHv13 13/17] cec: adv7842: " Hans Verkuil
2016-03-18 14:07 ` [PATCHv13 14/17] cec: adv7511: " Hans Verkuil
2016-03-18 14:07 ` [PATCHv13 15/17] cobalt: " Hans Verkuil
2016-03-18 14:07 ` [PATCHv13 16/17] cec: s5p-cec: Add s5p-cec driver Hans Verkuil
2016-03-18 14:07 ` [PATCHv13 17/17] vivid: add CEC emulation Hans Verkuil
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=56EF3ED6.3010308@samsung.com \
--to=k.kozlowski@samsung.com \
--cc=dri-devel@lists.freedesktop.org \
--cc=hans.verkuil@cisco.com \
--cc=hverkuil@xs4all.nl \
--cc=kamil@wypas.org \
--cc=krzk@kernel.org \
--cc=lars@opdenkamp.eu \
--cc=linux-input@vger.kernel.org \
--cc=linux-media@vger.kernel.org \
--cc=linux-samsung-soc@vger.kernel.org \
--cc=linux@arm.linux.org.uk \
/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.