All of lore.kernel.org
 help / color / mirror / Atom feed
From: Sakari Ailus <sakari.ailus@linux.intel.com>
To: linux-media@vger.kernel.org
Cc: laurent.pinchart@ideasonboard.com, jmondi@jmondi.org
Subject: [PATCH 5/5] v4l2-fwnode: Say it's fine to use v4l2_fwnode_endpoint_parse
Date: Wed, 30 Sep 2020 17:48:11 +0300	[thread overview]
Message-ID: <20200930144811.16612-6-sakari.ailus@linux.intel.com> (raw)
In-Reply-To: <20200930144811.16612-1-sakari.ailus@linux.intel.com>

Earlier it was expected that there would be more variable size endpoint
properties and that most if not all drivers would need them. For that
reason it was expected also that v4l2_fwnode_endpoint_parse would no
longer be needed.

What actually happened that not all drivers require "link-frequencies",
the only variable size media endpoint property without a small upper
limit. Therefore drivers that do not need that information are fine using
v4l2_fwnode_endpoint_parse. So don't tell drivers to use
v4l2_fwnode_endpoint_alloc_parse in all cases.

Signed-off-by: Sakari Ailus <sakari.ailus@linux.intel.com>
---
 include/media/v4l2-fwnode.h | 4 ++--
 1 file changed, 2 insertions(+), 2 deletions(-)

diff --git a/include/media/v4l2-fwnode.h b/include/media/v4l2-fwnode.h
index 0c28dc11e829..cbd872e59f8e 100644
--- a/include/media/v4l2-fwnode.h
+++ b/include/media/v4l2-fwnode.h
@@ -245,8 +245,8 @@ struct v4l2_fwnode_connector {
  * The function does not change the V4L2 fwnode endpoint state if it fails.
  *
  * NOTE: This function does not parse properties the size of which is variable
- * without a low fixed limit. Please use v4l2_fwnode_endpoint_alloc_parse() in
- * new drivers instead.
+ * without a low fixed limit. Please use v4l2_fwnode_endpoint_alloc_parse() if
+ * you need properties of variable size.
  *
  * Return: %0 on success or a negative error code on failure:
  *	   %-ENOMEM on memory allocation failure
-- 
2.27.0


  parent reply	other threads:[~2020-09-30 14:48 UTC|newest]

Thread overview: 20+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-09-30 14:48 [PATCH 0/5] V4L2 fwnode fixes, improvements and cleanups Sakari Ailus
2020-09-30 14:48 ` [PATCH 1/5] adv748x: Zero entire struct v4l2_fwnode_endpoint Sakari Ailus
2020-10-02 15:48   ` Niklas Söderlund
2020-10-04  8:31   ` Laurent Pinchart
2020-09-30 14:48 ` [PATCH 2/5] v4l2-fwnode: v4l2_fwnode_endpoint_parse caller must init vep argument Sakari Ailus
2020-10-02 15:53   ` Niklas Söderlund
2020-10-02 21:01     ` Sakari Ailus
2020-10-04  8:35   ` Laurent Pinchart
2020-09-30 14:48 ` [PATCH 3/5] v4l2-fwnode: Don't zero parts of struct v4l2_fwnode_endpoint anymore Sakari Ailus
2020-10-02 17:42   ` Niklas Söderlund
2020-10-04  8:36   ` Laurent Pinchart
2020-09-30 14:48 ` [PATCH 4/5] v4l2-fwnode: Rework v4l2_fwnode_endpoint_parse documentation Sakari Ailus
2020-10-02 17:21   ` Niklas Söderlund
2020-10-04  8:40   ` Laurent Pinchart
2020-10-05  6:53     ` Sakari Ailus
2020-09-30 14:48 ` Sakari Ailus [this message]
2020-10-02 17:22   ` [PATCH 5/5] v4l2-fwnode: Say it's fine to use v4l2_fwnode_endpoint_parse Niklas Söderlund
2020-10-04  8:41   ` Laurent Pinchart
2020-10-05  6:55     ` Sakari Ailus
2020-10-05  7:46     ` Sakari Ailus

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=20200930144811.16612-6-sakari.ailus@linux.intel.com \
    --to=sakari.ailus@linux.intel.com \
    --cc=jmondi@jmondi.org \
    --cc=laurent.pinchart@ideasonboard.com \
    --cc=linux-media@vger.kernel.org \
    /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.