From: John Hsu <KCHSU0@nuvoton.com>
To: Mark Brown <broonie@kernel.org>
Cc: AP MS30 Linux ALSA <alsa-devel@alsa-project.org>,
"anatol.pomozov@gmail.com" <anatol.pomozov@gmail.com>,
AC30 YHChuang <YHCHuang@nuvoton.com>,
"lgirdwood@gmail.com" <lgirdwood@gmail.com>,
"benzh@chromium.org" <benzh@chromium.org>,
"mac.chiang@intel.com" <mac.chiang@intel.com>,
AC30 CTLin0 <CTLIN0@nuvoton.com>,
"yong.zhi@intel.com" <yong.zhi@intel.com>,
John Hsu <supercraig0719@gmail.com>,
MS40 MHKuo <MHKuo@nuvoton.com>
Subject: Re: [PATCH] ASoC: nau8825: devicetree for crosstalk bypass
Date: Thu, 29 Jun 2017 08:08:15 +0800 [thread overview]
Message-ID: <595444EF.3030700@nuvoton.com> (raw)
In-Reply-To: <20170628181415.gj6cc4jn47636hf6@sirena.org.uk>
On 6/29/2017 2:14 AM, Mark Brown wrote:
> On Mon, Jun 26, 2017 at 02:53:48PM +0800, John Hsu wrote:
>
>> + - nuvoton,crosstalk-bypass: make crosstalk function bypass if set 1.
>
> This should just be a boolean property, no need for a value.
Get it. I'll change it. Thank you.
===========================================================================================
The privileged confidential information contained in this email is intended for use only by the addressees as indicated by the original sender of this email. If you are not the addressee indicated in this email or are not responsible for delivery of the email to such a person, please kindly reply to the sender indicating this fact and delete all copies of it from your computer and network server immediately. Your cooperation is highly appreciated. It is advised that any unauthorized use of confidential information of Nuvoton is strictly prohibited; and any information in this email irrelevant to the official business of Nuvoton shall be deemed as neither given nor endorsed by Nuvoton.
prev parent reply other threads:[~2017-06-29 0:08 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-06-26 6:53 [PATCH] ASoC: nau8825: devicetree for crosstalk bypass John Hsu
2017-06-28 18:14 ` Mark Brown
2017-06-29 0:08 ` John Hsu [this message]
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=595444EF.3030700@nuvoton.com \
--to=kchsu0@nuvoton.com \
--cc=CTLIN0@nuvoton.com \
--cc=MHKuo@nuvoton.com \
--cc=YHCHuang@nuvoton.com \
--cc=alsa-devel@alsa-project.org \
--cc=anatol.pomozov@gmail.com \
--cc=benzh@chromium.org \
--cc=broonie@kernel.org \
--cc=lgirdwood@gmail.com \
--cc=mac.chiang@intel.com \
--cc=supercraig0719@gmail.com \
--cc=yong.zhi@intel.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.