From: Mark Brown <broonie@kernel.org> To: Jean-Francois Moine <moinejf@free.fr> Cc: Jyri Sarha <jsarha@ti.com>, linux-arm-kernel@lists.infradead.org, linux-omap@vger.kernel.org, alsa-devel@alsa-project.org, dri-devel@lists.freedesktop.org, peter.ujfalusi@ti.com Subject: Re: [PATCH RFC 4/9] ASoC: hdmi-codec: Add devicetree binding with documentation Date: Wed, 20 Nov 2013 13:33:15 +0000 [thread overview] Message-ID: <20131120133315.GC2674@sirena.org.uk> (raw) In-Reply-To: <20131120133458.3822a165@armhf> [-- Attachment #1: Type: text/plain, Size: 1381 bytes --] On Wed, Nov 20, 2013 at 01:34:58PM +0100, Jean-Francois Moine wrote: > Mark Brown <broonie@kernel.org> wrote: > > We still want to be able to have users just name the CODEC on their > > board rather than have to type in all the details from the datasheet, > > if we're going to try to amalgamate the drivers it should still let > > people do that. > OK. But it seems to me that the codec is not tied to the board, but > rather to the audio connector / transmitter. No, not at all. The majority of these devices are simple CODECs, DACs and ADCs with no register control which are soldered down onto the board. What's connected beyond them is irrelevant. If anything the devices that don't have fixed functions are even more likely to want or need to have specific code, for example code could be written to enforce the results of HDMI capability discovery. > In the case of the tda998x HDMI transmitter, either i2s or s/pdif may > be used, thanks to the actual codecs 'hdmi' and 'spdif tx'. But they > don't work the same way: the 'hdmi' codec handles both playback and > record, and recording is disabled by program in the sound device, > while the 'spdif tx' codec is selected by the codec-dai-name > ("dit-hifi" - it is "dir-hifi" for recording). It would be nice if > these codecs would have the same behaviour... Well, send patches refactoring one or the other then... [-- Attachment #2: Digital signature --] [-- Type: application/pgp-signature, Size: 836 bytes --]
WARNING: multiple messages have this Message-ID (diff)
From: broonie@kernel.org (Mark Brown) To: linux-arm-kernel@lists.infradead.org Subject: [PATCH RFC 4/9] ASoC: hdmi-codec: Add devicetree binding with documentation Date: Wed, 20 Nov 2013 13:33:15 +0000 [thread overview] Message-ID: <20131120133315.GC2674@sirena.org.uk> (raw) In-Reply-To: <20131120133458.3822a165@armhf> On Wed, Nov 20, 2013 at 01:34:58PM +0100, Jean-Francois Moine wrote: > Mark Brown <broonie@kernel.org> wrote: > > We still want to be able to have users just name the CODEC on their > > board rather than have to type in all the details from the datasheet, > > if we're going to try to amalgamate the drivers it should still let > > people do that. > OK. But it seems to me that the codec is not tied to the board, but > rather to the audio connector / transmitter. No, not at all. The majority of these devices are simple CODECs, DACs and ADCs with no register control which are soldered down onto the board. What's connected beyond them is irrelevant. If anything the devices that don't have fixed functions are even more likely to want or need to have specific code, for example code could be written to enforce the results of HDMI capability discovery. > In the case of the tda998x HDMI transmitter, either i2s or s/pdif may > be used, thanks to the actual codecs 'hdmi' and 'spdif tx'. But they > don't work the same way: the 'hdmi' codec handles both playback and > record, and recording is disabled by program in the sound device, > while the 'spdif tx' codec is selected by the codec-dai-name > ("dit-hifi" - it is "dir-hifi" for recording). It would be nice if > these codecs would have the same behaviour... Well, send patches refactoring one or the other then... -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 836 bytes Desc: Digital signature URL: <http://lists.infradead.org/pipermail/linux-arm-kernel/attachments/20131120/14f218c0/attachment.sig>
next prev parent reply other threads:[~2013-11-20 13:33 UTC|newest] Thread overview: 110+ messages / expand[flat|nested] mbox.gz Atom feed top 2013-11-19 12:12 [PATCH RFC 0/9] Beaglebone-Black HDMI audio Jyri Sarha 2013-11-19 12:12 ` Jyri Sarha 2013-11-19 12:12 ` [PATCH RFC 1/9] clk: add gpio controlled clock Jyri Sarha 2013-11-19 12:12 ` Jyri Sarha 2013-11-19 12:12 ` [PATCH RFC 2/9] ASoC: davinci-evm: Add named clock reference to DT bindings Jyri Sarha 2013-11-19 12:12 ` Jyri Sarha 2013-11-19 18:18 ` Mark Brown 2013-11-19 18:18 ` Mark Brown 2013-11-19 12:12 ` [PATCH RFC 3/9] ASoC: davinci-evm: HDMI audio support for TDA998x trough McASP I2S bus Jyri Sarha 2013-11-19 12:12 ` Jyri Sarha 2013-11-19 15:07 ` Thomas Petazzoni 2013-11-19 15:07 ` Thomas Petazzoni 2013-11-19 12:12 ` [PATCH RFC 4/9] ASoC: hdmi-codec: Add devicetree binding with documentation Jyri Sarha 2013-11-19 12:12 ` Jyri Sarha 2013-11-19 17:50 ` Mark Brown 2013-11-19 17:50 ` Mark Brown 2013-11-20 9:23 ` Jean-Francois Moine 2013-11-20 9:23 ` Jean-Francois Moine 2013-11-20 10:09 ` Mark Brown 2013-11-20 10:09 ` Mark Brown 2013-11-20 12:34 ` Jean-Francois Moine 2013-11-20 12:34 ` Jean-Francois Moine 2013-11-20 13:33 ` Mark Brown [this message] 2013-11-20 13:33 ` Mark Brown 2013-11-19 12:12 ` [PATCH RFC 5/9] ASoC: hdmi-codec: Add SNDRV_PCM_FMTBIT_32_LE playback format Jyri Sarha 2013-11-19 12:12 ` Jyri Sarha 2013-11-19 18:21 ` Mark Brown 2013-11-19 18:21 ` Mark Brown 2013-11-19 12:12 ` [PATCH RFC 6/9] ASoC: davinci: HDMI audio build for AM33XX and TDA998x Jyri Sarha 2013-11-19 12:12 ` Jyri Sarha 2013-11-19 12:12 ` [PATCH RFC 7/9] drm/tilcdc: Add I2C HDMI audio config for tda998x Jyri Sarha 2013-11-19 12:12 ` Jyri Sarha 2013-11-19 12:12 ` [PATCH RFC 8/9] ARM: OMAP2+: omap2plus_defconfig: Enable tilcdc and TDA998X HDMI support Jyri Sarha 2013-11-19 12:12 ` Jyri Sarha 2013-11-19 12:12 ` [PATCH RFC 9/9] ARM: OMAP2+: omap2plus_defconfig: Enable BeagleBone Black HDMI audio support Jyri Sarha 2013-11-19 12:12 ` Jyri Sarha 2013-11-19 12:21 ` [PATCH RFC] DTS Changes for Beaglebone-Black HDMI audio Jyri Sarha 2013-11-19 12:21 ` Jyri Sarha 2013-11-19 12:21 ` [PATCH RFC] ARM/dts: am335x-boneblack: Add HDMI audio support Jyri Sarha 2013-11-19 12:21 ` Jyri Sarha 2013-11-19 13:02 ` Benoit Cousson 2013-11-19 13:02 ` Benoit Cousson 2013-11-19 13:29 ` Jyri Sarha 2013-11-19 13:29 ` Jyri Sarha 2013-12-08 12:16 ` [RFC v2 0/8] Beaglebone-Black HDMI audio Jyri Sarha 2013-12-08 12:16 ` [RFC v2 1/8] clk: add gpio controlled clock Jyri Sarha 2013-12-08 12:16 ` [RFC v2 2/8] ASoC: davinci-evm: Add named clock reference to DT bindings Jyri Sarha 2013-12-08 12:16 ` [RFC v2 3/8] ASoC: davinci-evm: HDMI audio support for TDA998x trough McASP I2S bus Jyri Sarha 2013-12-08 12:16 ` [RFC v2 4/8] ASoC: hdmi-codec: Add devicetree binding with documentation Jyri Sarha 2013-12-08 12:16 ` [RFC v2 5/8] ASoC: davinci: HDMI audio build for AM33XX and TDA998x Jyri Sarha 2013-12-08 12:16 ` [RFC v2 6/8] drm/tilcdc: Add I2C HDMI audio config for tda998x Jyri Sarha 2013-12-08 12:16 ` [RFC v2 7/8] ARM: OMAP2+: omap2plus_defconfig: Enable tilcdc and TDA998X HDMI support Jyri Sarha 2013-12-08 12:16 ` [RFC v2 8/8] ARM: OMAP2+: omap2plus_defconfig: Enable BeagleBone Black HDMI audio support Jyri Sarha 2013-12-08 12:20 ` [RFC v2] Beaglebone-Black HDMI audio Jyri Sarha 2013-12-08 12:20 ` [RFC v2] ARM/dts: am335x-boneblack: Add HDMI audio support Jyri Sarha 2013-12-10 18:52 ` Jyri Sarha [not found] ` <cover.1386504183.git.jsarha-l0cyMroinI0@public.gmane.org> 2013-12-10 18:52 ` Jyri Sarha [not found] ` <cover.1384862950.git.jsarha-l0cyMroinI0@public.gmane.org> 2013-12-10 18:52 ` [RFC v2] Beaglebone-Black HDMI audio Jyri Sarha 2013-12-20 10:36 ` [PATCH RFC v2 REPOST 0/8] " Jyri Sarha 2013-12-20 10:36 ` Jyri Sarha 2013-12-20 10:37 ` [PATCH RFC v2 REPOST 1/8] clk: add gpio controlled clock Jyri Sarha 2013-12-20 10:37 ` Jyri Sarha 2013-12-20 10:38 ` [PATCH RFC v2 REPOST 2/8] ASoC: davinci-evm: Add named clock reference to DT bindings Jyri Sarha 2013-12-20 10:38 ` Jyri Sarha 2013-12-31 13:16 ` Mark Brown 2013-12-31 13:16 ` Mark Brown 2014-01-15 11:12 ` Jyri Sarha 2014-01-15 11:12 ` Jyri Sarha 2013-12-20 10:39 ` [PATCH RFC v2 REPOST 3/8] ASoC: davinci-evm: HDMI audio support for TDA998x trough McASP I2S bus Jyri Sarha 2013-12-20 10:39 ` Jyri Sarha 2013-12-31 13:25 ` Mark Brown 2013-12-31 13:25 ` Mark Brown 2014-01-15 11:27 ` Jyri Sarha 2014-01-15 11:27 ` Jyri Sarha 2014-01-15 13:48 ` Anssi Hannula 2014-01-15 13:48 ` [alsa-devel] " Anssi Hannula 2014-01-15 16:28 ` Jyri Sarha 2014-01-15 16:28 ` [alsa-devel] " Jyri Sarha 2014-01-15 15:51 ` Jean-Francois Moine 2014-01-15 15:51 ` Jean-Francois Moine 2014-01-22 9:20 ` Jyri Sarha 2014-01-22 9:20 ` [alsa-devel] " Jyri Sarha 2014-01-22 10:19 ` Jean-Francois Moine 2014-01-22 10:19 ` Jean-Francois Moine 2014-01-22 10:46 ` Jean-Francois Moine 2014-01-22 10:46 ` Jean-Francois Moine 2014-01-24 12:57 ` Jyri Sarha 2014-01-24 12:57 ` [alsa-devel] " Jyri Sarha 2014-01-24 16:54 ` Jean-Francois Moine 2014-01-24 16:54 ` Jean-Francois Moine 2014-01-21 19:15 ` Mark Brown 2014-01-21 19:15 ` Mark Brown 2014-01-24 13:01 ` Jyri Sarha 2014-01-24 13:01 ` Jyri Sarha 2013-12-20 10:40 ` [PATCH RFC v2 REPOST 4/8] ASoC: hdmi-codec: Add devicetree binding with documentation Jyri Sarha 2013-12-20 10:40 ` Jyri Sarha 2013-12-31 13:26 ` Mark Brown 2013-12-31 13:26 ` Mark Brown 2013-12-20 10:40 ` [PATCH RFC v2 REPOST 5/8] ASoC: davinci: HDMI audio build for AM33XX and TDA998x Jyri Sarha 2013-12-20 10:40 ` Jyri Sarha 2013-12-20 10:41 ` [PATCH RFC v2 REPOST 6/8] drm/tilcdc: Add I2C HDMI audio config for tda998x Jyri Sarha 2013-12-20 10:41 ` Jyri Sarha 2013-12-20 10:42 ` [PATCH RFC v2 REPOST 7/8] ARM: OMAP2+: omap2plus_defconfig: Enable tilcdc and TDA998X HDMI support Jyri Sarha 2013-12-20 10:42 ` Jyri Sarha 2013-12-20 10:43 ` [PATCH RFC v2 REPOST 8/8] ARM: OMAP2+: omap2plus_defconfig: Enable BeagleBone Black HDMI audio support Jyri Sarha 2013-12-20 10:43 ` Jyri Sarha 2013-12-20 11:30 ` [alsa-devel] [PATCH RFC v2 REPOST 0/8] Beaglebone-Black HDMI audio Mark Brown 2013-12-20 11:30 ` Mark Brown 2013-12-20 11:51 ` Jyri Sarha 2013-12-20 11:51 ` [alsa-devel] " Jyri Sarha
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=20131120133315.GC2674@sirena.org.uk \ --to=broonie@kernel.org \ --cc=alsa-devel@alsa-project.org \ --cc=dri-devel@lists.freedesktop.org \ --cc=jsarha@ti.com \ --cc=linux-arm-kernel@lists.infradead.org \ --cc=linux-omap@vger.kernel.org \ --cc=moinejf@free.fr \ --cc=peter.ujfalusi@ti.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: linkBe 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.