> Only 3430 and 3630 TRMs says 0xd, 0xe, 0xf = Division not supported. > I tested a 3503 with clock divider values of 0x0d, 0x0e and 0x0f. It worked fine. I collected data off the SPI bus successfully at the expected frequencies of 5859 Hz, 2929 Hz and 1464 Hz. > But then again, the TRMs can have errors. > Looks like this is a case of that. My patches #2 and #3 are unnecessary then and #4 makes use of a new field added in #3. I can resubmit #4, "Use transfer speed_hz if provided". That was the original problem I was working on. Should I leave the hard-coded 0x0f in the code or would you prefer a named constant? -- To unsubscribe from this list: send the line "unsubscribe linux-omap" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
