From: Sakari Ailus <sakari.ailus@iki.fi>
To: linux-media@vger.kernel.org
Subject: [GIT PULL for 5.4] V4L2 fwnode parsing improvements
Date: Thu, 25 Jul 2019 14:19:27 +0300 [thread overview]
Message-ID: <20190725111927.GI1263@valkosipuli.retiisi.org.uk> (raw)
Hi Mauro,
This set contains the V4L2 fwnode parsing improvements that have had
lengthy reviews on the list.
Please pull.
The following changes since commit ebe15c7679680308268b99d911b1db15d514c7b8:
media: tegra-cec: use cec_notifier_cec_adap_(un)register (2019-07-23 08:40:57 -0400)
are available in the Git repository at:
ssh://linuxtv.org/git/sailus/media_tree.git tags/for-5.4-2-signed
for you to fetch changes up to 7e9afcd1b74ed7daf6c16b217d0fe2cea81dc510:
ipu3-cio2: Parse information from firmware without using callbacks (2019-07-25 11:41:18 +0300)
----------------------------------------------------------------
Fwnode parsing improvements
----------------------------------------------------------------
Sakari Ailus (8):
davinci-vpif: Don't dereference endpoint after putting it, fix refcounting
v4l2-async: Get fwnode reference when putting it to the notifier's list
v4l2-async: Add v4l2_async_notifier_add_fwnode_remote_subdev
omap3isp: Rework OF endpoint parsing
v4l2-async: Safely clean up an uninitialised notifier
ipu3-cio2: Clean up notifier's subdev list if parsing endpoints fails
ipu3-cio2: Proceed with notifier init even if there are no subdevs
ipu3-cio2: Parse information from firmware without using callbacks
drivers/media/pci/intel/ipu3/ipu3-cio2.c | 97 ++++----
drivers/media/platform/am437x/am437x-vpfe.c | 5 +-
drivers/media/platform/davinci/vpif_capture.c | 18 +-
drivers/media/platform/omap3isp/isp.c | 331 +++++++++++++++-----------
drivers/media/platform/qcom/camss/camss.c | 2 +-
drivers/media/platform/xilinx/xilinx-vipp.c | 2 +-
drivers/media/v4l2-core/v4l2-async.c | 28 ++-
drivers/media/v4l2-core/v4l2-fwnode.c | 23 +-
include/media/v4l2-async.h | 30 ++-
9 files changed, 323 insertions(+), 213 deletions(-)
--
Kind regards,
Sakari Ailus
reply other threads:[~2019-07-25 11:19 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=20190725111927.GI1263@valkosipuli.retiisi.org.uk \
--to=sakari.ailus@iki.fi \
--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.