From: Sakari Ailus <sakari.ailus@linux.intel.com>
To: linux-media@vger.kernel.org
Cc: laurent.pinchart@ideasonboard.com, jacopo.mondi@ideasonboard.com,
Bingbu Cao <bingbu.cao@intel.com>,
Tianshu Qiu <tian.shu.qiu@intel.com>,
Hans Verkuil <hverkuil-cisco@xs4all.nl>
Subject: [PATCH 0/4] Add link frequency to bitmap helper
Date: Mon, 11 Dec 2023 16:06:54 +0200 [thread overview]
Message-ID: <20231211140658.366268-1-sakari.ailus@linux.intel.com> (raw)
Hi folks,
This set adds a little helper for sensor drivers to match link frequencies
from system firmware with those supported the driver and generate a bitmap
suitable for passing to the control framework.
Imx319, imx334 and imx355 drivers are converted to use the helper, too.
I've tested imx319 and imx355 drivers.
Sakari Ailus (4):
media: v4l: Add a helper for setting up link-frequencies control
media: imx334: Use v4l2_link_frequencies_to_bitmap helper
media: imx319: Use v4l2_link_frequencies_to_bitmap helper
media: imx355: Use v4l2_link_frequencies_to_bitmap helper
drivers/media/i2c/imx319.c | 53 +++++++--------------------
drivers/media/i2c/imx334.c | 41 +++++++--------------
drivers/media/i2c/imx355.c | 53 +++++++--------------------
drivers/media/v4l2-core/v4l2-common.c | 48 ++++++++++++++++++++++++
include/media/v4l2-common.h | 27 ++++++++++++++
5 files changed, 116 insertions(+), 106 deletions(-)
--
2.39.2
next reply other threads:[~2023-12-11 14:07 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-12-11 14:06 Sakari Ailus [this message]
2023-12-11 14:06 ` [PATCH 1/4] media: v4l: Add a helper for setting up link-frequencies control Sakari Ailus
2023-12-12 16:07 ` kernel test robot
2023-12-11 14:06 ` [PATCH 2/4] media: imx334: Use v4l2_link_frequencies_to_bitmap helper Sakari Ailus
2023-12-11 20:37 ` kernel test robot
2023-12-11 14:06 ` [PATCH 3/4] media: imx319: " Sakari Ailus
2023-12-13 2:16 ` Cao, Bingbu
2023-12-13 9:51 ` Sakari Ailus
2023-12-11 14:06 ` [PATCH 4/4] media: imx355: " 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=20231211140658.366268-1-sakari.ailus@linux.intel.com \
--to=sakari.ailus@linux.intel.com \
--cc=bingbu.cao@intel.com \
--cc=hverkuil-cisco@xs4all.nl \
--cc=jacopo.mondi@ideasonboard.com \
--cc=laurent.pinchart@ideasonboard.com \
--cc=linux-media@vger.kernel.org \
--cc=tian.shu.qiu@intel.com \
/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