From: Tomi Valkeinen <tomi.valkeinen@ideasonboard.com>
To: Mauro Carvalho Chehab <mchehab@kernel.org>,
Hans Verkuil <hans.verkuil@cisco.com>,
linux-media@vger.kernel.org,
Laurent Pinchart <laurent.pinchart@ideasonboard.com>,
Sakari Ailus <sakari.ailus@linux.intel.com>
Cc: Tomi Valkeinen <tomi.valkeinen@ideasonboard.com>
Subject: [PATCH v2 0/1] RFC: media: v4l2-subdev: add subdev-wide config struct
Date: Fri, 23 Apr 2021 13:29:51 +0300 [thread overview]
Message-ID: <20210423102952.137638-1-tomi.valkeinen@ideasonboard.com> (raw)
Hi,
Second version of the RFC. The previous one is here:
https://lore.kernel.org/linux-media/20210409133659.389544-1-tomi.valkeinen@ideasonboard.com/
In v2:
- Rename v4l2_subdev_config -> v4l2_subdev_state
- Rename pad_configs -> pads
- Allocate the v4l2_subdev_state instead of embedding it
I didn't:
- Rename v4l2_subdev_pad_ops->init_cfg to init_state. There will be a
huge amount of changes to drivers, and I'd like to keep any extra
changes out of this series. For the same reason, I intend to keep
the v4l2_subdev_state variable names as 'cfg' instead of trying to
rename them to 'state'.
- Add number of pads or a pointer to subdev to v4l2_subdev_state. It can
be added easily if someone has a need for it.
I also dropped the few driver changes I made. They are obvious trivial
changes and don't really give anything to the discussion.
Tomi
Tomi Valkeinen (1):
RFC: media: v4l2-subdev: add subdev-wide state struct
drivers/media/v4l2-core/v4l2-subdev.c | 141 +++++++++++++++-----------
include/media/v4l2-subdev.h | 72 +++++++------
2 files changed, 120 insertions(+), 93 deletions(-)
--
2.25.1
next reply other threads:[~2021-04-23 10:30 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-04-23 10:29 Tomi Valkeinen [this message]
2021-04-23 10:29 ` [PATCH v2 1/1] RFC: media: v4l2-subdev: add subdev-wide state struct Tomi Valkeinen
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=20210423102952.137638-1-tomi.valkeinen@ideasonboard.com \
--to=tomi.valkeinen@ideasonboard.com \
--cc=hans.verkuil@cisco.com \
--cc=laurent.pinchart@ideasonboard.com \
--cc=linux-media@vger.kernel.org \
--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;
as well as URLs for NNTP newsgroup(s).