> On Tuesday 24 July 2007, David Brownell wrote:
>> I want to be sure I understand this correctly. You're saying that
>> the call to spi_setup() inside of spi_new_device() failed silently?
No, I did not make myself clear.
I was talking about this code in spi_imx.c:
/* SPI datarate */
tmp = spi_data_rate(spi->max_speed_hz);
if (tmp == SPI_CONTROL_DATARATE_BAD) {
status = -EINVAL;
dev_err(&spi->dev,
"setup - "
"HW min speed (%d Hz) exceeds required "
"max speed (%d Hz)\n",
spi_speed_hz(SPI_CONTROL_DATARATE_MIN),
spi->max_speed_hz);
if (first_setup)
goto err_first_setup;
else
/* Undo setup using chip as backup copy */
Since the reference clock feeding the SPI controller was too high, it
was not able to generate the required SPI clock. Probably I did not pay
enough attention, but it seems kernel did not print these error messages
so it took a while to recognize that the this was the problem.
--
llandre
DAVE Electronics System House - R&D Department
web: http://www.dave-tech.it
email: r&[EMAIL PROTECTED]
-------------------------------------------------------------------------
This SF.net email is sponsored by: Splunk Inc.
Still grepping through log files to find problems? Stop.
Now Search log events and configuration files using AJAX and a browser.
Download your FREE copy of Splunk now >> http://get.splunk.com/
_______________________________________________
spi-devel-general mailing list
spi-devel-general@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/spi-devel-general
