From: Mehdi Djait <mehdi.djait@linux.intel.com>
To: Miguel Vadillo <miguel.vadillo@intel.com>
Cc: linux-media@vger.kernel.org, wei.a.xu@intel.com,
atul.raut@intel.com, sakari.ailus@linux.intel.com,
antti.laakso@linux.intel.com, kieran.bingham@ideasonboard.com
Subject: Re: [PATCH v5 2/3] media: pci: intel: Add CVS support for IPU bridge driver
Date: Thu, 28 May 2026 19:06:10 +0200 [thread overview]
Message-ID: <ahh15eCp2hNeuIF1@mdjait-mobl> (raw)
In-Reply-To: <20260527170531.383871-3-miguel.vadillo@intel.com>
Hi Miguel,
Thank you for the patch!
On Wed, May 27, 2026 at 10:05:30AM -0700, Miguel Vadillo wrote:
> CVS is located between IPU device and sensors and is available in
> existing commercial platforms from multiple OEMs. The connection
> information between them in firmware is not enough to build a V4L2
> connection graph. This patch parses the connection properties from the
> SSDB buffer in DSDT and builds the connection using software nodes.
>
> From the IPU bridge point of view, CVS is just like IVSC.
>
> Signed-off-by: Miguel Vadillo <miguel.vadillo@intel.com>
Tested-by: Mehdi Djait <mehdi.djait@linux.intel.com> # Dell XPS 13 9350 + IPU7
Reviewed-by: Mehdi Djait <mehdi.djait@linux.intel.com>
--
Kind Regards
Mehdi Djait
next prev parent reply other threads:[~2026-05-28 17:06 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-05-27 17:05 [PATCH v5 0/3] media: i2c: cvs: Add Intel CVS driver Miguel Vadillo
2026-05-27 17:05 ` [PATCH v5 1/3] media: i2c: cvs: Add driver of Intel Computer Vision Sensing Controller(CVS) Miguel Vadillo
2026-05-28 17:05 ` Mehdi Djait
2026-05-27 17:05 ` [PATCH v5 2/3] media: pci: intel: Add CVS support for IPU bridge driver Miguel Vadillo
2026-05-28 17:06 ` Mehdi Djait [this message]
2026-05-27 17:05 ` [PATCH v5 3/3] ACPI: scan: Honor _DEP for Intel CVS devices Miguel Vadillo
2026-05-28 17:06 ` Mehdi Djait
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=ahh15eCp2hNeuIF1@mdjait-mobl \
--to=mehdi.djait@linux.intel.com \
--cc=antti.laakso@linux.intel.com \
--cc=atul.raut@intel.com \
--cc=kieran.bingham@ideasonboard.com \
--cc=linux-media@vger.kernel.org \
--cc=miguel.vadillo@intel.com \
--cc=sakari.ailus@linux.intel.com \
--cc=wei.a.xu@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