public inbox for linux-acpi@vger.kernel.org
 help / color / mirror / Atom feed
From: Jean Delvare <khali@linux-fr.org>
To: Matthew Garrett <mjg59@srcf.ucam.org>
Cc: linux-acpi@vger.kernel.org,
	LM Sensors <lm-sensors@lm-sensors.org>,
	Len Brown <lenb@kernel.org>
Subject: Re: [PATCH] hwmon: (asus_atk0110) Don't load if ACPI  resources aren't enforced
Date: Tue, 30 Mar 2010 22:32:51 +0200	[thread overview]
Message-ID: <20100330223251.76c6b000@hyperion.delvare> (raw)
In-Reply-To: <20100330194835.GA32322@srcf.ucam.org>

On Tue, 30 Mar 2010 20:48:36 +0100, Matthew Garrett wrote:
> On Tue, Mar 30, 2010 at 09:47:32PM +0200, Jean Delvare wrote:
> 
> > The asus_atk0110 driver loads automatically. The user doesn't configure
> > anything, and it just loads. That's the problem. If the driver didn't
> > load automatically, I wouldn't care. If you know of any way to prevent
> > the asus_atk0110 driver from auto-loading as soon as
> > acpi_enforce_resouce=lax or =no is passed, I am fine with this as well.
> > This is what I wanted to do originally, but I couldn't find a way to do
> > it, which is why I went for the more radical option of preventing the
> > asus_atk0110 driver from loading.
> 
> echo blacklist asus_atk0110 >/etc/modprobe.d/hwmon_blacklist.conf

Sure, but why do you insist on having the user configure this manually
when we can automate this at the kernel level? When
acpi_enforce_resouce=yes, the kernel doesn't let non-ACPI driver be
loaded, so I fail to see why we let ACPI drivers (for which we also
have native drivers) load when acpi_enforce_resouce=no.

Or is there something really wrong with my patch?

-- 
Jean Delvare

  reply	other threads:[~2010-03-30 20:32 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20100309135636.373a40a9@hyperion.delvare>
2010-03-30 10:03 ` [lm-sensors] [PATCH] hwmon: (asus_atk0110) Don't load if ACPI resources aren't enforced Jean Delvare
2010-03-30 13:21   ` Matthew Garrett
2010-03-30 19:47     ` Jean Delvare
2010-03-30 19:48       ` Matthew Garrett
2010-03-30 20:32         ` Jean Delvare [this message]
2010-03-30 21:10           ` Matthew Garrett
2010-03-30 21:45             ` [lm-sensors] " Luca Tettamanti
2010-03-30 21:53               ` Matthew Garrett
2010-03-31  7:30                 ` Jean Delvare
2010-03-31 12:51                   ` Matthew Garrett
2010-03-31 13:25                     ` Jean Delvare
2010-03-31 13:27                       ` Matthew Garrett
2010-03-31 13:37                         ` Jean Delvare
2010-03-31  7:42             ` Jean Delvare

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=20100330223251.76c6b000@hyperion.delvare \
    --to=khali@linux-fr.org \
    --cc=lenb@kernel.org \
    --cc=linux-acpi@vger.kernel.org \
    --cc=lm-sensors@lm-sensors.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox