public inbox for intel-gfx@lists.freedesktop.org
 help / color / mirror / Atom feed
From: Jani Nikula <jani.nikula@linux.intel.com>
To: Mitul Golani <mitulkumar.ajitkumar.golani@intel.com>,
	intel-gfx@lists.freedesktop.org
Subject: Re: [Intel-gfx] [RFC 1/4] drm/i915/hdmi: Add audio config related params in crtc_state
Date: Fri, 09 Jun 2023 12:36:27 +0300	[thread overview]
Message-ID: <87legtq8o4.fsf@intel.com> (raw)
In-Reply-To: <20230609084504.1929424-2-mitulkumar.ajitkumar.golani@intel.com>

On Fri, 09 Jun 2023, Mitul Golani <mitulkumar.ajitkumar.golani@intel.com> wrote:
> Add source audio-related config params in crtc_state.
> These params can be supported frequency, supported channel,
> and audio support, which can be further computed based on
> source capabilities.
>
> Signed-off-by: Mitul Golani <mitulkumar.ajitkumar.golani@intel.com>
> ---
>  drivers/gpu/drm/i915/display/intel_display_types.h | 12 +++++++++---
>  1 file changed, 9 insertions(+), 3 deletions(-)
>
> diff --git a/drivers/gpu/drm/i915/display/intel_display_types.h b/drivers/gpu/drm/i915/display/intel_display_types.h
> index 731f2ec04d5c..873a60f3f870 100644
> --- a/drivers/gpu/drm/i915/display/intel_display_types.h
> +++ b/drivers/gpu/drm/i915/display/intel_display_types.h
> @@ -1129,9 +1129,15 @@ struct intel_crtc_state {
>  	/* Whether we should send NULL infoframes. Required for audio. */
>  	bool has_hdmi_sink;
>  
> -	/* Audio enabled on this pipe. Only valid if either has_hdmi_sink or
> -	 * has_dp_encoder is set. */
> -	bool has_audio;
> +	struct {
> +		bool has_audio;
> +
> +		/* Audio rate in Hz */
> +		unsigned int max_frequency;
> +
> +		/* Number of audio channels */
> +		unsigned int max_channel;
> +	} audio_config;

This breaks the build. Every commit should build on its own.

audio_config is too verbose. Please just use "audio".

Please don't add the new members in this commit, just first add the
substruct and make the updates. Then add new members in a separate
commit.

BR,
Jani.

>  
>  	/*
>  	 * Enable dithering, used when the selected pipe bpp doesn't match the

-- 
Jani Nikula, Intel Open Source Graphics Center

  reply	other threads:[~2023-06-09  9:36 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-06-09  8:45 [Intel-gfx] [RFC 0/4] Get optimal audio frequency and channels Mitul Golani
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 [this message]
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=87legtq8o4.fsf@intel.com \
    --to=jani.nikula@linux.intel.com \
    --cc=intel-gfx@lists.freedesktop.org \
    --cc=mitulkumar.ajitkumar.golani@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