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 v7 1/3] media: cec: expose HDMI connector to CEC dev mapping
Date: Wed, 19 Jun 2019 13:26:55 +0200 [thread overview]
Message-ID: <4566a4db-86db-c9ee-3a5b-9e7c605a6da7@xs4all.nl> (raw)
In-Reply-To: <CALFZZQEao3vqVxKO-3mT5ATtC=ZWO+bc3dA_Xo-mgpqmna_fMQ@mail.gmail.com>
On 6/19/19 1:05 PM, Dariusz Marcinkiewicz wrote:
> Hi Hans.
>
> I would like to come back to this thread.
>
> On Fri, May 24, 2019 at 11:21 AM Hans Verkuil <hverkuil@xs4all.nl> wrote:
>>
>> Hi Dariusz,
>>
>> I did some more testing with the Khadas VIM2 and found another problem,
>> something that will, unfortunately, require some redesign.
>>
>> See my comments below...
>>
> ...
>>
>> Another issue here is that when the HDMI driver removes the notifier,
>> then it should also zero the connector info. Remember that both the
>> HDMI and the CEC drivers can be loaded and unloaded independently from
>> one another.
>>
>
> I took a peek at the changes in
> https://git.linuxtv.org/hverkuil/media_tree.git/log/?h=cec-conn. Do I
> understand it correctly, that the above problem is addressed there by
> unregistering an adapter in cec_notifier_conn_unregister (which will
> result in /dev/cecX node going away)? I wonder to what degree this
> solves the problem of HDMI and CEC drivers being loaded and unloaded
> independently. It seems that in cases where HDMI driver is unloaded
> and then loaded again, counterintuitively, the /dev/cecX might not
> come back again, is this right, or am I missing something? Also, is it
> guaranteed that adapter drivers won't try to access an adapter once it
> gets removed by cec_notifier_conn_unregister?
It's old code, I'm going to do it differently (closer to your version,
actually).
I just pushed my latest code, I'm much happier with it.
I'll try to post a patch series this week.
Regards,
Hans
prev parent reply other threads:[~2019-06-19 11:27 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-05-21 10:52 [PATCH v7 1/3] media: cec: expose HDMI connector to CEC dev mapping Dariusz Marcinkiewicz
2019-05-21 10:52 ` [PATCH v7 2/3] drm/bridge: dw-hdmi: pass connector info to the CEC adapter Dariusz Marcinkiewicz
2019-05-21 10:52 ` [PATCH v7 3/3] drm/i2c: tda9950: pass HDMI connector info to " Dariusz Marcinkiewicz
2019-05-24 9:21 ` [PATCH v7 1/3] media: cec: expose HDMI connector to CEC dev mapping Hans Verkuil
2019-05-28 7:53 ` Dariusz Marcinkiewicz
2019-05-28 8:05 ` Hans Verkuil
2019-05-29 14:47 ` Hans Verkuil
2019-06-19 11:05 ` Dariusz Marcinkiewicz
2019-06-19 11:26 ` Hans Verkuil [this message]
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=4566a4db-86db-c9ee-3a5b-9e7c605a6da7@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).