From: Laurent Pinchart <laurent.pinchart@ideasonboard.com>
To: Sakari Ailus <sakari.ailus@linux.intel.com>
Cc: linux-media@vger.kernel.org, dongcheng.yan@intel.com
Subject: Re: [PATCH v3 11/11] media: ccs-pll: Document the CCS PLL flags
Date: Wed, 23 Apr 2025 15:43:22 +0300 [thread overview]
Message-ID: <20250423124322.GG17813@pendragon.ideasonboard.com> (raw)
In-Reply-To: <20250423123359.1800904-12-sakari.ailus@linux.intel.com>
Hi Sakari,
Thank you for the patch.
On Wed, Apr 23, 2025 at 03:33:59PM +0300, Sakari Ailus wrote:
> Document the CCS PLL flags with short comments. The CCS spec has more
> information on them while the added documentation helps finding the
> relevant information in the CCS spec.
>
> Signed-off-by: Sakari Ailus <sakari.ailus@linux.intel.com>
> ---
> drivers/media/i2c/ccs-pll.c | 2 +-
> drivers/media/i2c/ccs-pll.h | 27 ++++++++++++++++++++++++---
> 2 files changed, 25 insertions(+), 4 deletions(-)
>
> diff --git a/drivers/media/i2c/ccs-pll.c b/drivers/media/i2c/ccs-pll.c
> index 87798616b76d..8f9a695bd9e5 100644
> --- a/drivers/media/i2c/ccs-pll.c
> +++ b/drivers/media/i2c/ccs-pll.c
> @@ -129,8 +129,8 @@ static void print_pll_flags(struct device *dev, struct ccs_pll *pll)
> {
> dev_dbg(dev, "PLL flags%s%s%s%s%s%s%s%s%s%s%s\n",
> pll->flags & PLL_FL(OP_PIX_CLOCK_PER_LANE) ? " op-pix-clock-per-lane" : "",
> - pll->flags & PLL_FL(NO_OP_CLOCKS) ? " no-op-clocks" : "",
> pll->flags & PLL_FL(EVEN_PLL_MULTIPLIER) ? " even-pll-multiplier" : "",
> + pll->flags & PLL_FL(NO_OP_CLOCKS) ? " no-op-clocks" : "",
> pll->flags & PLL_FL(LANE_SPEED_MODEL) ? " lane-speed" : "",
> pll->flags & PLL_FL(EXT_IP_PLL_DIVIDER) ?
> " ext-ip-pll-divider" : "",
> diff --git a/drivers/media/i2c/ccs-pll.h b/drivers/media/i2c/ccs-pll.h
> index 754eb5f52cc4..c668ee4d4493 100644
> --- a/drivers/media/i2c/ccs-pll.h
> +++ b/drivers/media/i2c/ccs-pll.h
> @@ -18,19 +18,40 @@
> #define CCS_PLL_BUS_TYPE_CSI2_DPHY 0x00
> #define CCS_PLL_BUS_TYPE_CSI2_CPHY 0x01
>
> -/* Old SMIA and implementation specific flags */
> -/* op pix clock is for all lanes in total normally */
> +/* Old SMIA and implementation specific flags. */
> +/* OP PIX clock is for all lanes in total normally. */
> #define CCS_PLL_FLAG_OP_PIX_CLOCK_PER_LANE BIT(0)
> -#define CCS_PLL_FLAG_NO_OP_CLOCKS BIT(1)
> +/* If set, the PLL multipliers are required to be even. */
> #define CCS_PLL_FLAG_EVEN_PLL_MULTIPLIER BIT(3)
> +
> /* CCS PLL flags */
> +
> +/* The sensor doesn't have OP clocks at all. */
> +#define CCS_PLL_FLAG_NO_OP_CLOCKS BIT(1)
> +/* System speed model if this flag is unset. */
> #define CCS_PLL_FLAG_LANE_SPEED_MODEL BIT(2)
> +/* If set, the pre-PLL divider may have odd values, too. */
> #define CCS_PLL_FLAG_EXT_IP_PLL_DIVIDER BIT(4)
> +/*
> + * If set, the OP PIX clock doesn't have to exactly match with data rate, it may
> + * be higher. See "OP Domain Formulas" in MIPI CCS 1.1 spec.
> + */
> #define CCS_PLL_FLAG_FLEXIBLE_OP_PIX_CLK_DIV BIT(5)
> +/* If set, the VT domain may run faster than the OP domain. */
> #define CCS_PLL_FLAG_FIFO_DERATING BIT(6)
> +/* If set, the VT domain may run slower than the OP domain. */
> #define CCS_PLL_FLAG_FIFO_OVERRATING BIT(7)
> +/* If set, the PLL tree has two PLLs instead of one. */
> #define CCS_PLL_FLAG_DUAL_PLL BIT(8)
> +/*
> + * If set, the OP SYS clock is a dual data rate clock, transferring two bits per
> + * cycle instead of one.
> + */
> #define CCS_PLL_FLAG_OP_SYS_DDR BIT(9)
> +/*
> + * If set, the OP PIX clock is a dual data rate clock, transferring two bits per
Same comment as for v2.
> + * cycle instead of one.
> + */
> #define CCS_PLL_FLAG_OP_PIX_DDR BIT(10)
>
> /**
--
Regards,
Laurent Pinchart
next prev parent reply other threads:[~2025-04-23 12:43 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-04-23 12:33 [PATCH v3 00/11] CCS PLL fixes and improvements Sakari Ailus
2025-04-23 12:33 ` [PATCH v3 01/11] media: ccs-pll: Start OP pre-PLL multiplier search from correct value Sakari Ailus
2025-04-23 12:33 ` [PATCH v3 02/11] media: ccs-pll: Start VT " Sakari Ailus
2025-04-23 12:33 ` [PATCH v3 03/11] media: ccs-pll: Check for too high VT PLL multiplier in dual PLL case Sakari Ailus
2025-04-23 12:33 ` [PATCH v3 04/11] media: ccs-pll: Correct the upper limit of maximum op_pre_pll_clk_div Sakari Ailus
2025-04-23 12:33 ` [PATCH v3 05/11] media: ccs-pll: Print a debug message on too high VT PLL OP clock Sakari Ailus
2025-04-23 12:33 ` [PATCH v3 06/11] media: ccs-pll: Drop LINK_DECOUPLED flag Sakari Ailus
2025-04-23 12:33 ` [PATCH v3 07/11] media: ccs-pll: Print missing PLL flags Sakari Ailus
2025-04-23 12:33 ` [PATCH v3 08/11] media: ccs-pll: Add a flag for even PLL multipliers Sakari Ailus
2025-04-23 21:49 ` Laurent Pinchart
2025-04-23 12:33 ` [PATCH v3 09/11] media: ccs-pll: Better validate VT PLL branch Sakari Ailus
2025-04-23 12:33 ` [PATCH v3 10/11] media: ccs-pll: Print PLL calculator flags in the beginning Sakari Ailus
2025-04-23 12:33 ` [PATCH v3 11/11] media: ccs-pll: Document the CCS PLL flags Sakari Ailus
2025-04-23 12:43 ` Laurent Pinchart [this message]
2025-04-23 12:51 ` Sakari Ailus
2025-04-23 15:37 ` [PATCH v4 " Sakari Ailus
2025-04-23 17:50 ` Laurent Pinchart
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=20250423124322.GG17813@pendragon.ideasonboard.com \
--to=laurent.pinchart@ideasonboard.com \
--cc=dongcheng.yan@intel.com \
--cc=linux-media@vger.kernel.org \
--cc=sakari.ailus@linux.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