devicetree.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Jyri Sarha <jsarha@ti.com>
To: Mark Rutland <mark.rutland@arm.com>
Cc: "dri-devel@lists.freedesktop.org"
	<dri-devel@lists.freedesktop.org>,
	"airlied@linux.ie" <airlied@linux.ie>,
	"linux-omap@vger.kernel.org" <linux-omap@vger.kernel.org>,
	"devicetree@vger.kernel.org" <devicetree@vger.kernel.org>,
	"bcousson@baylibre.com" <bcousson@baylibre.com>,
	"alsa-devel@alsa-project.org" <alsa-devel@alsa-project.org>,
	"tony@atomide.com" <tony@atomide.com>,
	"broonie@kernel.org" <broonie@kernel.org>,
	"liam.r.girdwood@linux.intel.com"
	<liam.r.girdwood@linux.intel.com>,
	"peter.ujfalusi@ti.com" <peter.ujfalusi@ti.com>,
	"detheridge@ti.com" <detheridge@ti.com>,
	"ezequiel.garcia@free-electrons.com"
	<ezequiel.garcia@free-electrons.com>,
	"t-kristo@ti.com" <t-kristo@ti.com>
Subject: Re: [PATCH v2 3/8] ASoC: davinci-evm: HDMI audio support for TDA998x trough McASP I2S bus
Date: Tue, 19 Aug 2014 22:40:51 +0300	[thread overview]
Message-ID: <53F3A843.4010409@ti.com> (raw)
In-Reply-To: <20140819131621.GL3302@leverpostej>

On 08/19/2014 04:16 PM, Mark Rutland wrote:
> On Mon, Aug 18, 2014 at 10:46:41PM +0100, Jyri Sarha wrote:
>> Add machine driver support for BeagleBone-Black HDMI audio. BBB has
>> NXP TDA998X HDMI transmitter connected to McASP port in I2S mode. The
>> 44100 Hz sample-rate and it's multiples can not be accurately produced
>> on BBB. The only supported sample format is SNDRV_PCM_FORMAT_S32_LE.
>> The 8 least significant bits are ignored.
>>
>> Signed-off-by: Jyri Sarha <jsarha@ti.com>
>> ---
>>   .../bindings/sound/davinci-evm-audio.txt           |    4 +-
>>   sound/soc/davinci/davinci-evm.c                    |   82 +++++++++++++++++++-
>>   2 files changed, 83 insertions(+), 3 deletions(-)
>>
>> diff --git a/Documentation/devicetree/bindings/sound/davinci-evm-audio.txt b/Documentation/devicetree/bindings/sound/davinci-evm-audio.txt
>> index 963e100..c137436 100644
>> --- a/Documentation/devicetree/bindings/sound/davinci-evm-audio.txt
>> +++ b/Documentation/devicetree/bindings/sound/davinci-evm-audio.txt
>> @@ -1,7 +1,9 @@
>>   * Texas Instruments SoC audio setups with TLV320AIC3X Codec
>>
>>   Required properties:
>> -- compatible : "ti,da830-evm-audio" : forDM365/DA8xx/OMAPL1x/AM33xx
>> +- compatible : "ti,da830-evm-audio" : for DM365/DA8xx/OMAPL1x/AM33xx
>> +               "ti,am335x-beaglebone-black-audio" : for Beaglebone-black HDMI
>> +                                                    audio
>
> To keep this legible I'd recommend reorganising this like:
>
> - compatible: should contain one of:
>     * "ti,da830-evm-audio" for DM365/DA8xx/OMAPL1x/AM33xx
>     * "ti,am335x-beaglebone-black-audio" for Beaglebone-black HDMI audio
>

The above looks indeed better. I'll make the change. Oh, and I probably 
should change the first line to something like:

* TI SoC audio using McASP to connect to TLV320AIC3X or HDMI endcoder

> For the BBB case, do you expect both strings or just the BBB-specific
> string?
>

Normally just the one. In theory a BBB with an audio-cape on top could 
utilize another sound node with "ti,da830-evm-audio" compatible property.

> Is the 'x' in the BBB string a wildcard? If we know the particular
> number for BBB we should use that.
>

Yes, its a wild card. BBBs have been made at least with AM3358 and 
AM3359 SoCs.

Thanks,
Jyri

  reply	other threads:[~2014-08-19 19:40 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-08-18 21:46 [PATCH v2 0/8] Beaglebone-Black HDMI audio Jyri Sarha
2014-08-18 21:46 ` [PATCH v2 1/8] clk: ti: add gpio controlled clock Jyri Sarha
2014-08-19 11:32   ` Mark Rutland
2014-08-19 12:23     ` Jyri Sarha
2014-08-19 12:37       ` Mark Rutland
     [not found] ` <cover.1408397864.git.jsarha-l0cyMroinI0@public.gmane.org>
2014-08-18 21:46   ` [PATCH v2 2/8] drm/tilcdc: Add I2S HDMI audio config for tda998x Jyri Sarha
2014-08-18 21:46 ` [PATCH v2 3/8] ASoC: davinci-evm: HDMI audio support for TDA998x trough McASP I2S bus Jyri Sarha
2014-08-19 13:16   ` Mark Rutland
2014-08-19 19:40     ` Jyri Sarha [this message]
2014-08-20 12:34       ` Mark Rutland
2014-08-20 13:03         ` Jyri Sarha
2014-08-21 18:24           ` Mark Brown
2014-08-18 21:46 ` [PATCH v2 4/8] ASoC: davinci: HDMI audio build for AM33XX and TDA998x Jyri Sarha
2014-08-18 21:46 ` [PATCH v2 5/8] ARM: dts: am33xx: Add external clock provider Jyri Sarha
2014-09-08 23:30   ` Tony Lindgren
     [not found]     ` <20140908233037.GT3238-4v6yS6AI5VpBDgjK7y7TUQ@public.gmane.org>
2014-09-09  7:57       ` Tero Kristo
2014-08-18 21:46 ` [PATCH v2 6/8] ARM: dts: am335x-boneblack: Add HDMI audio support Jyri Sarha
2014-08-18 21:46 ` [PATCH v2 7/8] ARM: OMAP2+: omap2plus_defconfig: TDA998X HDMI trough tilcdc,slave Jyri Sarha
2014-08-18 21:46 ` [PATCH v2 8/8] ARM: OMAP2+: omap2plus_defconfig: Enable BeagleBone Black HDMI audio support 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=53F3A843.4010409@ti.com \
    --to=jsarha@ti.com \
    --cc=airlied@linux.ie \
    --cc=alsa-devel@alsa-project.org \
    --cc=bcousson@baylibre.com \
    --cc=broonie@kernel.org \
    --cc=detheridge@ti.com \
    --cc=devicetree@vger.kernel.org \
    --cc=dri-devel@lists.freedesktop.org \
    --cc=ezequiel.garcia@free-electrons.com \
    --cc=liam.r.girdwood@linux.intel.com \
    --cc=linux-omap@vger.kernel.org \
    --cc=mark.rutland@arm.com \
    --cc=peter.ujfalusi@ti.com \
    --cc=t-kristo@ti.com \
    --cc=tony@atomide.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;
as well as URLs for NNTP newsgroup(s).