Linux Input Archive mirror
 help / color / mirror / Atom feed
From: Zhang Lixu <lixu.zhang@intel.com>
To: linux-input@vger.kernel.org, srinivas.pandruvada@linux.intel.com,
	jikos@kernel.org, benjamin.tissoires@redhat.com
Cc: lixu.zhang@intel.com
Subject: [PATCH 0/5] HID: intel-ish-hid: Implement loading firmware from host feature
Date: Mon,  6 May 2024 09:30:35 +0800	[thread overview]
Message-ID: <20240506013040.10700-1-lixu.zhang@intel.com> (raw)

This patch series is comprised of 5 patches. The first two patches are to add documentation
for firmware loading. The third and fourth patches introduce support for the 'Load Main
Firmware from Host' feature in the ISHTP driver, applicable to Lunar Lake and subsequent
platforms. The last patch enhances the firmware reset handler in the ISH driver. This
addresses an issue where the driver receives two MNG_RESET_NOTIFY messages upon implementing
the 'Load Main Firmware from Host' feature.

This patch series is based on the following 3 commits, which have already been included in the linux-next/master branch.
- HID: intel-ish-hid: ipc: Fix dev_err usage with uninitialized dev->devc
- HID: intel-ish-hid: Use PCI_VDEVICE() and rename device ID macros
- HID: intel-ish-hid: ipc: Add Lunar Lake-M PCI device ID

Qianru Huang (2):
  Documentation: hid: intel-ish-hid: remove section numbering
  Documentation: hid: intel-ish-hid: add section for firmware loading

Zhang Lixu (3):
  HID: intel-ish-hid: Add driver_data for specifying the firmware
    filename
  HID: intel-ish-hid: Implement loading firmware from host feature
  HID: intel-ish-hid: handler multiple MNG_RESET_NOTIFY messages

 Documentation/hid/intel-ish-hid.rst         | 137 +++++++---
 drivers/hid/intel-ish-hid/Makefile          |   1 +
 drivers/hid/intel-ish-hid/ipc/ipc.c         |   7 +-
 drivers/hid/intel-ish-hid/ipc/pci-ish.c     |  18 +-
 drivers/hid/intel-ish-hid/ishtp/hbm.c       |  21 ++
 drivers/hid/intel-ish-hid/ishtp/init.c      |   8 +
 drivers/hid/intel-ish-hid/ishtp/ishtp-dev.h |  28 ++
 drivers/hid/intel-ish-hid/ishtp/loader.c    | 275 ++++++++++++++++++++
 drivers/hid/intel-ish-hid/ishtp/loader.h    | 226 ++++++++++++++++
 9 files changed, 681 insertions(+), 40 deletions(-)
 create mode 100644 drivers/hid/intel-ish-hid/ishtp/loader.c
 create mode 100644 drivers/hid/intel-ish-hid/ishtp/loader.h


base-commit: 9221b2819b8a4196eecf5476d66201be60fbcf29
-- 
2.34.1


             reply	other threads:[~2024-05-06  1:30 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-05-06  1:30 Zhang Lixu [this message]
2024-05-06  1:30 ` [PATCH 1/5] Documentation: hid: intel-ish-hid: remove section numbering Zhang Lixu
2024-05-06  1:30 ` [PATCH 2/5] Documentation: hid: intel-ish-hid: add section for firmware loading Zhang Lixu
2024-05-06  1:30 ` [PATCH 3/5] HID: intel-ish-hid: Add driver_data for specifying the firmware filename Zhang Lixu
2024-05-06  1:30 ` [PATCH 4/5] HID: intel-ish-hid: Implement loading firmware from host feature Zhang Lixu
2024-05-06  1:30 ` [PATCH 5/5] HID: intel-ish-hid: handler multiple MNG_RESET_NOTIFY messages Zhang Lixu
2024-05-06 21:34 ` [PATCH 0/5] HID: intel-ish-hid: Implement loading firmware from host feature Jiri Kosina

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=20240506013040.10700-1-lixu.zhang@intel.com \
    --to=lixu.zhang@intel.com \
    --cc=benjamin.tissoires@redhat.com \
    --cc=jikos@kernel.org \
    --cc=linux-input@vger.kernel.org \
    --cc=srinivas.pandruvada@linux.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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).