From: "Ville Syrjälä" <ville.syrjala@linux.intel.com>
To: "Augustine.Chen" <augustine.chen@intel.com>
Cc: Juergen Gross <jgross@suse.com>,
Dou Liyang <douly.fnst@cn.fujitsu.com>,
alsa-devel@alsa-project.org, tiwai@suse.de,
intel-gfx@lists.freedesktop.org, linux-kernel@vger.kernel.org,
Ingo Molnar <mingo@redhat.com>, "H. Peter Anvin" <hpa@zytor.com>,
Thomas Gleixner <tglx@linutronix.de>,
Jiang Liu <jiang.liu@linux.intel.com>,
pierre-louis.bossart@intel.com
Subject: Re: [PATCH] drm/i915: Remove unused IRQ chip data of HDMI LPE audio
Date: Fri, 8 Dec 2017 13:44:04 +0200 [thread overview]
Message-ID: <20171208114404.GN10981@intel.com> (raw)
In-Reply-To: <20171208093323.2212-1-augustine.chen@intel.com>
On Fri, Dec 08, 2017 at 05:33:23PM +0800, Augustine.Chen wrote:
> The chip data of HDMI LPE audio is set to drm_i915_private which is not
> consistent with the expectation by x86 APIC driver.
Hmm. Why is the apic code looking at data for an irq chip it
hasn't created?
Do we need something like
- dev_priv->lpe_audio.irq = irq_alloc_desc(0);
+ dev_priv->lpe_audio.irq = irq_alloc_desc(-1);
?
That *looks* more correct to me based on a cursory glance at the x86
code, but I didn't trawl very deeply.
> In the case of not
> enabling CONFIG_CPUMASK_OFFSTACK, this would cause kernel panic while doing
> CPU hotplug. Since the dependency of IRQ chip data was removed from HDMI
> LPE audio by Commit 9bd9590997b92fbd79fd028f704f6c584b4439d7 ("drm/i915:
> Stop pretending to mask/unmask LPE audio interrupts"), remove the
> code of setting IRQ chip data to resolve this issue.
>
> Bugzilla: https://bugs.freedesktop.org/show_bug.cgi?id=103731
> Cc: Pierre-Louis Bossart <pierre-louis.bossart@intel.com>
> Cc: Jerome Anand <jerome.anand@intel.com>
> Cc: Takashi Iwai <tiwai@suse.de>
> Signed-off-by: Augustine.Chen <augustine.chen@intel.com>
> ---
> drivers/gpu/drm/i915/intel_lpe_audio.c | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
>
> diff --git a/drivers/gpu/drm/i915/intel_lpe_audio.c b/drivers/gpu/drm/i915/intel_lpe_audio.c
> index 3bf6528..56176f9 100644
> --- a/drivers/gpu/drm/i915/intel_lpe_audio.c
> +++ b/drivers/gpu/drm/i915/intel_lpe_audio.c
> @@ -176,7 +176,7 @@ static int lpe_audio_irq_init(struct drm_i915_private *dev_priv)
> handle_simple_irq,
> "hdmi_lpe_audio_irq_handler");
>
> - return irq_set_chip_data(irq, dev_priv);
> + return 0;
> }
>
> static bool lpe_audio_detect(struct drm_i915_private *dev_priv)
> --
> 1.9.1
>
> _______________________________________________
> Intel-gfx mailing list
> Intel-gfx@lists.freedesktop.org
> https://lists.freedesktop.org/mailman/listinfo/intel-gfx
--
Ville Syrjälä
Intel OTC
_______________________________________________
Intel-gfx mailing list
Intel-gfx@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/intel-gfx
WARNING: multiple messages have this Message-ID (diff)
From: "Ville Syrjälä" <ville.syrjala@linux.intel.com>
To: "Augustine.Chen" <augustine.chen@intel.com>
Cc: intel-gfx@lists.freedesktop.org, alsa-devel@alsa-project.org,
jerome.anand@intel.com, pierre-louis.bossart@intel.com,
tiwai@suse.de, Thomas Gleixner <tglx@linutronix.de>,
Ingo Molnar <mingo@redhat.com>, "H. Peter Anvin" <hpa@zytor.com>,
Jiang Liu <jiang.liu@linux.intel.com>,
Juergen Gross <jgross@suse.com>,
Dou Liyang <douly.fnst@cn.fujitsu.com>,
linux-kernel@vger.kernel.org
Subject: Re: [Intel-gfx] [PATCH] drm/i915: Remove unused IRQ chip data of HDMI LPE audio
Date: Fri, 8 Dec 2017 13:44:04 +0200 [thread overview]
Message-ID: <20171208114404.GN10981@intel.com> (raw)
In-Reply-To: <20171208093323.2212-1-augustine.chen@intel.com>
On Fri, Dec 08, 2017 at 05:33:23PM +0800, Augustine.Chen wrote:
> The chip data of HDMI LPE audio is set to drm_i915_private which is not
> consistent with the expectation by x86 APIC driver.
Hmm. Why is the apic code looking at data for an irq chip it
hasn't created?
Do we need something like
- dev_priv->lpe_audio.irq = irq_alloc_desc(0);
+ dev_priv->lpe_audio.irq = irq_alloc_desc(-1);
?
That *looks* more correct to me based on a cursory glance at the x86
code, but I didn't trawl very deeply.
> In the case of not
> enabling CONFIG_CPUMASK_OFFSTACK, this would cause kernel panic while doing
> CPU hotplug. Since the dependency of IRQ chip data was removed from HDMI
> LPE audio by Commit 9bd9590997b92fbd79fd028f704f6c584b4439d7 ("drm/i915:
> Stop pretending to mask/unmask LPE audio interrupts"), remove the
> code of setting IRQ chip data to resolve this issue.
>
> Bugzilla: https://bugs.freedesktop.org/show_bug.cgi?id=103731
> Cc: Pierre-Louis Bossart <pierre-louis.bossart@intel.com>
> Cc: Jerome Anand <jerome.anand@intel.com>
> Cc: Takashi Iwai <tiwai@suse.de>
> Signed-off-by: Augustine.Chen <augustine.chen@intel.com>
> ---
> drivers/gpu/drm/i915/intel_lpe_audio.c | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
>
> diff --git a/drivers/gpu/drm/i915/intel_lpe_audio.c b/drivers/gpu/drm/i915/intel_lpe_audio.c
> index 3bf6528..56176f9 100644
> --- a/drivers/gpu/drm/i915/intel_lpe_audio.c
> +++ b/drivers/gpu/drm/i915/intel_lpe_audio.c
> @@ -176,7 +176,7 @@ static int lpe_audio_irq_init(struct drm_i915_private *dev_priv)
> handle_simple_irq,
> "hdmi_lpe_audio_irq_handler");
>
> - return irq_set_chip_data(irq, dev_priv);
> + return 0;
> }
>
> static bool lpe_audio_detect(struct drm_i915_private *dev_priv)
> --
> 1.9.1
>
> _______________________________________________
> Intel-gfx mailing list
> Intel-gfx@lists.freedesktop.org
> https://lists.freedesktop.org/mailman/listinfo/intel-gfx
--
Ville Syrjälä
Intel OTC
next prev parent reply other threads:[~2017-12-08 11:44 UTC|newest]
Thread overview: 32+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-12-08 9:33 [PATCH] drm/i915: Remove unused IRQ chip data of HDMI LPE audio Augustine.Chen
2017-12-08 11:16 ` ✓ Fi.CI.BAT: success for " Patchwork
2017-12-08 11:44 ` Ville Syrjälä [this message]
2017-12-08 11:44 ` [Intel-gfx] [PATCH] " Ville Syrjälä
2017-12-08 22:51 ` Thomas Gleixner
2017-12-08 22:51 ` [Intel-gfx] " Thomas Gleixner
2017-12-11 8:33 ` Anand, Jerome
2017-12-11 8:33 ` [Intel-gfx] " Anand, Jerome
2017-12-11 13:20 ` Ville Syrjälä
2017-12-11 13:20 ` [Intel-gfx] " Ville Syrjälä
2017-12-11 13:23 ` Takashi Iwai
2017-12-12 9:26 ` Chen, Augustine
2017-12-12 9:26 ` [Intel-gfx] " Chen, Augustine
2017-12-12 9:45 ` Takashi Iwai
2017-12-12 9:45 ` Takashi Iwai
2017-12-13 9:25 ` Chen, Augustine
2017-12-13 9:25 ` [Intel-gfx] " Chen, Augustine
2017-12-12 17:06 ` Thomas Gleixner
2017-12-12 17:06 ` [Intel-gfx] " Thomas Gleixner
2017-12-13 2:15 ` Anand, Jerome
2017-12-13 11:35 ` Thomas Gleixner
2017-12-13 11:35 ` [Intel-gfx] " Thomas Gleixner
2017-12-13 11:52 ` Takashi Iwai
2017-12-13 11:52 ` [Intel-gfx] " Takashi Iwai
2017-12-13 14:06 ` Thomas Gleixner
2017-12-13 14:06 ` [Intel-gfx] " Thomas Gleixner
2018-01-29 17:09 ` Ville Syrjälä
2018-02-20 18:49 ` Ville Syrjälä
2018-02-20 18:49 ` [Intel-gfx] " Ville Syrjälä
2017-12-08 14:39 ` ✗ Fi.CI.IGT: warning for " Patchwork
-- strict thread matches above, loose matches on Subject: below --
2017-12-08 8:34 [PATCH] " Chen, Augustine
2017-12-08 11:18 ` Ville Syrjälä
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=20171208114404.GN10981@intel.com \
--to=ville.syrjala@linux.intel.com \
--cc=alsa-devel@alsa-project.org \
--cc=augustine.chen@intel.com \
--cc=douly.fnst@cn.fujitsu.com \
--cc=hpa@zytor.com \
--cc=intel-gfx@lists.freedesktop.org \
--cc=jgross@suse.com \
--cc=jiang.liu@linux.intel.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@redhat.com \
--cc=pierre-louis.bossart@intel.com \
--cc=tglx@linutronix.de \
--cc=tiwai@suse.de \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.