From: Kevin Hao <kexin.hao@windriver.com>
To: "Maciej W. Rozycki" <macro@linux-mips.org>
Cc: Clemens Ladisch <clemens@ladisch.de>,
venkatesh.pallipadi@intel.com, bob.picco@hp.com,
mingo@redhat.com, tglx@linutronix.de,
linux-kernel@vger.kernel.org, Balaji Rao <balajirrao@gmail.com>
Subject: Re: [PATCH] x86: Get irq for hpet timer
Date: Fri, 30 May 2008 13:32:05 +0800 [thread overview]
Message-ID: <1212125525.8050.23.camel@kevin-desktop> (raw)
In-Reply-To: <Pine.LNX.4.55.0805291319250.8254@cliff.in.clinika.pl>
On Thu, 2008-05-29 at 15:32 +0100, Maciej W. Rozycki wrote:
> CONFIG_PCI is optional for the x86 platform. You could argue this is a
> bug in acpi_register_gsi() and I tend to agree -- I think the existence of
> the ELCR is implied for ACPI-compliant systems, though I am happy to be
> corrected. The ACPI spec does not mention the register, but quotes:
> "Existing industry standard register interfaces to: CMOS, PIC, PITs, ..."
Oh, I overlook the existence of CONFIG_PCI.
After look into the code, I think we should add a acpi_pic_set_trigger
to replace eisa_set_level_irq and remove CONFIG_PCI dependency.
>
> Anyway, blindly attaching to an IRQ line is not a terribly good idea as
> there may be an edge-triggered line from a device wired there after all.
Yes, I agree with you. But at present we have not a better way to
resolve this problem.
Thanks,
Kevin
next prev parent reply other threads:[~2008-05-30 5:33 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-05-16 6:05 Kevin Hao
2008-05-16 7:53 ` Balaji Rao R
2008-05-16 8:03 ` Kevin Hao
2008-05-16 8:30 ` Balaji Rao
2008-05-16 8:46 ` Clemens Ladisch
2008-05-16 9:14 ` Kevin Hao
2008-05-19 16:10 ` Clemens Ladisch
2008-05-19 21:21 ` Maciej W. Rozycki
2008-05-20 9:03 ` Kevin Hao
2008-05-20 15:46 ` Maciej W. Rozycki
2008-05-21 8:28 ` Clemens Ladisch
2008-05-22 3:47 ` Maciej W. Rozycki
2008-05-22 7:27 ` Kevin Hao
2008-05-22 15:25 ` Maciej W. Rozycki
2008-05-28 10:42 ` Kevin Hao
2008-05-29 3:13 ` Maciej W. Rozycki
2008-05-29 10:41 ` Kevin Hao
2008-05-29 14:32 ` Maciej W. Rozycki
2008-05-30 5:32 ` Kevin Hao [this message]
2008-06-02 9:35 ` Ingo Molnar
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=1212125525.8050.23.camel@kevin-desktop \
--to=kexin.hao@windriver.com \
--cc=balajirrao@gmail.com \
--cc=bob.picco@hp.com \
--cc=clemens@ladisch.de \
--cc=linux-kernel@vger.kernel.org \
--cc=macro@linux-mips.org \
--cc=mingo@redhat.com \
--cc=tglx@linutronix.de \
--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®