From: Lars-Peter Clausen <lars@metafoo.de>
To: Nicolas Ferre <nicolas.ferre@atmel.com>,
Mark Brown <broonie@kernel.org>,
Liam Girdwood <lgirdwood@gmail.com>
Cc: alsa-devel@alsa-project.org
Subject: Re: [PATCH] ASoC: at91sam9g20ek: Automatically disconnect non-connected pins
Date: Mon, 13 Apr 2015 11:02:17 +0200 [thread overview]
Message-ID: <552B8619.5070703@metafoo.de> (raw)
In-Reply-To: <552B841A.20008@atmel.com>
On 04/13/2015 10:53 AM, Nicolas Ferre wrote:
> Le 11/04/2015 11:18, Lars-Peter Clausen a écrit :
>> According to the schematics the both LHPOUT and RHPOUT are connected to the
>> external connector. RHPOUT is missing from the DAPM routes, but otherwise
>> they seem to be complete.
>>
>> This patch adds the missing route and then sets the fully_routed flag for
>> the card. This allows to remove all the manual calls to
>> snd_soc_dapm_nc_pin().
>
> I don't understand: on the schematics, both the "RLINEIN" and "LLINEIN"
> are actually not connected. So, why remove these calls to
> snd_soc_dapm_nc_pin(). Note also that "ROUT" and "LOUT" signals are not
> connected as well.
>
For legacy reasons by default a INPUT or OUTPUT pin is considered connected
unless explicitly marked as non-connected. When the fully_routed flag is set
INPUT and OUTPUT pins are considered to be not connected unless explicitly
connected. What the patch does is set the fully_routed flag and remove the
explicit calls to snd_soc_dapm_nc_pin() since the pins are now considered to
be non-connected by default.
- Lars
next prev parent reply other threads:[~2015-04-13 9:02 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-04-11 9:18 [PATCH] ASoC: at91sam9g20ek: Automatically disconnect non-connected pins Lars-Peter Clausen
2015-04-13 8:53 ` Nicolas Ferre
2015-04-13 9:02 ` Lars-Peter Clausen [this message]
2015-04-13 9:07 ` Nicolas Ferre
2015-04-13 9:07 ` Nicolas Ferre
2015-04-18 12:20 ` 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=552B8619.5070703@metafoo.de \
--to=lars@metafoo.de \
--cc=alsa-devel@alsa-project.org \
--cc=broonie@kernel.org \
--cc=lgirdwood@gmail.com \
--cc=nicolas.ferre@atmel.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox