From: Xavi Drudis Ferran <xdrudis@tinet.cat>
To: Nicolin Chen <nicoleotsuka@gmail.com>
Cc: Xavi Drudis Ferran <xdrudis@tinet.cat>,
fabio.estevam@nxp.com, Timur Tabi <timur@tabi.org>,
Xiubo Li <Xiubo.Lee@gmail.com>,
Shengjiu Wang <shengjiu.wang@freescale.com>,
alsa-devel@alsa-project.org, linuxppc-dev@lists.ozlabs.org
Subject: Re: Setting some clocks back to DUMMY fixes spdif output on imx6q wandboard rev B1
Date: Mon, 29 Aug 2016 21:54:28 +0200 [thread overview]
Message-ID: <20160829195428.GD1967@begut> (raw)
In-Reply-To: <20160829192820.GA14207@Asurada-Nvidia>
El Mon, Aug 29, 2016 at 12:28:21PM -0700, Nicolin Chen deia:
>
> Yes, it seems that it also tried to correct the clock sources
> as those were not available when adding the S/PDIF support at
> the first place.
>
I wonder if maybe they need to be defined, assigned or somehow listed
elsewhere and they are not for wandboard quad (but are for other boards)?
> > The issue is fixed for me with this patch but I'm not sure what's the
> > best way to help fix any issue someone else may have or what other
> > info or test you might need. Any guidance welcome.
>
> > --- linux-4.7-no-spdif-out/arch/arm/boot/dts/imx6qdl.dtsi 2016-07-25 00:19:43.000000000 +0200
> > +++ linux-4.7/arch/arm/boot/dts/imx6qdl.dtsi 2016-08-28 17:59:14.276774409 +0200
> > @@ -240,9 +240,9 @@
> > <&sdma 15 18 0>;
> > dma-names = "rx", "tx";
> > clocks = <&clks IMX6QDL_CLK_SPDIF_GCLK>, <&clks IMX6QDL_CLK_OSC>,
> > - <&clks IMX6QDL_CLK_SPDIF>, <&clks IMX6QDL_CLK_ASRC>,
> > - <&clks IMX6QDL_CLK_DUMMY>, <&clks IMX6QDL_CLK_ESAI_EXTAL>,
> > - <&clks IMX6QDL_CLK_IPG>, <&clks IMX6QDL_CLK_MLB>,
> > + <&clks IMX6QDL_CLK_SPDIF>, <&clks IMX6QDL_CLK_DUMMY>,
> > + <&clks IMX6QDL_CLK_DUMMY>, <&clks IMX6QDL_CLK_DUMMY>,
> > + <&clks IMX6QDL_CLK_DUMMY>, <&clks IMX6QDL_CLK_DUMMY>,
> > <&clks IMX6QDL_CLK_DUMMY>, <&clks IMX6QDL_CLK_SPBA>;
> > clock-names = "core", "rxtx0",
> > "rxtx1", "rxtx2",
>
> This looks like that you merely revert the SPDIF_GCLK.
I revert only some clocks, yes. I left SPDIF_GCLK and CLK_SBPA intact.
So it is a partial revert of the commit.
> Would you
> please do a little debug using "#define DEBUG 1" and check printk
> from fsl_spdif_probe_txclk() to see the difference between before
> and after Shengjiu's commit?
Yes, but I'm compiling the kernel in the wandboard, so it'll take me some time.
Thank you.
next prev parent reply other threads:[~2016-08-29 20:10 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20160828160055.GA2122@begut>
2016-08-29 19:28 ` Setting some clocks back to DUMMY fixes spdif output on imx6q wandboard rev B1 Nicolin Chen
2016-08-29 19:54 ` Xavi Drudis Ferran [this message]
2016-08-30 11:14 ` Xavi Drudis Ferran
2016-08-31 4:21 ` Nicolin Chen
2016-08-31 9:10 ` Xavi Drudis Ferran
2016-08-31 13:11 ` [alsa-devel] " Fabio Estevam
2016-08-31 13:30 ` Fabio Estevam
2016-08-31 13:47 ` Xavi Drudis Ferran
2016-08-31 14:02 ` Fabio Estevam
2016-08-31 13:49 ` Xavi Drudis Ferran
2016-08-31 17:49 ` Xavi Drudis Ferran
2016-08-31 18:02 ` Fabio Estevam
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=20160829195428.GD1967@begut \
--to=xdrudis@tinet.cat \
--cc=Xiubo.Lee@gmail.com \
--cc=alsa-devel@alsa-project.org \
--cc=fabio.estevam@nxp.com \
--cc=linuxppc-dev@lists.ozlabs.org \
--cc=nicoleotsuka@gmail.com \
--cc=shengjiu.wang@freescale.com \
--cc=timur@tabi.org \
/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;
as well as URLs for NNTP newsgroup(s).