From: Vinod Koul <vinod.koul@intel.com>
To: Pradeep Tewani <pradeep.d.tewani@intel.com>
Cc: tiwai@suse.de, patches.audio@intel.com,
alsa-devel@alsa-project.org, broonie@kernel.org,
lgirdwood@gmail.com
Subject: Re: [PATCH] ASoC: Intel: Skylake: Add IPC to configure the copier secondary pins
Date: Fri, 1 Sep 2017 16:34:12 +0530 [thread overview]
Message-ID: <20170901110411.GB3053@localhost> (raw)
In-Reply-To: <1504253173-16647-1-git-send-email-pradeep.d.tewani@intel.com>
On Fri, Sep 01, 2017 at 01:36:13PM +0530, Pradeep Tewani wrote:
> Copier can support upto 4 output pins. However, only pin 0 is configured
> as a part of copier initialization. Configuring rest of pins require the
> separate IPC to be sent to fw.
Acked-By: Vinod Koul <vinod.koul@intel.com>
--
~Vinod
next prev parent reply other threads:[~2017-09-01 11:00 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-09-01 8:06 [PATCH] ASoC: Intel: Skylake: Add IPC to configure the copier secondary pins Pradeep Tewani
2017-09-01 11:04 ` Vinod Koul [this message]
2017-09-01 11:11 ` Applied "ASoC: Intel: Skylake: Add IPC to configure the copier secondary pins" to the asoc tree 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=20170901110411.GB3053@localhost \
--to=vinod.koul@intel.com \
--cc=alsa-devel@alsa-project.org \
--cc=broonie@kernel.org \
--cc=lgirdwood@gmail.com \
--cc=patches.audio@intel.com \
--cc=pradeep.d.tewani@intel.com \
--cc=tiwai@suse.de \
/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.