mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Tommaso Merciai <tomm.merciai@gmail.com>
Cc: linuxfancy@googlegroups.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 v2 0/4] media: i2c: alvium: store frame interval in subdev
Date: Wed, 20 Dec 2023 09:56:05 +0100	[thread overview]
Message-ID: <20231220085609.2595732-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.
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 (4):
  media: i2c: alvium: removal of dft_fr, min_fr and max_fr
  media: i2c: alvium: removal of fr field
  media: i2c: alvium: inline set_frame_interval into s_frame_interval
  media: i2c: alvium: store frame interval in subdev state

 drivers/media/i2c/alvium-csi2.c | 99 ++++++++++-----------------------
 drivers/media/i2c/alvium-csi2.h |  5 --
 2 files changed, 29 insertions(+), 75 deletions(-)

-- 
2.34.1


             reply	other threads:[~2023-12-20  8:56 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-12-20  8:56 Tommaso Merciai [this message]
2023-12-20  8:56 ` [PATCH v2 1/4] media: i2c: alvium: removal of dft_fr, min_fr and max_fr Tommaso Merciai
2023-12-20  9:08   ` Laurent Pinchart
2023-12-20  8:56 ` [PATCH v2 2/4] media: i2c: alvium: removal of fr field Tommaso Merciai
2023-12-20  9:13   ` Laurent Pinchart
2023-12-20 10:02     ` Tommaso Merciai
2023-12-20 10:06       ` Laurent Pinchart
2023-12-20 11:19         ` Tommaso Merciai
2023-12-20 11:29           ` Laurent Pinchart
2023-12-20 12:03             ` Tommaso Merciai
2023-12-20 12:19               ` Laurent Pinchart
2023-12-20 12:42                 ` Tommaso Merciai
2023-12-20  8:56 ` [PATCH v2 3/4] media: i2c: alvium: inline set_frame_interval into s_frame_interval Tommaso Merciai
2023-12-20  9:14   ` Laurent Pinchart
2023-12-20 10:04     ` Tommaso Merciai
2023-12-20  8:56 ` [PATCH v2 4/4] media: i2c: alvium: store frame interval in subdev state Tommaso Merciai
2023-12-20  9:17   ` Laurent Pinchart

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=20231220085609.2595732-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 \
    /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®