From: Tommaso Merciai <tomm.merciai@gmail.com>
Cc: linuxfancy@googlegroups.com, sakari.ailus@linux.intel.com,
laurent.pinchart@ideasonboard.com, martin.hecht@avnet.eu,
tomm.merciai@gmail.com,
Mauro Carvalho Chehab <mchehab@kernel.org>,
linux-media@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: [PATCH v3 0/5] media: i2c: alvium: store frame interval in subdev
Date: Wed, 20 Dec 2023 13:40:18 +0100 [thread overview]
Message-ID: <20231220124023.2801417-1-tomm.merciai@gmail.com> (raw)
Hi All,
The goal of this series as suggested by LPinchart is to remove the following
data from alvium_dev struct:
- struct v4l2_fract frame_interval;
- u64 dft_fr;
- u64 min_fr;
- u64 max_fr;
- u64 fr;
And use instead the the newly added storage for frame interval in the subdev state.
Last patch fix req_fr check into alvium_s_frame_interval().
This series is made on top of the media_stage tree[1]:
- media: i2c: mt9m114: use fsleep() in place of udelay() (02d4e62ae245)
- [1] https://git.linuxtv.org/media_stage.git/log/
Tommaso Merciai (5):
media: i2c: alvium: removal of dft_fr, min_fr and max_fr
media: i2c: alvium: remove the fr field of the alvium_dev structure
media: i2c: alvium: inline set_frame_interval into s_frame_interval
media: i2c: alvium: store frame interval in subdev state
media: i2c: alvium: fix req_fr check into alvium_s_frame_interval()
drivers/media/i2c/alvium-csi2.c | 99 +++++++++------------------------
drivers/media/i2c/alvium-csi2.h | 5 --
2 files changed, 27 insertions(+), 77 deletions(-)
--
2.34.1
next reply other threads:[~2023-12-20 12:40 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-12-20 12:40 Tommaso Merciai [this message]
2023-12-20 12:40 ` [PATCH v3 1/5] media: i2c: alvium: removal of dft_fr, min_fr and max_fr Tommaso Merciai
2023-12-20 12:40 ` [PATCH v3 2/5] media: i2c: alvium: remove the fr field of the alvium_dev structure Tommaso Merciai
2023-12-20 12:40 ` [PATCH v3 3/5] media: i2c: alvium: inline set_frame_interval into s_frame_interval Tommaso Merciai
2023-12-20 12:40 ` [PATCH v3 4/5] media: i2c: alvium: store frame interval in subdev state Tommaso Merciai
2023-12-20 12:40 ` [PATCH v3 5/5] media: i2c: alvium: fix req_fr check into alvium_s_frame_interval() Tommaso Merciai
2023-12-20 13:02 ` Laurent Pinchart
2023-12-20 13:52 ` Tommaso Merciai
2024-02-14 11:14 ` Sakari Ailus
2024-02-14 15:24 ` Tommaso Merciai
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=20231220124023.2801417-1-tomm.merciai@gmail.com \
--to=tomm.merciai@gmail.com \
--cc=laurent.pinchart@ideasonboard.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-media@vger.kernel.org \
--cc=linuxfancy@googlegroups.com \
--cc=martin.hecht@avnet.eu \
--cc=mchehab@kernel.org \
--cc=sakari.ailus@linux.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
all inboxes | Powered by JetHome®