From: "Ilpo Järvinen" <ilpo.jarvinen@linux.intel.com>
To: Matthias Fetzer <kontakt@matthias-fetzer.de>
Cc: hmh@hmh.eng.br, Hans de Goede <hdegoede@redhat.com>,
ibm-acpi-devel@lists.sourceforge.net,
platform-driver-x86@vger.kernel.org,
LKML <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH] platform/x86: thinkpad_acpi: Add Thinkpad Edge E531 fan support
Date: Mon, 12 Aug 2024 10:17:48 +0300 (EEST) [thread overview]
Message-ID: <456fea75-b6d2-4150-86db-ce385e2860b1@linux.intel.com> (raw)
In-Reply-To: <5a22f1ff-44e9-4e1a-bdbe-cc168f718693@matthias-fetzer.de>
[-- Attachment #1: Type: text/plain, Size: 1846 bytes --]
On Fri, 9 Aug 2024, Matthias Fetzer wrote:
>
> Thanks for the review!
>
> Am 08.08.24 um 15:14 schrieb Ilpo Järvinen:
> > On Sun, 14 Jul 2024, Matthias Fetzer wrote:
> >
> > > Fan control on the E531 is done using the ACPI methods FANG and
> > > FANW. The correct parameters and register values were found by
> > > analyzing EC firmware as well as DSDT. This has been tested on
> > > my Thinkpad Edge E531 (6885CTO, BIOS HEET52WW 1.33).
> > >
> > > Signed-off-by: Matthias Fetzer <kontakt@matthias-fetzer.de>
> > > @@ -8157,6 +8213,7 @@ static int fan2_get_speed(unsigned int *speed)
> > > static int fan_set_level(int level)
> > > {
> > > + int rc;
> > > if (!fan_control_allowed)
> > > return -EPERM;
> > > @@ -8206,6 +8263,36 @@ static int fan_set_level(int level)
> > > tp_features.fan_ctrl_status_undef = 0;
> > > break;
> > > + case TPACPI_FAN_WR_ACPI_FANW:
> > > + if ((!(level & TP_EC_FAN_AUTO) &&
> > > + ((level < 0) || (level > 7))) ||
> > > + (level & TP_EC_FAN_FULLSPEED))
> > > + return -EINVAL;
> >
> > I'd split this into two to make it more readable:
> >
> > if (!(level & TP_EC_FAN_AUTO) && (level < 0 || level > 7))
> > return -EINVAL;
> > if (level & TP_EC_FAN_FULLSPEED)
> > return -EINVAL;
>
> This is much better, thanks.
>
> >
> > I'm not sure if -EINVAL is really the right code to return though in these
> > cases.
> >
>
> I thought that since those are invalid values/parameters the return code of
> -EINVAL
> would be a good choice. What do you suggest to use instead?
Actually, now that I look into it more carefully, forget what I said.
I think -EINVAL is correct to return in these cases because the input
value is invalid (I previously assumed something else based on the
define names).
--
i.
next prev parent reply other threads:[~2024-08-12 7:17 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-07-14 16:50 Matthias Fetzer
2024-08-08 13:14 ` Ilpo Järvinen
2024-08-09 21:06 ` Matthias Fetzer
2024-08-12 7:17 ` Ilpo Järvinen [this message]
2024-08-12 12:33 ` Hans de Goede
2024-08-13 21:24 ` [PATCH v2] " Matthias Fetzer
2024-08-14 10:47 ` Ilpo Järvinen
2024-08-14 21:39 ` [PATCH v3] " Matthias Fetzer
2024-08-15 9:43 ` Ilpo Järvinen
2024-08-15 19:00 ` kernel test robot
2024-08-15 20:17 ` Matthias Fetzer
2024-08-16 13:38 ` Ilpo Järvinen
2024-08-16 14:12 ` [PATCH v4] " Matthias Fetzer
2024-08-16 14:15 ` Ilpo Järvinen
2024-08-19 14:33 ` Hans de Goede
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=456fea75-b6d2-4150-86db-ce385e2860b1@linux.intel.com \
--to=ilpo.jarvinen@linux.intel.com \
--cc=hdegoede@redhat.com \
--cc=hmh@hmh.eng.br \
--cc=ibm-acpi-devel@lists.sourceforge.net \
--cc=kontakt@matthias-fetzer.de \
--cc=linux-kernel@vger.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
all inboxes | Powered by JetHome®