dri-devel Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Jani Nikula <jani.nikula@linux.intel.com>
To: Arnaud Pouliquen <arnaud.pouliquen@st.com>,
	alsa-devel@alsa-project.org, dri-devel@lists.freedesktop.org
Cc: Daniel Vetter <daniel.vetter@intel.com>,
	broonie@kernel.org, lgirdwood@gmail.com,
	Jyri Sarha <jsarha@ti.com>,
	Takashi Sakamoto <o-takashi@sakamocchi.jp>
Subject: Re: [PATCH v3 1/4] DRM: add help to get ELD speaker allocation
Date: Tue, 20 Dec 2016 16:07:51 +0200	[thread overview]
Message-ID: <8760meofrc.fsf@intel.com> (raw)
In-Reply-To: <1482145726-16782-2-git-send-email-arnaud.pouliquen@st.com>

On Mon, 19 Dec 2016, Arnaud Pouliquen <arnaud.pouliquen@st.com> wrote:
> Add helper to allow users to retrieve the speaker allocations without
> knowledge of the ELD structure.
>
> Signed-off-by: Arnaud Pouliquen <arnaud.pouliquen@st.com>

I've already replied with my Reviewed-by, please take care to include
them.

Reviewed-by: Jani Nikula <jani.nikula@intel.com>


> ---
>  include/drm/drm_edid.h | 13 +++++++++++++
>  1 file changed, 13 insertions(+)
>
> diff --git a/include/drm/drm_edid.h b/include/drm/drm_edid.h
> index c3a7d44..de93543 100644
> --- a/include/drm/drm_edid.h
> +++ b/include/drm/drm_edid.h
> @@ -248,6 +248,7 @@ struct detailed_timing {
>  # define DRM_ELD_AUD_SYNCH_DELAY_MAX	0xfa	/* 500 ms */
>  
>  #define DRM_ELD_SPEAKER			7
> +# define DRM_ELD_SPEAKER_MASK		0x7f
>  # define DRM_ELD_SPEAKER_RLRC		(1 << 6)
>  # define DRM_ELD_SPEAKER_FLRC		(1 << 5)
>  # define DRM_ELD_SPEAKER_RC		(1 << 4)
> @@ -415,6 +416,18 @@ static inline int drm_eld_size(const uint8_t *eld)
>  }
>  
>  /**
> + * drm_eld_get_spk_alloc - Get speaker allocation
> + * @eld: pointer to an ELD memory structure
> + *
> + * The returned value is the speakers mask. User has to use %DRM_ELD_SPEAKER
> + * field definitions to identify speakers.
> + */
> +static inline u8 drm_eld_get_spk_alloc(const uint8_t *eld)
> +{
> +	return eld[DRM_ELD_SPEAKER] & DRM_ELD_SPEAKER_MASK;
> +}
> +
> +/**
>   * drm_eld_get_conn_type - Get device type hdmi/dp connected
>   * @eld: pointer to an ELD memory structure
>   *

-- 
Jani Nikula, Intel Open Source Technology Center
_______________________________________________
dri-devel mailing list
dri-devel@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/dri-devel

  reply	other threads:[~2016-12-20 14:07 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-12-19 11:08 [PATCH v3 0/4] Generic HDMI codec: Add channel mapping control Arnaud Pouliquen
2016-12-19 11:08 ` [PATCH v3 1/4] DRM: add help to get ELD speaker allocation Arnaud Pouliquen
2016-12-20 14:07   ` Jani Nikula [this message]
2016-12-19 11:08 ` [PATCH v3 2/4] ALSA pcm: allow non constant snd_pcm_chmap_elem Arnaud Pouliquen
2016-12-19 16:31   ` [alsa-devel] " kbuild test robot
2016-12-19 17:16     ` Arnaud Pouliquen
2016-12-19 11:08 ` [PATCH v3 3/4] ASoC: core: add optional pcm_new callback for DAI driver Arnaud Pouliquen
2016-12-19 11:08 ` [PATCH v3 4/4] ASoC: hdmi-codec: add channel mapping control Arnaud Pouliquen
2016-12-19 19:49 ` [PATCH v3 0/4] Generic HDMI codec: Add " Takashi Sakamoto

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=8760meofrc.fsf@intel.com \
    --to=jani.nikula@linux.intel.com \
    --cc=alsa-devel@alsa-project.org \
    --cc=arnaud.pouliquen@st.com \
    --cc=broonie@kernel.org \
    --cc=daniel.vetter@intel.com \
    --cc=dri-devel@lists.freedesktop.org \
    --cc=jsarha@ti.com \
    --cc=lgirdwood@gmail.com \
    --cc=o-takashi@sakamocchi.jp \
    /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