Linux kernel -stable discussions
 help / color / mirror / Atom feed
From: "Ville Syrjälä" <ville.syrjala@linux.intel.com>
To: Giacomo Comes <comes@naic.edu>
Cc: intel-gfx@lists.freedesktop.org, stable@vger.kernel.org
Subject: Re: [Intel-gfx] kernel 5.6: baytrail hdmi audio not working
Date: Thu, 2 Apr 2020 16:52:03 +0300	[thread overview]
Message-ID: <20200402135203.GV13686@intel.com> (raw)
In-Reply-To: <20200401225317.GA13834@monopoli.naic.edu>

On Wed, Apr 01, 2020 at 06:53:17PM -0400, Giacomo Comes wrote:
> Hi,
> on my Intel Compute Stick STCK1 (baytrail hdmi audio) 
> sound is not working with the kernel 5.6
> 
> I have bisected the kernel and I found the commit that introduced the issue:
> 
> commit 58d124ea2739e1440ddd743d46c470fe724aca9a
> Author: Maarten Lankhorst <maarten.lankhorst@linux.intel.com>
> Date:   Thu Oct 31 12:26:04 2019 +0100
> 
>     drm/i915: Complete crtc hw/uapi split, v6.
>     
>     Now that we separated everything into uapi and hw, it's
>     time to make the split definitive. Remove the union and
>     make a copy of the hw state on modeset and fastset.
>     
>     Color blobs are copied in crtc atomic_check(), right
>     before color management is checked.
> 
> If more information is required please let me know.

Should hopefully be fixed with
commit 2bdd4c28baff ("drm/i915/display: Fix mode private_flags
comparison at atomic_check")

Stable folks, please pick that up for 5.6.x stable releases.

-- 
Ville Syrjälä
Intel

       reply	other threads:[~2020-04-02 13:52 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20200401225317.GA13834@monopoli.naic.edu>
2020-04-02 13:52 ` Ville Syrjälä [this message]
2020-04-02 14:53   ` [Intel-gfx] kernel 5.6: baytrail hdmi audio not working Giacomo Comes
2020-04-03  9:18     ` Greg KH

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=20200402135203.GV13686@intel.com \
    --to=ville.syrjala@linux.intel.com \
    --cc=comes@naic.edu \
    --cc=intel-gfx@lists.freedesktop.org \
    --cc=stable@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