From: Andy Shevchenko <andy.shevchenko@gmail.com>
To: Daniel Dadap <ddadap@nvidia.com>
Cc: Platform Driver <platform-driver-x86@vger.kernel.org>,
Hans de Goede <hdegoede@redhat.com>,
mario.limonciello@outlook.com, pobrn@protonmail.org,
Andy Shevchenko <andy@infradead.org>,
Darren Hart <dvhart@infradead.org>,
Aaron Plattner <aplattner@nvidia.com>
Subject: Re: [PATCH v3] platform/x86: Add driver for ACPI WMAA EC-based backlight control
Date: Wed, 25 Aug 2021 12:05:54 +0300 [thread overview]
Message-ID: <CAHp75VfjSrq7vF=ry1dTHJWbKLF9AqK8kZbddO-1A3FQ5pCvhQ@mail.gmail.com> (raw)
In-Reply-To: <20210824220437.14175-1-ddadap@nvidia.com>
On Wed, Aug 25, 2021 at 1:09 AM Daniel Dadap <ddadap@nvidia.com> wrote:
>
> A number of upcoming notebook computer designs drive the internal
> display panel's backlight PWM through the Embedded Controller (EC).
> This EC-based backlight control can be plumbed through to an ACPI
> "WMAA" method interface, which in turn can be wrapped by WMI with
> the GUID handle 603E9613-EF25-4338-A3D0-C46177516DB7.
>
> Add a new driver, aliased to the WMAA WMI GUID, to expose a sysfs
> backlight class driver to control backlight levels on systems with
> EC-driven backlights.
I tried to avoid repetition of the comments given by others.
So, mine below.
...
> +config WMAA_BACKLIGHT_WMI
> + tristate "ACPI WMAA Backlight Driver"
> + depends on ACPI_WMI
> + depends on BACKLIGHT_CLASS_DEVICE
> + help
> + This driver provides a sysfs backlight interface for notebook
> + systems which expose the WMAA ACPI method and an associated WMI
> + wrapper to drive LCD backlight levels through the system's
> + Embedded Controller.
Please, add a sentence to tell how the module will be called. There
are plenty of examples in the kernel.
...
> +struct wmaa_args {
> + u32 set;
> + u32 val;
> + u32 ret;
> + u32 ignored[3];
> +};
I guess this structure deserves a kernel doc.
...
> +static const struct wmi_device_id wmaa_backlight_wmi_id_table[] = {
> + { .guid_string = WMAA_WMI_GUID },
> + { },
No comma for termination.
> +};
...
> +static int wmaa_backlight_get_brightness(struct backlight_device *bd)
> +{
> + u32 level;
> + int ret;
> +
> + ret = wmaa_get_brightness(&level);
> + WARN_ON(ret != 0);
Why?
> + return ret == 0 ? level : 0;
> +}
...
> +static int wmaa_backlight_wmi_probe(struct wmi_device *w, const void *ctx)
> +{
> + struct backlight_properties props = {0};
{} is slightly better.
> + struct wmi_wmaa_priv *priv;
> + u32 source;
> + int ret;
> +
> + priv = devm_kmalloc(&w->dev, sizeof(*priv), GFP_KERNEL);
> + if(!priv)
> + return -ENOMEM;
> + wdev = w;
I'm wondering if it's possible to avoid having a global variable.
> + ret = wmaa_get_brightness_source(&source);
> + if (ret)
> + goto done;
> +
> + if (source != WMAA_SOURCE_EC) {
> + ret = -ENODEV;
> + goto done;
> + }
> +
> + // Register a backlight handler
> + props.type = BACKLIGHT_PLATFORM;
> + ret = wmaa_get_max_brightness(&props.max_brightness);
> + if (ret)
> + goto done;
> +
> + ret = wmaa_get_brightness(&props.brightness);
> + if (ret)
> + goto done;
> +
> + priv->backlight = backlight_device_register("wmaa_backlight",
> + NULL, NULL, &wmaa_backlight_ops, &props);
> + if (IS_ERR(priv->backlight))
> + return PTR_ERR(priv->backlight);
> +
> + dev_set_drvdata(&w->dev, priv);
> +done:
Useless. Return directly.
> + return ret;
> +}
...
> +static struct wmi_driver wmaa_backlight_wmi_driver = {
> + .driver = {
> + .name = "wmaa-backlight",
> + },
> + .probe = wmaa_backlight_wmi_probe,
> + .remove = wmaa_backlight_wmi_remove,
> + .id_table = wmaa_backlight_wmi_id_table,
> +};
> +
Redundant blank line.
> +module_wmi_driver(wmaa_backlight_wmi_driver);
...
> +
> +MODULE_ALIAS("wmi:"WMAA_WMI_GUID);
Can you move this closer to GUID? But I'm not sure what is the
preferred style. Hans?
--
With Best Regards,
Andy Shevchenko
next prev parent reply other threads:[~2021-08-25 9:06 UTC|newest]
Thread overview: 52+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <DM6PR19MB2636AB267CD321DE40EF324AFA730@DM6PR19MB2636.namprd19.prod.outlook.com>
[not found] ` <20200731202154.11382-1-ddadap@nvidia.com>
[not found] ` <20200731202154.11382-2-ddadap@nvidia.com>
2020-11-10 9:34 ` [PATCH v2 2/2] platform/x86: wmi: fail wmi_driver_register when no GUID is found Hans de Goede
2020-11-12 18:54 ` Daniel Dadap
2021-08-24 22:04 ` [PATCH v3] platform/x86: Add driver for ACPI WMAA EC-based backlight control Daniel Dadap
2021-08-24 22:47 ` Barnabás Pőcze
2021-08-25 16:36 ` Daniel Dadap
2021-08-25 22:26 ` Daniel Dadap
2021-08-27 16:47 ` Daniel Dadap
2021-08-27 17:12 ` Daniel Dadap
2021-08-25 9:05 ` Andy Shevchenko [this message]
2021-08-25 16:47 ` Daniel Dadap
2021-08-25 22:06 ` Thomas Weißschuh
2021-08-25 22:28 ` Daniel Dadap
2021-08-26 13:35 ` Andy Shevchenko
2021-08-26 15:39 ` Daniel Dadap
2021-08-31 22:49 ` [PATCH v4] " Daniel Dadap
2021-09-01 9:25 ` Thomas Weißschuh
2021-09-02 2:12 ` Daniel Dadap
2021-09-02 10:19 ` Thomas Weißschuh
2021-09-02 20:15 ` Daniel Dadap
2021-09-02 20:31 ` Hans de Goede
2021-09-02 21:47 ` [PATCH v5] " Daniel Dadap
2021-09-02 23:20 ` Thomas Weißschuh
2021-09-03 0:22 ` Daniel Dadap
2021-09-03 8:14 ` Andy Shevchenko
2021-09-03 17:55 ` Daniel Dadap
2021-09-03 0:38 ` [PATCH v6] " Daniel Dadap
2021-09-13 9:01 ` Hans de Goede
2021-09-20 13:29 ` Pali Rohár
2021-09-20 13:33 ` Hans de Goede
2021-09-20 13:51 ` Pali Rohár
2021-09-20 17:34 ` Daniel Dadap
2021-09-20 17:55 ` Pali Rohár
2021-09-20 19:38 ` Daniel Dadap
2021-09-20 19:52 ` Pali Rohár
2021-09-21 13:53 ` Hans de Goede
2021-09-21 14:02 ` Pali Rohár
2021-09-21 14:29 ` Daniel Dadap
2021-09-21 14:58 ` Hans de Goede
2021-09-27 20:23 ` [PATCH 1/2] platform/x86: Remove "WMAA" from identifier names in wmaa-backlight-wmi.c Daniel Dadap
2021-09-27 20:23 ` [PATCH 2/2] platform/x86: Rename wmaa-backlight-wmi to nvidia-wmi-ec-backlight Daniel Dadap
2021-10-11 13:00 ` [PATCH 1/2] platform/x86: Remove "WMAA" from identifier names in wmaa-backlight-wmi.c Hans de Goede
2021-09-27 22:52 ` [PATCH v6] platform/x86: Add driver for ACPI WMAA EC-based backlight control Daniel Dadap
2021-09-02 9:28 ` [PATCH v4] " Andy Shevchenko
2021-09-02 9:33 ` Thomas Weißschuh
2021-09-02 9:36 ` Andy Shevchenko
2021-09-01 15:57 ` Andy Shevchenko
2021-09-01 23:12 ` Aaron Plattner
2021-09-02 2:37 ` Daniel Dadap
2021-09-02 9:35 ` Andy Shevchenko
2021-09-02 20:15 ` Daniel Dadap
2021-09-03 8:10 ` Andy Shevchenko
2021-09-02 15:38 ` 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='CAHp75VfjSrq7vF=ry1dTHJWbKLF9AqK8kZbddO-1A3FQ5pCvhQ@mail.gmail.com' \
--to=andy.shevchenko@gmail.com \
--cc=andy@infradead.org \
--cc=aplattner@nvidia.com \
--cc=ddadap@nvidia.com \
--cc=dvhart@infradead.org \
--cc=hdegoede@redhat.com \
--cc=mario.limonciello@outlook.com \
--cc=platform-driver-x86@vger.kernel.org \
--cc=pobrn@protonmail.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;
as well as URLs for NNTP newsgroup(s).