public inbox for intel-gfx@lists.freedesktop.org
 help / color / mirror / Atom feed
From: Ramalingam C <ramalingam.c@intel.com>
To: intel-gfx <intel-gfx@lists.freedesktop.org>,
	dri-devel <dri-devel@lists.freedesktop.org>
Cc: lucas.demarchi@intel.com
Subject: [Intel-gfx] [PATCH 0/2] hda/i915: split wait for component binding
Date: Thu, 24 Feb 2022 01:22:01 +0530	[thread overview]
Message-ID: <20220223195203.13708-1-ramalingam.c@intel.com> (raw)

To avoid the intended wait being reported as kworker hung, split the
wait for i915 component bind, in multiples of
sysctl_hung_task_timeout_secs.

To facilitate this we are exporting sysctl_hung_task_timeout_secs from
kernel/hung_task.c for the kernel modules' use.

Ramalingam C (2):
  kernel/hung_task: Exporting sysctl_hung_task_timeout_secs
  hda/i915: split the wait for the component binding

 kernel/hung_task.c    |  1 +
 sound/hda/hdac_i915.c | 17 ++++++++++++++---
 2 files changed, 15 insertions(+), 3 deletions(-)

-- 
2.20.1


             reply	other threads:[~2022-02-23 19:52 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-02-23 19:52 Ramalingam C [this message]
2022-02-23 19:52 ` [Intel-gfx] [PATCH 1/2] kernel/hung_task: Exporting sysctl_hung_task_timeout_secs Ramalingam C
2022-02-24 16:33   ` Lucas De Marchi
2022-02-23 19:52 ` [Intel-gfx] [PATCH 2/2] hda/i915: split the wait for the component binding Ramalingam C
2022-02-24 16:34   ` Kai Vehmanen
2022-02-25 11:42     ` Takashi Iwai
2022-02-24 17:13   ` Lucas De Marchi
2022-02-24 14:52 ` [Intel-gfx] ✓ Fi.CI.BAT: success for hda/i915: split wait for " Patchwork
2022-02-25  4:21 ` [Intel-gfx] ✓ Fi.CI.IGT: " Patchwork

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=20220223195203.13708-1-ramalingam.c@intel.com \
    --to=ramalingam.c@intel.com \
    --cc=dri-devel@lists.freedesktop.org \
    --cc=intel-gfx@lists.freedesktop.org \
    --cc=lucas.demarchi@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