From: Hans de Goede <hdegoede@redhat.com>
To: Luke Jones <luke@ljones.dev>, Mohamed Ghanmi <mohamed.ghanmi@supcom.tn>
Cc: corentin.chary@gmail.com,
"Ilpo Järvinen" <ilpo.jarvinen@linux.intel.com>,
platform-driver-x86@vger.kernel.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH v4 1/1] platform/x86: asus-wmi: add support for vivobook fan profiles
Date: Thu, 1 Aug 2024 16:01:12 +0200 [thread overview]
Message-ID: <c3be1b7f-8a4c-42d8-9a5d-6a341c5beb33@redhat.com> (raw)
In-Reply-To: <d21a1be5-7589-49e4-a96b-cddf9b6c15eb@app.fastmail.com>
Hi,
On 7/31/24 11:06 PM, Luke Jones wrote:
...
>>>>> If Hans and Ilpo don't have any requirements then:
>>>>>
>>>>> Signed-off-by: Luke D. Jones <luke@ljones.dev>
>
> I have no issues with this patch and it needs to be merged before I submit a stream of work. My signed-off tag is above.
Reading back the comments about the function names I believe that
the asus_wmi_platform_profile_mode_[to|from]_vivo() names are fine.
And the rest of the patch looks good to me to:
Reviewed-by: Hans de Goede <hdegoede@redhat.com>
I have merged this into my review-hans branch now with one small change,
both asus_wmi_platform_profile_mode_[to|from]_vivo() ended in:
return mode;
}
I have dropped the empty line after the return mode; statement
(in both functions) while merging this.
I've also dropped a spurious whitespace change (extra empty line)
added to asus_wmi_platform_profile_get().
Luke, please base your coming work on top of pdx86/review-hans.
Regards,
Hans
p.s.
One thing which I noticed while reviewing is this:
static int fan_curve_get_factory_default(struct asus_wmi *asus, u32 fan_dev)
{
struct fan_curve_data *curves;
u8 buf[FAN_CURVE_BUF_LEN];
int err, fan_idx;
u8 mode = 0;
if (asus->throttle_thermal_policy_dev)
mode = asus->throttle_thermal_policy_mode;
/* DEVID_<C/G>PU_FAN_CURVE is switched for OVERBOOST vs SILENT */
if (mode == 2)
mode = 1;
else if (mode == 1)
mode = 2;
err = asus_wmi_evaluate_method_buf(asus->dsts_id, fan_dev, mode, buf,
FAN_CURVE_BUF_LEN);
Since asus->throttle_thermal_policy_mode stores the raw mode, which has
silent/overboost swapped for vivo notebooks I wonder if we should still
do the mode 1/2 swapping here when on a vivo notebook ?
I have a feeling the swapping here should not be done when one a vivo
notebook but I'm not sure.
If the swapping here should be skipped on Vivobooks please submit
a separate follow-up patch for that.
Regards,
Hans
prev parent reply other threads:[~2024-08-01 14:01 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-06-09 14:48 [PATCH v4 0/1] " Mohamed Ghanmi
2024-06-09 14:48 ` [PATCH v4 1/1] " Mohamed Ghanmi
2024-06-11 5:31 ` Luke Jones
2024-06-24 10:04 ` Mohamed Ghanmi
2024-06-24 21:46 ` Luke Jones
2024-07-31 12:07 ` Mohamed Ghanmi
2024-07-31 21:06 ` Luke Jones
2024-08-01 14:01 ` Hans de Goede [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=c3be1b7f-8a4c-42d8-9a5d-6a341c5beb33@redhat.com \
--to=hdegoede@redhat.com \
--cc=corentin.chary@gmail.com \
--cc=ilpo.jarvinen@linux.intel.com \
--cc=linux-kernel@vger.kernel.org \
--cc=luke@ljones.dev \
--cc=mohamed.ghanmi@supcom.tn \
--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
all inboxes | Powered by JetHome®