All of lore.kernel.org
 help / color / mirror / Atom feed
From: Mark Brown <broonie-DgEjT+Ai2ygdnm+yROfE0A@public.gmane.org>
To: Jean-Francois Moine <moinejf-GANU6spQydw@public.gmane.org>
Cc: Andrew Lunn <andrew-g2DYL2Zd6BY@public.gmane.org>,
	Russell King - ARM Linux
	<linux-lFZ/pmaqli7XmaaqVzeoHQ@public.gmane.org>,
	devicetree-u79uwXL29TY76Z2rM5mHXA@public.gmane.org,
	alsa-devel-K7yf7f+aM1XWsZ/bQMPhNw@public.gmane.org,
	lgirdwood-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org,
	dri-devel-PD4FTy7X32lNgt0PjOBp9y5qC8QIuHrW@public.gmane.org,
	linux-kernel-u79uwXL29TY76Z2rM5mHXA@public.gmane.org,
	Rob Clark <robdclark-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>,
	Dave Airlie <airlied-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>,
	linux-arm-kernel-IAPFreCvJWM7uuMidbF8XUB+6BGkLq7r@public.gmane.org
Subject: Re: [PATCH] ASoC: tda998x: add a codec to the HDMI transmitter
Date: Thu, 3 Jul 2014 12:59:24 +0100	[thread overview]
Message-ID: <20140703115924.GY410@sirena.org.uk> (raw)
In-Reply-To: <20140703133406.2d3e3a1d@armhf>

[-- Attachment #1: Type: text/plain, Size: 918 bytes --]

On Thu, Jul 03, 2014 at 01:34:06PM +0200, Jean-Francois Moine wrote:
> Mark Brown <broonie-DgEjT+Ai2ygdnm+yROfE0A@public.gmane.org> wrote:

> > Your board happens to only be able to present the same input on both I2S
> > and S/PDIF but that might not apply to other boards, they may be able to
> > route different signals to each which would present a practical problem.

> If there are two different streamss on I2S and S/PDIF, and if the audio
> subsystem wants to route these streams to the same connector (widget
> 'hdmi-out'), then, somewhere, there should be a software or a design
> bug. No?

Yes, which is why the driver shouldn't silently ignore the situation.

> Anyway, the tda998x cannot know if the double route is wanted or not.

It doesn't need to know, it just needs to identify something it can't
support either by providing a way to pick which interface is used or by
rejecting the second interface.

[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 819 bytes --]

WARNING: multiple messages have this Message-ID (diff)
From: broonie@kernel.org (Mark Brown)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH] ASoC: tda998x: add a codec to the HDMI transmitter
Date: Thu, 3 Jul 2014 12:59:24 +0100	[thread overview]
Message-ID: <20140703115924.GY410@sirena.org.uk> (raw)
In-Reply-To: <20140703133406.2d3e3a1d@armhf>

On Thu, Jul 03, 2014 at 01:34:06PM +0200, Jean-Francois Moine wrote:
> Mark Brown <broonie@kernel.org> wrote:

> > Your board happens to only be able to present the same input on both I2S
> > and S/PDIF but that might not apply to other boards, they may be able to
> > route different signals to each which would present a practical problem.

> If there are two different streamss on I2S and S/PDIF, and if the audio
> subsystem wants to route these streams to the same connector (widget
> 'hdmi-out'), then, somewhere, there should be a software or a design
> bug. No?

Yes, which is why the driver shouldn't silently ignore the situation.

> Anyway, the tda998x cannot know if the double route is wanted or not.

It doesn't need to know, it just needs to identify something it can't
support either by providing a way to pick which interface is used or by
rejecting the second interface.
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 819 bytes
Desc: Digital signature
URL: <http://lists.infradead.org/pipermail/linux-arm-kernel/attachments/20140703/d5383422/attachment.sig>

WARNING: multiple messages have this Message-ID (diff)
From: Mark Brown <broonie@kernel.org>
To: Jean-Francois Moine <moinejf@free.fr>
Cc: Andrew Lunn <andrew@lunn.ch>,
	Russell King - ARM Linux <linux@arm.linux.org.uk>,
	devicetree@vger.kernel.org, alsa-devel@alsa-project.org,
	lgirdwood@gmail.com, dri-devel@lists.freedesktop.org,
	linux-kernel@vger.kernel.org, Rob Clark <robdclark@gmail.com>,
	Dave Airlie <airlied@gmail.com>,
	linux-arm-kernel@lists.infradead.org
Subject: Re: [PATCH] ASoC: tda998x: add a codec to the HDMI transmitter
Date: Thu, 3 Jul 2014 12:59:24 +0100	[thread overview]
Message-ID: <20140703115924.GY410@sirena.org.uk> (raw)
In-Reply-To: <20140703133406.2d3e3a1d@armhf>

