public inbox for linux-acpi@vger.kernel.org
 help / color / mirror / Atom feed
From: Andrew Morton <akpm@osdl.org>
To: Bjorn Helgaas <bjorn.helgaas@hp.com>
Cc: bob.picco@hp.com, robert.picco@hp.com,
	venkatesh.pallipadi@intel.com, linux-acpi@vger.kernel.org,
	len.brown@intel.com, ambx1@neo.rr.com, rdunlap@xenotime.net
Subject: Re: [PATCH] HPET: handle multiple ACPI EXTENDED_IRQ resources
Date: Mon, 13 Feb 2006 13:49:13 -0800	[thread overview]
Message-ID: <20060213134913.13352735.akpm@osdl.org> (raw)
In-Reply-To: <200602131424.28369.bjorn.helgaas@hp.com>

Bjorn Helgaas <bjorn.helgaas@hp.com> wrote:
>
>  Andrew, I know it's late in the 2.6.16 cycle, but it would be really
>  nice if this patch made it.  Without it, HPETs on new HP boxes don't
>  work, so we're going to have to get it in the distros some way or
>  another.

OK..

What about hpet-fix-acpi-memory-range-length-handling.patch?


From: Bjorn Helgaas <bjorn.helgaas@hp.com>

ACPI address space descriptors contain _MIN, _MAX, and _LEN.  _MIN and _MAX
are the bounds within which the region can be moved (this is clarified in
Table 6-38 of the ACPI 3.0 spec).  We should use _LEN to determine the size
of the region, not _MAX - _MIN + 1.

Signed-off-by: Bjorn Helgaas <bjorn.helgaas@hp.com>
Signed-off-by: Andrew Morton <akpm@osdl.org>
---

 drivers/char/hpet.c |    5 +----
 1 files changed, 1 insertion(+), 4 deletions(-)

diff -puN drivers/char/hpet.c~hpet-fix-acpi-memory-range-length-handling drivers/char/hpet.c
--- 25/drivers/char/hpet.c~hpet-fix-acpi-memory-range-length-handling	Tue Feb  7 15:47:01 2006
+++ 25-akpm/drivers/char/hpet.c	Tue Feb  7 15:47:01 2006
@@ -925,11 +925,8 @@ static acpi_status hpet_resources(struct
 	status = acpi_resource_to_address64(res, &addr);
 
 	if (ACPI_SUCCESS(status)) {
-		unsigned long size;
-
-		size = addr.maximum - addr.minimum + 1;
 		hdp->hd_phys_address = addr.minimum;
-		hdp->hd_address = ioremap(addr.minimum, size);
+		hdp->hd_address = ioremap(addr.minimum, addr.address_length);
 
 		if (hpet_is_known(hdp)) {
 			printk(KERN_DEBUG "%s: 0x%lx is busy\n",
_


(It's hard for me to judge when people don't describe what the impact of
the problem is, so thanks for the poke).


  reply	other threads:[~2006-02-13 21:50 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-02-07 23:50 [PATCH] HPET: handle multiple ACPI EXTENDED_IRQ resources Bjorn Helgaas
2006-02-12 22:55 ` Bob Picco
2006-02-13 21:24   ` Bjorn Helgaas
2006-02-13 21:49     ` Andrew Morton [this message]
2006-02-13 21:55       ` Bjorn Helgaas

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=20060213134913.13352735.akpm@osdl.org \
    --to=akpm@osdl.org \
    --cc=ambx1@neo.rr.com \
    --cc=bjorn.helgaas@hp.com \
    --cc=bob.picco@hp.com \
    --cc=len.brown@intel.com \
    --cc=linux-acpi@vger.kernel.org \
    --cc=rdunlap@xenotime.net \
    --cc=robert.picco@hp.com \
    --cc=venkatesh.pallipadi@intel.com \
    /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