From: Sakari Ailus <sakari.ailus@linux.intel.com>
To: linux-media@vger.kernel.org
Cc: antti.laakso@intel.com, Lixu Zhang <lixu.zhang@intel.com>,
Miguel Vadillo <miguel.vadillo@intel.com>,
Dan Scally <dan.scally@ideasonboard.com>,
Hans de Goede <hansg@kernel.org>,
"Sapre, Sarang" <sarang.sapre@intel.com>
Subject: [PATCH 0/3] Rework IPU6 PCI table
Date: Wed, 9 Sep 2026 11:19:49 +0300 [thread overview]
Message-ID: <20260909081953.3089179-1-sakari.ailus@linux.intel.com> (raw)
Hello everyone,
This set reworks IPU PCI tables a little, by moving them from the IVSC and
CVS drivers to the IPU bridge. The IPU 6 driver will need a copy of the
PCI ID table for module device table whereas another copy will reside on
the IPU bridge. That's one copy less.
since v1:
- Use static inline for ipu_bridge_get_ipu6() in non-CONFIG_IPU_BRIDGE=[my]
case and move the line above the comment related to the line following
the comment.
Sakari Ailus (3):
media: ipu-bridge: Add ipu_bridge_get_ipu6()
media: cvs: Use ipu_bridge_get_ipu6()
media: ivsc: Use ipu_bridge_get_ipu6()
drivers/media/i2c/cvs/core.c | 7 ++-----
drivers/media/pci/intel/ipu-bridge.c | 14 ++++++++++++++
drivers/media/pci/intel/ivsc/mei_csi.c | 7 +------
include/media/ipu-bridge.h | 2 ++
4 files changed, 19 insertions(+), 11 deletions(-)
base-commit: bc4257aa73edad2ba94a725f8f156eca69fc60ce
--
2.47.3
next reply other threads:[~2026-09-09 8:19 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-09-09 8:19 Sakari Ailus [this message]
2026-09-09 8:19 ` [PATCH v2 1/3] media: ipu-bridge: Add ipu_bridge_get_ipu6() Sakari Ailus
2026-09-09 9:18 ` Antti Laakso
2026-09-09 14:24 ` Dan Scally
2026-09-09 8:19 ` [PATCH v2 2/3] media: cvs: Use ipu_bridge_get_ipu6() Sakari Ailus
2026-09-09 9:19 ` Antti Laakso
2026-09-09 14:24 ` Dan Scally
2026-09-09 8:19 ` [PATCH v2 3/3] media: ivsc: " Sakari Ailus
2026-09-09 9:20 ` Antti Laakso
2026-09-09 14:24 ` Dan Scally
-- strict thread matches above, loose matches on Subject: below --
2026-09-07 20:31 [PATCH 0/3] Rework IPU6 PCI table 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=20260909081953.3089179-1-sakari.ailus@linux.intel.com \
--to=sakari.ailus@linux.intel.com \
--cc=antti.laakso@intel.com \
--cc=dan.scally@ideasonboard.com \
--cc=hansg@kernel.org \
--cc=linux-media@vger.kernel.org \
--cc=lixu.zhang@intel.com \
--cc=miguel.vadillo@intel.com \
--cc=sarang.sapre@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 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.