linuxppc-dev.lists.ozlabs.org archive mirror
 help / color / mirror / Atom feed
From: Jon Smirl <jonsmirl@gmail.com>
To: linuxppc-dev <Linuxppc-dev@ozlabs.org>,
	Grant Likely <grant.likely@secretlab.ca>
Subject: PSC clock divider
Date: Fri, 7 Aug 2009 12:03:33 -0400	[thread overview]
Message-ID: <9e4733910908070903p539b8987p8351df5b3d328fdd@mail.gmail.com> (raw)

mpc52xx_set_psc_clkdiv() has problems. It take the clk divider as a
parameter. But this divisor is not always gettting calculated
correctly. My code in i2s was doing it wrong.

Take this snippet from the SPI driver, it just assumes a fsystem of
512Mhz. fsystem is 533Mhz on my boards.

	/* default sysclk is 512MHz */
	mclken_div = (mps->sysclk ? mps->sysclk : 512000000) / MCLK;
	mpc52xx_set_psc_clkdiv(psc_id, mclken_div);

Is it also not accounting for the hardware adding one to the divisor.

I've change i2s to this:

			if (!fsystem) {
				np = of_find_matching_node(NULL, mpc52xx_cdm_ids);
				mpc52xx_cdm = of_iomap(np, 0);
				fsystem = mpc5xxx_get_bus_frequency(np);
				of_node_put(np);
				val = in_be32(&mpc52xx_cdm->rstcfg);
				if (val & (1 << 5))
					fsystem *= 8;
				else
					fsystem *= 4;
				iounmap(mpc52xx_cdm);
			}
			clkdiv = fsystem / freq;
			err = fsystem % freq;
			if (err > freq / 2)
				clkdiv++;

			dev_dbg(psc_dma->dev, "psc_i2s_set_sysclk(clkdiv %d freq error=%dHz)\n",
					clkdiv, (fsystem / clkdiv - freq));

			/* PSC is 1-6 */
			/* Hardware adds 1 to divisor */
			return mpc52xx_set_psc_clkdiv(psc_dma->id + 1, clkdiv - 1);


Should I modify mpc52xx_set_psc_clkdiv() to take in a frequency and
them move this code into mpc52xx_common.c? That allows the sysclk
parameter to be eliminated for SPI.


-- 
Jon Smirl
jonsmirl@gmail.com

             reply	other threads:[~2009-08-07 16:03 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-08-07 16:03 Jon Smirl [this message]
2009-08-07 16:15 ` PSC clock divider Grant Likely
2009-08-07 16:34   ` Jon Smirl
2009-08-07 18:29     ` Grant Likely

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=9e4733910908070903p539b8987p8351df5b3d328fdd@mail.gmail.com \
    --to=jonsmirl@gmail.com \
    --cc=Linuxppc-dev@ozlabs.org \
    --cc=grant.likely@secretlab.ca \
    /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).