From: Cory Keitz <ckeitz@amazon.com>
To: <dumitru.ceclan@analog.com>
Cc: "Tomi Valkeinen" <tomi.valkeinen+renesas@ideasonboard.com>,
"Mauro Carvalho Chehab" <mchehab@kernel.org>,
"Sakari Ailus" <sakari.ailus@linux.intel.com>,
"Laurent Pinchart" <laurent.pinchart@ideasonboard.com>,
"Julien Massot" <julien.massot@collabora.com>,
"Rob Herring" <robh@kernel.org>,
"Niklas Söderlund" <niklas.soderlund@ragnatech.se>,
"Greg Kroah-Hartman" <gregkh@linuxfoundation.org>,
linux-media@vger.kernel.org, linux-kernel@vger.kernel.org,
devicetree@vger.kernel.org, linux-gpio@vger.kernel.org,
linux-staging@lists.linux.dev, mitrutzceclan@gmail.com,
"Cosmin Tanislav" <demonsingur@gmail.com>
Subject: Re: [PATCH RESEND v8 14/21] media: i2c: add Maxim GMSL2/3 deserializer framework
Date: Tue, 10 Mar 2026 09:35:25 -0700 [thread overview]
Message-ID: <abBITdEEs4tJCQWa@bcd074ae11bb> (raw)
In-Reply-To: <20251208-gmsl2-3_serdes-v8-14-7b8d457e2e04@analog.com>
On Mon, Dec 08, 2025 at 04:13:06PM +0200, Dumitru Ceclan via B4 Relay wrote:
> +#define MAX_DES_LINK_FREQUENCY_MIN 100000000ull
> +#define MAX_DES_LINK_FREQUENCY_DEFAULT 750000000ull
> +#define MAX_DES_LINK_FREQUENCY_MAX 1250000000ull
Related to my comments on patch 16 [1], I believe this should be set
differently between DPHY and CPHY. As I test more cameras I've patched
this to allow CPHY link frequencies up to 2500MHz. I'm also wondering
whether these should be driver-specific rather than defined at the
framework level to allow for higher capacities in future silicon.
[1] https://lore.kernel.org/linux-media/aaxWATynXaVFglvS@bcd074ae11bb/
--
R,
Cory
prev parent reply other threads:[~2026-03-10 16:35 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20251208-gmsl2-3_serdes-v8-0-7b8d457e2e04@analog.com>
[not found] ` <20251208-gmsl2-3_serdes-v8-16-7b8d457e2e04@analog.com>
2026-03-07 17:03 ` [PATCH RESEND v8 16/21] media: i2c: maxim-serdes: add MAX96724 driver Cory Keitz
[not found] ` <20251208-gmsl2-3_serdes-v8-14-7b8d457e2e04@analog.com>
2026-03-10 16:35 ` Cory Keitz [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=abBITdEEs4tJCQWa@bcd074ae11bb \
--to=ckeitz@amazon.com \
--cc=demonsingur@gmail.com \
--cc=devicetree@vger.kernel.org \
--cc=dumitru.ceclan@analog.com \
--cc=gregkh@linuxfoundation.org \
--cc=julien.massot@collabora.com \
--cc=laurent.pinchart@ideasonboard.com \
--cc=linux-gpio@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-media@vger.kernel.org \
--cc=linux-staging@lists.linux.dev \
--cc=mchehab@kernel.org \
--cc=mitrutzceclan@gmail.com \
--cc=niklas.soderlund@ragnatech.se \
--cc=robh@kernel.org \
--cc=sakari.ailus@linux.intel.com \
--cc=tomi.valkeinen+renesas@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