From: "Yan, Dongcheng" <dongcheng.yan@linux.intel.com>
To: Hans Verkuil <hverkuil@xs4all.nl>,
Sakari Ailus <sakari.ailus@linux.intel.com>
Cc: Dongcheng Yan <dongcheng.yan@intel.com>,
linux-media@vger.kernel.org, laurent.pinchart@ideasonboard.com,
tomi.valkeinen@ideasonboard.com, jacopo.mondi@ideasonboard.com,
daxing.li@intel.com, hao.yao@intel.com
Subject: Re: [PATCH v3] media: i2c: add lt6911uxe hdmi bridge driver
Date: Fri, 29 Nov 2024 13:49:29 +0800 [thread overview]
Message-ID: <f72dc944-9a91-4691-bf45-4644058f0732@linux.intel.com> (raw)
In-Reply-To: <07ce5885-04af-4872-81cc-bff3d0dbcb60@xs4all.nl>
Hi Hans,
On 10/25/2024 3:05 PM, Hans Verkuil wrote:
> On 25/10/2024 08:49, Sakari Ailus wrote:
>> Hi Hans,
>>
>> On Wed, Oct 23, 2024 at 02:28:02PM +0200, Hans Verkuil wrote:
>>> Hi Dongcheng,
>>>
>>> Since this is an HDMI receiver, you need to implement the DV Timings API.
>>
>> "Must"? Why?
>
> The DV Timings API is used to deal with the HDMI interface part.
>
>>
>> I don't know the tc358743 driver but it'd unlikely to work with current
>> CSI-2 RX drivers. They expect the LINK_FREQ control for instance, not the
>> DV timing API.
>> <URL:https://hverkuil.home.xs4all.nl/spec/driver-api/tx-rx.html#transmitter-receiver>
>>
>
> The tc358743 predates these controls. It just uses get_mbus_config. The CSI
> configuration is defined in the dts:
>
> Documentation/devicetree/bindings/media/i2c/tc358743.txt
>
the lt6911uxe driver gets mbus_config in lt6911uxe_fwnode_parse, however
we still need to support v4l2_ctl link_freq and pixel_rate for the
related sensor users who follow the CSI-2 rules, like Intel IPU.
Thanks,
Dongcheng
> It is fine to add support for these controls, but the DV Timings API to deal
> with the HDMI interface is required for HDMI receivers.
>
> The CSI lanes/frequencies are typically fixed for HDMI receivers (i.e. they
> don't change if the resolution changes).
>
> Regards,
>
> Hans
>
next prev parent reply other threads:[~2024-11-29 5:49 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-10-17 3:08 [PATCH v3] media: i2c: add lt6911uxe hdmi bridge driver Dongcheng Yan
2024-10-23 12:28 ` Hans Verkuil
2024-10-25 6:49 ` Sakari Ailus
2024-10-25 7:05 ` Hans Verkuil
2024-11-29 5:49 ` Yan, Dongcheng [this message]
[not found] ` <4c2322d8-03cb-4d5d-97a8-3d9c327d3a72@linux.intel.com>
2024-10-25 5:52 ` Yan, Dongcheng
2024-10-25 6:58 ` Hans Verkuil
2024-11-29 6:13 ` Yan, Dongcheng
2024-11-29 13:16 ` Hans Verkuil
2024-12-01 16:40 ` Yan, Dongcheng
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=f72dc944-9a91-4691-bf45-4644058f0732@linux.intel.com \
--to=dongcheng.yan@linux.intel.com \
--cc=daxing.li@intel.com \
--cc=dongcheng.yan@intel.com \
--cc=hao.yao@intel.com \
--cc=hverkuil@xs4all.nl \
--cc=jacopo.mondi@ideasonboard.com \
--cc=laurent.pinchart@ideasonboard.com \
--cc=linux-media@vger.kernel.org \
--cc=sakari.ailus@linux.intel.com \
--cc=tomi.valkeinen@ideasonboard.com \
/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