From: Jyri Sarha <jsarha@ti.com>
To: Mark Brown <broonie@kernel.org>
Cc: detheridge@ti.com, alsa-devel@alsa-project.org,
dri-devel@lists.freedesktop.org, peter.ujfalusi@ti.com,
bcousson@baylibre.com, linux-omap@vger.kernel.org,
linux-arm-kernel@lists.infradead.org
Subject: Re: [PATCH RFC v3 4/8] ASoC: davinci-evm: HDMI audio support for TDA998x trough McASP I2S bus
Date: Tue, 28 Jan 2014 09:47:13 +0200 [thread overview]
Message-ID: <52E76081.3030905@ti.com> (raw)
In-Reply-To: <20140127204910.GB11841@sirena.org.uk>
On 01/27/2014 10:49 PM, Mark Brown wrote:
> On Mon, Jan 27, 2014 at 05:37:53PM +0200, Jyri Sarha wrote:
>> Add machine driver support for BeagleBone-Black and other boards with
>> tilcdc support and NXP TDA998X HDMI transmitter connected to McASP
>> port in I2S mode. McASP produces the bit clock for the i2s bus from
>> the masted clock by a simple divider and the available sample rates
>
> I have to say I agree with Lars' comments about where the code to set
> the constraints is here - I don't doubt that these limitations are valid
> but it would be better to factor them into the relevant chip drivers so
> that other systems with similar limitations can be handled correctly
> too.
>
Ok, I'll push them into mcasp driver then.
Thanks,
Jyri
WARNING: multiple messages have this Message-ID (diff)
From: jsarha@ti.com (Jyri Sarha)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH RFC v3 4/8] ASoC: davinci-evm: HDMI audio support for TDA998x trough McASP I2S bus
Date: Tue, 28 Jan 2014 09:47:13 +0200 [thread overview]
Message-ID: <52E76081.3030905@ti.com> (raw)
In-Reply-To: <20140127204910.GB11841@sirena.org.uk>
On 01/27/2014 10:49 PM, Mark Brown wrote:
> On Mon, Jan 27, 2014 at 05:37:53PM +0200, Jyri Sarha wrote:
>> Add machine driver support for BeagleBone-Black and other boards with
>> tilcdc support and NXP TDA998X HDMI transmitter connected to McASP
>> port in I2S mode. McASP produces the bit clock for the i2s bus from
>> the masted clock by a simple divider and the available sample rates
>
> I have to say I agree with Lars' comments about where the code to set
> the constraints is here - I don't doubt that these limitations are valid
> but it would be better to factor them into the relevant chip drivers so
> that other systems with similar limitations can be handled correctly
> too.
>
Ok, I'll push them into mcasp driver then.
Thanks,
Jyri
next prev parent reply other threads:[~2014-01-28 7:47 UTC|newest]
Thread overview: 46+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-01-27 15:37 [PATCH RFC v3 0/8] Beaglebone-Black HDMI audio Jyri Sarha
2014-01-27 15:37 ` Jyri Sarha
2014-01-27 15:37 ` [PATCH RFC v3 1/8] clk: add gpio controlled clock Jyri Sarha
2014-01-27 15:37 ` Jyri Sarha
2014-01-27 15:37 ` [PATCH RFC v3 2/8] ASoC: davinci-evm: Add named clock reference to DT bindings Jyri Sarha
2014-01-27 15:37 ` Jyri Sarha
2014-01-27 18:10 ` Mark Brown
2014-01-27 18:10 ` Mark Brown
2014-01-27 15:37 ` [PATCH RFC v3 3/8] ASoC: davinci-mcasp: Set BCLK divider if McASP is BCLK master Jyri Sarha
2014-01-27 15:37 ` Jyri Sarha
2014-01-27 20:46 ` Mark Brown
2014-01-27 20:46 ` Mark Brown
2014-01-27 15:37 ` [PATCH RFC v3 4/8] ASoC: davinci-evm: HDMI audio support for TDA998x trough McASP I2S bus Jyri Sarha
2014-01-27 15:37 ` Jyri Sarha
2014-01-27 20:49 ` Mark Brown
2014-01-27 20:49 ` Mark Brown
2014-01-28 7:47 ` Jyri Sarha [this message]
2014-01-28 7:47 ` Jyri Sarha
2014-01-27 15:37 ` [PATCH RFC v3 5/8] ASoC: davinci: HDMI audio build for AM33XX and TDA998x Jyri Sarha
2014-01-27 15:37 ` Jyri Sarha
2014-01-27 15:37 ` [PATCH RFC v3 6/8] drm/tilcdc: Add I2C HDMI audio config for tda998x Jyri Sarha
2014-01-27 15:37 ` Jyri Sarha
2014-01-27 15:37 ` [PATCH RFC v3 7/8] ARM: OMAP2+: omap2plus_defconfig: Enable tilcdc and TDA998X HDMI support Jyri Sarha
2014-01-27 15:37 ` Jyri Sarha
2014-01-27 15:37 ` [PATCH RFC v3 8/8] ARM: OMAP2+: omap2plus_defconfig: Enable BeagleBone Black HDMI audio support Jyri Sarha
2014-01-27 15:37 ` Jyri Sarha
2014-01-27 15:51 ` [PATCH RFC v3 0/8] Beaglebone-Black HDMI audio Lars-Peter Clausen
2014-01-27 15:51 ` [alsa-devel] " Lars-Peter Clausen
2014-01-27 16:17 ` Jyri Sarha
2014-01-27 16:17 ` [alsa-devel] " Jyri Sarha
2014-01-27 16:32 ` Lars-Peter Clausen
2014-01-27 16:32 ` Lars-Peter Clausen
2014-01-27 19:40 ` Jyri Sarha
2014-01-27 19:40 ` [alsa-devel] " Jyri Sarha
2014-01-27 19:47 ` Lars-Peter Clausen
2014-01-27 19:47 ` Lars-Peter Clausen
2014-01-27 18:06 ` Jean-Francois Moine
2014-01-27 18:06 ` Jean-Francois Moine
2014-01-27 19:31 ` Jyri Sarha
2014-01-27 19:31 ` [alsa-devel] " Jyri Sarha
2014-01-28 9:23 ` Jean-Francois Moine
2014-01-28 9:23 ` Jean-Francois Moine
2014-01-30 12:20 ` Jyri Sarha
2014-01-30 12:20 ` [alsa-devel] " Jyri Sarha
2014-01-30 18:00 ` Jean-Francois Moine
2014-01-30 18:00 ` 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=52E76081.3030905@ti.com \
--to=jsarha@ti.com \
--cc=alsa-devel@alsa-project.org \
--cc=bcousson@baylibre.com \
--cc=broonie@kernel.org \
--cc=detheridge@ti.com \
--cc=dri-devel@lists.freedesktop.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-omap@vger.kernel.org \
--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: 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.