max310x: bug in driver when using MAX3107 with crystal

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



Hello folks,

I've been using the MAX3107 IC and I had to tweak a bit the driver code to make things work. We use a crystal connected to the internal crystal oscillator to generate the clock and the CLKSRC register was not set properly. When using a crystal both bits alternatively select by this line of code should be set:

max310x.c:574
clksrc = xtal ? MAX310X_CLKSRC_CRYST_BIT : MAX310X_CLKSRC_EXTCLK_BIT;

The MAX310X_CLKSRC_EXTCLK_BIT is named ClockEnable in the MAX3107 documentation (http://datasheets.maximintegrated.com/en/ds/MAX3107.pdf). It actually connects / disconnects the clock signal to the PLL block - the signal being generated by either the crystal/oscillator pair or by some other external source.

As this driver needs to work with other devices that I would rather not propose a patch.

  I would though be available to do some testing.

  Best regards

--
Gaetan
--
To unsubscribe from this list: send the line "unsubscribe linux-serial" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at  http://vger.kernel.org/majordomo-info.html




[Index of Archives]     [Kernel Newbies]     [Security]     [Netfilter]     [Bugtraq]     [Linux PPP]     [Linux FS]     [Yosemite News]     [MIPS Linux]     [ARM Linux]     [Linux Security]     [Linux RAID]     [Samba]     [Video 4 Linux]     [Linmodem]     [Device Mapper]     [Linux Kernel for ARM]

  Powered by Linux