X86 platform drivers
 help / color / mirror / Atom feed
From: Maximilian Luz <luzmaximilian@gmail.com>
To: Hans de Goede <hdegoede@redhat.com>
Cc: Maximilian Luz <luzmaximilian@gmail.com>,
	Mark Gross <markgross@kernel.org>,
	platform-driver-x86@vger.kernel.org,
	linux-kernel@vger.kernel.org
Subject: [PATCH 07/10] platform/surface: aggregator: Add comment for KIP subsystem category
Date: Fri, 20 May 2022 20:34:19 +0200	[thread overview]
Message-ID: <20220520183422.7185-8-luzmaximilian@gmail.com> (raw)
In-Reply-To: <20220520183422.7185-1-luzmaximilian@gmail.com>

The KIP subsystem (full name unknown, abbreviation has been obtained
through reverse engineering) handles detachable peripherals such as the
keyboard cover on the Surface Pro X and Surface Pro 8.

It is currently not entirely clear what this subsystem entails, but at
the very least it provides event notifications for when the keyboard
cover on the Surface Pro X and Surface Pro 8 have been detached or
re-attached, as well as the state that the keyboard cover is currently
in (e.g. folded-back, folded laptop-like, closed, etc.).

Signed-off-by: Maximilian Luz <luzmaximilian@gmail.com>
---
 include/linux/surface_aggregator/serial_hub.h | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/include/linux/surface_aggregator/serial_hub.h b/include/linux/surface_aggregator/serial_hub.h
index c3de43edcffa..26b95ec12733 100644
--- a/include/linux/surface_aggregator/serial_hub.h
+++ b/include/linux/surface_aggregator/serial_hub.h
@@ -306,7 +306,7 @@ enum ssam_ssh_tc {
 	SSAM_SSH_TC_LPC = 0x0b,
 	SSAM_SSH_TC_TCL = 0x0c,
 	SSAM_SSH_TC_SFL = 0x0d,
-	SSAM_SSH_TC_KIP = 0x0e,
+	SSAM_SSH_TC_KIP = 0x0e,	/* Manages detachable peripherals (Pro X/8 keyboard cover) */
 	SSAM_SSH_TC_EXT = 0x0f,
 	SSAM_SSH_TC_BLD = 0x10,
 	SSAM_SSH_TC_BAS = 0x11,	/* Detachment system (Surface Book 2/3). */
-- 
2.36.1


  parent reply	other threads:[~2022-05-20 18:34 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-05-20 18:34 [PATCH 00/10] platform/surface: aggregator: Add support for client hot-removal Maximilian Luz
2022-05-20 18:34 ` [PATCH 01/10] platform/surface: aggregator: Allow devices to be marked as hot-removed Maximilian Luz
2022-05-20 18:34 ` [PATCH 02/10] platform/surface: aggregator: Allow notifiers to avoid communication on unregistering Maximilian Luz
2022-05-20 18:34 ` [PATCH 03/10] platform/surface: aggregator_registry: Use client device wrappers for notifier registration Maximilian Luz
2022-05-20 18:34 ` [PATCH 04/10] power/supply: surface_charger: " Maximilian Luz
2022-05-20 18:34 ` [PATCH 05/10] power/supply: surface_battery: " Maximilian Luz
2022-05-20 18:34 ` [PATCH 06/10] HID: surface-hid: Add support for hot-removal Maximilian Luz
2022-05-26 23:55   ` kernel test robot
2022-05-20 18:34 ` Maximilian Luz [this message]
2022-05-20 18:34 ` [PATCH 08/10] platform/surface: aggregator_registry: Generify subsystem hub functionality Maximilian Luz
2022-05-20 18:34 ` [PATCH 09/10] platform/surface: aggregator_registry: Add KIP device hub Maximilian Luz
2022-05-20 18:34 ` [PATCH 10/10] platform/surface: aggregator_registry: Add support for keyboard cover on Surface Pro 8 Maximilian Luz

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=20220520183422.7185-8-luzmaximilian@gmail.com \
    --to=luzmaximilian@gmail.com \
    --cc=hdegoede@redhat.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=markgross@kernel.org \
    --cc=platform-driver-x86@vger.kernel.org \
    /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