Linux Media Controller development
 help / color / mirror / Atom feed
From: Sakari Ailus <sakari.ailus@linux.intel.com>
To: Laurent Pinchart <laurent.pinchart@ideasonboard.com>
Cc: linux-media@vger.kernel.org, "Keke Li" <keke.li@amlogic.com>,
	"Hans Verkuil" <hverkuil@kernel.org>,
	"Nicolas Dufresne" <nicolas.dufresne@collabora.com>,
	"Tomi Valkeinen" <tomi.valkeinen@ideasonboard.com>,
	"Jonas Karlman" <jonas@kwiboo.se>,
	"Mehdi Djait" <mehdi.djait@linux.intel.com>,
	"Daniel Scally" <dan.scally+renesas@ideasonboard.com>,
	"Niklas Söderlund" <niklas.soderlund+renesas@ragnatech.se>
Subject: Re: [PATCH v3 3/3] media: v4l2-common: Update v4l2_get_link_freq() documentation
Date: Thu, 21 Aug 2025 15:57:51 +0300	[thread overview]
Message-ID: <aKcXz7BomAQo_gnS@kekkonen.localdomain> (raw)
In-Reply-To: <20250821124056.GD8865@pendragon.ideasonboard.com>

Hi Laurent,

On Thu, Aug 21, 2025 at 03:40:56PM +0300, Laurent Pinchart wrote:
> Hi Sakari,
> 
> Thank you for the patch.
> 
> On Thu, Aug 21, 2025 at 03:12:07PM +0300, Sakari Ailus wrote:
> > Document that v4l2_get_link_freq() obtains the link frequency primarily
> > by calling the get_mbus_config sub-device pad operation.
> > 
> > Signed-off-by: Sakari Ailus <sakari.ailus@linux.intel.com>
> > ---
> >  include/media/v4l2-common.h | 8 +++++---
> >  1 file changed, 5 insertions(+), 3 deletions(-)
> > 
> > diff --git a/include/media/v4l2-common.h b/include/media/v4l2-common.h
> > index ab0ce8e605c3..c387deffbdd0 100644
> > --- a/include/media/v4l2-common.h
> > +++ b/include/media/v4l2-common.h
> > @@ -567,9 +567,11 @@ int v4l2_fill_pixfmt_mp(struct v4l2_pix_format_mplane *pixfmt, u32 pixelformat,
> >   *	 times two on D-PHY, 1 on parallel. 0 otherwise.
> >   *
> >   * This function is intended for obtaining the link frequency from the
> > - * transmitter sub-device's pad. It returns the link rate, either from the
> > - * V4L2_CID_LINK_FREQ control implemented by the transmitter, or value
> > - * calculated based on the V4L2_CID_PIXEL_RATE implemented by the transmitter.
> > + * transmitter sub-device's @pad. It returns the link rate, primarily obtained
> > + * through the get_mbus_config sub-device pad operation or secondarily through
> > + * either from the V4L2_CID_LINK_FREQ control implemented by the transmitter, or
> 
> "through either from" should be either "through either" or "either
> from".
> 
> > + * value calculated based on the V4L2_CID_PIXEL_RATE implemented by the
> > + * transmitter.
> 
> I think this can be clarified further:
> 
>  * This function obtains and returns the link frequency from the transmitter
>  * sub-device's pad. The link frequency is retrieved using the get_mbus_config
>  * sub-device pad operation. If this fails, the function falls back to obtaining
>  * the frequency either directly from the V4L2_CID_LINK_FREQ control if
>  * implemented by the transmitter, or by calculating it from the pixel rate
>  * obtained from the V4L2_CID_PIXEL_RATE control.
> 
> Reviewed-by: Laurent Pinchart <laurent.pinchart+renesas@ideasonboard.com>

Thanks. I'll use the text in v4.

-- 
Sakari Ailus

  reply	other threads:[~2025-08-21 12:57 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-08-21 12:12 [PATCH v2 0/3] Drop control handler argument support for v4l2_get_link_freq() Sakari Ailus
2025-08-21 12:12 ` [PATCH v3 1/3] media: amlogic: c3-mipi-csi2: Call v4l2_get_link_freq() on source pad Sakari Ailus
2025-08-21 12:12 ` [PATCH v3 2/3] media: v4l2-common: Drop the workaround from v4l2_get_link_freq() Sakari Ailus
2025-08-21 12:35   ` Laurent Pinchart
2025-08-21 12:12 ` [PATCH v3 3/3] media: v4l2-common: Update v4l2_get_link_freq() documentation Sakari Ailus
2025-08-21 12:40   ` Laurent Pinchart
2025-08-21 12:57     ` Sakari Ailus [this message]
2025-08-21 12:41 ` [PATCH v2 0/3] Drop control handler argument support for v4l2_get_link_freq() Laurent Pinchart
2025-08-21 12:56   ` Sakari Ailus
2025-08-21 13:01     ` Laurent Pinchart
2025-08-21 13:24       ` Sakari Ailus
2025-08-21 13:27         ` Laurent Pinchart
2025-08-21 13:30           ` Sakari Ailus
2025-08-21 13:45             ` Laurent Pinchart
2025-08-22 10:03               ` 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=aKcXz7BomAQo_gnS@kekkonen.localdomain \
    --to=sakari.ailus@linux.intel.com \
    --cc=dan.scally+renesas@ideasonboard.com \
    --cc=hverkuil@kernel.org \
    --cc=jonas@kwiboo.se \
    --cc=keke.li@amlogic.com \
    --cc=laurent.pinchart@ideasonboard.com \
    --cc=linux-media@vger.kernel.org \
    --cc=mehdi.djait@linux.intel.com \
    --cc=nicolas.dufresne@collabora.com \
    --cc=niklas.soderlund+renesas@ragnatech.se \
    --cc=tomi.valkeinen@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