From: Scott Ellis <scott@jumpnowtek.com>
To: linux-omap@vger.kernel.org
Subject: [PATCH] omap2_mcspi.c: Clock divider range check wrong for OMAP3
Date: Mon, 08 Mar 2010 06:56:51 -0500 [thread overview]
Message-ID: <1268049411.2558.76.camel@quad> (raw)
The clock divider range check is wrong for the OMAP3.
The MCSPI_CHxCONF.CLKD register field has a max value 0x0C
not 0x0F. Reference was the OMAP3 TRM Rev. D manual.
I don't know whether the old value was correct for OMAP24xxx
boards so I put in some #ifdef stuff. Maybe someone with access
to the OMAP24xxx manual could check if that is necessary.
Signed-off-by: Scott Ellis <scott@jumpnowtek.com>
drivers/spi/omap2_mcspi.c | 24 +++++++++++++++++-------
1 files changed, 17 insertions(+), 7 deletions(-)
diff --git a/drivers/spi/omap2_mcspi.c b/drivers/spi/omap2_mcspi.c
index fe1b56d..a73127b 100644
--- a/drivers/spi/omap2_mcspi.c
+++ b/drivers/spi/omap2_mcspi.c
@@ -38,8 +38,17 @@
#include <plat/dma.h>
#include <plat/clock.h>
+#if defined(CONFIG_ARCH_OMAP3) || defined(CONFIG_ARCH_OMAP4)
+#define OMAP2_MCSPI_MAX_CLK_DIV 12
+#else
+/* could be 12 for OMAP24xxx also, no docs to check */
+#define OMAP2_MCSPI_MAX_CLK_DIV 15
+#endif
#define OMAP2_MCSPI_MAX_FREQ 48000000
+#define OMAP2_MCSPI_MIN_FREQ (OMAP2_MCSPI_MAX_FREQ \
+ / (1 << OMAP2_MCSPI_MAX_CLK_DIV))
+
/* OMAP2 has 3 SPI controllers, while OMAP3 has 4 */
#define OMAP2_MCSPI_MAX_CTRL 4
@@ -588,11 +597,12 @@ static int omap2_mcspi_setup_transfer(struct spi_device *spi,
cs->word_len = word_len;
if (spi->max_speed_hz) {
- while (div <= 15 && (OMAP2_MCSPI_MAX_FREQ / (1 << div))
- > spi->max_speed_hz)
+ while (div <= OMAP2_MCSPI_MAX_CLK_DIV &&
+ (OMAP2_MCSPI_MAX_FREQ / (1 << div)) > spi->max_speed_hz)
div++;
- } else
- div = 15;
+ } else {
+ div = OMAP2_MCSPI_MAX_CLK_DIV;
+ }
l = mcspi_cached_chconf0(spi);
@@ -917,10 +927,10 @@ static int omap2_mcspi_transfer(struct spi_device *spi, struct spi_message *m)
t->bits_per_word);
return -EINVAL;
}
- if (t->speed_hz && t->speed_hz < OMAP2_MCSPI_MAX_FREQ/(1<<16)) {
- dev_dbg(&spi->dev, "%d Hz max exceeds %d\n",
+ if (t->speed_hz && t->speed_hz < OMAP2_MCSPI_MIN_FREQ) {
+ dev_dbg(&spi->dev, "%d Hz slower then hardware minimum %d\n",
t->speed_hz,
- OMAP2_MCSPI_MAX_FREQ/(1<<16));
+ OMAP2_MCSPI_MIN_FREQ);
return -EINVAL;
}
next reply other threads:[~2010-03-08 11:56 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-03-08 11:56 Scott Ellis [this message]
2010-03-08 12:03 ` [PATCH] omap2_mcspi.c: Clock divider range check wrong for OMAP3 Gadiyar, Anand
2010-03-08 15:53 ` Felipe Balbi
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=1268049411.2558.76.camel@quad \
--to=scott@jumpnowtek.com \
--cc=linux-omap@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