Tool/software: Linux
Hi,
I'm working on latest ti sdk ti-processor-sdk-linux-am335x-evm-03.02.00.05-Linux-x86-Install and wants to use rtcwake command but getting an error.
Could anyone suggest me the changes required to mak ertcwake up work.
Below are logs:
root@ngt:~# rtcwake -d /dev/rtc0 -m standby -s 5
wakeup from "standby" at Sat Jan 1 00:22:41 2000
rtcwake: short write
Thanks and Regards
Deshvir Malik
Deshvir,
Deshvir Malik said:But in my customized board, I'm not getting "cpufreq"
Deshvir Malik said:Could you please suggest what configurations are required to get this?
If you are using linuxkernel 4.4.x, refer to the below wiki:
http://processors.wiki.ti.com/index.php/Linux_Core_Power_Management_User's_Guide_%28v4.4%29#Kernel_Configuration_Options
See also the below e2e threads:
Regards,
Pavel
Hi Pavel,
I have tried with couple of options but it didn't workout.
I'll tell you about my old working SDK configuration and new SDK configuration.
Old Working SDK
In old working SDK /drivers/rtc/rtc-omap.c was modified and below I have mentioned the modified section. While giving the "rtcwake -d /dev/rtc0 -m standby -s 5" or "rtcwake -d /dev/rtc0 -m mem -s 5", current is going upto 15mA and the board used to get restart after the time mentioned. (Board doesn't restart in new SDK)
They are few preconditions, which we need to make out board in rtc-only mode. We are satisfying these preconditions and then only board go in rtc-only mode. (This is not happening with new SDK, even after satisfying preconditiond board goes upto 55mA and if we do not satisfy preconditions, still board goes to 55mA).
1. power off function is commented here.
static struct rtc_class_ops omap_rtc_ops = {
.read_time = omap_rtc_read_time,
.set_time = omap_rtc_set_time,
.read_alarm = omap_rtc_read_alarm,
.set_alarm = omap_rtc_set_alarm,
/* .power_off = rtc_power_off, commented to remove compile error*/
.alarm_irq_enable = omap_rtc_alarm_irq_enable,
};
2. suspend function is commented and rtc_power_off() is called from omap_rtc_suspend() function.
static int omap_rtc_suspend(struct device *dev)
{
printk(KERN_INFO "***omap_rtc_suspend***\n");
#if 0
u8 irqwake_stat;
struct platform_device *pdev = to_platform_device(dev);
const struct platform_device_id *id_entry =
platform_get_device_id(pdev);
irqstat = rtc_read(OMAP_RTC_INTERRUPTS_REG);
/* FIXME the RTC alarm is not currently acting as a wakeup event
* source on some platforms, and in fact this enable() call is just
* saving a flag that's never used...
*/
if (device_may_wakeup(dev)) {
enable_irq_wake(omap_rtc_alarm);
if (id_entry->driver_data & OMAP_RTC_HAS_IRQWAKEEN) {
irqwake_stat = rtc_read(OMAP_RTC_IRQWAKEEN);
irqwake_stat |= OMAP_RTC_IRQWAKEEN_ALARM_WAKEEN;
rtc_write(irqwake_stat, OMAP_RTC_IRQWAKEEN);
}
} else {
rtc_write(0, OMAP_RTC_INTERRUPTS_REG);
}
/* Disable the clock/module */
pm_runtime_put_sync(dev);
return 0;
#endif
rtc_power_off();
return 0;
}
3. Some part of this function is commented
static void rtc_power_off(void)
{
printk(KERN_INFO "***rtc_power_off***\n");
u32 val;
struct rtc_time tm;
#if 0
/*Configuration may or may not needed*/
/* Set PMIC power enable SM */
val = readl(rtc_base + OMAP_RTC_PMIC_REG);
val |= OMAP_RTC_PWR_ENABLE_SM;
rtc_writel(val,OMAP_RTC_PMIC_REG);
/* Set PMIC polarity - active low */
val = readl(rtc_base + OMAP_RTC_PMIC_REG);
val |= OMAP_RTC_PMIC_EXT_WAKEUP_POL;
rtc_writel(val,OMAP_RTC_PMIC_REG);
#endif
/* Set OMAP_RTC_PMIC_EXT_WAKEUP_EN */
val = readl(rtc_base + OMAP_RTC_PMIC_REG);
val |= OMAP_RTC_PMIC_EXT_WAKEUP_EN;
rtc_writel(val,OMAP_RTC_PMIC_REG);
/* Set PMIC power enable */
val = readl(rtc_base + OMAP_RTC_PMIC_REG);
val |= OMAP_RTC_PMIC_POWER_EN_EN ;
rtc_writel(val,OMAP_RTC_PMIC_REG);
/* Wait few seconds instead of rollover */
do {
omap_rtc_read_time(NULL, &tm);
if (WAIT_AFTER <= tm.tm_sec)
mdelay(WAIT_TIME_MS);
} while (WAIT_AFTER <= tm.tm_sec);
/* Add shutdown time to the current value */
tm.tm_sec += SHUTDOWN_TIME_SEC;
if (tm2bcd(&tm) < 0)
return;
pr_info("System will go to power_off state in approx. %d secs\n",
SHUTDOWN_TIME_SEC);
/* Set the ALARM2 time */
rtc_write(tm.tm_sec, OMAP_RTC_ALARM2_SECONDS_REG);
rtc_write(tm.tm_min, OMAP_RTC_ALARM2_MINUTES_REG);
rtc_write(tm.tm_hour, OMAP_RTC_ALARM2_HOURS_REG);
rtc_write(tm.tm_mday, OMAP_RTC_ALARM2_DAYS_REG);
rtc_write(tm.tm_mon, OMAP_RTC_ALARM2_MONTHS_REG);
rtc_write(tm.tm_year, OMAP_RTC_ALARM2_YEARS_REG);
/* Enable alarm2 interrupt */
val = readl(rtc_base + OMAP_RTC_INTERRUPTS_REG);
writel(val | OMAP_RTC_INTERRUPTS_IT_ALARM2,
rtc_base + OMAP_RTC_INTERRUPTS_REG);
/* Do not allow to execute any other task */
while (1);
}
In new SDK, we have not done any changes in /drivers/rtc/rtc-omap.c and our current is going upto 55mA rather than going upto 15mA . Whether we satisfy our preconditions or not satisfy, in both cases current is going upto 55mA.
Also after giving rtcwake command we want the board to get restart.
Can you please let us know how to modify the rtc-omap driver so that our condition is satisfied.
Thanks and Regards,
Deshvir Malik
