From: Maximilian Luz <luzmaximilian@gmail.com>
To: "Barnabás Pőcze" <pobrn@protonmail.com>
Cc: "linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
"Hans de Goede" <hdegoede@redhat.com>,
"Mark Gross" <mgross@linux.intel.com>,
"Arnd Bergmann" <arnd@arndb.de>,
"Greg Kroah-Hartman" <gregkh@linuxfoundation.org>,
"Rob Herring" <robh@kernel.org>,
"Jiri Slaby" <jirislaby@kernel.org>,
"Rafael J . Wysocki" <rjw@rjwysocki.net>,
"Len Brown" <lenb@kernel.org>, "Blaž Hrastnik" <blaz@mxxn.io>,
"Dorian Stoll" <dorian.stoll@tmsp.io>,
"platform-driver-x86@vger.kernel.org"
<platform-driver-x86@vger.kernel.org>,
"linux-serial@vger.kernel.org" <linux-serial@vger.kernel.org>,
"linux-acpi@vger.kernel.org" <linux-acpi@vger.kernel.org>
Subject: Re: [PATCH 1/9] platform/surface: Add Surface Aggregator subsystem
Date: Thu, 19 Nov 2020 18:35:52 +0100 [thread overview]
Message-ID: <dc6cc00a-4761-96e7-78f6-99dbf2447bad@gmail.com> (raw)
In-Reply-To: <5Qk-wNPtfpjNiK7HHId4qBNTWj9K_2h7fNe15o2J80gZsrSOfVYoKzdzPE8-r3NT7PLjxIgx08YLv2s38CWROho_womMqN2yGl3v13dJlMg=@protonmail.com>
On 11/19/20 4:54 PM, Barnabás Pőcze wrote:
> Hi
[...]
>>>> +enum ssam_ssh_tc {
>>>> + /* Known SSH/EC target categories. */
>>>> + // category 0x00 is invalid for EC use
>>>> + SSAM_SSH_TC_SAM = 0x01, // generic system functionality, real-time clock
>>>> + SSAM_SSH_TC_BAT = 0x02, // battery/power subsystem
>>>> + SSAM_SSH_TC_TMP = 0x03, // thermal subsystem
>>>> + SSAM_SSH_TC_PMC = 0x04,
>>>> + SSAM_SSH_TC_FAN = 0x05,
>>>> + SSAM_SSH_TC_PoM = 0x06,
>>>> + SSAM_SSH_TC_DBG = 0x07,
>>>> + SSAM_SSH_TC_KBD = 0x08, // legacy keyboard (Laptop 1/2)
>>>> + SSAM_SSH_TC_FWU = 0x09,
>>>> + SSAM_SSH_TC_UNI = 0x0a,
>>>> + SSAM_SSH_TC_LPC = 0x0b,
>>>> + SSAM_SSH_TC_TCL = 0x0c,
>>>> + SSAM_SSH_TC_SFL = 0x0d,
>>>> + SSAM_SSH_TC_KIP = 0x0e,
>>>> + SSAM_SSH_TC_EXT = 0x0f,
>>>> + SSAM_SSH_TC_BLD = 0x10,
>>>> + SSAM_SSH_TC_BAS = 0x11, // detachment system (Surface Book 2/3)
>>>> + SSAM_SSH_TC_SEN = 0x12,
>>>> + SSAM_SSH_TC_SRQ = 0x13,
>>>> + SSAM_SSH_TC_MCU = 0x14,
>>>> + SSAM_SSH_TC_HID = 0x15, // generic HID input subsystem
>>>> + SSAM_SSH_TC_TCH = 0x16,
>>>> + SSAM_SSH_TC_BKL = 0x17,
>>>> + SSAM_SSH_TC_TAM = 0x18,
>>>> + SSAM_SSH_TC_ACC = 0x19,
>>>> + SSAM_SSH_TC_UFI = 0x1a,
>>>> + SSAM_SSH_TC_USC = 0x1b,
>>>> + SSAM_SSH_TC_PEN = 0x1c,
>>>> + SSAM_SSH_TC_VID = 0x1d,
>>>> + SSAM_SSH_TC_AUD = 0x1e,
>>>> + SSAM_SSH_TC_SMC = 0x1f,
>>>> + SSAM_SSH_TC_KPD = 0x20,
>>>> + SSAM_SSH_TC_REG = 0x21,
>>>> +};
>>>
>>> Is it known what these abbreviations stand for? Maybe I missed them?
>>
>> The comments state all we really know about these (through observation
>> and experimentation). The table itself has been extracted from the
>> Windows driver, but the abbreviations and values are all we're getting
>> from it.
>
> I see, thanks for the clarification. For some reason, I believed the
> "Known SSH/EC target categories" comment means that those are known, as in,
> it is known what they are for, etc., not just the abbreviation.
Right, that can be misunderstood, sorry. It's probably best if I add a
comment explaining that in a bit more detail and noting where those
values and abbreviations come from.
Thanks,
Max
next prev parent reply other threads:[~2020-11-19 17:36 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-11-15 19:21 [PATCH 0/9] Add support for Microsoft Surface System Aggregator Module Maximilian Luz
2020-11-15 19:21 ` [PATCH 9/9] platform/surface: Add Surface ACPI Notify driver Maximilian Luz
2020-11-17 20:09 ` Randy Dunlap
2020-11-17 20:18 ` Maximilian Luz
[not found] ` <20201115192143.21571-2-luzmaximilian@gmail.com>
2020-11-16 13:33 ` [PATCH 1/9] platform/surface: Add Surface Aggregator subsystem Andy Shevchenko
2020-11-16 17:03 ` Maximilian Luz
2020-11-17 6:05 ` Maximilian Luz
2020-11-18 0:28 ` Barnabás Pőcze
2020-11-18 23:06 ` Maximilian Luz
2020-11-19 15:54 ` Barnabás Pőcze
2020-11-19 17:35 ` Maximilian Luz [this message]
2020-11-24 11:59 ` [PATCH 0/9] Add support for Microsoft Surface System Aggregator Module Hans de Goede
2020-11-24 13:43 ` 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=dc6cc00a-4761-96e7-78f6-99dbf2447bad@gmail.com \
--to=luzmaximilian@gmail.com \
--cc=arnd@arndb.de \
--cc=blaz@mxxn.io \
--cc=dorian.stoll@tmsp.io \
--cc=gregkh@linuxfoundation.org \
--cc=hdegoede@redhat.com \
--cc=jirislaby@kernel.org \
--cc=lenb@kernel.org \
--cc=linux-acpi@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-serial@vger.kernel.org \
--cc=mgross@linux.intel.com \
--cc=platform-driver-x86@vger.kernel.org \
--cc=pobrn@protonmail.com \
--cc=rjw@rjwysocki.net \
--cc=robh@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