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

On 08/20/2014 03:34 PM, Mark Rutland wrote:
...
> Sorry, I meant in the same node. I take it we never expect:
>
> compatible = "ti,am335x-beaglebone-black-audio", "ti,da830-evm-audio";
>

No never like that.

>>> > >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.
> In general we've pushed back against wildcard strings, and used the
> first implementation for the naming. We should be able to use
> "ti,am3358-beaglebone-black-audio" for AM335{8,9} assuming the block is
> the same? Otherwise we might need separate strings anyway.

At least the relevant block (McASP) is the same. AM335x is commonly used 
in all TI documentation, but I am not picky am3358 is fine with me.

Could we drop the SoC id completely and make it just 
"beaglebone-black-audio"?

The board design is the unique factor here, not the SoC. McASP block can 
be found from several TI SoCs.

Cheers,
Jyri

  reply	other threads:[~2014-08-20 13:03 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
2014-08-20 12:34       ` Mark Rutland
2014-08-20 13:03         ` Jyri Sarha [this message]
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=53F49CB2.5020801@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 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.