From: Takashi Iwai <tiwai@suse.de>
To: Mark Brown <broonie@kernel.org>
Cc: alsa-devel@alsa-project.org, Vinod Koul <vinod.koul@intel.com>,
liam.r.girdwood@linux.intel.com, patches.audio@intel.com,
Jeeja KP <jeeja.kp@intel.com>,
"Subhransu S. Prusty" <subhransu.s.prusty@intel.com>
Subject: Re: [PATCH v4 5/7] ASoC: intel - add Skylake HDA audio driver
Date: Tue, 02 Jun 2015 12:48:50 +0200 [thread overview]
Message-ID: <s5hvbf6e67h.wl-tiwai@suse.de> (raw)
In-Reply-To: <20150602104233.GG14071@sirena.org.uk>
At Tue, 2 Jun 2015 11:42:33 +0100,
Mark Brown wrote:
>
> On Mon, Jun 01, 2015 at 07:32:14AM +0200, Takashi Iwai wrote:
> > Vinod Koul wrote:
>
> > > > > + ret = request_threaded_irq(hda->pci->irq, azx_interrupt,
> > > > > + azx_threaded_handler,
> > > > > + hda->msi ? 0 : IRQF_SHARED,
> > > > > + KBUILD_MODNAME, sbus);
>
> > > > Why not just always request the interrupt as shared - we don't seem to
> > > > care in the interrupt handling code?
>
> > > I think we can move this to shared only
>
> > MSI is the exclusive irq, thus shouldn't be shared.
>
> Why does the driver care though? IRQF_SHARED is advertising the
> capabilities of the hander, not a requirement on the hardware - if the
> interrupt physically can't be shared then the ability to share it will
> never get used but that shouldn't matter.
Because the kernel doesn't guarantee the exclusiveness of irq handler
registration as long as you pass IRQF_SHARED. That is, if we keep
IRQF_SHARED and another driver tries to request_irq() for the same irq
with again IRQF_SHARED. But this shouldn't happen with MSI.
Takashi
next prev parent reply other threads:[~2015-06-02 10:48 UTC|newest]
Thread overview: 57+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-05-11 10:53 [PATCH v4 0/7] ASoC: intel - add skylake PCM driver Vinod Koul
2015-05-11 10:53 ` [PATCH v4 1/7] ASoC: hda - add ASoC HDA codec match function Vinod Koul
2015-05-22 12:56 ` Mark Brown
2015-05-22 13:35 ` Takashi Iwai
2015-05-22 17:41 ` Mark Brown
2015-05-22 18:13 ` Takashi Iwai
2015-05-23 5:51 ` Vinod Koul
2015-05-25 10:48 ` Mark Brown
2015-05-25 11:21 ` Vinod Koul
2015-05-25 11:55 ` Takashi Iwai
2015-05-25 13:58 ` Mark Brown
2015-05-26 5:24 ` Takashi Iwai
2015-05-26 13:32 ` Mark Brown
2015-05-26 13:41 ` Takashi Iwai
2015-05-26 19:43 ` Mark Brown
2015-05-27 6:05 ` Takashi Iwai
2015-05-27 18:34 ` Mark Brown
2015-05-27 19:17 ` Takashi Iwai
2015-05-28 19:53 ` Mark Brown
2015-05-29 4:58 ` Takashi Iwai
2015-05-29 8:15 ` Vinod Koul
2015-05-29 17:35 ` Mark Brown
2015-06-01 5:05 ` Vinod Koul
2015-06-02 10:38 ` Mark Brown
2015-06-02 12:25 ` Vinod Koul
2015-05-11 10:54 ` [PATCH v4 2/7] ALSA: hda - add new HDA registers Vinod Koul
2015-05-22 12:58 ` Mark Brown
2015-05-22 13:32 ` Takashi Iwai
2015-05-11 10:54 ` [PATCH v4 3/7] ASoC: hda - add asoc hda core bus, controller and stream helpers Vinod Koul
2015-05-26 18:51 ` Mark Brown
2015-05-27 5:40 ` Vinod Koul
2015-05-11 10:54 ` [PATCH v4 4/7] ASoC: intel - add Skylake HDA platform driver Vinod Koul
2015-05-11 10:54 ` [PATCH v4 5/7] ASoC: intel - add Skylake HDA audio driver Vinod Koul
2015-05-29 17:41 ` Mark Brown
2015-05-29 18:25 ` Takashi Iwai
2015-06-02 10:45 ` Mark Brown
2015-06-02 10:53 ` Takashi Iwai
2015-06-02 11:07 ` Mark Brown
2015-06-02 11:57 ` Takashi Iwai
2015-06-02 12:39 ` Vinod Koul
2015-06-02 14:30 ` Mark Brown
2015-06-01 5:13 ` Vinod Koul
2015-06-01 5:32 ` Takashi Iwai
2015-06-02 10:42 ` Mark Brown
2015-06-02 10:48 ` Takashi Iwai [this message]
2015-06-02 11:10 ` Mark Brown
2015-06-02 11:44 ` Takashi Iwai
2015-06-02 12:29 ` Vinod Koul
2015-05-11 10:54 ` [PATCH v4 6/7] ASoC: intel - add makefile support for SKL driver Vinod Koul
2015-05-11 10:54 ` [PATCH v4 7/7] ASoC: intel - adds support for decoupled mode in skl driver Vinod Koul
2015-05-22 12:20 ` [PATCH v4 0/7] ASoC: intel - add skylake PCM driver Vinod Koul
2015-05-22 13:12 ` Mark Brown
2015-05-25 6:57 ` Takashi Iwai
2015-05-25 11:24 ` Vinod Koul
2015-05-25 11:58 ` Takashi Iwai
2015-05-26 4:14 ` Vinod Koul
2015-05-26 5:27 ` Takashi Iwai
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=s5hvbf6e67h.wl-tiwai@suse.de \
--to=tiwai@suse.de \
--cc=alsa-devel@alsa-project.org \
--cc=broonie@kernel.org \
--cc=jeeja.kp@intel.com \
--cc=liam.r.girdwood@linux.intel.com \
--cc=patches.audio@intel.com \
--cc=subhransu.s.prusty@intel.com \
--cc=vinod.koul@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;
as well as URLs for NNTP newsgroup(s).