All of lore.kernel.org
 help / color / mirror / Atom feed
From: Zidan Wang <zidan.wang@freescale.com>
To: Nicolin Chen <nicoleotsuka@gmail.com>
Cc: fabio.estevam@freescale.com, alsa-devel@alsa-project.org,
	tiwai@suse.com, timur@tabi.org, broonie@kernel.org
Subject: Re: [PATCH] ASoC: fsl-asoc-card: add wm8960 support
Date: Fri, 14 Aug 2015 15:38:16 +0800	[thread overview]
Message-ID: <20150814073758.GB11145@shlinux2> (raw)
In-Reply-To: <20150814035805.GA2180@Asurada>

On Thu, Aug 13, 2015 at 08:58:06PM -0700, Nicolin Chen wrote:
> On Fri, Aug 14, 2015 at 10:21:18AM +0800, Zidan Wang wrote:
> 
> > > And there is a crucial problem I can imagine:
> > >   Is it okay to set this bit while setting SD1_CLK PAD as one
> > >   of other functions rather than SAI MCLK? -- Customers might
> > >   keep your code as they also use SAI2 while using SD1_CLK PAD
> > >   as a GPIO input.
> 
> > I just add a gpr node in device tree, if customer want to use SD1_CLK
> > PAD as a GPIO input, remove the gpr node.
> 
> My question was whether setting this bit would cause a hardware
> damage -- Customers might not notice your gpr node in the Device
> Tree at all, not to mention the possibility of an accidental wrong
> configurations.
> 
> And another reason I asked that is to find out if we can set these
> bits anyway in the SoC level driver of imx6ul when this bit would
> not cause anything dangerous and when there's no extra clock MUX
> for the SAI MCLK between internal CCM and external clock source.
> 
This bit will not cause any hardware damage. 

ccm ----->1------------------>2<------------>3
	  |                   |
    	  |                   |		
	  4 SAIx MCLK1        5 SAIx MCLK2

If this bit is set, the clock route is ccm->1->2->3, 2 to 5 is disconnect.
If this bit is clear, the clock route is 3->2->5, 1 to 2 is disconnect.

Best Regards,
Zidan Wang

> Nicolin

  reply	other threads:[~2015-08-14  8:49 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-08-12  3:22 [PATCH] ASoC: fsl-asoc-card: add wm8960 support Zidan Wang
2015-08-12  3:42 ` Nicolin Chen
2015-08-12  4:45   ` Zidan Wang
2015-08-12  6:40     ` Nicolin Chen
2015-08-12  7:39       ` Zidan Wang
2015-08-12  9:03         ` Nicolin Chen
2015-08-12 22:27         ` Nicolin Chen
2015-08-14  2:21           ` Zidan Wang
2015-08-14  3:58             ` Nicolin Chen
2015-08-14  7:38               ` Zidan Wang [this message]
2015-08-14  9:22                 ` Nicolin Chen
2015-09-06 11:33                   ` Shawn Guo
2015-09-17  8:03                     ` Nicolin Chen
2015-09-18 13:19                       ` Shawn Guo
2015-09-19 17:50                         ` Nicolin Chen
2015-08-12 12:05 ` 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=20150814073758.GB11145@shlinux2 \
    --to=zidan.wang@freescale.com \
    --cc=alsa-devel@alsa-project.org \
    --cc=broonie@kernel.org \
    --cc=fabio.estevam@freescale.com \
    --cc=nicoleotsuka@gmail.com \
    --cc=timur@tabi.org \
    --cc=tiwai@suse.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.