public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Pierre-Louis Bossart <pierre-louis.bossart@linux.intel.com>
To: Azat Khuzhin <dohardgopro@gmail.com>
Cc: Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: [GIT PULL] sound updates for 4.21
Date: Fri, 4 Jan 2019 20:12:44 -0600	[thread overview]
Message-ID: <53fa01e6-5cf8-9a42-8efd-8a82cf039770@linux.intel.com> (raw)
In-Reply-To: <CAAW1UO-P5cWWx-orjCHvHw3deStJTiUmT5BHveTTiJotvB9aNA@mail.gmail.com>


On 1/4/19 6:34 PM, Azat Khuzhin wrote:
>> This is unfortunately a known issue with this driver, Takashi and I had
>> a couple of email threads on this. Even without errors removing the
>> module doesn't seem to release all resources. I don't like this at all,
>> and for the Sound Open Firmware (SOF) driver I mandated module
>> load-unload as a functional requirement along with zero warnings w/
>> Sparse, Coccinelle and friends, but on this legacy code I am afraid
>> there is no simple fix - at least not in a merge window or a single
>> kernel cycle.
> And the fact that kernel crashes after?
> Just want extra confirmation
The kernel crash is related to an HDMI issue that we haven't been able 
to reproduce on our development and validation devices so far but that's 
not an excuse and we do need to figure it out. Things work e.g. fine 
with the KBL Dell XPS13 but not on Linus' SKL Dell XPS13 device, so I'll 
get one and will also work on additional devices remotely.

      reply	other threads:[~2019-01-05  2:12 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-12-20 15:38 [GIT PULL] sound updates for 4.21 Takashi Iwai
2018-12-25 23:20 ` pr-tracker-bot
2018-12-27  3:31 ` Linus Torvalds
2018-12-28 12:43   ` Ingo Molnar
2018-12-28 17:07     ` Takashi Iwai
2018-12-28 19:04       ` Linus Torvalds
2018-12-30  9:21         ` Takashi Iwai
     [not found]           ` <82bb7f60-c3c2-4715-a0a0-f1f2a8b14c74@linux.intel.com>
2018-12-31  0:19             ` Linus Torvalds
2018-12-31  0:54               ` Pierre-Louis Bossart
2018-12-31  8:11             ` Takashi Iwai
2018-12-31 10:24               ` Pierre-Louis Bossart
2018-12-31 18:15                 ` Takashi Iwai
2018-12-31 20:10                   ` Pierre-Louis Bossart
2018-12-31 21:02                     ` Hans de Goede
2018-12-31 13:43               ` Azat Khuzhin
2018-12-31 15:22                 ` Pierre-Louis Bossart
2019-01-05  0:34                   ` Azat Khuzhin
2019-01-05  2:12                     ` Pierre-Louis Bossart [this message]

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=53fa01e6-5cf8-9a42-8efd-8a82cf039770@linux.intel.com \
    --to=pierre-louis.bossart@linux.intel.com \
    --cc=dohardgopro@gmail.com \
    --cc=linux-kernel@vger.kernel.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