All of lore.kernel.org
 help / color / mirror / Atom feed
From: Peter Ujfalusi <peter.ujfalusi@ti.com>
To: Belisko Marek <marek.belisko@gmail.com>, jarkko.nikula@bitmer.com
Cc: "linux-omap@vger.kernel.org" <linux-omap@vger.kernel.org>,
	alsa-devel@alsa-project.org,
	"Dr. H. Nikolaus Schaller" <hns@goldelico.com>
Subject: Re: ti,codec property in sound/soc/omap/omap-twl4030.c not used
Date: Thu, 12 Mar 2015 11:19:06 +0200	[thread overview]
Message-ID: <55015A0A.1060309@ti.com> (raw)
In-Reply-To: <CAAfyv34ebp1oL7t9GKT20_c4VYMM=3rfJTrj-MfT6NUBXk6d2A@mail.gmail.com>

On 03/12/2015 12:12 AM, Belisko Marek wrote:
> Hi,
> 
> I'm looking at sources for omap-twl4030.c driver which is used by many
> boards. In DT bindings documentation is property ti,codec described as
> mandatory but it's never parsed in driver code. I did small experiment
> in gta04 board and remove ti,codec from devicetree and sound was
> working. I think it can be removed from documentation and also from
> various device trees. Is my assumption correct? Thanks.

Correct. The ti,twl4030-audio is for the MFD driver and the device for the
ASoC codec is created in there w/o actual DT compatible string. The audio part
of the twl4030 is responsible for the audio and the vibra functionality.

Are you going to send the patches?

Thanks,
Péter
--
To unsubscribe from this list: send the line "unsubscribe linux-omap" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html

  reply	other threads:[~2015-03-12  9:19 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-03-11 22:12 ti,codec property in sound/soc/omap/omap-twl4030.c not used Belisko Marek
2015-03-12  9:19 ` Peter Ujfalusi [this message]
2015-03-12  9:27   ` Belisko Marek

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=55015A0A.1060309@ti.com \
    --to=peter.ujfalusi@ti.com \
    --cc=alsa-devel@alsa-project.org \
    --cc=hns@goldelico.com \
    --cc=jarkko.nikula@bitmer.com \
    --cc=linux-omap@vger.kernel.org \
    --cc=marek.belisko@gmail.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.