All of lore.kernel.org
 help / color / mirror / Atom feed
From: Jean-Francois Moine <moinejf@free.fr>
To: Russell King - ARM Linux <linux@arm.linux.org.uk>
Cc: Andrew Lunn <andrew@lunn.ch>,
	alsa-devel@alsa-project.org, devicetree@vger.kernel.org,
	lgirdwood@gmail.com, dri-devel@lists.freedesktop.org,
	linux-kernel@vger.kernel.org, Mark Brown <broonie@kernel.org>,
	linux-arm-kernel@lists.infradead.org
Subject: Re: [PATCH] ASoC: tda998x: add a codec to the HDMI transmitter
Date: Thu, 3 Jul 2014 18:26:00 +0200	[thread overview]
Message-ID: <20140703182600.7a98c5b6@armhf> (raw)
In-Reply-To: <20140703154325.GY32514@n2100.arm.linux.org.uk>

On Thu, 3 Jul 2014 16:43:25 +0100
Russell King - ARM Linux <linux@arm.linux.org.uk> wrote:

> What you're doing in kirkwood-i2s is providing two plain DAI links,
> and then insisting that only one can be active any any one time.
> 
> A DPCM solution provides at least one frontend DAI link and at least
> one backend DAI link.  Your code does not do this.

You know why I did not insert the DPCM code in the kirkwood driver: it
does not work. But, as I tested it end 2013, I still have the code.
Do you want I propose a patch?

> Which bit of "we need to support both I2S and SPDIF" in my previous
> emails was not clear.  Which bit of "We should only support SPDIF
> on the Cubox" was not clear?
> 
> I *fully* acknowledge that we need to support both, but I'm putting
> a _strong_ recommendation to you _with_ technical reasons why we
> should _only_ support SPDIF on the Cubox.

Sorry, I still don't see why only S/PDIF should be supported on the
Cubox. I have both, and both are working on HDMI. I hope someone will
tell me it also works on S/PDIF: there is no reason it could not.

I don't see your technical reasons: you know the constraints of each
protocol I2S and S/PDIF. If you don't want I2S, just don't declare it
in the DT (see my previous mail). You may also note that I did not put
any change relative to the Cubox DT in my patch.

-- 
Ken ar c'hentañ	|	      ** Breizh ha Linux atav! **
Jef		|		http://moinejf.free.fr/
_______________________________________________
dri-devel mailing list
dri-devel@lists.freedesktop.org
http://lists.freedesktop.org/mailman/listinfo/dri-devel

WARNING: multiple messages have this Message-ID (diff)
From: moinejf@free.fr (Jean-Francois Moine)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH] ASoC: tda998x: add a codec to the HDMI transmitter
Date: Thu, 3 Jul 2014 18:26:00 +0200	[thread overview]
Message-ID: <20140703182600.7a98c5b6@armhf> (raw)
In-Reply-To: <20140703154325.GY32514@n2100.arm.linux.org.uk>

On Thu, 3 Jul 2014 16:43:25 +0100
Russell King - ARM Linux <linux@arm.linux.org.uk> wrote:

> What you're doing in kirkwood-i2s is providing two plain DAI links,
> and then insisting that only one can be active any any one time.
> 
> A DPCM solution provides at least one frontend DAI link and at least
> one backend DAI link.  Your code does not do this.

You know why I did not insert the DPCM code in the kirkwood driver: it
does not work. But, as I tested it end 2013, I still have the code.
Do you want I propose a patch?

> Which bit of "we need to support both I2S and SPDIF" in my previous
> emails was not clear.  Which bit of "We should only support SPDIF
> on the Cubox" was not clear?
> 
> I *fully* acknowledge that we need to support both, but I'm putting
> a _strong_ recommendation to you _with_ technical reasons why we
> should _only_ support SPDIF on the Cubox.

Sorry, I still don't see why only S/PDIF should be supported on the
Cubox. I have both, and both are working on HDMI. I hope someone will
tell me it also works on S/PDIF: there is no reason it could not.

I don't see your technical reasons: you know the constraints of each
protocol I2S and S/PDIF. If you don't want I2S, just don't declare it
in the DT (see my previous mail). You may also note that I did not put
any change relative to the Cubox DT in my patch.

-- 
Ken ar c'henta?	|	      ** Breizh ha Linux atav! **
Jef		|		http://moinejf.free.fr/

WARNING: multiple messages have this Message-ID (diff)
From: Jean-Francois Moine <moinejf@free.fr>
To: Russell King - ARM Linux <linux@arm.linux.org.uk>
Cc: Mark Brown <broonie@kernel.org>, Andrew Lunn <andrew@lunn.ch>,
	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 18:26:00 +0200	[thread overview]
Message-ID: <20140703182600.7a98c5b6@armhf> (raw)
In-Reply-To: <20140703154325.GY32514@n2100.arm.linux.org.uk>

On Thu, 3 Jul 2014 16:43:25 +0100
Russell King - ARM Linux <linux@arm.linux.org.uk> wrote:

> What you're doing in kirkwood-i2s is providing two plain DAI links,
> and then insisting that only one can be active any any one time.
> 
> A DPCM solution provides at least one frontend DAI link and at least
> one backend DAI link.  Your code does not do this.

You know why I did not insert the DPCM code in the kirkwood driver: it
does not work. But, as I tested it end 2013, I still have the code.
Do you want I propose a patch?

> Which bit of "we need to support both I2S and SPDIF" in my previous
> emails was not clear.  Which bit of "We should only support SPDIF
> on the Cubox" was not clear?
> 
> I *fully* acknowledge that we need to support both, but I'm putting
> a _strong_ recommendation to you _with_ technical reasons why we
> should _only_ support SPDIF on the Cubox.

Sorry, I still don't see why only S/PDIF should be supported on the
Cubox. I have both, and both are working on HDMI. I hope someone will
tell me it also works on S/PDIF: there is no reason it could not.

I don't see your technical reasons: you know the constraints of each
protocol I2S and S/PDIF. If you don't want I2S, just don't declare it
in the DT (see my previous mail). You may also note that I did not put
any change relative to the Cubox DT in my patch.

-- 
Ken ar c'hentañ	|	      ** Breizh ha Linux atav! **
Jef		|		http://moinejf.free.fr/

  reply	other threads:[~2014-07-03 16:26 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
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 [this message]
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=20140703182600.7a98c5b6@armhf \
    --to=moinejf@free.fr \
    --cc=alsa-devel@alsa-project.org \
    --cc=andrew@lunn.ch \
    --cc=broonie@kernel.org \
    --cc=devicetree@vger.kernel.org \
    --cc=dri-devel@lists.freedesktop.org \
    --cc=lgirdwood@gmail.com \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux@arm.linux.org.uk \
    /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.