From: Jean Delvare <khali@linux-fr.org>
To: "Mark M. Hoffman" <mhoffman@lightlink.com>,
Andrew Morton <akpm@osdl.org>
Cc: Thomas Renninger <trenn@suse.de>,
linux-acpi <linux-acpi@vger.kernel.org>,
linux-kernel <linux-kernel@vger.kernel.org>,
Len Brown <lenb@kernel.org>
Subject: Re: [PATCH 0/5] Detect hwmon and i2c bus drivers interfering with ACPI Operation Region resources
Date: Thu, 25 Oct 2007 17:54:01 +0200 [thread overview]
Message-ID: <20071025175401.6a5ac8cc@hyperion.delvare> (raw)
In-Reply-To: <20071025120438.GJ30546@jupiter.solarsys.private>
Hi Mark,
On Thu, 25 Oct 2007 08:04:38 -0400, Mark M. Hoffman wrote:
> Hi Thomas:
>
> I recently told someone in private that ACPI vs. hwmon conflicts are the
> biggest open problems for the hwmon subsystem. Thank you (and Jean) for
> doing this.
>
> * Thomas Renninger <trenn@suse.de> [2007-10-24 16:31:59 +0200]:
> > Hi,
> >
> > it seems Len's test tree and Linus tree diverged a bit, at least with
> > this patch set things do not apply cleanly.
> >
> > Therefore I post these for discussion whether and in which kernel tree
> > they should end up before doing work for nothing.
> > If they are still a candidate for 2.6.24 (rather unintrusive), pls tell
> > me whether and when I should base them against Len's test/release branch
> > or whatever other tree.
> > If not, it would be great if they can be included into the -mm tree and
> > I can rebase them against this one.
>
> Andrew has already picked this series; I vote for extended time in -mm. On the
> hwmon side, there is almost guaranteed to be fallout from this that may take
> time to resolve.
Of course, otherwise we wouldn't have done it ;)
> > A boot parameter acpi_enforce_resources=strict/lax/no is provided, which
> > is default set to lax:
> > - strict: let conflicting drivers fail to load with an error message
> > - lax: let conflicting driver work normal with a warning message
> > - no: no functional change at all
> > Depending on the feedback and the kind of interferences we see, this
> > should be set to strict at later time.
>
> As long as it's in -mm, you may as well default to =strict right away. This
> will force people to report. Open the floodgates; I hope I don't drown.
Good point. Here's a patch. Andrew, can you please apply this on top of
the other patches? Thanks.
Subject: Enforce ACPI resource conflict checks
In -mm, enforce ACPI resource conflict checks, so that users will report
to us.
This patch is NOT meant to go to Linus at this point.
Signed-off-by: Jean Delvare <khali@linux-fr.org>
---
drivers/acpi/osl.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
--- linux-2.6.24-rc1.orig/drivers/acpi/osl.c 2007-10-24 10:01:16.000000000 +0200
+++ linux-2.6.24-rc1/drivers/acpi/osl.c 2007-10-25 17:13:58.000000000 +0200
@@ -1076,7 +1076,7 @@ __setup("acpi_wake_gpes_always_on", acpi
#define ENFORCE_RESOURCES_LAX 1
#define ENFORCE_RESOURCES_NO 0
-static unsigned int acpi_enforce_resources = ENFORCE_RESOURCES_LAX;
+static unsigned int acpi_enforce_resources = ENFORCE_RESOURCES_STRICT;
static int __init acpi_enforce_resources_setup(char *str)
{
--
Jean Delvare
next prev parent reply other threads:[~2007-10-25 15:54 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-10-24 14:31 [PATCH 0/5] Detect hwmon and i2c bus drivers interfering with ACPI Operation Region resources Thomas Renninger
2007-10-25 3:57 ` Andrew Morton
2007-10-25 13:51 ` Jean Delvare
2007-10-25 13:51 ` Jean Delvare
2007-10-25 20:24 ` Andrew Morton
2007-10-25 20:24 ` Andrew Morton
2007-10-26 19:23 ` Jean Delvare
2007-10-26 19:23 ` Jean Delvare
2007-10-25 12:04 ` Mark M. Hoffman
2007-10-25 15:54 ` Jean Delvare [this message]
2007-10-25 15:06 ` Bjorn Helgaas
2007-10-25 22:55 ` Thomas Renninger
2007-10-26 3:59 ` Bjorn Helgaas
2007-10-26 10:45 ` Thomas Renninger
2007-10-26 13:09 ` Bjorn Helgaas
2007-10-26 20:39 ` Jean Delvare
2007-10-27 15:09 ` Matthew Garrett
2007-10-29 2:50 ` Bjorn Helgaas
2007-10-29 13:11 ` Matthew Garrett
2007-10-30 18:43 ` Jean Delvare
2007-10-25 21:36 ` Len Brown
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=20071025175401.6a5ac8cc@hyperion.delvare \
--to=khali@linux-fr.org \
--cc=akpm@osdl.org \
--cc=lenb@kernel.org \
--cc=linux-acpi@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mhoffman@lightlink.com \
--cc=trenn@suse.de \
/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.