All of lore.kernel.org
 help / color / mirror / Atom feed
From: Vishal Thanki <vishalthanki@gmail.com>
To: Mark Brown <broonie@kernel.org>
Cc: alsa-devel@alsa-project.org, tiwai@suse.com,
	Liam Girdwood <lgirdwood@gmail.com>
Subject: Re: [PATCH] ASoC: utils: Add DT support
Date: Mon, 15 May 2017 10:41:43 +0200	[thread overview]
Message-ID: <CAC3a_SCJU_pxNhJOyXdW8x8Eeso8bVV38PkfRL+cRzd+rOoO7Q@mail.gmail.com> (raw)
In-Reply-To: <20170514095651.jbk2fkea6th24yay@sirena.org.uk>

On Sun, May 14, 2017 at 11:56 AM, Mark Brown <broonie@kernel.org> wrote:
> On Tue, May 02, 2017 at 10:08:28AM +0200, Vishal Thanki wrote:
>> Add device tree support for the dummy codec
>> driver.
>
> Why would this be useful?  If the device is a dummy device for internal
> use obviously it doesn't actually exist which tends to suggest that it
> shouldn't be represented in the DT either as the DT should describe the
> hardware.

Thanks for you comments. Actually in our custom hardware, the codec is
not accessible/visible from kernel directly, rather additional MCU
controls and configures it. However MCU needs the I2S clocks and data
from kernel. So I am using I2S platform driver from Linux just to
configure I2S clocks, and registering a dummy codec driver to DAI link
in DT, so that codec can be instantiated and clocks can be enabled
from user-space ALSA utils while accessing this dummy codec. Please
suggest if there is any better way to achieve this kind of
configuration.

Thanks,
Vishal

  reply	other threads:[~2017-05-15  8:42 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-05-02  8:08 [PATCH] ASoC: utils: Add DT support Vishal Thanki
2017-05-14  9:56 ` Mark Brown
2017-05-15  8:41   ` Vishal Thanki [this message]
2017-05-15 10:21     ` Mark Brown

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=CAC3a_SCJU_pxNhJOyXdW8x8Eeso8bVV38PkfRL+cRzd+rOoO7Q@mail.gmail.com \
    --to=vishalthanki@gmail.com \
    --cc=alsa-devel@alsa-project.org \
    --cc=broonie@kernel.org \
    --cc=lgirdwood@gmail.com \
    --cc=tiwai@suse.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.