From: Sakari Ailus <sakari.ailus@linux.intel.com>
To: Umang Jain <umang.jain@ideasonboard.com>
Cc: linux-media@vger.kernel.org,
Kieran Bingham <kieran.bingham@ideasonboard.com>,
Mauro Carvalho Chehab <mchehab@kernel.org>,
open list <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH v2 3/5] media: i2c: imx335: Support multiple link frequency
Date: Thu, 15 Feb 2024 12:53:09 +0000 [thread overview]
Message-ID: <Zc4JNYxvLCfkyQKb@kekkonen.localdomain> (raw)
In-Reply-To: <20240131055208.170934-4-umang.jain@ideasonboard.com>
Hi Umang,
On Wed, Jan 31, 2024 at 11:22:06AM +0530, Umang Jain wrote:
> Support link frequency of 445MHz in addition to 594MHz.
> Break out the register set specific to each data lane rate and also add
> the general timing register set corresponding to the each data
> lane rate.
>
> Signed-off-by: Umang Jain <umang.jain@ideasonboard.com>
Please use the same subject line prefix (i.e. without "i2c: ").
--
Regards,
Sakari Ailus
next prev parent reply other threads:[~2024-02-15 12:59 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-01-31 5:52 [PATCH v2 0/5] imx335: Support additional link-freq and TPG Umang Jain
2024-01-31 5:52 ` [PATCH v2 1/5] media: i2c: imx335: Drop setting of 0x3a00 register Umang Jain
2024-01-31 9:52 ` Kieran Bingham
2024-01-31 10:32 ` Matthias Fend
2024-02-07 4:21 ` Umang Jain
2024-02-15 12:50 ` Sakari Ailus
2024-01-31 5:52 ` [PATCH v2 2/5] media: imx335: Use v4l2_link_freq_to_bitmap helper Umang Jain
2024-02-15 12:51 ` Sakari Ailus
2024-02-15 12:53 ` Sakari Ailus
2024-01-31 5:52 ` [PATCH v2 3/5] media: i2c: imx335: Support multiple link frequency Umang Jain
2024-02-15 12:53 ` Sakari Ailus [this message]
2024-01-31 5:52 ` [PATCH v2 4/5] media: i2c: imx335: Refactor power sequence to set controls Umang Jain
2024-01-31 5:52 ` [PATCH v2 5/5] media: i2c: imx335: Add support for test pattern generator Umang Jain
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=Zc4JNYxvLCfkyQKb@kekkonen.localdomain \
--to=sakari.ailus@linux.intel.com \
--cc=kieran.bingham@ideasonboard.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-media@vger.kernel.org \
--cc=mchehab@kernel.org \
--cc=umang.jain@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
all inboxes | Powered by JetHome®