All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Shankar, Uma" <uma.shankar@intel.com>
To: Kai Vehmanen <kai.vehmanen@linux.intel.com>
Cc: "intel-gfx@lists.freedesktop.org" <intel-gfx@lists.freedesktop.org>
Subject: Re: [Intel-gfx] [PATCH] drm/i915/audio: set HDA link parameters in driver
Date: Wed, 24 Mar 2021 11:20:26 +0000	[thread overview]
Message-ID: <72848ff6735d4e2b827edd65fbf2ebe9@intel.com> (raw)
In-Reply-To: <alpine.DEB.2.22.394.2103221352330.864696@eliteleevi.tm.intel.com>



> -----Original Message-----
> From: Kai Vehmanen <kai.vehmanen@linux.intel.com>
> Sent: Monday, March 22, 2021 5:24 PM
> To: Kai Vehmanen <kai.vehmanen@linux.intel.com>
> Cc: intel-gfx@lists.freedesktop.org; Shankar, Uma <uma.shankar@intel.com>
> Subject: Re: [PATCH] drm/i915/audio: set HDA link parameters in driver
> 
> Hi,
> 
> On Fri, 12 Feb 2021, Kai Vehmanen wrote:
> 
> > Update logic to program AUD_FREQ_CNTRL register based on new guidance.
> > Earlier this register was configured by BIOS and driver discovered the
> > value at init. This is no longer recommended and instead driver should
> > set the values based on the hardware revision.
> 
> any chance to get this merged? This has a reviewed-by already and all tests pass:

Hi Kai,
Can you rebase and resend, I will help merge this.

Regards,
Uma Shankar

> https://patchwork.freedesktop.org/series/87040/
> 
> Br, Kai
_______________________________________________
Intel-gfx mailing list
Intel-gfx@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/intel-gfx

      reply	other threads:[~2021-03-24 11:20 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-02-12 15:08 [Intel-gfx] [PATCH] drm/i915/audio: set HDA link parameters in driver Kai Vehmanen
2021-02-12 17:51 ` [Intel-gfx] ✓ Fi.CI.BAT: success for " Patchwork
2021-02-12 19:32 ` [Intel-gfx] ✓ Fi.CI.IGT: " Patchwork
2021-03-22 11:53 ` [Intel-gfx] [PATCH] " Kai Vehmanen
2021-03-24 11:20   ` Shankar, Uma [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=72848ff6735d4e2b827edd65fbf2ebe9@intel.com \
    --to=uma.shankar@intel.com \
    --cc=intel-gfx@lists.freedesktop.org \
    --cc=kai.vehmanen@linux.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 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.