From: Hans Verkuil <hverkuil@xs4all.nl>
To: Dariusz Marcinkiewicz <darekm@google.com>
Cc: linux-media@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH v6 2/3] drm/bridge: dw-hdmi: pass connector info to the CEC adapter
Date: Fri, 24 May 2019 09:25:20 +0200 [thread overview]
Message-ID: <dc7a5a31-ca37-167f-5ebe-9b27e0830a87@xs4all.nl> (raw)
In-Reply-To: <CALFZZQHjc8WxuuGzcWUjDJ2TU9Pyp+f0XN0p8iPahPFAOtw6AA@mail.gmail.com>
On 5/21/19 12:54 PM, Dariusz Marcinkiewicz wrote:
> On Mon, May 20, 2019 at 1:30 PM Hans Verkuil <hverkuil@xs4all.nl> wrote:
>>
>> On 5/17/19 5:42 PM, Dariusz Marcinkiewicz wrote:
>>> This patch makes dw-hdmi pass DRM connector info to a respective
>>> CEC adapter. In order to be able to do that it delays creation of
>>> the dw-hdmi-cec platform device until DRM connector is initialized.
>>>
>>> Requires testing.
>>
>> Testing this patch with the Khadas VIM2 board gives this kernel warning:
>>
> Thank you for testing!
>
> This was probably because the platform device info was not fully
> initialized. Hopefully it is better in v7.
This now works without a crash on my Khadas board!
Thanks,
Hans
next prev parent reply other threads:[~2019-05-24 7:25 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-05-17 15:42 [PATCH v6 1/3] media: cec: expose HDMI connector to CEC dev mapping Dariusz Marcinkiewicz
2019-05-17 15:42 ` [PATCH v6 2/3] drm/bridge: dw-hdmi: pass connector info to the CEC adapter Dariusz Marcinkiewicz
2019-05-20 11:30 ` Hans Verkuil
2019-05-21 10:54 ` Dariusz Marcinkiewicz
2019-05-24 7:25 ` Hans Verkuil [this message]
2019-05-17 15:42 ` [PATCH v6 3/3] drm/i2c: tda9950: pass HDMI connector info to " Dariusz Marcinkiewicz
2019-05-20 10:25 ` [PATCH v6 1/3] media: cec: expose HDMI connector to CEC dev mapping Hans Verkuil
2019-05-20 10:50 ` Hans Verkuil
2019-05-21 11:02 ` Dariusz Marcinkiewicz
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=dc7a5a31-ca37-167f-5ebe-9b27e0830a87@xs4all.nl \
--to=hverkuil@xs4all.nl \
--cc=darekm@google.com \
--cc=linux-kernel@vger.kernel.org \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).