From: Sakari Ailus <sakari.ailus@iki.fi>
To: linux-media@vger.kernel.org
Subject: [GIT PULL for 5.2] Sensor, IPU3 driver patches and fwnode fixes
Date: Tue, 19 Mar 2019 11:23:56 +0200 [thread overview]
Message-ID: <20190319092356.tnyctkhxmw7347se@valkosipuli.retiisi.org.uk> (raw)
Hi Mauro,
Here's a set of sensor and IPU3 driver patches as well as fwnode fixes in
the frameworks as well as in the DaVinci VPE driver. Also put the lens
drivers in Kconfig into their own section (they were in the decoder
section).
Please pull.
The following changes since commit 9e98c678c2d6ae3a17cb2de55d17f69dddaa231b:
Linux 5.1-rc1 (2019-03-17 14:22:26 -0700)
are available in the git repository at:
ssh://linuxtv.org/git/sailus/media_tree.git tags/for-5.2-1-signed
for you to fetch changes up to 4feeb6c9436bda15b8146ca4d4a07b3bb110e863:
v4l2-fwnode: Add a deprecation note in the old ACPI parsing example (2019-03-19 11:20:10 +0200)
----------------------------------------------------------------
sensor stuff for 5.2
----------------------------------------------------------------
Akinobu Mita (2):
media: ov7670: restore default settings after power-up
media: ov7670: don't access registers when the device is powered off
Arnd Bergmann (3):
media: staging/intel-ipu3-v4l: reduce kernel stack usage
media: staging/intel-ipu3: mark PM function as __maybe_unused
media: staging/intel-ipu3: reduce kernel stack usage
Sakari Ailus (7):
v4l2-fwnode: Defaults may not override endpoint configuration in firmware
v4l2-fwnode: The first default data lane is 0 on C-PHY
pxa-camera: Match with device node, not the port node
ti-vpe: Parse local endpoint for properties, not the remote one
v4l: i2c: Regroup lens drivers under their own section
ipu3-cio2: Set CSI-2 receiver sub-device entity function
v4l2-fwnode: Add a deprecation note in the old ACPI parsing example
drivers/media/i2c/Kconfig | 76 ++++++++++++++++----------------
drivers/media/i2c/ov7670.c | 32 +++++++++++---
drivers/media/pci/intel/ipu3/ipu3-cio2.c | 1 +
drivers/media/platform/pxa_camera.c | 2 +-
drivers/media/platform/ti-vpe/cal.c | 12 +----
drivers/media/v4l2-core/v4l2-fwnode.c | 17 +++++--
drivers/staging/media/ipu3/ipu3-css.c | 35 ++++++++++-----
drivers/staging/media/ipu3/ipu3-v4l2.c | 40 ++++++++++-------
drivers/staging/media/ipu3/ipu3.c | 2 +-
9 files changed, 133 insertions(+), 84 deletions(-)
--
Regards,
Sakari Ailus
reply other threads:[~2019-03-19 9:25 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=20190319092356.tnyctkhxmw7347se@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.