From: Sakari Ailus <sakari.ailus@linux.intel.com>
To: linux-media@vger.kernel.org
Cc: laurent.pinchart@ideasonboard.com, hverkuil@xs4all.nl
Subject: [PATCH 0/2] Unified fwnode endpoint parser
Date: Thu, 29 Jun 2017 10:30:08 +0300 [thread overview]
Message-ID: <1498721410-28199-1-git-send-email-sakari.ailus@linux.intel.com> (raw)
Hi folks,
We have a large influx of new, unmerged, drivers that are now parsing
fwnode endpoints and each one of them is doing this a little bit
differently. The needs are still exactly the same for the graph data
structure is device independent. This is still a non-trivial task and the
majority of the driver implementations are buggy, just buggy in different
ways.
Facilitate parsing endpoints by adding a convenience function for parsing
the endpoints, and make the omap3isp driver use it as an example.
The parser succeeds an essential bugfix in the set.
Sakari Ailus (2):
v4l: fwnode: link_frequency is an optional property
v4l: fwnode: Support generic parsing of graph endpoints in V4L2
drivers/media/platform/omap3isp/isp.c | 91 +++++++------------------
drivers/media/platform/omap3isp/isp.h | 3 -
drivers/media/v4l2-core/v4l2-fwnode.c | 124 ++++++++++++++++++++++++++++++----
include/media/v4l2-async.h | 4 +-
include/media/v4l2-fwnode.h | 9 +++
5 files changed, 147 insertions(+), 84 deletions(-)
--
2.1.4
next reply other threads:[~2017-06-29 7:30 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-06-29 7:30 Sakari Ailus [this message]
2017-06-29 7:30 ` [PATCH 1/2] v4l: fwnode: link_frequency is an optional property Sakari Ailus
2017-06-29 8:40 ` Niklas Söderlund
2017-06-29 7:30 ` [PATCH 2/2] v4l: fwnode: Support generic parsing of graph endpoints in V4L2 Sakari Ailus
2017-06-29 9:02 ` Niklas Söderlund
2017-06-29 9:05 ` Niklas Söderlund
2017-06-29 9:57 ` Sakari Ailus
2017-06-29 10:18 ` Niklas Söderlund
2017-06-29 10: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=1498721410-28199-1-git-send-email-sakari.ailus@linux.intel.com \
--to=sakari.ailus@linux.intel.com \
--cc=hverkuil@xs4all.nl \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox