From: "H. Peter Anvin" <hpa@zytor.com>
To: Thomas Gleixner <tglx@linutronix.de>, carl peng <carlpeng008@gmail.com>
Cc: mingo@redhat.com, x86@kernel.org, pingfank@linux.vnet.ibm.com,
yoshihiro.yunomae.ez@hitachi.com, linux-kernel@vger.kernel.org
Subject: Re: Does it need to implement irq_set_type method in the ioapic_chip?
Date: Wed, 19 Feb 2014 05:28:15 -0800 [thread overview]
Message-ID: <5e7b7684-2f67-4dca-b889-94b942cc72dd@email.android.com> (raw)
In-Reply-To: <alpine.DEB.2.02.1402191259590.4468@ionos.tec.linutronix.de>
In the casee of your ACPI-enabled AMBA device I believe the BIOS, which provides the ACPI tables, is expected to set the interrupt type.
On February 19, 2014 4:07:09 AM PST, Thomas Gleixner <tglx@linutronix.de> wrote:
>On Wed, 19 Feb 2014, carl peng wrote:
>> At last, the device will be connected to AMBA bus, so the interrupt
>> pin will be connected to IOAPIC through AMBA bus. The device now
>> is in the pre-silicon verification stage.
>>
>> So my question is the same:
>> Why does APIC driver not implement the irq_set_type method? if
>
>Because we do not need it. All devices are properly connected and
>configured by the BIOS and bus discovery.
>
>> implement it, will supply more free space for the device driver
>> developer(they can set the interrupttrigger mode by calling
>request_irq).
>
>There are 3 different mechanisms already to tell the kernel to
>configure a particular irq line: ACPI, MP Tables and SFI.
>
>That's the way x86 does its interrupt configuration and there is no
>need to provide another one.
>
>Thanks,
>
> tglx
--
Sent from my mobile phone. Please pardon brevity and lack of formatting.
next prev parent reply other threads:[~2014-02-19 13:29 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <CAC5e1FoLrHWSa_7BnRt-u451ZJOVqKhSpbyp8O_ExDbgcXtU+g@mail.gmail.com>
2014-02-18 20:13 ` Thomas Gleixner
2014-02-19 2:32 ` carl peng
2014-02-19 2:34 ` H. Peter Anvin
2014-02-19 3:13 ` carl peng
2014-02-19 12:07 ` Thomas Gleixner
2014-02-19 13:28 ` H. Peter Anvin [this message]
2014-02-19 16:37 ` H. Peter Anvin
2014-02-18 7:18 carl peng
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=5e7b7684-2f67-4dca-b889-94b942cc72dd@email.android.com \
--to=hpa@zytor.com \
--cc=carlpeng008@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@redhat.com \
--cc=pingfank@linux.vnet.ibm.com \
--cc=tglx@linutronix.de \
--cc=x86@kernel.org \
--cc=yoshihiro.yunomae.ez@hitachi.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
Powered by JetHome