From: "Ilpo Järvinen" <ilpo.jarvinen@linux.intel.com>
To: Luke Jones <luke@ljones.dev>
Cc: platform-driver-x86@vger.kernel.org,
LKML <linux-kernel@vger.kernel.org>,
acpi4asus-user@lists.sourceforge.net, hdegoede@redhat.com,
corentin.chary@gmail.com, markgross@kernel.org,
jdelvare@suse.com, linux@roeck-us.net
Subject: Re: [PATCH v2 1/1] platform/x86: asus-wmi: add support for ASUS screenpad
Date: Mon, 8 May 2023 11:21:10 +0300 (EEST) [thread overview]
Message-ID: <39570a-d3a-13b9-f2d-e75b3d60c6c4@linux.intel.com> (raw)
In-Reply-To: <TWL7UR.KE812U8BYMG8@ljones.dev>
[-- Attachment #1: Type: text/plain, Size: 2372 bytes --]
On Sat, 6 May 2023, Luke Jones wrote:
> On Fri, May 5 2023 at 16:08:16 +0300, Ilpo Järvinen
> <ilpo.jarvinen@linux.intel.com> wrote:
> > On Fri, 5 May 2023, Luke D. Jones wrote:
> >
> > > Add support for the WMI methods used to turn off and adjust the
> > > brightness of the secondary "screenpad" device found on some high-end
> > > ASUS laptops like the GX650P series and others.
> > >
> > > These methods are utilised in a new backlight device named:
> > > - asus_screenpad
> > >
> > > Signed-off-by: Luke D. Jones <luke@ljones.dev>
> > > ---
> > > @@ -3208,6 +3209,129 @@ static int is_display_toggle(int code)
> > > return 0;
> > > }
> > >
> > > +/* Screenpad backlight */
> > > +
> > > +static int read_screenpad_backlight_power(struct asus_wmi *asus)
> > > +{
> > > + int ret = asus_wmi_get_devstate_simple(asus,
> > > ASUS_WMI_DEVID_SCREENPAD_POWER);
> >
> > Please move this to own line because now you have the extra newline
> > in between the call and error handling.
>
> I don't understand what you mean sorry. Remove the new line or:
> int ret;
> ret = asus_wmi_get_devstate_simple(asus, ASUS_WMI_DEVID_SCREENPAD_POWER);
Don't do:
int func()
{
int ret = func();
if (ret < 0)
return ret;
...
}
But do:
int func()
{
int ret;
ret = func();
if (ret < 0)
return ret;
...
}
This keeps the error handling next to the actual call following the usual
error handling pattern (natural logic grouping). The added clarity is well
worth the one extra line required.
> > > +static int update_screenpad_bl_status(struct backlight_device *bd)
> > > +{
> > > + struct asus_wmi *asus = bl_get_data(bd);
> > > + int power, err = 0;
> > > + u32 ctrl_param;
> > > +
> > > + power = read_screenpad_backlight_power(asus);
> > > + if (power == -ENODEV)
> > > + return err;
> >
> > Just return 0. Or is there perhaps something wrong/missing here?
>
> I thought the correct thing was to return any possible error state (here,
> anything less than 0 would be an error, right?)
I think this was covered already but here what I meant, use either:
return 0;
because err is always 0 at that point, or:
return power;
Depending on which is correct, I wasn't sure because you had this after
it:
> > > + else if (power < 0)
> > > + return power;
...So I thought you might really intentionally wanted to return 0 there.
--
i.
next prev parent reply other threads:[~2023-05-08 8:22 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-05-05 4:30 [PATCH v2 0/1] platform/x86: asus-wmi: add support for ASUS screenpad Luke D. Jones
2023-05-05 4:30 ` [PATCH v2 1/1] " Luke D. Jones
2023-05-05 13:08 ` Ilpo Järvinen
2023-05-05 23:43 ` Luke Jones
2023-05-06 1:30 ` Guenter Roeck
2023-05-06 3:48 ` Luke Jones
2023-05-06 4:43 ` Guenter Roeck
2023-05-06 8:09 ` Luke Jones
2023-05-06 13:24 ` Guenter Roeck
2023-05-08 8:21 ` Ilpo Järvinen [this message]
2023-05-06 11:52 ` [PATCH v2 0/1] " Hans de Goede
2023-05-15 12:39 ` Hans de Goede
2023-05-15 22:34 ` Luke Jones
2023-05-25 11:09 ` Hans de Goede
2023-06-04 4:52 ` Luke Jones
2023-06-06 8:58 ` Hans de Goede
2023-06-06 22:45 ` Luke Jones
2023-06-13 10:27 ` 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=39570a-d3a-13b9-f2d-e75b3d60c6c4@linux.intel.com \
--to=ilpo.jarvinen@linux.intel.com \
--cc=acpi4asus-user@lists.sourceforge.net \
--cc=corentin.chary@gmail.com \
--cc=hdegoede@redhat.com \
--cc=jdelvare@suse.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux@roeck-us.net \
--cc=luke@ljones.dev \
--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