From: "Yan, Dongcheng" <dongcheng.yan@linux.intel.com>
To: Hans Verkuil <hverkuil@xs4all.nl>,
Sakari Ailus <sakari.ailus@linux.intel.com>,
"Yan, Dongcheng" <dongcheng.yan@intel.com>
Cc: linux-media@vger.kernel.org, laurent.pinchart@ideasonboard.com,
ricardo.ribalda@gmail.com, bingbu.cao@linux.intel.com,
tomi.valkeinen@ideasonboard.com, jacopo.mondi@ideasonboard.com,
daxing.li@intel.com, ong.hock.yu@intel.com,
balamurugan.c@intel.com, wei.a.fu@intel.com
Subject: Re: [PATCH v4] media: i2c: add lt6911uxe hdmi bridge driver
Date: Mon, 23 Dec 2024 14:22:03 +0800 [thread overview]
Message-ID: <9782b615-3ed0-4c99-aabd-2a7f4e6cd041@linux.intel.com> (raw)
In-Reply-To: <7b690b8e-2fff-46ec-9f61-d46360ed9213@xs4all.nl>
Hi hans,
On 12/12/2024 4:54 PM, Hans Verkuil wrote:
> Sakari, Dongcheng,
>
> On 12/12/2024 09:15, Sakari Ailus wrote:
>> Hi Dongcheng,
>>
>> On Thu, Dec 12, 2024 at 03:24:16PM +0800, Yan, Dongcheng wrote:
>>> Hi Sakari,
>>>
>>> Since you are planning to PR this patch, I will continue to use
>
> Please note that I still need to review v4. I hope to do that tomorrow
> before my Christmas vacation starts.
>
> Regards,
>
> Hans
>
>>> CUR_LINK_FREQ to initialize the link_freq v4l2_ctl.
>>>
>>> Besides, I see your patch in intel/ipu6 that obtains the link frequency from
>>> the sub-device instead of a control handler.
>>>
>>> Maybe I don't need init link_freq v4l2_ctl anymore?
>>
>> Please use get_mbus_config() operation.
>>
>
>
Wishing you a happy Christmas holiday in advance! I wonder if you
have some new comments on patch v4?
Thanks,
Dongcheng
next prev parent reply other threads:[~2024-12-23 6:22 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-11-29 6:15 [PATCH v4] media: i2c: add lt6911uxe hdmi bridge driver Dongcheng Yan
2024-11-29 10:48 ` kernel test robot
2024-12-10 14:19 ` Sakari Ailus
2024-12-11 14:39 ` Yan, Dongcheng
2024-12-11 21:12 ` Sakari Ailus
2024-12-12 7:24 ` Yan, Dongcheng
2024-12-12 8:15 ` Sakari Ailus
2024-12-12 8:54 ` Hans Verkuil
2024-12-23 6:22 ` Yan, Dongcheng [this message]
2024-12-23 9:50 ` Hans Verkuil
2025-01-06 11:56 ` Hans Verkuil
2025-01-09 3:36 ` Yan, Dongcheng
2025-01-09 10:27 ` 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=9782b615-3ed0-4c99-aabd-2a7f4e6cd041@linux.intel.com \
--to=dongcheng.yan@linux.intel.com \
--cc=balamurugan.c@intel.com \
--cc=bingbu.cao@linux.intel.com \
--cc=daxing.li@intel.com \
--cc=dongcheng.yan@intel.com \
--cc=hverkuil@xs4all.nl \
--cc=jacopo.mondi@ideasonboard.com \
--cc=laurent.pinchart@ideasonboard.com \
--cc=linux-media@vger.kernel.org \
--cc=ong.hock.yu@intel.com \
--cc=ricardo.ribalda@gmail.com \
--cc=sakari.ailus@linux.intel.com \
--cc=tomi.valkeinen@ideasonboard.com \
--cc=wei.a.fu@intel.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