alsa-devel.alsa-project.org archive mirror
 help / color / mirror / Atom feed
From: Lars-Peter Clausen <lars@metafoo.de>
To: Jun Nie <jun.nie@linaro.org>, broonie@kernel.org, lgirdwood@gmail.com
Cc: alsa-devel@alsa-project.org, shawn.guo@linaro.org, wan.zhijun@zte.com.cn
Subject: Re: [PATCH v3 6/6] ASoC: zx: add zx296702 hdmi codec
Date: Fri, 29 May 2015 16:10:54 +0200	[thread overview]
Message-ID: <5568736E.5090801@metafoo.de> (raw)
In-Reply-To: <1432906281-27698-7-git-send-email-jun.nie@linaro.org>

On 05/29/2015 03:31 PM, Jun Nie wrote:
> Add zx296702 hdmi codec to enable SPDIF and I2S output
> via HDMI. The SPDIF/I2S route is exclusive with current
> software config and need specify which is valid in
> defconfig.

That's an issue, the hardware configuration should not depend on kernel 
configuration setting. This makes it impossible to run the same kernel on 
platforms with conflicting settings. It should be possible to configure this 
dynamically at boot time based on platform_data/devicetree, etc.

But is this device real hardware anyway?

>
> Signed-off-by: Jun Nie <jun.nie@linaro.org>
> ---
>   include/sound/zx_hdmi_audio.h    |   7 +++
>   sound/soc/codecs/Kconfig         |   3 +
>   sound/soc/codecs/Makefile        |   1 +
>   sound/soc/codecs/zx296702_hdmi.c | 121 +++++++++++++++++++++++++++++++++++++++
>   4 files changed, 132 insertions(+)
>   create mode 100644 include/sound/zx_hdmi_audio.h
>   create mode 100644 sound/soc/codecs/zx296702_hdmi.c
>
> diff --git a/include/sound/zx_hdmi_audio.h b/include/sound/zx_hdmi_audio.h
> new file mode 100644
> index 0000000..7eb0e81
> --- /dev/null
> +++ b/include/sound/zx_hdmi_audio.h
> @@ -0,0 +1,7 @@
> +#ifndef __ZX_HDMI_AUDIO_H__
> +#define __ZX_HDMI_AUDIO_H__
> +
> +int zx_hdmi_audio_cfg(int audio_codec, int audio_way,
> +		      u32 sample_rate, u32 sample_len);
> +void zx_hdmi_audio_en(int on);

Where is the implementation for these functions? The fact that they seem to 
operate on global state indicates that something is wrong wit this API.

> +#endif /* __ZX_HDMI_AUDIO_H__ */

  reply	other threads:[~2015-05-29 14:10 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-05-29 13:31 [PATCH v3 0/6] Support ZTE zx296702 SPDIF/I2S Jun Nie
2015-05-29 13:31 ` [PATCH v3 1/6] dt: Add documentation for the ZTE SPDIF controller Jun Nie
2015-05-29 13:31 ` [PATCH v3 2/6] dt: Add documentation for the ZTE I2S controller Jun Nie
2015-05-29 13:31 ` [PATCH v3 3/6] dt: Add doc for the ZTE HDMI audio codec binding Jun Nie
2015-05-29 13:31 ` [PATCH v3 4/6] ASoC: zx: Add zx296702 SPDIF support Jun Nie
2015-05-29 14:03   ` Lars-Peter Clausen
2015-05-29 13:31 ` [PATCH v3 5/6] ASoC: zx: Add ZTE zx296702 I2S DAI driver Jun Nie
2015-06-03 16:02   ` Mark Brown
2015-05-29 13:31 ` [PATCH v3 6/6] ASoC: zx: add zx296702 hdmi codec Jun Nie
2015-05-29 14:10   ` Lars-Peter Clausen [this message]
2015-05-29 15:18     ` Mark Brown
2015-06-01  1:42       ` Jun Nie
2015-06-02 18:13         ` Mark Brown
2015-06-03  1:47           ` Jun Nie
2015-06-03 11:01             ` Mark Brown
2015-06-03 12:40               ` Jun Nie
2015-06-03 15:09                 ` Mark Brown
2015-06-03 17:58   ` Mark Brown
2015-06-04  3:35     ` Jun Nie

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=5568736E.5090801@metafoo.de \
    --to=lars@metafoo.de \
    --cc=alsa-devel@alsa-project.org \
    --cc=broonie@kernel.org \
    --cc=jun.nie@linaro.org \
    --cc=lgirdwood@gmail.com \
    --cc=shawn.guo@linaro.org \
    --cc=wan.zhijun@zte.com.cn \
    /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;
as well as URLs for NNTP newsgroup(s).