linux-pci.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Russell King - ARM Linux <linux@arm.linux.org.uk>
To: Andrew Lunn <andrew@lunn.ch>
Cc: Sebastian Hesselbarth <sebastian.hesselbarth@gmail.com>,
	Jason Cooper <jason@lakedaemon.net>,
	Sebastian Hesselbarth <sebastian.hesselbarth@googlemail.com>,
	Gregory Clement <gregory.clement@free-electrons.com>,
	Mark Brown <broonie@kernel.org>,
	alsa-devel@alsa-project.org,
	Daniel Lezcano <daniel.lezcano@linaro.org>,
	"Rafael J. Wysocki" <rjw@rjwysocki.net>,
	linux-pm@vger.kernel.org, Tejun Heo <tj@kernel.org>,
	linux-ide@vger.kernel.org, Zhang Rui <rui.zhang@intel.com>,
	Bryan Wu <cooloney@gmail.com>, Richard Purdie <rpurdie@rpsys.net>,
	linux-leds@vger.kernel.org, Bjorn Helgaas <bhelgaas@google.com>,
	linux-pci@vger.kernel.org, Kishon Vijay Abraham I <kishon@ti.com>,
	Alessandro Zummo <a.zummo@towertech.it>,
	rtc-linux@googlegroups.com, Wim Van Sebroeck <wim@iguana.be>,
	linux-watchdog@vger.kernel.org
Subject: Re: [PATCH 00/13] Remove mach-kirkwood and mach-dove
Date: Mon, 30 Jun 2014 19:08:53 +0100	[thread overview]
Message-ID: <20140630180853.GF32514@n2100.arm.linux.org.uk> (raw)
In-Reply-To: <20140630174351.GI18520@lunn.ch>

On Mon, Jun 30, 2014 at 07:43:51PM +0200, Andrew Lunn wrote:
> > > If you are talking about "Kirkwood ASoC updates", you got a Tested-by
> > > from Andrew even before I read your patches. And besides, just because
> > > I am interested in Dove does not mean I just swallowed the whole Linux
> > > API knowledge. I simply avoided commenting on it, because there is
> > > /nothing/ I can add to it.
> > 
> > No I am not - and those are the patches which I referred to as having
> > been already taken by Mark into his tree.  The patch I'm referring to
> > which can never be merged now is the one which I replied to Jean
> > Francois just now - and if you read through it, you'll understand
> > why - that's because it /totally/ breaks the simple DT bindings that
> > are now established - independently - for Kirkwood stuff.
> 
> Hi Russell
> 
> Are you referring to http://www.spinics.net/lists/arm-kernel/msg328068.html

I'm referring to the _entire_ addition of DT support for the sound stuff
on mvebu.

The timeline from my point of view started around March/April 2013, which
is where I was told that the kirkwood stuff should be converted to DPCM
in order to allow the SPDIF output to be used.  The documentation and
hints how to use it fell way short of what was required - and moreover,
the ASoC code to support this feature was missing several patches that
Liam had (and was freezing on to, eventually sending them after last
year's kernel summit.)

However, eventually it got sorted through face to face discussions with
Mark and Liam at kernel summit, but not before Jean-Francois patches
had been merged.  My solution was developed and tested without Jean's
patches in place.

While I was sorting out the fallout from that, the patches to convert
kirkwood to use the simple-card stuff were merged.  At this point, I
basically decided that was the end of nine months of effort to get SPDIF
with DPCM properly supported, and earlier this year I emailed Mark to
say that I regard that effort as being completely dead (even though I
still use it, because it's the only way to get SPDIF output properly
working with MPEG/AC3 compressed output.)

Jean is only interested in feeding I2S out to the HDMI port, he's not
interested in the SPDIF optical connector on the side, neither is he
interested in the compressed stream support.  Neither of these are now
possible without breaking the DT bindings for the ASoC implementation.

This is the problem - in the mad headlong rush for DT support as if
it's the most important thing on the planet, it seems that things
haven't been properly considered - and it's not like I haven't been
publishing these ASoC patches.  I've sent numerous rounds of patches
during 2013.

So, what do we do now with support for compressed audio streams via
SPDIF on kirkwood hardware?  As far as I can see, it's no longer
possible and mainline kernels will never support this.  Please tell
me I'm wrong...

-- 
FTTC broadband for 0.8mile line: now at 9.7Mbps down 460kbps up... slowly
improving, and getting towards what was expected from it.

  reply	other threads:[~2014-06-30 18:09 UTC|newest]

Thread overview: 23+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-06-29 20:59 [PATCH 00/13] Remove mach-kirkwood and mach-dove Andrew Lunn
2014-06-29 20:59 ` [PATCH 09/13] PCI: Remove ARCH_KIRKWOOD and ARCH_DOVE dependency Andrew Lunn
2014-07-05 17:54   ` Bjorn Helgaas
2014-07-05 17:52     ` Andrew Lunn
2014-06-29 21:35 ` [PATCH 00/13] Remove mach-kirkwood and mach-dove Russell King - ARM Linux
2014-06-30  7:16   ` [alsa-devel] " Jean-Francois Moine
2014-06-30  8:49     ` Russell King - ARM Linux
2014-06-30  9:47       ` Jean-Francois Moine
2014-06-30 10:00         ` Russell King - ARM Linux
2014-06-30 12:15   ` Sebastian Hesselbarth
2014-06-30 12:43     ` Russell King - ARM Linux
2014-06-30 13:22       ` Sebastian Hesselbarth
2014-06-30 14:25         ` Russell King - ARM Linux
2014-06-30 15:35           ` Sebastian Hesselbarth
2014-06-30 16:56             ` Russell King - ARM Linux
2014-06-30 17:31               ` Sebastian Hesselbarth
2014-06-30 19:35                 ` Russell King - ARM Linux
2014-06-30 17:43               ` Andrew Lunn
2014-06-30 18:08                 ` Russell King - ARM Linux [this message]
2014-06-30 18:16                   ` Andrew Lunn
2014-07-06  9:49                     ` [rtc-linux] " Alexander Holler
2014-06-30 22:21           ` Ezequiel Garcia
2014-07-08 12:13 ` Jason Cooper

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=20140630180853.GF32514@n2100.arm.linux.org.uk \
    --to=linux@arm.linux.org.uk \
    --cc=a.zummo@towertech.it \
    --cc=alsa-devel@alsa-project.org \
    --cc=andrew@lunn.ch \
    --cc=bhelgaas@google.com \
    --cc=broonie@kernel.org \
    --cc=cooloney@gmail.com \
    --cc=daniel.lezcano@linaro.org \
    --cc=gregory.clement@free-electrons.com \
    --cc=jason@lakedaemon.net \
    --cc=kishon@ti.com \
    --cc=linux-ide@vger.kernel.org \
    --cc=linux-leds@vger.kernel.org \
    --cc=linux-pci@vger.kernel.org \
    --cc=linux-pm@vger.kernel.org \
    --cc=linux-watchdog@vger.kernel.org \
    --cc=rjw@rjwysocki.net \
    --cc=rpurdie@rpsys.net \
    --cc=rtc-linux@googlegroups.com \
    --cc=rui.zhang@intel.com \
    --cc=sebastian.hesselbarth@gmail.com \
    --cc=sebastian.hesselbarth@googlemail.com \
    --cc=tj@kernel.org \
    --cc=wim@iguana.be \
    /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).