From: marc.zyngier@arm.com (Marc Zyngier)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH v5] PCI: Xilinx NWL: Modifying irq chip for legacy interrupts
Date: Thu, 9 Feb 2017 12:14:59 +0000 [thread overview]
Message-ID: <131228fb-d3f8-3836-3713-e948ed30d398@arm.com> (raw)
In-Reply-To: <8520D5D51A55D047800579B094147198263E68AA@XAP-PVEXMBX02.xlnx.xilinx.com>
On 09/02/17 12:01, Bharat Kumar Gogada wrote:
>> On 06/02/17 07:03, Bharat Kumar Gogada wrote:
>>> +static struct irq_chip nwl_leg_irq_chip = {
>>> + .name = "nwl_pcie:legacy",
>>> + .irq_enable = nwl_unmask_leg_irq,
>>> + .irq_disable = nwl_mask_leg_irq,
>>
>> You don't need these two if they are implemented in terms of mask/unmask.
>
> These are being invoked by some drivers other than interrupt flow.
> Ex: drivers/net/wireless/ath/ath9k/main.c
> static int ath_reset_internal(struct ath_softc *sc, struct ath9k_channel *hchan)
> {
> ....
> disable_irq(sc->irq);
> tasklet_disable(&sc->intr_tq);
> ...
> ...
> enable_irq(sc->irq);
> spin_unlock_bh(&sc->sc_pcu_lock);
> }
> For us masking/unmasking is the way to enable/disable interrupts.
And if you looked at the way disable_irq is implemented, you would have
found out that it falls back to masking if there is no disable method,
preserving the semantic you expect.
M.
--
Jazz is not dead. It just smells funny...
next prev parent reply other threads:[~2017-02-09 12:14 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-02-06 7:03 [PATCH v5] PCI: Xilinx NWL: Modifying irq chip for legacy interrupts Bharat Kumar Gogada
2017-02-09 8:51 ` Marc Zyngier
2017-02-09 12:01 ` Bharat Kumar Gogada
2017-02-09 12:14 ` Marc Zyngier [this message]
2017-02-09 15:16 ` Bharat Kumar Gogada
2017-02-09 16:03 ` Marc Zyngier
2017-02-09 16:25 ` Bharat Kumar Gogada
2017-03-01 9:47 ` Bharat Kumar Gogada
2017-03-07 5:48 ` Bharat Kumar Gogada
-- strict thread matches above, loose matches on Subject: below --
2017-04-14 15:04 Bharat Kumar Gogada
2017-05-17 22:13 ` 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=131228fb-d3f8-3836-3713-e948ed30d398@arm.com \
--to=marc.zyngier@arm.com \
--cc=linux-arm-kernel@lists.infradead.org \
/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