All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Yan, Dongcheng" <dongcheng.yan@intel.com>
To: Sakari Ailus <sakari.ailus@linux.intel.com>
Cc: linux-media@vger.kernel.org, laurent.pinchart@ideasonboard.com,
	hverkuil@xs4all.nl, ricardo.ribalda@gmail.com,
	bingbu.cao@linux.intel.com, tomi.valkeinen@ideasonboard.com,
	jacopo.mondi@ideasonboard.com, daxing.li@intel.com,
	dongcheng.yan@linux.intel.com, ong.hock.yu@intel.com,
	balamurugan.c@intel.com, wei.a.fu@intel.com,
	xiaohong.zou@intel.com
Subject: Re: [PATCH v7] media: i2c: add lt6911uxe hdmi bridge driver
Date: Fri, 7 Mar 2025 21:36:30 +0800	[thread overview]
Message-ID: <f1dec7e7-b2ee-4746-b266-5927faf36c61@intel.com> (raw)
In-Reply-To: <Z8rQp2OCPZbvSnjH@kekkonen.localdomain>

Hi Sakari,

On 3/7/2025 6:55 PM, Sakari Ailus wrote:
> Hi Dongcheng,
> 
> On Fri, Mar 07, 2025 at 06:00:56PM +0800, Yan, Dongcheng wrote:
>>>> +		/* MIPI Clock Rate = ByteClock × 4, defined in lt6911uxe spec */
>>>
>>> What does the byte clock actually signify? Bytes per second on CSI-2?
>>>
>>
>> This is more like a DSI related calculation, I think lontium uses the
>> expression related to HDMI and DSI in the video field.
>> dsi_clk = Bitclk / 2 = Byteclk * 4, dsi_clk is mipi clk, which is used
>> as link_freq.
>> Here Bitclk = HTS * VTS * fps * bpp / lanes.
> 
> The PHY for CSI-2 and DSI is the same, so the same formula is applicable.
> The chip is HDMI/CSI-2 (isn'it it?), so I wonder how DSI is related to
> this. How many HDMI lanes are in use?
> 

My expression misunderstood you. I am just explaining why ByteClock is
used here to name. Yes, ByteClock is Bytes per second on CSI-2, and
because CSI-2 uses DDR(Double Data Rate), here link_freq = bitclk / 2 =
ByteClock * 4.

Thanks,
Dongcheng

  reply	other threads:[~2025-03-07 13:36 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-03-06  6:04 [PATCH v7] media: i2c: add lt6911uxe hdmi bridge driver Dongcheng Yan
2025-03-07  9:39 ` Sakari Ailus
2025-03-07  9:45   ` Hans Verkuil
2025-03-07 10:00   ` Yan, Dongcheng
2025-03-07 10:55     ` Sakari Ailus
2025-03-07 13:36       ` Yan, Dongcheng [this message]
2025-03-10 10:08         ` Sakari Ailus
2025-03-08  4:45 ` kernel test robot

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=f1dec7e7-b2ee-4746-b266-5927faf36c61@intel.com \
    --to=dongcheng.yan@intel.com \
    --cc=balamurugan.c@intel.com \
    --cc=bingbu.cao@linux.intel.com \
    --cc=daxing.li@intel.com \
    --cc=dongcheng.yan@linux.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 \
    --cc=xiaohong.zou@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 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.