From: Clifford Wolf <clifford@clifford.at>
To: galak@kernel.crashing.org
Cc: lkml <linux-kernel@vger.kernel.org>
Subject: [PATCH] spi_mpc83xx.c underclocking hotfix
Date: Wed, 6 Jun 2007 19:34:03 +0200 [thread overview]
Message-ID: <20070606173402.GA15877@clifford.at> (raw)
[-- Attachment #1: Type: text/plain, Size: 700 bytes --]
Hi kumar (spi_mpc83xx maintainer), Hi list,
the MPC83xx SPI controller clock divider can divide the system clock by not
more then 1024. The spi_mpc83xx driver does not check this and silently
writes garbage to the SPI controller registers when asked to run at lower
frequencies. I've tried to run the SPI on a 266MHz MPC8349E with 100kHz for
debugging a bus problem and suddenly was confronted with a 2nd problem to
debug.. ;-)
The attached patch adds an additional check which avoids writing garbage to
the SPI controller registers and warn the user about it. This might help
others to avoid simmilar problems.
yours,
- clifford
--
Hardware /nm./: the part of the computer that you can kick.
[-- Attachment #2: spi_mpc83xx_hotfix.patch --]
[-- Type: text/plain, Size: 691 bytes --]
Index: drivers/spi/spi_mpc83xx.c
===================================================================
--- drivers/spi/spi_mpc83xx.c (revision 170)
+++ drivers/spi/spi_mpc83xx.c (working copy)
@@ -158,6 +158,12 @@
if ((mpc83xx_spi->sysclk / spi->max_speed_hz) >= 64) {
u8 pm = mpc83xx_spi->sysclk / (spi->max_speed_hz * 64);
+ if (pm > 0x0f) {
+ printk(KERN_WARNING "MPC83xx SPI: SPICLK can't be less then a SYSCLK/1024!\n"
+ "Requested SPICLK is %d Hz. Will use %d Hz instead.\n",
+ spi->max_speed_hz, mpc83xx_spi->sysclk / 1024);
+ pm = 0x0f;
+ }
regval |= SPMODE_PM(pm) | SPMODE_DIV16;
} else {
u8 pm = mpc83xx_spi->sysclk / (spi->max_speed_hz * 4);
reply other threads:[~2007-06-06 17:31 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=20070606173402.GA15877@clifford.at \
--to=clifford@clifford.at \
--cc=galak@kernel.crashing.org \
--cc=linux-kernel@vger.kernel.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
all inboxes | Powered by JetHome®