From: Sakari Ailus <sakari.ailus@linux.intel.com>
To: Wentong Wu <wentong.wu@intel.com>
Cc: gregkh@linuxfoundation.org, tomas.winkler@intel.com,
hdegoede@redhat.com, andriy.shevchenko@linux.intel.com,
alexander.usyskin@intel.com, zhifeng.wang@intel.com,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH 2/2] mei: Add MEI hardware support for IVSC device
Date: Wed, 29 Nov 2023 09:26:47 +0000 [thread overview]
Message-ID: <ZWcD18B916Xs1JiU@kekkonen.localdomain> (raw)
In-Reply-To: <1701174846-16316-3-git-send-email-wentong.wu@intel.com>
Hi Wentong,
On Tue, Nov 28, 2023 at 08:34:06PM +0800, Wentong Wu wrote:
> The protocol used for the IVSC device to communicate with HOST is MEI.
> The MEI hardware interfaces for the IVSC device are implemented.
>
> The APIs are exposed by MEI framework to mei clients, e.g. mei_csi and
> mei_ace.
>
> Signed-off-by: Wentong Wu <wentong.wu@intel.com>
> Reviewed-by: Alexander Usyskin <alexander.usyskin@intel.com>
> Reviewed-by: Sakari Ailus <sakari.ailus@linux.intel.com>
> ---
> drivers/misc/mei/Kconfig | 13 ++
> drivers/misc/mei/Makefile | 3 +
> drivers/misc/mei/platform-vsc.c | 442 ++++++++++++++++++++++++++++++++++++++++
> 3 files changed, 458 insertions(+)
> create mode 100644 drivers/misc/mei/platform-vsc.c
>
> diff --git a/drivers/misc/mei/Kconfig b/drivers/misc/mei/Kconfig
> index 470957a..2c5312b 100644
> --- a/drivers/misc/mei/Kconfig
> +++ b/drivers/misc/mei/Kconfig
> @@ -71,6 +71,19 @@ config INTEL_MEI_VSC_HW
> This driver can also be built as a module. If so, the module
> will be called mei-vsc-hw.
>
> +config INTEL_MEI_VSC
> + tristate "Intel visual sensing controller device with ME interface"
> + select INTEL_MEI_VSC_HW
Changing the select here to depends on addresses the Kconfig option
dependency issue (as select just blindly selects the options while ignoring
their dependencies).
I wouldn't mind having a single Kconfig option for the two drivers either.
They're always used together, aren't they?
> + depends on INTEL_MEI
> + help
> + Intel MEI over SPI driver for Intel visual sensing controller
> + (IVSC) device embedded in IA platform. It supports camera sharing
> + between IVSC for context sensing and IPU for typical media usage.
> + Select this config will enable transport layer for IVSC device.
> +
> + This driver can also be built as a module. If so, the module
> + will be called mei-vsc.
> +
> source "drivers/misc/mei/hdcp/Kconfig"
> source "drivers/misc/mei/pxp/Kconfig"
> source "drivers/misc/mei/gsc_proxy/Kconfig"
--
Regards,
Sakari Ailus
next prev parent reply other threads:[~2023-11-29 9:27 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-11-28 12:34 [PATCH 0/2] mei: Add " Wentong Wu
2023-11-28 12:34 ` [PATCH 1/2] mei: Add transport driver " Wentong Wu
2023-12-06 7:40 ` Winkler, Tomas
2023-11-28 12:34 ` [PATCH 2/2] mei: Add MEI hardware support " Wentong Wu
2023-11-28 22:50 ` kernel test robot
2023-11-29 9:26 ` Sakari Ailus [this message]
2023-11-29 10:21 ` Andy Shevchenko
2023-11-29 10:26 ` Sakari Ailus
2023-11-29 14:11 ` Wu, Wentong
2023-11-29 12:28 ` Krzysztof Kozlowski
2023-11-29 13:56 ` Wu, Wentong
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=ZWcD18B916Xs1JiU@kekkonen.localdomain \
--to=sakari.ailus@linux.intel.com \
--cc=alexander.usyskin@intel.com \
--cc=andriy.shevchenko@linux.intel.com \
--cc=gregkh@linuxfoundation.org \
--cc=hdegoede@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=tomas.winkler@intel.com \
--cc=wentong.wu@intel.com \
--cc=zhifeng.wang@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
all inboxes | Powered by JetHome®