Search

Technical Discussion Group Forum

This forum is provided for user discussion. While Logic PD support staff and engineers participate, Logic PD does not guarantee the accuracy of all information within in the Technical Discussion Group (TDG).

The "Articles" forums provide brief Articles written by Logic PD engineers that address the most frequently asked technical questions.

To receive email notifications when updates are posted for a Logic PD product download, please subscribe to the TDG Forum of interest.

PrevPrev Go to previous topic
NextNext Go to next topic
Last Post 23 Apr 2018 08:25 AM by  Marco Fonseca
RTC issues on 4.9.x ?
 2 Replies
Sort:
You are not authorized to post a reply.
Author Messages
Marco Fonseca
New Member
New Member
Posts:15


--
19 Apr 2018 05:42 PM

    Hello Adam,                                                                                                                                        
     

    Are there any known problems with the RTC using a mainline kernel?  I'm currently at 4.9.94 and seeing inconsistant readings from the rtc.    I sprinkled twl_rtc_read_time() with some logging and noticed about half the time I get incorrect values.

     

    Also, I noticed (via another thread) you are close to release a 4.9 kernel.  Are there patches on your end that are not in mainline that would be avalible?

                                                                                         
    Thanks,                                                                                                                                       

    Marco Fonseca

    Adam Ford
    Advanced Member
    Advanced Member
    Posts:783


    --
    23 Apr 2018 06:59 AM
    The patches I submitted to help are: https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux-stable.git/commit/arch/arm/boot/dts/logicpd-torpedo-som.dtsi?h=v4.9.95&id=c737c8d04d16c4259ced96fdd69e6664aa64d926

    I think they part of 4.9.94, so if you're still having issues, try slowing the I2C1 clock from 2.6MHz to 400KHz.

    &i2c1 {
    pinctrl-names = "default";
    pinctrl-0 = <&i2c1_pins>;
    clock-frequency = <400000>;
    ...
    };
    Marco Fonseca
    New Member
    New Member
    Posts:15


    --
    23 Apr 2018 08:25 AM

    Changing the clock form 2.6mhz to 400khz did indeed solve the problem!

    Also as you said, the patch you linked to had alread been applied.

    Thank you!

     

    Marco Fonseca

    You are not authorized to post a reply.