From: Sakari Ailus <sakari.ailus@iki.fi>
To: Sakari Ailus <sakari.ailus@linux.intel.com>
Cc: linux-media@vger.kernel.org,
Antti Laakso <antti.laakso@linux.intel.com>,
mchehab@kernel.org, sarang.sapre@intel.com, daxing.li@intel.com,
ong.hock.yu@intel.com
Subject: Re: [PATCH v2 1/1] media: ipu6: Add a Kconfig option for IPU 7, 7.5 support
Date: Thu, 3 Sep 2026 13:25:01 +0300 [thread overview]
Message-ID: <aplK_YMgVfqhf-4H@valkosipuli.retiisi.eu> (raw)
In-Reply-To: <20260903081614.1841716-1-sakari.ailus@linux.intel.com>
On Thu, Sep 03, 2026 at 11:16:14AM +0300, Sakari Ailus wrote:
> Add a Kconfig option for IPU 7 and IPU 7.5 support in the IPU 6 driver.
> Enabling this option adds the IPU 7 and IPU 7.5 PCI IDs to the IPU 6
> driver and disables the IPU 7 staging driver.
>
> Signed-off-by: Sakari Ailus <sakari.ailus@linux.intel.com>
> ---
I itend to squash this to the last patch in Antti's ipu7/7.5 support set,
with the following commit message:
media: ipu6: Enable support for IPU 7 and IPU 7.5
Enable support for Intel IPU 7 and IPU 7.5, found in Lunar lake and
Panther lake, respectively.
Add a Kconfig option for IPU 7 and IPU 7.5 support in the IPU 6 driver.
Enabling this option adds the IPU 7 and IPU 7.5 PCI IDs to the IPU 6
driver and disables the IPU 7 staging driver.
Signed-off-by: Antti Laakso <antti.laakso@linux.intel.com>
[Sakari Ailus: Add Kconfig option and #ifdefs.]
Signed-off-by: Sakari Ailus <sakari.ailus@linux.intel.com>
--
Regards,
Sakari Ailus
next prev parent reply other threads:[~2026-09-03 10:25 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20260827123336.2219048-1-antti.laakso@linux.intel.com, Ricardo Ribalda Delgado <ricardo@ribalda.com>
2026-09-03 8:16 ` [PATCH v2 1/1] media: ipu6: Add a Kconfig option for IPU 7, 7.5 support Sakari Ailus
2026-09-03 10:25 ` Sakari Ailus [this message]
2026-09-03 19:59 ` [PATCH 1/1] staging: media: ipu7: Update TODO file 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=aplK_YMgVfqhf-4H@valkosipuli.retiisi.eu \
--to=sakari.ailus@iki.fi \
--cc=antti.laakso@linux.intel.com \
--cc=daxing.li@intel.com \
--cc=linux-media@vger.kernel.org \
--cc=mchehab@kernel.org \
--cc=ong.hock.yu@intel.com \
--cc=sakari.ailus@linux.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.