From: Maximilian Luz <luzmaximilian@gmail.com>
To: Ivor Wanders <ivor@iwanders.net>,
Jean Delvare <jdelvare@suse.com>,
Guenter Roeck <linux@roeck-us.net>,
Jonathan Corbet <corbet@lwn.net>,
Hans de Goede <hdegoede@redhat.com>,
Mark Gross <markgross@kernel.org>
Cc: linux-hwmon@vger.kernel.org, linux-doc@vger.kernel.org,
linux-kernel@vger.kernel.org,
platform-driver-x86@vger.kernel.org
Subject: Re: [PATCH v2 2/2] platform/surface: aggregator_registry: add entry for fan speed
Date: Sat, 30 Dec 2023 18:19:18 +0100 [thread overview]
Message-ID: <224b0db9-4fab-4a7e-b240-a2b60f06c52d@gmail.com> (raw)
In-Reply-To: <33a556e3-a7ac-47a3-a621-4db12dbac208@gmail.com>
On 12/29/23 23:42, Maximilian Luz wrote:
> On 12/28/23 01:34, Ivor Wanders wrote:
>> Add an entry for the fan speed function.
>> Add this new entry to the Surface Pro 9 group.
>>
>> Signed-off-by: Ivor Wanders <ivor@iwanders.net>
>> Link: https://github.com/linux-surface/kernel/pull/144
>> ---
>> Changes in v2:
>> - No changes in this patch.
>> ---
>> drivers/platform/surface/surface_aggregator_registry.c | 7 +++++++
>> 1 file changed, 7 insertions(+)
>>
>> diff --git a/drivers/platform/surface/surface_aggregator_registry.c b/drivers/platform/surface/surface_aggregator_registry.c
>> index 530db4db7..b0db25886 100644
>> --- a/drivers/platform/surface/surface_aggregator_registry.c
>> +++ b/drivers/platform/surface/surface_aggregator_registry.c
>> @@ -74,6 +74,12 @@ static const struct software_node ssam_node_tmp_pprof = {
>> .parent = &ssam_node_root,
>> };
>> +/* Fan speed function. */
>> +static const struct software_node ssam_node_fan_speed = {
>> + .name = "ssam:01:05:01:01:01",
>> + .parent = &ssam_node_root,
>> +};
>
> I would prefer if we could keep the subsystem prefix for node names. So
> something like `ssam_node_tmp_fan_speed`.
Please disregard that comment. Somehow I thought it's part of the TMP
subsystem, but it's in its own FAN subsystem. So all is good.
> Otherwise, this looks good to me. With that changed:
>
> Reviewed-by: Maximilian Luz <luzmaximilian@gmail.com>
>
>> +
>> /* Tablet-mode switch via KIP subsystem. */
>> static const struct software_node ssam_node_kip_tablet_switch = {
>> .name = "ssam:01:0e:01:00:01",
>> @@ -319,6 +325,7 @@ static const struct software_node *ssam_node_group_sp9[] = {
>> &ssam_node_bat_ac,
>> &ssam_node_bat_main,
>> &ssam_node_tmp_pprof,
>> + &ssam_node_fan_speed,
>> &ssam_node_pos_tablet_switch,
>> &ssam_node_hid_kip_keyboard,
>> &ssam_node_hid_kip_penstash,
prev parent reply other threads:[~2023-12-30 17:19 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-12-28 0:34 [PATCH v2 0/2] Surface fan monitoring driver Ivor Wanders
2023-12-28 0:34 ` [PATCH v2 1/2] hwmon: add fan speed monitoring driver for Surface devices Ivor Wanders
2023-12-28 15:28 ` Armin Wolf
2023-12-28 23:50 ` Ivor Wanders
2023-12-30 16:32 ` Maximilian Luz
2023-12-30 22:46 ` Ivor Wanders
2023-12-28 0:34 ` [PATCH v2 2/2] platform/surface: aggregator_registry: add entry for fan speed Ivor Wanders
2023-12-29 22:42 ` Maximilian Luz
2023-12-30 17:19 ` Maximilian Luz [this message]
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=224b0db9-4fab-4a7e-b240-a2b60f06c52d@gmail.com \
--to=luzmaximilian@gmail.com \
--cc=corbet@lwn.net \
--cc=hdegoede@redhat.com \
--cc=ivor@iwanders.net \
--cc=jdelvare@suse.com \
--cc=linux-doc@vger.kernel.org \
--cc=linux-hwmon@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux@roeck-us.net \
--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