From: "Balaji Rao R" <balajirrao@gmail.com>
To: "Kevin Hao" <kexin.hao@windriver.com>
Cc: venkatesh.pallipadi@intel.com, clemens@ladisch.de,
bob.picco@hp.com, mingo@redhat.com, tglx@linutronix.de,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH] x86: Get irq for hpet timer
Date: Fri, 16 May 2008 13:23:52 +0530 [thread overview]
Message-ID: <569c97d20805160053n8a5deceu25c8b37f02e02842@mail.gmail.com> (raw)
In-Reply-To: <1210917912.10881.1.camel@kevin-desktop>
On Fri, May 16, 2008 at 11:35 AM, Kevin Hao <kexin.hao@windriver.com> wrote:
>
> Hi,
>
> x86: get irq for hpet timer
>
> HPET timer's IRQ is 0 by default, so we have to select which irq
> will be used for these timers. We wait to set the timer's irq until
> we really turn on interrupt in order to reduce the chance of
> conflicting with some legacy device.
>
Yes, this is alright. But i've seen some machines where we have a
valid IRQ in 'devp->hd_hdwirq' which you should not ignore. So, first
check if it is zero and only then do a hpet_timer_get_irq.
--
warm regards
Balaji Rao
NITK Surathkal
next prev parent reply other threads:[~2008-05-16 7:54 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 [this message]
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
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=569c97d20805160053n8a5deceu25c8b37f02e02842@mail.gmail.com \
--to=balajirrao@gmail.com \
--cc=bob.picco@hp.com \
--cc=clemens@ladisch.de \
--cc=kexin.hao@windriver.com \
--cc=linux-kernel@vger.kernel.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®