The Linux Kernel Mailing List
 help / color / mirror / Atom feed
From: Hao Yao <hao.yao@intel.com>
To: Wentong Wu <wentong.wu@intel.com>, <gregkh@linuxfoundation.org>,
	<tomas.winkler@intel.com>, <hdegoede@redhat.com>,
	<krzk@kernel.org>
Cc: <andriy.shevchenko@linux.intel.com>,
	<sakari.ailus@linux.intel.com>, <alexander.usyskin@intel.com>,
	<zhifeng.wang@intel.com>, <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH v2 0/2] misc: mei: Add support for IVSC device
Date: Wed, 6 Dec 2023 13:58:00 +0800	[thread overview]
Message-ID: <fdc7e70b-67a6-4e5d-a622-450cf4270690@intel.com> (raw)
In-Reply-To: <1701651344-20723-1-git-send-email-wentong.wu@intel.com>

Wentong,

On mainline v6.6, I cherry-picked IVSC/LCJA related patches and these v2 
patches, added Intel IPU6 driver on Github, then made some changes on 
IPU6 HAL to auto link IVSC device. I tested the build on a Dell Latitude 
7440 which is using HI556 camera sensor and it previews normally.

If it's properly, you can add my "Tested-by:" tag.

Tested-by: Hao Yao <hao.yao@intel.com>

On 2023/12/4 08:55, Wentong Wu wrote:
> The Intel visual sensing controller (IVSC) device is designed to
> control the camera sharing between host IPU for media usage and
> IVSC for context sensing (face detection).
> 
> IVSC is exposed to host as a SPI device and the protocol used
> for communicating with host is MEI. This driver implements the
> transport protocol and MEI hardware interfaces for IVSC device.
> 
> The firmware downloading for IVSC device is implemented as well.
> 
> ---
> v2:
>    - change to `depends on INTEL_MEI_VSC_HW` for INTEL_MEI_VSC Kconfig
>    - remove MODULE_ALIAS and add MODULE_DEVICE_TABLE in platform-vsc.c
> 
> Wentong Wu (2):
>    mei: Add transport driver for IVSC device
>    mei: Add MEI hardware support for IVSC device
> 
>   drivers/misc/mei/Kconfig         |  24 ++
>   drivers/misc/mei/Makefile        |   7 +
>   drivers/misc/mei/platform-vsc.c  | 450 +++++++++++++++++++++
>   drivers/misc/mei/vsc-fw-loader.c | 822 +++++++++++++++++++++++++++++++++++++++
>   drivers/misc/mei/vsc-tp.c        | 555 ++++++++++++++++++++++++++
>   drivers/misc/mei/vsc-tp.h        |  50 +++
>   6 files changed, 1908 insertions(+)
>   create mode 100644 drivers/misc/mei/platform-vsc.c
>   create mode 100644 drivers/misc/mei/vsc-fw-loader.c
>   create mode 100644 drivers/misc/mei/vsc-tp.c
>   create mode 100644 drivers/misc/mei/vsc-tp.h
> 

  parent reply	other threads:[~2023-12-06  5:58 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-12-04  0:55 [PATCH v2 0/2] misc: mei: Add support for IVSC device Wentong Wu
2023-12-04  0:55 ` [PATCH v2 1/2] mei: Add transport driver " Wentong Wu
2023-12-04  0:55 ` [PATCH v2 2/2] mei: Add MEI hardware support " Wentong Wu
2023-12-06  7:42   ` Winkler, Tomas
2023-12-06  5:58 ` Hao Yao [this message]
2023-12-06  7:14   ` [PATCH v2 0/2] misc: mei: Add " 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=fdc7e70b-67a6-4e5d-a622-450cf4270690@intel.com \
    --to=hao.yao@intel.com \
    --cc=alexander.usyskin@intel.com \
    --cc=andriy.shevchenko@linux.intel.com \
    --cc=gregkh@linuxfoundation.org \
    --cc=hdegoede@redhat.com \
    --cc=krzk@kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=sakari.ailus@linux.intel.com \
    --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