public inbox for linux-kernel@vger.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: "Kuankuan.Yang" <ykk@rock-chips.com>,
	"Mark Rutland" <mark.rutland@arm.com>,
	"Heiko Stuebner" <heiko@sntech.de>,
	devicetree@vger.kernel.org, "David Airlie" <airlied@linux.ie>,
	dri-devel@lists.freedesktop.org,
	"Liam Girdwood" <lgirdwood@gmail.com>,
	"Max Filippov" <jcmvbkbc@gmail.com>,
	"Bard Liao" <bardliao@realtek.com>,
	"Lars-Peter Clausen" <lars@metafoo.de>,
	"Pawel Moll" <pawel.moll@arm.com>, "Takashi Iwai" <tiwai@suse.de>,
	linux-rockchip@lists.infradead.org,
	"Grant Likely" <grant.likely@linaro.org>,
	"Dylan Reid" <dgreid@chromium.org>,
	"Xu Jianqun" <jay.xu@rock-chips.com>,
	"Oder Chiou" <oder_chiou@realtek.com>,
	Zubair.Kakakhel@imgtec.com, "Arnd Bergmann" <arnd@arndb.de>,
	"Ian Campbell" <ijc+devicetree@hellion.org.uk>,
	"Jyri Sarha" <jsarha@ti.com>, "Ben Zhang" <benzh@chromium.org>,
	"Rob Herring" <robh+dt@kernel.org>,
	"Daniel Kurtz" <djkurtz@chromium.org>,
	"Stéphane Marchesin" <marcheu@chromium.org>,
	"Jaroslav Kysela" <perex@perex.cz>,
	"Sonny Rao" <sonnyrao@chromium.org>,
	"Sean Cross" <xobs@kosagi.com>,
	linux-arm-kernel@lists.infradead.org,
	"Fabio Estevam" <fabio.estevam@freescale.com>,
	"Brian Austin" <brian.austin@cirrus.com>,
	"Greg Kroah-Hartman" <gregkh@linuxfoundation.org>,
	linux-kernel@vger.kernel.org, "Mark Brown" <broonie@kernel.org>,
	"Philipp Zabel" <p.zabel@pengutronix.de>,
	"Kumar Gala" <galak@codeaurora.org>,
	"Shawn Guo" <shawn.guo@linaro.org>
Subject: Re: [RFC PATCH 0/6] Those patches is used for dw_hdmi audio.
Date: Mon, 15 Dec 2014 16:48:08 +0100	[thread overview]
Message-ID: <20141215164808.092cc7ac@armhf> (raw)
In-Reply-To: <20141215120013.GH11285@n2100.arm.linux.org.uk>

On Mon, 15 Dec 2014 12:00:13 +0000
Russell King - ARM Linux <linux@arm.linux.org.uk> wrote:

> I really don't want to end up in another cocked up situation like
> what happened with the Dove audio, where it became politically
> impossible for the SolidRun platform to be properly supported by
> mainline kernels.

Hi Russell,

I don't see what you mean. The last patches I proposed for the TDA998x
and the HDMI CODEC do exactly what you wanted: S/PDIF out from the
kirkwood audio device towards both S/PDIF optical and HDMI output2 by
default.

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

      parent reply	other threads:[~2014-12-15 15:47 UTC|newest]

Thread overview: 23+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-12-15  2:11 [RFC PATCH 0/6] Those patches is used for dw_hdmi audio Yakir Yang
2014-12-15  2:11 ` [PATCH 1/6] drm: bridge/dw_hdmi: add hdmi audio config interfaces Yakir Yang
2014-12-15  2:11 ` [PATCH 2/6] drm: bridge/bridge: add support for rk3288 hdmi-audio Yakir Yang
2014-12-15  2:11 ` [PATCH 3/6] ASoC: dw-hdmi-audio: add codec driver for dw hdmi audio Yakir Yang
2014-12-15  2:11 ` [PATCH 4/6] ASoC: rockchip-hdmi-audio: add sound driver for " Yakir Yang
2014-12-15  2:55 ` [PATCH 5/6] dt-bindings: Add documentation for Rockchip hdmi-audio Yakir Yang
2014-12-15  9:02   ` Lars-Peter Clausen
2014-12-15  9:46     ` Kuankuan.Yang
2014-12-15 10:40   ` Russell King - ARM Linux
2014-12-15 12:02     ` Mark Brown
2014-12-15 13:10       ` Kuankuan.Yang
2014-12-15 16:18         ` Mark Brown
2014-12-16  2:14           ` Kuankuan.Yang
2014-12-16  2:38           ` Kuankuan.Yang
2014-12-16  6:17           ` Kuankuan.Yang
2014-12-16  9:34             ` Russell King - ARM Linux
2014-12-16  9:48               ` Kuankuan.Yang
2014-12-15  2:56 ` [PATCH 6/6] ARM: dts: rockchip: add hdmi audio nodes Yakir Yang
2014-12-15 10:38 ` [RFC PATCH 0/6] Those patches is used for dw_hdmi audio Russell King - ARM Linux
     [not found]   ` <548EC9E1.5040206@rock-chips.com>
2014-12-15 11:52     ` Kuankuan.Yang
2014-12-15 12:00       ` Russell King - ARM Linux
2014-12-15 12:46         ` Kuankuan.Yang
2014-12-15 15:48         ` Jean-Francois Moine [this message]

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=20141215164808.092cc7ac@armhf \
    --to=moinejf@free.fr \
    --cc=Zubair.Kakakhel@imgtec.com \
    --cc=airlied@linux.ie \
    --cc=arnd@arndb.de \
    --cc=bardliao@realtek.com \
    --cc=benzh@chromium.org \
    --cc=brian.austin@cirrus.com \
    --cc=broonie@kernel.org \
    --cc=devicetree@vger.kernel.org \
    --cc=dgreid@chromium.org \
    --cc=djkurtz@chromium.org \
    --cc=dri-devel@lists.freedesktop.org \
    --cc=fabio.estevam@freescale.com \
    --cc=galak@codeaurora.org \
    --cc=grant.likely@linaro.org \
    --cc=gregkh@linuxfoundation.org \
    --cc=heiko@sntech.de \
    --cc=ijc+devicetree@hellion.org.uk \
    --cc=jay.xu@rock-chips.com \
    --cc=jcmvbkbc@gmail.com \
    --cc=jsarha@ti.com \
    --cc=lars@metafoo.de \
    --cc=lgirdwood@gmail.com \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-rockchip@lists.infradead.org \
    --cc=linux@arm.linux.org.uk \
    --cc=marcheu@chromium.org \
    --cc=mark.rutland@arm.com \
    --cc=oder_chiou@realtek.com \
    --cc=p.zabel@pengutronix.de \
    --cc=pawel.moll@arm.com \
    --cc=perex@perex.cz \
    --cc=robh+dt@kernel.org \
    --cc=shawn.guo@linaro.org \
    --cc=sonnyrao@chromium.org \
    --cc=tiwai@suse.de \
    --cc=xobs@kosagi.com \
    --cc=ykk@rock-chips.com \
    /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