All of lore.kernel.org
 help / color / mirror / Atom feed
From: Alex Davis <alex14641@yahoo.com>
To: "mjg59@srcf.ucam.org" <mjg59@srcf.ucam.org>,
	"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
	Levente Kurusa <levex@linux.com>
Subject: Re: [PATCH] dell-laptop: add parameter to disable the backlight device.
Date: Sun, 8 Dec 2013 12:38:16 -0800 (PST)	[thread overview]
Message-ID: <1386535096.90326.YahooMailBasic@web160402.mail.bf1.yahoo.com> (raw)
In-Reply-To: <52A47CCC.50000@linux.com>



--------------------------------------------
On Sun, 12/8/13, Levente Kurusa <levex@linux.com> wrote:

> Subject: Re: [PATCH] dell-laptop: add parameter to disable the backlight device.
> To: "Alex Davis" <alex14641@yahoo.com>, "mjg59@srcf.ucam.org" <mjg59@srcf.ucam.org>, >"linux->kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
> Date: Sunday, December 8, 2013, 9:06 AM
 
 
 >>2013-12-08 14:40, Alex Davis:
 >> I have a Dell Inspiron N7010 Laptop with Intel
 graphics. When the dell-laptop module is loaded,
 >> two backlight device devices are created;
 dell_backlight, and intel_backlight from the Intel
 >> graphics driver. The dell_backlight device is
 non-functional, but the graphics subsystem uses
 >> it instead of the functioning intel_backlight device.
 The result is that, when running KDE,
 >> screen brightness cannot be controlled. I've added a
 module parameter, disable_backlight
 >> which, when true, will disable the dell_backlight
 device, and leave only the intel_backlight:
 >> with this, screen brightness can be controlled.
 >> 
 
> Hi,
 
 >I think it would be better if we could figure out why the
 >dell_blacklight device is not working rather than disabling
 >it.
 
 
> Regarding your patch, it creates a memory leak as you:
>  * allocate a platform device
>  * you add it
>  * you allocated a page for SMI
> 
> Your if(disable_blacklight) code should go
> where it checks the DMI.
> 
> -- Regards,
> Levente Kurusa

Levante,

You are correct. The existing code also has a memory leak. I will submit a patch for that.


 

  reply	other threads:[~2013-12-08 20:44 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-12-08 13:40 [PATCH] dell-laptop: add parameter to disable the backlight device Alex Davis
2013-12-08 14:06 ` Levente Kurusa
2013-12-08 20:38   ` Alex Davis [this message]
2013-12-08 23:43     ` Alex Davis

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=1386535096.90326.YahooMailBasic@web160402.mail.bf1.yahoo.com \
    --to=alex14641@yahoo.com \
    --cc=levex@linux.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mjg59@srcf.ucam.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.