mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Dmitry Torokhov <dmitry.torokhov@gmail.com>
To: Bob Rodgers <Robert_Rodgers@dell.com>
Cc: Matthew Garrett <mjg59@srcf.ucam.org>,
	"lenb@kernel.org" <lenb@kernel.org>,
	"rpurdie@rpsys.net" <rpurdie@rpsys.net>,
	Linux-kernel <linux-kernel@vger.kernel.org>,
	Louis Davis <Louis_Davis@dell.com>,
	Jim Dailey <Jim_Dailey@dell.com>,
	Mario Limonciello <Mario_Limonciello@dell.com>,
	Michael Brown <Michael_E_Brown@dell.com>,
	Matt Domsch <Matt_Domsch@dell.com>,
	Dan Carpenter <error27@gmail.com>
Subject: Re: [PATCH] v2 - Add Dell Business Class Netbook LED driver
Date: Tue, 16 Feb 2010 21:49:11 -0800	[thread overview]
Message-ID: <20100217054911.GE7160@core.coreip.homeip.net> (raw)
In-Reply-To: <4B75617B.4000805@dell.com>

Hi Bob,

On Fri, Feb 12, 2010 at 08:11:07AM -0600, Bob Rodgers wrote:
> This patch adds an LED driver to support the Dell Activity LED on the 
> Dell Latitude 2100 netbook and future products to come. The Activity LED 
> is visible externally in the lid so classroom instructors can observe it 
> from a distance. The driver uses the sysfs led_class and provides a 
> standard LED interface. This driver is ready for submission upstream.
> 
> Signed-off by: Bob Rodgers <Robert_Rodgers@dell.com>
> Signed-off-by: Louis Davis <Louis_Davis@dell.com>
> Signed-off-by: Jim Dailey <Jim_Dailey@dell.com>, Developers
> Acked-by: Matthew Garrett <mjg@redhat.com>
> 
> ---
> Description of changes in v2:
> 1) Added X86 and ACPI_WMI dependencies to the Kconfig file.
> 2) Removed platform_driver and platform_device as they are not needed in this driver.
> 

With the platform device stiff gone it looks much better, still a few
things:

> +
> +#include <linux/platform_device.h>

Do you still need platform_device.h?

> +#include <linux/acpi.h>
> +#include <linux/leds.h>
> +
> +MODULE_AUTHOR("Louis Davis/Jim Dailey");
> +MODULE_DESCRIPTION("Dell LED Control Driver");
> +MODULE_LICENSE("GPL");
> +
> +#define DELL_LED_BIOS_GUID "F6E4FE6E-909D-47cb-8BAB-C9F6F2F8D396"
> +MODULE_ALIAS("wmi:" DELL_LED_BIOS_GUID);
> +
> +/* Error Result Codes: */
> +#define INVALID_DEVICE_ID	250
> +#define INVALID_PARAMETER	251
> +#define INVALID_BUFFER		252
> +#define INTERFACE_ERROR		253
> +#define UNSUPPORTED_COMMAND	254
> +#define UNSPECIFIED_ERROR	255
> +
> +/* Device ID */
> +#define DEVICE_ID_PANEL_BACK	1
> +
> +/* LED Commands */
> +#define CMD_LED_ON	16
> +#define CMD_LED_OFF	17
> +#define CMD_LED_BLINK	18
> +
> +struct bios_args {
> +	unsigned char length;
> +	unsigned char result_code;
> +	unsigned char device_id;
> +	unsigned char command;
> +	unsigned char on_time;
> +	unsigned char off_time;
> +};
> +
> +static u8 dell_led_perform_fn(u8 length,
> +		u8 result_code,
> +		u8 device_id,
> +		u8 command,
> +		u8 on_time,
> +		u8 off_time)
> +{
> +	struct bios_args *bios_return;
> +	u8 return_code;
> +	union acpi_object *obj;
> +	struct acpi_buffer output = { ACPI_ALLOCATE_BUFFER, NULL };
> +	struct acpi_buffer input;
> +
> +	struct bios_args args;
> +	args.length = length;
> +	args.result_code = result_code;
> +	args.device_id = device_id;
> +	args.command = command;
> +	args.on_time = on_time;
> +	args.off_time = off_time;
> +
> +	input.length = sizeof(struct bios_args);
> +	input.pointer = &args;
> +
> +	wmi_evaluate_method(DELL_LED_BIOS_GUID,
> +		1,
> +		1,
> +		&input,
> +		&output);

This needs error handling.

> +
> +	obj = output.pointer;
> +
> +	if (!obj || obj->type != ACPI_TYPE_BUFFER)
> +		return -EINVAL;

You are leaking obj when obj is not NULL and is not a buffer.

> +
> +static int __init dell_led_init(void)
> +{
> +	int error = 0;
> +
> +	if (!wmi_has_guid(DELL_LED_BIOS_GUID)) {
> +		printk(KERN_DEBUG KBUILD_MODNAME
> +			": could not find: DELL_LED_BIOS_GUID\n");

Please ocnsider using pr_xxx() family.

> +		return -ENODEV;
> +	}
> +
> +	error = led_off();
> +	if (error != 0) {
> +		printk(KERN_DEBUG KBUILD_MODNAME

This is a warning or an error, not a debug.

Thank you.

-- 
Dmitry

      reply	other threads:[~2010-02-17  5:55 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-02-12 14:11 Bob Rodgers
2010-02-17  5:49 ` Dmitry Torokhov [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=20100217054911.GE7160@core.coreip.homeip.net \
    --to=dmitry.torokhov@gmail.com \
    --cc=Jim_Dailey@dell.com \
    --cc=Louis_Davis@dell.com \
    --cc=Mario_Limonciello@dell.com \
    --cc=Matt_Domsch@dell.com \
    --cc=Michael_E_Brown@dell.com \
    --cc=Robert_Rodgers@dell.com \
    --cc=error27@gmail.com \
    --cc=lenb@kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mjg59@srcf.ucam.org \
    --cc=rpurdie@rpsys.net \
    /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®