From: Sakari Ailus <sakari.ailus@linux.intel.com>
To: linux-media@vger.kernel.org
Cc: laurent.pinchart@ideasonboard.com, jmondi@jmondi.org
Subject: [PATCH 0/5] V4L2 fwnode fixes, improvements and cleanups
Date: Wed, 30 Sep 2020 17:48:06 +0300 [thread overview]
Message-ID: <20200930144811.16612-1-sakari.ailus@linux.intel.com> (raw)
Hi all,
This small set improves V4L2 fwnode framework in small but in an important
ways. In particular:
- Default parameters are no longer zeroed for V4L2_MBUS_UNKNOWN --- this
makes defaults for multiple bus types actually working, so it's a bugfix
- Don't tell to use v4l2_fwnode_endpoint_alloc_parse in all drivers;
v4l2_fwnode_endpoint_parse is just as good if the device doesn't need
link-frequencies.
- Rewrite v4l2_fwnode_endpoint(_alloc)_parse documentation
Laurent: I believe this addresses your request to parse multiple bus types
with a single call to v4l2_fwnode_endpoint_(alloc_)parse --- please see
the 4th patch. You don't really need to tell the default, but the caller
will need to check the result is one of the known types. But as the caller
very probably needs to do some work based on the bus type right afterwards
this is hardly an actual burden for drivers.
Sakari Ailus (5):
adv748x: Zero entire struct v4l2_fwnode_endpoint
v4l2-fwnode: v4l2_fwnode_endpoint_parse caller must init vep argument
v4l2-fwnode: Don't zero parts of struct v4l2_fwnode_endpoint anymore
v4l2-fwnode: Rework v4l2_fwnode_endpoint_parse documentation
v4l2-fwnode: Say it's fine to use v4l2_fwnode_endpoint_parse
drivers/media/i2c/adv748x/adv748x-core.c | 3 +-
drivers/media/v4l2-core/v4l2-fwnode.c | 12 ----
include/media/v4l2-fwnode.h | 70 ++++++++++++++++--------
3 files changed, 47 insertions(+), 38 deletions(-)
--
2.27.0
next 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 Sakari Ailus [this message]
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 ` [PATCH 5/5] v4l2-fwnode: Say it's fine to use v4l2_fwnode_endpoint_parse Sakari Ailus
2020-10-02 17:22 ` 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-1-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.