public inbox for intel-gfx@lists.freedesktop.org
 help / color / mirror / Atom feed
From: Mitul Golani <mitulkumar.ajitkumar.golani@intel.com>
To: intel-gfx@lists.freedesktop.org
Subject: [Intel-gfx] [RFC 0/4] Get optimal audio frequency and channels
Date: Fri,  9 Jun 2023 14:15:00 +0530	[thread overview]
Message-ID: <20230609084504.1929424-1-mitulkumar.ajitkumar.golani@intel.com> (raw)

Currently we do not check if there is enough bandwidth for
audio, and what channels and freq it can really support.
Also sometimes there can be HW constraints e.g. GLK where audio
channels supported are only 2.

https://patchwork.freedesktop.org/series/107647/

Obtain the optimal audio rate and channel based on available display
timing constraints.

This can be achieved by:
- Retrieve the supported channel and rate information from SADs
- Adding audio-related config parameters in the CRTC state, such
as audio support, rate, and channel.
- Initializing the audio config parameters with the maximum supported
rate and channel by the audio source.
- Computing the SADs based on the audio source's capabilities.

Mitul Golani (4):
  drm/i915/hdmi: Add audio config related params in crtc_state
  drm/i915/display: Update access of has_audio param
  drm/i915/display: Add wrapper to Compute SAD
  drm/i915/display: Initialize and compute HDMI Audio source cap

 drivers/gpu/drm/i915/display/g4x_dp.c         |  4 +-
 drivers/gpu/drm/i915/display/g4x_hdmi.c       | 16 ++---
 drivers/gpu/drm/i915/display/intel_audio.c    | 72 ++++++++++++++++++-
 drivers/gpu/drm/i915/display/intel_audio.h    |  1 +
 drivers/gpu/drm/i915/display/intel_cdclk.c    |  6 +-
 .../drm/i915/display/intel_crtc_state_dump.c  |  4 +-
 drivers/gpu/drm/i915/display/intel_ddi.c      |  2 +-
 drivers/gpu/drm/i915/display/intel_display.c  |  4 +-
 .../drm/i915/display/intel_display_types.h    | 12 +++-
 drivers/gpu/drm/i915/display/intel_dp.c       |  2 +-
 drivers/gpu/drm/i915/display/intel_dp_mst.c   |  2 +-
 drivers/gpu/drm/i915/display/intel_hdmi.c     | 39 +++++++++-
 drivers/gpu/drm/i915/display/intel_hdmi.h     |  1 +
 drivers/gpu/drm/i915/display/intel_sdvo.c     | 10 +--
 14 files changed, 143 insertions(+), 32 deletions(-)

-- 
2.25.1


             reply	other threads:[~2023-06-09  8:44 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-06-09  8:45 Mitul Golani [this message]
2023-06-09  8:45 ` [Intel-gfx] [RFC 1/4] drm/i915/hdmi: Add audio config related params in crtc_state Mitul Golani
2023-06-09  9:36   ` Jani Nikula
2023-06-09 17:44     ` Golani, Mitulkumar Ajitkumar
2023-06-09  9:38   ` Jani Nikula
2023-06-09 17:42     ` Golani, Mitulkumar Ajitkumar
2023-06-09  8:45 ` [Intel-gfx] [RFC 2/4] drm/i915/display: Update access of has_audio param Mitul Golani
2023-06-09  9:39   ` Jani Nikula
2023-06-09 17:45     ` Golani, Mitulkumar Ajitkumar
2023-06-09  8:45 ` [Intel-gfx] [RFC 3/4] drm/i915/display: Add wrapper to Compute SAD Mitul Golani
2023-06-09  8:45 ` [Intel-gfx] [RFC 4/4] drm/i915/display: Initialize and compute HDMI Audio source cap Mitul Golani
2023-06-09  9:09 ` [Intel-gfx] ✗ Fi.CI.SPARSE: warning for Get optimal audio frequency and channels Patchwork
2023-06-09 17:16 ` [Intel-gfx] ✓ Fi.CI.BAT: success " 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=20230609084504.1929424-1-mitulkumar.ajitkumar.golani@intel.com \
    --to=mitulkumar.ajitkumar.golani@intel.com \
    --cc=intel-gfx@lists.freedesktop.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