AnsweredAssumed Answered

RTC SEC_MON ISSUE

Question asked by Nitesh Agrawal on Oct 4, 2016
Latest reply on Oct 12, 2016 by Nitesh Agrawal
I tried some changes in ls1021a.dtsi file, adding RTC device in device tree and enable the freescale rtc snvs driver support in kernel.
And also checking the driver by enabling prints in rtc_snvs.c (rtc driver).
It seems like we have problem in probing, we are not getting exact register address.
Following are  the dtsi file contents corresponding to freescale rtc snvs driver support.
sec_mon: sec_mon@1e90000 {
   compatible = "fsl,sec-v4.0-mon","simple-bus";
   #address-cells = <1>;
   #size_cells = <1>;
   ranges = <0x0 0x0 0x1e90000 0x10000>;

   

   snvs_rtc: snvs_rtc_lp@34 {

      compatible = "VVDN";
      reg = <0x34 0x58>;
      interrupts = <GIC_SPI 110 IRQ_TYPE_LEVEL_HIGH>, <GIC_SPI 111 IRQ_TYPE_LEVEL_HIGH>;
   };
};
now the logs are.-
[  162.852196] snvs_rtc_probe****************
[  162.856290] snvs_rtc 3400000058.snvs_rtc_lp: invalid resource
[  162.862033] snvs_rtc: probe of 3400000058.snvs_rtc_lp failed with error -22
[  163.164138] drivers/rtc/hctosys.c: unable to open rtc device (rtc0)
please suggest something on this issue.

Outcomes