[-- Attachment #1: Type: text/plain, Size: 889 bytes --]

On Thu, Jul 03, 2014 at 01:34:06PM +0200, Jean-Francois Moine wrote:
> Mark Brown <broonie@kernel.org> wrote:

> > Your board happens to only be able to present the same input on both I2S
> > and S/PDIF but that might not apply to other boards, they may be able to
> > route different signals to each which would present a practical problem.

> If there are two different streamss on I2S and S/PDIF, and if the audio
> subsystem wants to route these streams to the same connector (widget
> 'hdmi-out'), then, somewhere, there should be a software or a design
> bug. No?

Yes, which is why the driver shouldn't silently ignore the situation.

> Anyway, the tda998x cannot know if the double route is wanted or not.

It doesn't need to know, it just needs to identify something it can't
support either by providing a way to pick which interface is used or by
rejecting the second interface.

[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 819 bytes --]

  reply	other threads:[~2014-07-03 11:59 UTC|newest]

Thread overview: 42+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-07-02 16:38 [PATCH] ASoC: tda998x: add a codec to the HDMI transmitter Jean-Francois Moine
2014-07-02 16:38 ` Jean-Francois Moine
2014-07-02 16:38 ` Jean-Francois Moine
2014-07-02 16:56 ` Andrew Lunn
2014-07-02 16:56   ` Andrew Lunn
2014-07-02 17:51   ` Jean-Francois Moine
2014-07-02 17:51     ` Jean-Francois Moine
2014-07-02 17:51     ` Jean-Francois Moine
2014-07-02 18:02     ` Russell King - ARM Linux
2014-07-02 18:02       ` Russell King - ARM Linux
2014-07-02 18:02       ` Russell King - ARM Linux
2014-07-02 19:37       ` Mark Brown
2014-07-02 19:37         ` Mark Brown
2014-07-02 19:42     ` Mark Brown
2014-07-02 19:42       ` Mark Brown
2014-07-03  5:49       ` Jean-Francois Moine
2014-07-03  5:49         ` Jean-Francois Moine
2014-07-03  5:49         ` Jean-Francois Moine
2014-07-03 10:44         ` Mark Brown
2014-07-03 10:44           ` Mark Brown
2014-07-03 10:44           ` Mark Brown
2014-07-03 11:34           ` Jean-Francois Moine
2014-07-03 11:34             ` Jean-Francois Moine
2014-07-03 11:34             ` Jean-Francois Moine
2014-07-03 11:59             ` Mark Brown [this message]
2014-07-03 11:59               ` Mark Brown
2014-07-03 11:59               ` Mark Brown
2014-07-03 13:28               ` Jean-Francois Moine
2014-07-03 13:28                 ` Jean-Francois Moine
2014-07-03 13:28                 ` Jean-Francois Moine
2014-07-03 13:43                 ` Russell King - ARM Linux
2014-07-03 13:43                   ` Russell King - ARM Linux
2014-07-03 13:43                   ` Russell King - ARM Linux
     [not found]                   ` <20140703134346.GW32514-l+eeeJia6m9vn6HldHNs0ANdhmdF6hFW@public.gmane.org>
2014-07-03 15:29                     ` Jean-Francois Moine
2014-07-03 15:29                       ` Jean-Francois Moine
2014-07-03 15:29                       ` Jean-Francois Moine
2014-07-03 15:43                       ` Russell King - ARM Linux
2014-07-03 15:43                         ` Russell King - ARM Linux
2014-07-03 15:43                         ` Russell King - ARM Linux
2014-07-03 16:26                         ` Jean-Francois Moine
2014-07-03 16:26                           ` Jean-Francois Moine
2014-07-03 16:26                           ` Jean-Francois Moine

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=20140703115924.GY410@sirena.org.uk \
    --to=broonie-dgejt+ai2ygdnm+yrofe0a@public.gmane.org \
    --cc=airlied-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org \
    --cc=alsa-devel-K7yf7f+aM1XWsZ/bQMPhNw@public.gmane.org \
    --cc=andrew-g2DYL2Zd6BY@public.gmane.org \
    --cc=devicetree-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
    --cc=dri-devel-PD4FTy7X32lNgt0PjOBp9y5qC8QIuHrW@public.gmane.org \
    --cc=lgirdwood-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org \
    --cc=linux-arm-kernel-IAPFreCvJWM7uuMidbF8XUB+6BGkLq7r@public.gmane.org \
    --cc=linux-kernel-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
    --cc=linux-lFZ/pmaqli7XmaaqVzeoHQ@public.gmane.org \
    --cc=moinejf-GANU6spQydw@public.gmane.org \
    --cc=robdclark-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.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 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.