mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Bjorn Helgaas <bjorn.helgaas@hp.com>
To: Randy Dunlap <randy_d_dunlap@linux.intel.com>
Cc: lkml <linux-kernel@vger.kernel.org>, akpm <akpm@osdl.org>,
	venki <venkatesh.pallipadi@intel.com>,
	bob.picco@hp.com, Adam Belay <ambx1@neo.rr.com>
Subject: Re: [PATCH 1/3] hpet: allow fixed_mem32 ACPI resource type
Date: Wed, 12 Oct 2005 14:08:32 -0600	[thread overview]
Message-ID: <200510121408.32163.bjorn.helgaas@hp.com> (raw)
In-Reply-To: <20051012115814.1d367a94.randy_d_dunlap@linux.intel.com>

On Wednesday 12 October 2005 12:58 pm, Randy Dunlap wrote:
> Allow the ACPI HPET description table to use a resource type
> of FIXED_MEM32 for the HPET reource.  Use the fixed resoure
> size of 1 KB for the HPET resource as per the HPET spec.

I have a patch in my tree to convert HPET from an ACPI
driver to a PNP driver, using PNPACPI.  That should take
care of issues like this.

But my patch is waiting on some PNP work by Adam to allow
PNPACPI devices to have more than 2 IRQs.

In the meantime, I think your patch is fine.

> +#define HPET_RANGE_SIZE		1024	/* from HPET spec */

Out of curiosity, why do you need this?  ACPI_RSTYPE_FIXED_MEM32
contains a length field, and my patch uses it.  Did you run
into some firmware that supplies incorrect information about the
size of the HPET MMIO area?

Another minor HPET nit I fixed is that it currently doesn't
use request_mem_region().  I did it in PNP terms, so it's
waiting on Adam's work, but maybe it'd be worth an interim
patch until that's ready.

  reply	other threads:[~2005-10-12 20:08 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-10-12 18:58 Randy Dunlap
2005-10-12 20:08 ` Bjorn Helgaas [this message]
2005-10-12 21:55   ` Randy.Dunlap

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=200510121408.32163.bjorn.helgaas@hp.com \
    --to=bjorn.helgaas@hp.com \
    --cc=akpm@osdl.org \
    --cc=ambx1@neo.rr.com \
    --cc=bob.picco@hp.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=randy_d_dunlap@linux.intel.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

all inboxes | Powered by JetHome®