From: "Maciej S. Szmigiero" <mail@maciej.szmigiero.name>
To: Timur Tabi <timur@tabi.org>,
"alsa-devel@alsa-project.org" <alsa-devel@alsa-project.org>
Cc: Nicolin Chen <nicoleotsuka@gmail.com>,
Xiubo Li <Xiubo.Lee@gmail.com>,
Liam Girdwood <lgirdwood@gmail.com>,
Mark Brown <broonie@kernel.org>, Jaroslav Kysela <perex@perex.cz>,
Takashi Iwai <tiwai@suse.de>,
linuxppc-dev@lists.ozlabs.org,
linux-kernel <linux-kernel@vger.kernel.org>,
Fabio Estevam <festevam@gmail.com>
Subject: Re: [PATCH 3/6] ASoC: fsl_ssi: enable AC'97 asymmetric rates
Date: Sun, 28 Jun 2015 21:12:19 +0200 [thread overview]
Message-ID: <55904713.4020101@maciej.szmigiero.name> (raw)
In-Reply-To: <558FFE4E.703@tabi.org>
W dniu 28.06.2015 16:01, Timur Tabi pisze:
> Maciej S. Szmigiero wrote:
>> /* Are the RX and the TX clocks locked? */
>> if (!of_find_property(np, "fsl,ssi-asynchronous", NULL)) {
>> - ssi_private->cpu_dai_drv.symmetric_rates = 1;
>> + if (!fsl_ssi_is_ac97(ssi_private))
>> + ssi_private->cpu_dai_drv.symmetric_rates = 1;
>> +
>
> Is this necessary? Why not just add fsl,ssi-asynchronous to the AC97 device tree node?
Because in the AC'97 mode the driver supports only one channel config and one sample format
anyway the remaining settings controlled by this property don't do anything.
Since it should be safe to enable asymmetric rates with any AC'97 CODEC I think it is good
to do it in driver than to add "fsl,ssi-asynchronous" to every AC'97 DT node.
Also the description of this property in fsl,ssi.txt looks like that it only makes sense in
non-AC'97 mode.
Best regards,
Maciej Szmigiero
next prev parent reply other threads:[~2015-06-28 19:12 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-06-28 13:46 Maciej S. Szmigiero
2015-06-28 14:01 ` Timur Tabi
2015-06-28 19:12 ` Maciej S. Szmigiero [this message]
2015-07-30 14:34 Maciej S. Szmigiero
2015-07-31 5:27 ` Markus Pargmann
2015-07-31 5:53 ` Markus Pargmann
2015-07-31 14:38 ` Maciej S. Szmigiero
2015-08-02 18:46 ` Markus Pargmann
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=55904713.4020101@maciej.szmigiero.name \
--to=mail@maciej.szmigiero.name \
--cc=Xiubo.Lee@gmail.com \
--cc=alsa-devel@alsa-project.org \
--cc=broonie@kernel.org \
--cc=festevam@gmail.com \
--cc=lgirdwood@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linuxppc-dev@lists.ozlabs.org \
--cc=nicoleotsuka@gmail.com \
--cc=perex@perex.cz \
--cc=timur@tabi.org \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®