• State TI Thinks Resolved
  • Locked Locked
  • Replies 34 replies
  • Answers 1 answer
  • Subscribers 101 subscribers
  • Views 5015 views
  • Users 0 members are here
Support feedback
Options
Options
Similar topics

This thread has been locked.

If you have a related question, please click the "Ask a related question" button in the top right corner. The newly created question will be automatically linked to this question.

AM335x wakeup issue with SDK 3.00.00.04

veera anjaneyulu
Expert 1920 points
Other Parts Discussed in Thread: TMDSSK3358, AM3352, SYSCONFIG

Hi all,

we are facing power wakeup resuming issue.while running below commands

echo mem > /sys/power/state

4 or five its getting automatically resuming .whats the reason.Any body solve this issue can you give me idea.

  • 0
    TI__Guru**** 393215 points
    Please provide your boot log file.
  • 0 in reply to Biser Gatchev-XID
    Expert 1920 points

    ya we followed above link only.my boot logs attached below .please find my boot logs.

    Thanks 

    veera

    power-wakeup-boot-logs.txt 
    U-Boot SPL 2016.05 (Oct 07 2016 - 17:48:39)
Trying to boot from MMC1
reading args
spl_load_image_fat_os: error reading image args, err - -1
reading u-boot.img
reading u-boot.img
reading u-boot.img
reading u-boot.img


U-Boot 2016.05 (Oct 07 2016 - 17:48:39 +0530)

       Watchdog enabled
I2C:   ready
DRAM:  256 MiB
NAND:  0 MiB
MMC:   OMAP SD/MMC: 0, OMAP SD/MMC: 1
reading uboot.env
Net:   
Warning: ethernet@4a100000 MAC addresses don't match:
Address in SROM is         68:9e:19:84:24:e7
Address in environment is  68:c9:0b:7d:26:22
eth0: ethernet@4a100000
Warning: usb_ether MAC addresses don't match:
Address in SROM is         de:ad:be:ef:00:01
Address in environment is  68:c9:0b:7d:26:24
, eth1: usb_ether
Press SPACE to abort autoboot in 1 seconds
switch to partitions #0, OK
mmc0 is current device
Scanning mmc 0:1...
switch to partitions #0, OK
mmc0 is current device
SD/MMC found on device 0
2117672 bytes read in 143 ms (14.1 MiB/s)
39990 bytes read in 17 ms (2.2 MiB/s)
Kernel image @ 0x82000000 [ 0x000000 - 0x205028 ]
## Flattened Device Tree blob at 88000000
   Booting using the fdt blob at 0x88000000
   Loading Device Tree to 8ef1d000, end 8ef29c35 ... OK

Starting kernel ...

[    0.000000] Booting Linux on physical CPU 0x0
[    0.000000] Initializing cgroup subsys cpu
[    0.000000] Initializing cgroup subsys cpuacct
[    0.000000] Linux version 4.4.12-g3639bea54a (santosh@FSETBLR1LX057) (gcc version 5.3.1 20160113 (Linaro GCC 5.3-2016.02) ) #6 PREEMPT Thu Oct 13 13:33:05 IST 2016
[    0.000000] CPU: ARMv7 Processor [413fc082] revision 2 (ARMv7), cr=10c5387d
[    0.000000] CPU: PIPT / VIPT nonaliasing data cache, VIPT aliasing instruction cache
[    0.000000] Machine model: TI AM335x EVM-SK
[    0.000000] cma: Reserved 24 MiB at 0x8d000000
[    0.000000] Memory policy: Data cache writeback
[    0.000000] CPU: All CPU(s) started in SVC mode.
[    0.000000] AM335X ES2.1 (neon )
[    0.000000] Built 1 zonelists in Zone order, mobility grouping on.  Total pages: 64960
[    0.000000] Kernel command line: console=ttyO0,115200n8 root=PARTUUID=0004e8ac-02 rw rootfstype=ext4 rootwait
[    0.000000] PID hash table entries: 1024 (order: 0, 4096 bytes)
[    0.000000] Dentry cache hash table entries: 32768 (order: 5, 131072 bytes)
[    0.000000] Inode-cache hash table entries: 16384 (order: 4, 65536 bytes)
[    0.000000] Memory: 228552K/262144K available (4015K kernel code, 153K rwdata, 1604K rodata, 220K init, 218K bss, 9016K reserved, 24576K cma-reserved, 0K highmem)
[    0.000000] Virtual kernel memory layout:
[    0.000000]     vector  : 0xffff0000 - 0xffff1000   (   4 kB)
[    0.000000]     fixmap  : 0xffc00000 - 0xfff00000   (3072 kB)
[    0.000000]     vmalloc : 0xd0800000 - 0xff800000   ( 752 MB)
[    0.000000]     lowmem  : 0xc0000000 - 0xd0000000   ( 256 MB)
[    0.000000]     pkmap   : 0xbfe00000 - 0xc0000000   (   2 MB)
[    0.000000]     modules : 0xbf000000 - 0xbfe00000   (  14 MB)
[    0.000000]       .text : 0xc0008000 - 0xc0584e34   (5620 kB)
[    0.000000]       .init : 0xc0585000 - 0xc05bc000   ( 220 kB)
[    0.000000]       .data : 0xc05bc000 - 0xc05e24d8   ( 154 kB)
[    0.000000]        .bss : 0xc05e4000 - 0xc061aab4   ( 219 kB)
[    0.000000] SLUB: HWalign=64, Order=0-3, MinObjects=0, CPUs=1, Nodes=1
[    0.000000] Preemptible hierarchical RCU implementation.
[    0.000000]  Build-time adjustment of leaf fanout to 32.
[    0.000000] NR_IRQS:16 nr_irqs:16 16
[    0.000000] IRQ: Found an INTC at 0xfa200000 (revision 5.0) with 128 interrupts
[    0.000000] OMAP clockevent source: timer2 at 24000000 Hz
[    0.000014] sched_clock: 32 bits at 24MHz, resolution 41ns, wraps every 89478484971ns
[    0.000038] clocksource: timer1: mask: 0xffffffff max_cycles: 0xffffffff, max_idle_ns: 79635851949 ns
[    0.000049] OMAP clocksource: timer1 at 24000000 Hz
[    0.000535] clocksource_probe: no matching clocksources found
[    0.000574] WARNING: Your 'console=ttyO0' has been replaced by 'ttyS0'
[    0.000581] This ensures that you still see kernel messages. Please
[    0.000588] update your kernel commandline.
[    0.000611] Calibrating delay loop... 795.44 BogoMIPS (lpj=3977216)
[    0.088994] pid_max: default: 32768 minimum: 301
[    0.089141] Mount-cache hash table entries: 1024 (order: 0, 4096 bytes)
[    0.089155] Mountpoint-cache hash table entries: 1024 (order: 0, 4096 bytes)
[    0.089906] Initializing cgroup subsys io
[    0.089937] Initializing cgroup subsys memory
[    0.089974] Initializing cgroup subsys devices
[    0.089991] Initializing cgroup subsys freezer
[    0.090006] Initializing cgroup subsys pids
[    0.090039] CPU: Testing write buffer coherency: ok
[    0.090459] Setting up static identity map for 0x80008200 - 0x80008258
[    0.092750] devtmpfs: initialized
[    0.105220] VFP support v0.3: implementor 41 architecture 3 part 30 variant c rev 3
[    0.119934] omap_hwmod: debugss: _wait_target_disable failed
[    0.175740] clocksource: jiffies: mask: 0xffffffff max_cycles: 0xffffffff, max_idle_ns: 19112604462750000 ns
[    0.177943] pinctrl core: initialized pinctrl subsystem
[    0.179336] NET: Registered protocol family 16
[    0.181656] DMA: preallocated 256 KiB pool for atomic coherent allocations
[    0.208994] cpuidle: using governor ladder
[    0.238980] cpuidle: using governor menu
[    0.243772] OMAP GPIO hardware version 0.1
[    0.297016] edma 49000000.edma: TI EDMA DMA engine driver
[    0.299562] usbcore: registered new interface driver usbfs
[    0.299647] usbcore: registered new interface driver hub
[    0.299757] usbcore: registered new device driver usb
[    0.300379] omap_i2c 44e0b000.i2c: could not find pctldev for node /ocp/l4_wkup@44c00000/scm@210000/pinmux@800/pinmux_i2c0_pins, deferring probe
[    0.300555] pps_core: LinuxPPS API ver. 1 registered
[    0.300565] pps_core: Software ver. 5.3.6 - Copyright 2005-2007 Rodolfo Giometti <giometti@linux.it>
[    0.300597] PTP clock support registered
[    0.301375] omap-mailbox 480c8000.mailbox: omap mailbox rev 0x400
[    0.302394] clocksource: Switched to clocksource timer1
[    0.304633] NET: Registered protocol family 2
[    0.305464] TCP established hash table entries: 2048 (order: 1, 8192 bytes)
[    0.305500] TCP bind hash table entries: 2048 (order: 1, 8192 bytes)
[    0.305528] TCP: Hash tables configured (established 2048 bind 2048)
[    0.305623] UDP hash table entries: 256 (order: 0, 4096 bytes)
[    0.305644] UDP-Lite hash table entries: 256 (order: 0, 4096 bytes)
[    0.305800] NET: Registered protocol family 1
[    0.308317] futex hash table entries: 256 (order: -1, 3072 bytes)
[    0.316667] ntfs: driver 2.1.32 [Flags: R/O].
[    0.322133] Block layer SCSI generic (bsg) driver version 0.4 loaded (major 251)
[    0.322165] io scheduler noop registered
[    0.322180] io scheduler deadline registered
[    0.322352] io scheduler cfq registered (default)
[    0.323637] pinctrl-single 44e10800.pinmux: 142 pins at pa f9e10800 size 568
[    0.324728] wkup_m3_ipc 44e11324.wkup_m3_ipc: could not get rproc handle
[    0.325188] Serial: 8250/16550 driver, 3 ports, IRQ sharing disabled
[    0.327331] 44e09000.serial: ttyS0 at MMIO 0x44e09000 (irq = 158, base_baud = 3000000) is a 8250
[    0.861010] console [ttyS0] enabled
[    0.865492] 48024000.serial: ttyS2 at MMIO 0x48024000 (irq = 159, base_baud = 3000000) is a 8250
[    0.875734] libphy: Fixed MDIO Bus: probed
[    0.942431] davinci_mdio 4a101000.mdio: davinci mdio revision 1.6
[    0.948569] davinci_mdio 4a101000.mdio: detected phy mask ffffffbe
[    0.956277] libphy: 4a101000.mdio: probed
[    0.960324] davinci_mdio 4a101000.mdio: phy[0]: device 4a101000.mdio:00, driver SMSC LAN8740
[    0.968898] davinci_mdio 4a101000.mdio: phy[6]: device 4a101000.mdio:06, driver SMSC LAN8740
[    0.978026] cpsw 4a100000.ethernet: Detected MACID = 68:c9:0b:7d:26:22
[    0.985719] cpsw 4a100000.ethernet: cpsw: Detected MACID = 68:c9:0b:7d:26:24
[    0.993666] PPP generic driver version 2.4.2
[    0.998364] usbcore: registered new interface driver cdc_ether
[    1.004386] usbcore: registered new interface driver cdc_subset
[    1.010457] usbcore: registered new interface driver cdc_ncm
[    1.016230] usbcore: registered new interface driver qmi_wwan
[    1.022615] ehci_hcd: USB 2.0 'Enhanced' Host Controller (EHCI) Driver
[    1.029180] ehci-platform: EHCI generic platform driver
[    1.034650] ehci-omap: OMAP-EHCI Host Controller driver
[    1.040011] ohci_hcd: USB 1.1 'Open' Host Controller (OHCI) Driver
[    1.046251] ohci-platform: OHCI generic platform driver
[    1.051950] usbcore: registered new interface driver cdc_acm
[    1.057660] cdc_acm: USB Abstract Control Model driver for USB modems and ISDN adapters
[    1.065779] usbcore: registered new interface driver cdc_wdm
[    1.071595] usbcore: registered new interface driver usbserial
[    1.077531] usbcore: registered new interface driver option
[    1.083209] usbserial: USB Serial support registered for GSM modem (1-port)
[    1.092063] 47401b00.usb-phy supply vcc not found, using dummy regulator
[    1.124551] musb-hdrc musb-hdrc.0.auto: Failed to request rx1.
[    1.130450] musb-hdrc musb-hdrc.0.auto: musb_init_controller failed with status -517
[    1.146325] omap_rtc 44e3e000.rtc: rtc core: registered 44e3e000.rtc as rtc0
[    1.153711] i2c /dev entries driver
[    1.157918] cpuidle: enable-method property 'ti,am3352' found operations
[    1.164907] sdhci: Secure Digital Host Controller Interface driver
[    1.171113] sdhci: Copyright(c) Pierre Ossman
[    1.175959] omap_hsmmc 48060000.mmc: Got CD GPIO
[    1.180681] omap_hsmmc 48060000.mmc: Got WP GPIO
[    1.332742] sdhci-pltfm: SDHCI platform and OF driver helper
[    1.342243] usbcore: registered new interface driver usbhid
[    1.347946] usbhid: USB HID core driver
[    1.351827] omap_hsmmc 481d8000.mmc: card claims to support voltages below defined range
[    1.360553]  remoteproc0: wkup_m3 is available
[    1.365068]  remoteproc0: Note: remoteproc is still under development and considered experimental.
[    1.374108]  remoteproc0: THE BINARY FORMAT IS NOT YET FINALIZED, and backward compatibility isn't yet guaranteed.
[    1.385640] nf_conntrack version 0.5.0 (3955 buckets, 15820 max)
[    1.393096] ip_tables: (C) 2000-2006 Netfilter Core Team
[    1.398609] arp_tables: (C) 2002 David S. Miller
[    1.403433] NET: Registered protocol family 17
[    1.408017] Key type dns_resolver registered
[    1.412474] omap_voltage_late_init: Voltage driver support not added
[    1.419842] PM: Cannot get wkup_m3_ipc handle
[    1.424364] ThumbEE CPU extension supported.
[    1.428711] Registering SWP/SWPB emulation handler
[    1.438904] mmc0: queuing unknown CIS tuple 0x91 (3 bytes)
[    1.445228] mmc0: new high speed SDIO card at address 0001
[    1.452574] tps65910 0-002d: No interrupt support, no core IRQ
[    1.481031] omap_i2c 44e0b000.i2c: bus 0 rev0.11 at 400 kHz
[    1.492485]  remoteproc0: powering up wkup_m3
[    1.496891]  remoteproc0: Booting fw image am335x-pm-firmware.elf, size 217100
[    1.505822] musb-hdrc musb-hdrc.0.auto: MUSB HDRC host driver
[    1.511626] musb-hdrc musb-hdrc.0.auto: new USB bus registered, assigned bus number 1
[    1.519758]  remoteproc0: remote processor wkup_m3 is now up
[    1.525458] wkup_m3_ipc 44e11324.wkup_m3_ipc: CM3 Firmware Version = 0x191
[    1.532573] wkup_m3_ipc 44e11324.wkup_m3_ipc: Direct firmware load for am335x-evm-scale-data.bin failed with error -2
[    1.544443] hub 1-0:1.0: USB hub found
[    1.548269] hub 1-0:1.0: 1 port detected
[    1.552312] wkup_m3_ipc 44e11324.wkup_m3_ipc: Falling back to user helper
[    1.583016] omap_hsmmc 48060000.mmc: Got CD GPIO
[    1.587754] omap_hsmmc 48060000.mmc: Got WP GPIO
[    1.593015] mmc_card_regulator: supplied by vbat
[    1.633010] PM: bootloader does not support rtc-only!
[    1.638296] omap_rtc 44e3e000.rtc: setting system clock to 2000-01-01 00:00:00 UTC (946684800)
[    1.647616] lis3_reg: disabling
[    1.694151] Waiting for root device PARTUUID=0004e8ac-02...
[    1.838423] mmc1: new high speed SDHC card at address aaaa
[    1.844778] mmcblk0: mmc1:aaaa SS08G 7.40 GiB 
[    1.855644]  mmcblk0: p1 p2
[    2.028805] EXT4-fs (mmcblk0p2): recovery complete
[    2.040363] EXT4-fs (mmcblk0p2): mounted filesystem with ordered data mode. Opts: (null)
[    2.048664] VFS: Mounted root (ext4 filesystem) on device 179:2.
[    2.062673] devtmpfs: mounted
[    2.066073] Freeing unused kernel memory: 220K (c0585000 - c05bc000)
[    2.072694] This architecture does not have kernel memory protection.
[    2.339224] systemd[1]: System time before build time, advancing clock.
[    2.412213] random: systemd urandom read with 23 bits of entropy available
[    2.436443] systemd[1]: systemd 229 running in system mode. (+PAM -AUDIT -SELINUX +IMA -APPARMOR +SMACK +SYSVINIT +UTMP -LIBCRYPTSETUP -GCRYPT -GNUTLS +ACL +XZ -LZ4 -)
[    2.455513] systemd[1]: Detected architecture arm.

Welcome to Arago 2016.07!

[    2.488571] systemd[1]: Set hostname to <am335x-evm>.
[    3.035842] systemd[1]: Listening on Journal Socket.
[  OK  ] Listening on Journal Socket.
[    3.063416] systemd[1]: Listening on udev Kernel Socket.
[  OK  ] Listening on udev Kernel Socket.
[    3.107108] systemd[1]: Created slice System Slice.
[  OK  ] Created slice System Slice.
[    3.151012] systemd[1]: Mounting /media/ram...
         Mounting /media/ram...
[    3.195275] systemd[1]: Mounting /var/volatile...
         Mounting /var/volatile...
[    3.254991] systemd[1]: Starting Load Kernel Modules...
         Starting Load Kernel Modules...
[    3.285501] systemd[1]: Created slice system-serial\x2dgetty.slice.
[  OK  ] Created slice system-serial\x2dgetty.slice.
[    3.308655] systemd[1]: Created slice system-getty.slice.
[  OK  ] Created slice system-getty.slice.
[    3.342002] systemd[1]: Listening on udev Control Socket.
[  OK  ] Listening on udev Control Socket.
[    3.386201] systemd[1]: Starting udev Kernel Device Manager...
         Starting udev Kernel Device Manager...
[    3.444370] systemd[1]: Starting udev Coldplug all Devices...
         Starting udev Coldplug all Devices...
[    3.527385] systemd[1]: Mounted /var/volatile.
[  OK  ] Mounted /var/volatile.
[    3.563276] systemd[1]: Mounted /media/ram.
[  OK  ] Mounted /media/ram.
[    3.774687] systemd[1]: Started udev Kernel Device Manager.
[  OK  ] Started udev Kernel Device Manager.
[    3.861662] systemd[1]: Started Load Kernel Modules.
[  OK  ] Started Load Kernel Modules.
[    3.987245] cfg80211: World regulatory domain updated:
[    4.055699] cfg80211:  DFS Master region: unset
[    4.060110] cfg80211:   (start_freq - end_freq @ bandwidth), (max_antenna_gain, max_eirp), (dfs_cac_time)
[    4.142630] cfg80211:   (2402000 KHz - 2472000 KHz @ 40000 KHz), (N/A, 2000 mBm), (N/A)
[    4.150700] cfg80211:   (2457000 KHz - 2482000 KHz @ 40000 KHz), (N/A, 2000 mBm), (N/A)
[    4.159713] wlcore: wl18xx HW: 183x or 180x, PG 2.2 (ROM 0x11)
[    4.229615] cfg80211:   (2474000 KHz - 2494000 KHz @ 20000 KHz), (N/A, 2000 mBm), (N/A)
[    4.262550] cfg80211:   (5170000 KHz - 5250000 KHz @ 80000 KHz, 160000 KHz AUTO), (N/A, 2000 mBm), (N/A)
[    4.272103] cfg80211:   (5250000 KHz - 5330000 KHz @ 80000 KHz, 160000 KHz AUTO), (N/A, 2000 mBm), (0 s)
[    4.322641] cfg80211:   (5490000 KHz - 5730000 KHz @ 160000 KHz), (N/A, 2000 mBm), (0 s)
[    4.330797] cfg80211:   (5735000 KHz - 5835000 KHz @ 80000 KHz), (N/A, 2000 mBm), (N/A)
[    4.372753] cfg80211:   (57240000 KHz - 63720000 KHz @ 2160000 KHz), (N/A, 0 mBm), (N/A)
[    4.391944] wlcore: loaded
[    4.757632] vdd_mpu: supplied by vbat
[    4.916491] systemd[1]: Started udev Coldplug all Devices.
[  OK  ] Started udev Coldplug all Devices.
[    5.170335] systemd[1]: Found device /dev/ttyS0.
[  OK  ] Found device /dev/ttyS0.
[    6.752844] systemd[1]: Listening on Journal Socket (/dev/log).
[  OK  ] Listening on Journal Socket (/dev/log).
[    6.788103] systemd[1]: Starting Journal Service...
         Starting Journal Service...
[    6.823025] systemd[1]: Reached target Sockets.
[  OK  ] Reached target Sockets.
[    6.853616] systemd[1]: Reached target Local File Systems.
[  OK  ] Reached target Local File Systems.
[    6.878092] systemd[1]: Starting Create Volatile Files and Directories...
         Starting Create Volatile Files and Directories...
[    7.063376] systemd[1]: Started Journal Service.
[  OK  ] Started Journal Service.
[  OK  ] Started Create Volatile Files and Directories.
[  OK  ] Reached target System Initialization.
         Starting Network Service...
[  OK  ] Reached target Basic System.
[  OK  ] Started Serial Getty on ttyS0.
         Starting custom application modules...
[  OK  ] Started Network Service.
[  OK  ] Reached target Network.
[    7.952969] wlcore: PHY firmware version: Rev 8.2.0.0.237
[    8.065967] wlcore: firmware booted (Rev 8.9.0.0.70)
[    8.096605] net eth1: initializing cpsw version 1.12 (0)
[    8.101972] net eth0: initialized cpsw ale version 1.4
[    8.135724] net eth1: phy found : id is : 0x7c111
[    8.151242] net eth0: initializing cpsw version 1.12 (0)
[    8.185845] net eth0: phy found : id is : 0x7c111
[    8.313571] wlcore: down
[    8.359871] random: nonblocking pool is initialized
[    8.522657] usb 1-1: new high-speed USB device number 2 using musb-hdrc
[    8.672277] option 1-1:1.0: GSM modem (1-port) converter detected
[    8.687895] usb 1-1: GSM modem (1-port) converter now attached to ttyUSB0
[    8.696908] option 1-1:1.1: GSM modem (1-port) converter detected
[    8.709379] usb 1-1: GSM modem (1-port) converter now attached to ttyUSB1
[    8.720494] option 1-1:1.2: GSM modem (1-port) converter detected
[    8.730905] usb 1-1: GSM modem (1-port) converter now attached to ttyUSB2
[    8.741897] option 1-1:1.3: GSM modem (1-port) converter detected
[    8.752229] usb 1-1: GSM modem (1-port) converter now attached to ttyUSB3
[    8.763553] option 1-1:1.4: GSM modem (1-port) converter detected
[    8.771745] usb 1-1: GSM modem (1-port) converter now attached to ttyUSB4
[    8.788434] qmi_wwan 1-1:1.5: cdc-wdm0: USB WDM device
[    8.805837] qmi_wwan 1-1:1.5 wwan0: register 'qmi_wwan' at usb-musb-hdrc.0.auto-1, WWAN/QMI device, ea:e4:b1:20:fd:a4

am335x-evm login: root (automatic login)
root@am335x-evm:~# ifconfig -a
eth0      Link encap:Ethernet  HWaddr 68:C9:0B:7D:26:22  
          inet addr:192.168.3.1  Bcast:192.168.3.255  Mask:255.255.255.0
          UP BROADCAST MULTICAST  MTU:1500  Metric:1
          RX packets:0 errors:0 dropped:0 overruns:0 frame:0
          TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:1000 
          RX bytes:0 (0.0 B)  TX bytes:0 (0.0 B)
          Interrupt:173 

eth1      Link encap:Ethernet  HWaddr 68:C9:0B:7D:26:24  
          inet addr:192.168.4.1  Bcast:192.168.4.255  Mask:255.255.255.0
          UP BROADCAST MULTICAST  MTU:1500  Metric:1
          RX packets:0 errors:0 dropped:0 overruns:0 frame:0
          TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:1000 
          RX bytes:0 (0.0 B)  TX bytes:0 (0.0 B)

lo        Link encap:Local Loopback  
          inet addr:127.0.0.1  Mask:255.0.0.0
          UP LOOPBACK RUNNING  MTU:65536  Metric:1
          RX packets:0 errors:0 dropped:0 overruns:0 frame:0
          TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:1 
          RX bytes:0 (0.0 B)  TX bytes:0 (0.0 B)

wlan0     Link encap:Ethernet  HWaddr F4:B8:5E:26:81:79  
          inet addr:192.168.99.1  Bcast:192.168.99.255  Mask:255.255.255.0
          UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
          RX packets:0 errors:0 dropped:1 overruns:0 frame:0
          TX packets:4 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:1000 
          RX bytes:0 (0.0 B)  TX bytes:1408 (1.3 KiB)

wwan0     Link encap:Ethernet  HWaddr 36:18:07:5B:25:CB  
          UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
          RX packets:0 errors:0 dropped:0 overruns:0 frame:0
          TX packets:2 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:1000 
          RX bytes:0 (0.0 B)  TX bytes:684 (684.0 B)

root@am335x-evm:~# echo mem > /sys/power/state 
[   34.514292] PM: Syncing filesystems ... done.
[   34.545126] Freezing user space processes ... (elapsed 0.002 seconds) done.
[   34.554588] Freezing remaining freezable tasks ... (elapsed 0.001 seconds) done.
[   34.564000] Suspending console(s) (use no_console_suspend to debug)
[   34.585266] wlcore: down
[   34.585850] queueing ieee80211 work while going to suspend
[   34.607504] PM: suspend of devices complete after 36.327 msecs
[   34.609461] PM: late suspend of devices complete after 1.918 msecs
[   34.612354] PM: noirq suspend of devices complete after 2.855 msecs
[   34.612599] PM: Successfully put all powerdomains to target state
[   34.632956] PM: noirq resume of devices complete after 20.168 msecs
[   34.635236] PM: early resume of devices complete after 2.018 msecs
[   34.637116] net eth0: initializing cpsw version 1.12 (0)
[   34.637142] net eth0: initialized cpsw ale version 1.4
[   34.641383] net eth0: phy found : id is : 0x7c111
[   34.645139] net eth1: initializing cpsw version 1.12 (0)
[   34.649375] net eth1: phy found : id is : 0x7c111
[   35.193781] wlcore: PHY firmware version: Rev 8.2.0.0.237
[   35.282660] wlcore: firmware booted (Rev 8.9.0.0.70)
[   39.842549] dpm_run_callback(): usb_dev_resume+0x0/0x18 returns -110
[   39.842628] PM: Device 1-1 failed to resume async: error -110
[   39.843492] PM: resume of devices complete after 5208.225 msecs
[   39.944903] Restarting tasks ... 
[   39.948366] usb 1-1: USB disconnect, device number 2
[   39.964889] done.
root@am335x-evm:~# 
root@am335x-evm:~# [   39.989920] option1 ttyUSB0: GSM modem (1-port) converter now disconnected from ttyUSB0
[   40.028193] option 1-1:1.0: device disconnected
[   40.044943] option1 ttyUSB1: GSM modem (1-port) converter now disconnected from ttyUSB1
[   40.068828] option 1-1:1.1: device disconnected
[   40.083457] option1 ttyUSB2: GSM modem (1-port) converter now disconnected from ttyUSB2
[   40.091640] option 1-1:1.2: device disconnected
[   40.118398] option1 ttyUSB3: GSM modem (1-port) converter now disconnected from ttyUSB3
[   40.142150] option 1-1:1.3: device disconnected
[   40.155968] option1 ttyUSB4: GSM modem (1-port) converter now disconnected from ttyUSB4
[   40.181991] option 1-1:1.4: device disconnected
[   40.195668] qmi_wwan 1-1:1.5 wwan0: unregister 'qmi_wwan' usb-musb-hdrc.0.auto-1, WWAN/QMI device
[   40.512512] usb 1-1: new high-speed USB device number 3 using musb-hdrc
[   40.671777] option 1-1:1.0: GSM modem (1-port) converter detected
[   40.694304] usb 1-1: GSM modem (1-port) converter now attached to ttyUSB0
[   40.708443] option 1-1:1.1: GSM modem (1-port) converter detected
[   40.718358] usb 1-1: GSM modem (1-port) converter now attached to ttyUSB1
[   40.734580] option 1-1:1.2: GSM modem (1-port) converter detected
[   40.748946] usb 1-1: GSM modem (1-port) converter now attached to ttyUSB2
[   40.759982] option 1-1:1.3: GSM modem (1-port) converter detected
[   40.775191] usb 1-1: GSM modem (1-port) converter now attached to ttyUSB3
[   40.790357] option 1-1:1.4: GSM modem (1-port) converter detected
[   40.800285] usb 1-1: GSM modem (1-port) converter now attached to ttyUSB4
[   40.821517] qmi_wwan 1-1:1.5: cdc-wdm0: USB WDM device
[   40.849898] qmi_wwan 1-1:1.5 wwan0: register 'qmi_wwan' at usb-musb-hdrc.0.auto-1, WWAN/QMI device, 36:18:07:5b:25:cb

  • 0 in reply to veera anjaneyulu
    TI__Guru**** 170625 points
    Hi Veera,

    Do you use AM335x TI board (EVM, SK) or it is custom board? What is your wake-up source (UART, GPIO, touchscreen)?

    Try with issue a "sync" command before suspending the system. Try also with the latest AM335x TI SDK 03_01_00_06.

    Regards,
    Pavel
  • 0 in reply to Pavel Botev
    TI__Guru**** 170625 points
    Veera,

    Looking into the logs, the unwanted wake-up might be cause from USB. Do you have something attached on the USB ports of your board?

    See also if the below pointers will be in help:
    e2e.ti.com/.../539493
    processors.wiki.ti.com/.../Debugging_AM335x_Suspend-Resume_Issues

    Regards,
    Pavel
  • 0 in reply to Pavel Botev
    Expert 1920 points

    Hi Guru,

    Thanks for your reply.

    we are using AM335X-SK  custom board. uart is my wake-up source. SDK 3.00.00.04 we are using.But some times with out giving sync also its working .Some times automatically resumming.

    whats is the reason.

    Thanks 

    veera

    power-wakeup-resuming-immediately-logs-oct18.txt 
    root@am335x-evm:~# echo mem > /sys/power/state 
[  176.439638] PM: Syncing filesystems ... done.
[  176.458482] Freezing user space processes ... (elapsed 0.001 seconds) done.
[  176.467972] Freezing remaining freezable tasks ... (elapsed 0.001 seconds) done.
[  176.477233] Suspending console(s) (use no_console_suspend to debug)
[  176.656745] PM: suspend of devices complete after 172.525 msecs
[  176.659315] PM: late suspend of devices complete after 2.533 msecs
[  176.662244] PM: noirq suspend of devices complete after 2.887 msecs
[  176.662256] PM: Kernel suspend failure
[  176.681948] PM: noirq resume of devices complete after 19.377 msecs
[  176.685184] PM: early resume of devices complete after 2.829 msecs
[  176.687373] net eth0: initializing cpsw version 1.12 (0)
[  176.687399] net eth0: initialized cpsw ale version 1.4
[  176.691659] net eth0: phy found : id is : 0x7c111
[  176.694597] net eth1: initializing cpsw version 1.12 (0)
[  176.698805] net eth1: phy found : id is : 0x7c111
[  181.892397] dpm_run_callback(): usb_dev_resume+0x0/0x18 returns -110
[  181.892472] PM: Device 1-1 failed to resume async: error -110
[  181.893326] PM: resume of devices complete after 5208.112 msecs
[  181.973485] Restarting tasks ... 
[  181.976942] usb 1-1: USB disconnect, device number 3
[  181.989759] done.
sh: write error: Invalid argument
root@am335x-evm:~# [  182.005787] option1 ttyUSB0: GSM modem (1-port) converter now disconnected from ttyUSB0
[  182.033203] option 1-1:1.0: device disconnected
[  182.047022] option1 ttyUSB1: GSM modem (1-port) converter now disconnected from ttyUSB1
[  182.067248] option 1-1:1.1: device disconnected
[  182.081991] option1 ttyUSB2: GSM modem (1-port) converter now disconnected from ttyUSB2
[  182.100597] option 1-1:1.2: device disconnected
[  182.115584] option1 ttyUSB3: GSM modem (1-port) converter now disconnected from ttyUSB3
[  182.138152] option 1-1:1.3: device disconnected
[  182.153231] option1 ttyUSB4: GSM modem (1-port) converter now disconnected from ttyUSB4
[  182.175180] option 1-1:1.4: device disconnected
[  182.182011] qmi_wwan 1-1:1.5 wwan0: unregister 'qmi_wwan' usb-musb-hdrc.0.auto-1, WWAN/QMI device
[  182.492429] usb 1-1: new high-speed USB device number 4 using musb-hdrc
[  182.643087] option 1-1:1.0: GSM modem (1-port) converter detected
[  182.656167] usb 1-1: GSM modem (1-port) converter now attached to ttyUSB0
[  182.664755] option 1-1:1.1: GSM modem (1-port) converter detected
[  182.675420] usb 1-1: GSM modem (1-port) converter now attached to ttyUSB1
[  182.684176] option 1-1:1.2: GSM modem (1-port) converter detected
[  182.691880] usb 1-1: GSM modem (1-port) converter now attached to ttyUSB2
[  182.704477] option 1-1:1.3: GSM modem (1-port) converter detected
[  182.713892] usb 1-1: GSM modem (1-port) converter now attached to ttyUSB3
[  182.724114] option 1-1:1.4: GSM modem (1-port) converter detected
[  182.731952] usb 1-1: GSM modem (1-port) converter now attached to ttyUSB4
[  182.747041] qmi_wwan 1-1:1.5: cdc-wdm0: USB WDM device
[  182.760374] qmi_wwan 1-1:1.5 wwan0: register 'qmi_wwan' at usb-musb-hdrc.0.auto-1, WWAN/QMI device, 9e:6d:ac:65:df:7c
    power-wakeup-press-key-logs.txt 
    root@am335x-evm:~# echo mem > /sys/power/state 
[  131.804420] PM: Syncing filesystems ... done.
[  131.845165] Freezing user space processes ... (elapsed 0.001 seconds) done.
[  131.853842] Freezing remaining freezable tasks ... (elapsed 0.001 seconds) done.
[  131.863060] Suspending console(s) (use no_console_suspend to debug)

[  132.286287] PM: suspend of devices complete after 416.373 msecs
[  132.288179] PM: late suspend of devices complete after 1.850 msecs
[  132.291132] PM: noirq suspend of devices complete after 2.914 msecs
[  132.291145] PM: Successfully put all powerdomains to target state
[  132.311708] PM: noirq resume of devices complete after 20.390 msecs
[  132.314105] PM: early resume of devices complete after 2.129 msecs
[  132.316049] net eth0: initializing cpsw version 1.12 (0)
[  132.316074] net eth0: initialized cpsw ale version 1.4
[  132.320318] net eth0: phy found : id is : 0x7c111
[  132.324021] net eth1: initializing cpsw version 1.12 (0)
[  132.328244] net eth1: phy found : id is : 0x7c111
[  137.512514] dpm_run_callback(): usb_dev_resume+0x0/0x18 returns -110
[  137.512585] PM: Device 1-1 failed to resume async: error -110
[  137.513423] PM: resume of devices complete after 5199.288 msecs
[  137.596078] Restarting tasks ... 
[  137.599537] usb 1-1: USB disconnect, device number 2
[  137.613243] done.
root@am335x-evm:~# 
root@am335x-evm:~# [  137.626766] option1 ttyUSB0: GSM modem (1-port) converter now disconnected from ttyUSB0
[  137.658891] option 1-1:1.0: device disconnected
[  137.674922] option1 ttyUSB1: GSM modem (1-port) converter now disconnected from ttyUSB1
[  137.698449] option 1-1:1.1: device disconnected
[  137.713340] option1 ttyUSB2: GSM modem (1-port) converter now disconnected from ttyUSB2
[  137.721519] option 1-1:1.2: device disconnected
[  137.747333] option1 ttyUSB3: GSM modem (1-port) converter now disconnected from ttyUSB3
[  137.770910] option 1-1:1.3: device disconnected
[  137.784430] option1 ttyUSB4: GSM modem (1-port) converter now disconnected from ttyUSB4
[  137.810085] option 1-1:1.4: device disconnected
[  137.822071] qmi_wwan 1-1:1.5 wwan0: unregister 'qmi_wwan' usb-musb-hdrc.0.auto-1, WWAN/QMI device
[  138.142535] usb 1-1: new high-speed USB device number 3 using musb-hdrc
[  138.291537] option 1-1:1.0: GSM modem (1-port) converter detected
[  138.304563] usb 1-1: GSM modem (1-port) converter now attached to ttyUSB0
[  138.314704] option 1-1:1.1: GSM modem (1-port) converter detected
[  138.324369] usb 1-1: GSM modem (1-port) converter now attached to ttyUSB1
[  138.334661] option 1-1:1.2: GSM modem (1-port) converter detected
[  138.344145] usb 1-1: GSM modem (1-port) converter now attached to ttyUSB2
[  138.354221] option 1-1:1.3: GSM modem (1-port) converter detected
[  138.362064] usb 1-1: GSM modem (1-port) converter now attached to ttyUSB3
[  138.373672] option 1-1:1.4: GSM modem (1-port) converter detected
[  138.381424] usb 1-1: GSM modem (1-port) converter now attached to ttyUSB4
[  138.396426] qmi_wwan 1-1:1.5: cdc-wdm0: USB WDM device
[  138.411664] qmi_wwan 1-1:1.5 wwan0: register 'qmi_wwan' at usb-musb-hdrc.0.auto-1, WWAN/QMI device, 9e:6d:ac:65:df:7c

  • 0 in reply to Pavel Botev
    Expert 1920 points
    Hi Guru,
    Through usb interface we connected 4g modem.usb power wakeup already disabled.Before putting sleep mode we kept usb power wake-up is disabled.

    root@am335x-evm:~# cat /sys/bus/platform/devices/47401b00.usb-phy/power/wakeup
    disabled
  • 0 in reply to Pavel Botev
    Expert 1920 points
    Hi pavel

    what is the reason to use sync before suspending the system?can please explain me.

    Thanks
    veera
  • 0 in reply to veera anjaneyulu
    TI__Guru**** 170625 points
    Veera,

    Do you reproduce this issue on the AM335x Starter Kit TMDSSK3358? Or it is valid only for your custom board?

    Can you also send me a log when you have successful suspend-resume procedure with wake up from UART?

    Can you try the suspend-resume procedure when completely disable USB? What is the result then?

    In order to avoid data loss, it is recommended that the users issue a "sync" command before suspending the system

    $ sync
    $ echo mem > /sys/power/state

    Regards,
    Pavel
  • 0 in reply to Pavel Botev
    Expert 1920 points

    Hi pavel,

    We are working on custom board only.we did not check on evm board.uart wakeup succes logs attached below.please find attached uart wakeup file.we already disable all usb power wakeup sources.Before we checked.all the usb's sources are disabled condition only.

    if we run echo mem > /sys/power/state/

    our pheripherals wifi,4gmodem,ethernet all are in sleep mode only .when we press any key from uart. Its waking up.wifi and ethernet pheripherals all are restarted and we can access wifi ap and ethernet from pc.But we are not enabling 4g modem,we configured qmi_wwan driver through usb1 interface.

    we read Kernel release notes:LCPD-985 P3-Medium Power: Kernel suspend failure seen sometimes Power & Thermal am335x-evm, am335x-sk, beaglebone, beaglebone-black, am437x-idk, am43xx-gpevm

    Still that is bug?

    thanks

    7455.power-wakeup-press-key-logs.txt 
    root@am335x-evm:~# echo mem > /sys/power/state 
[  131.804420] PM: Syncing filesystems ... done.
[  131.845165] Freezing user space processes ... (elapsed 0.001 seconds) done.
[  131.853842] Freezing remaining freezable tasks ... (elapsed 0.001 seconds) done.
[  131.863060] Suspending console(s) (use no_console_suspend to debug)

[  132.286287] PM: suspend of devices complete after 416.373 msecs
[  132.288179] PM: late suspend of devices complete after 1.850 msecs
[  132.291132] PM: noirq suspend of devices complete after 2.914 msecs
[  132.291145] PM: Successfully put all powerdomains to target state
[  132.311708] PM: noirq resume of devices complete after 20.390 msecs
[  132.314105] PM: early resume of devices complete after 2.129 msecs
[  132.316049] net eth0: initializing cpsw version 1.12 (0)
[  132.316074] net eth0: initialized cpsw ale version 1.4
[  132.320318] net eth0: phy found : id is : 0x7c111
[  132.324021] net eth1: initializing cpsw version 1.12 (0)
[  132.328244] net eth1: phy found : id is : 0x7c111
[  137.512514] dpm_run_callback(): usb_dev_resume+0x0/0x18 returns -110
[  137.512585] PM: Device 1-1 failed to resume async: error -110
[  137.513423] PM: resume of devices complete after 5199.288 msecs
[  137.596078] Restarting tasks ... 
[  137.599537] usb 1-1: USB disconnect, device number 2
[  137.613243] done.
root@am335x-evm:~# 
root@am335x-evm:~# [  137.626766] option1 ttyUSB0: GSM modem (1-port) converter now disconnected from ttyUSB0
[  137.658891] option 1-1:1.0: device disconnected
[  137.674922] option1 ttyUSB1: GSM modem (1-port) converter now disconnected from ttyUSB1
[  137.698449] option 1-1:1.1: device disconnected
[  137.713340] option1 ttyUSB2: GSM modem (1-port) converter now disconnected from ttyUSB2
[  137.721519] option 1-1:1.2: device disconnected
[  137.747333] option1 ttyUSB3: GSM modem (1-port) converter now disconnected from ttyUSB3
[  137.770910] option 1-1:1.3: device disconnected
[  137.784430] option1 ttyUSB4: GSM modem (1-port) converter now disconnected from ttyUSB4
[  137.810085] option 1-1:1.4: device disconnected
[  137.822071] qmi_wwan 1-1:1.5 wwan0: unregister 'qmi_wwan' usb-musb-hdrc.0.auto-1, WWAN/QMI device
[  138.142535] usb 1-1: new high-speed USB device number 3 using musb-hdrc
[  138.291537] option 1-1:1.0: GSM modem (1-port) converter detected
[  138.304563] usb 1-1: GSM modem (1-port) converter now attached to ttyUSB0
[  138.314704] option 1-1:1.1: GSM modem (1-port) converter detected
[  138.324369] usb 1-1: GSM modem (1-port) converter now attached to ttyUSB1
[  138.334661] option 1-1:1.2: GSM modem (1-port) converter detected
[  138.344145] usb 1-1: GSM modem (1-port) converter now attached to ttyUSB2
[  138.354221] option 1-1:1.3: GSM modem (1-port) converter detected
[  138.362064] usb 1-1: GSM modem (1-port) converter now attached to ttyUSB3
[  138.373672] option 1-1:1.4: GSM modem (1-port) converter detected
[  138.381424] usb 1-1: GSM modem (1-port) converter now attached to ttyUSB4
[  138.396426] qmi_wwan 1-1:1.5: cdc-wdm0: USB WDM device
[  138.411664] qmi_wwan 1-1:1.5 wwan0: register 'qmi_wwan' at usb-musb-hdrc.0.auto-1, WWAN/QMI device, 9e:6d:ac:65:df:7c

  • 0 in reply to veera anjaneyulu
    TI__Guru**** 170625 points

    veera anjaneyulu said:
    uart wakeup succes logs attached below.please find attached uart wakeup file

    This is your log:

    root@am335x-evm:~# echo mem > /sys/power/state
    [  131.804420] PM: Syncing filesystems ... done.
    [  131.845165] Freezing user space processes ... (elapsed 0.001 seconds) done.
    [  131.853842] Freezing remaining freezable tasks ... (elapsed 0.001 seconds) done.
    [  131.863060] Suspending console(s) (use no_console_suspend to debug)

    [  132.286287] PM: suspend of devices complete after 416.373 msecs
    [  132.288179] PM: late suspend of devices complete after 1.850 msecs
    [  132.291132] PM: noirq suspend of devices complete after 2.914 msecs
    [  132.291145] PM: Successfully put all powerdomains to target state
    [  132.311708] PM: noirq resume of devices complete after 20.390 msecs
    [  132.314105] PM: early resume of devices complete after 2.129 msecs
    [  132.316049] net eth0: initializing cpsw version 1.12 (0)
    [  132.316074] net eth0: initialized cpsw ale version 1.4
    [  132.320318] net eth0: phy found : id is : 0x7c111
    [  132.324021] net eth1: initializing cpsw version 1.12 (0)
    [  132.328244] net eth1: phy found : id is : 0x7c111
    [  137.512514] dpm_run_callback(): usb_dev_resume+0x0/0x18 returns -110
    [  137.512585] PM: Device 1-1 failed to resume async: error -110
    [  137.513423] PM: resume of devices complete after 5199.288 msecs
    [  137.596078] Restarting tasks ...
    [  137.599537] usb 1-1: USB disconnect, device number 2

    It doesn't look like the expected log when successful suspend-resume with UART wake up is performed. Have you made any changes in the CM3 Firmware or you are using the default? Have you made any changes in the linux kernel code related to power management?

    veera anjaneyulu said:
    we already disable all usb power wakeup sources

    What I mean is to disable USB at all, not only usb wake up.

    veera anjaneyulu said:

    we read Kernel release notes:LCPD-985 P3-Medium Power: Kernel suspend failure seen sometimes Power & Thermal am335x-evm, am335x-sk, beaglebone, beaglebone-black, am437x-idk, am43xx-gpevm

    Still that is bug?


    At the moment I have no access to the processor wiki. Once I have, I will check and come back to you regarding this.

    Regards,
    Pavel

  • 0 in reply to Pavel Botev
    Expert 1920 points
    Hi pavel,
    we did not change anything in CM3 we are using default firmware only(means sdk firmware only).Any changes needed?
    in menuconfig we configured by following below link
    processors.wiki.ti.com/.../Linux_Core_Power_Management_User's_Guide_(v4.1)

    any changes needed can suggest me.
    Thanks
    veera
  • 0 in reply to veera anjaneyulu
    TI__Guru**** 170625 points

    veera anjaneyulu said:

    we read Kernel release notes:LCPD-985 P3-Medium Power: Kernel suspend failure seen sometimes Power & Thermal am335x-evm, am335x-sk, beaglebone, beaglebone-black, am437x-idk, am43xx-gpevm

    Still that is bug?

    thanks

    Processor SDK Linux Kernel Release Notes - Texas Instruments Wiki

    processors.wiki.ti.com

    Yes, this LCPD-985 seems to be fixed in the latest processor-sdk-linux-03.01.00, as I can not find this "known issue" in the latest kernel release notes:

    There is also one more known issue for processor-sdk-linux-03.00.00, that is fixed in processor-sdk-linux-03.01.00

    LCPD-869  AM335x: Connectivity: USB data transfer fails if board is suspended/resumed

    Regards,
    Pavel

  • 0
    Expert 1920 points

    Hi All,

    How to disable uart0 wakeup source for am3352?

    Any firmware changes needed? we are using sdk default firmware binaries.

    Any changes needed in cm3 firmware file Can suggest me .i can do..

     

    In Menu config we have pm wakup changes done.And enabled external firmeare +CONFIG_EXTRA_FIRMWARE="am335x-pm-firmware.elf am335x-evm-scale-data.bin"

    those Firmwares copied into kernel source firmware directory.And then build/compile kernel source. 

    Is it correct to disable uart0 wakup for below changes? 

    we have done below uart driver changes in  driver/tty/serial/8250/8250_omap.c file . 

    default:

    #define OMAP_UART_WER_HAS_TX_WAKEUP (1 << 1)

    changes to :

    #define OMAP_UART_WER_HAS_TX_WAKEUP (0<< 1)

    default:-

    //#define OMAP_UART_WER_MOD_WKUP 0x7f
    //#define OMAP_UART_TX_WAKEUP_EN (1 << 7)

    changed to :
    #define OMAP_UART_WER_MOD_WKUP 0x00
    #define OMAP_UART_TX_WAKEUP_EN (0 << 7)

    we disabled uart wakeup registers.But still we are getting power waking .

    #if we enabled power wakup from uart0 .we are not getting message PM: Wakeup source uart0.

    How to get the above message

    .My logs below

    357.547932] PM: Syncing filesystems ... done.
    [ 357.567142] Freezing user space processes ... (elapsed 0.001 seconds) done.
    [ 357.575910] Freezing remaining freezable tasks ... (elapsed 0.001 seconds) done.
    [ 357.589607] wlcore: down
    [ 357.590184] queueing ieee80211 work while going to suspend
    [ 357.601622] PM: suspend of devices complete after 16.090 msecs
    [ 357.604405] PM: late suspend of devices complete after 2.736 msecs
    [ 357.607347] PM: noirq suspend of devices complete after 2.902 msecs
    [ 357.607359] PM: Successfully put all powerdomains to target state

    =====> here we are not getting uart 0 wakeup message whats the reason we are not getting the message?


    [ 357.627571] PM: noirq resume of devices complete after 20.031 msecs
    [ 357.630710] PM: early resume of devices complete after 2.857 msecs
    [ 357.633049] net eth0: initializing cpsw version 1.12 (0)
    [ 357.633076] net eth0: initialized cpsw ale version 1.4
    [ 357.639138] net eth0: phy found : id is : 0x7c111
    [ 357.642128] net eth1: initializing cpsw version 1.12 (0)
    [ 357.648170] net eth1: phy found : id is : 0x7c111
    [ 358.181834] wlcore: PHY firmware version: Rev 8.2.0.0.237
    [ 358.270024] wlcore: firmware booted (Rev 8.9.0.0.70)
    [ 361.642589] cpsw 4a100000.ethernet eth1: Link is Up - 100Mbps/Half - flow control off
    [ 362.842126] dpm_run_callback(): usb_dev_resume+0x0/0x18 returns -110
    [ 362.842201] PM: Device 1-1 failed to resume async: error -110
    [ 362.843079] PM: resume of devices complete after 5212.335 msecs
    [ 362.951211] Restarting tasks ... 

  • 0 in reply to veera anjaneyulu
    TI__Guru**** 170625 points

    veera anjaneyulu said:
    How to disable uart0 wakeup source for am3352?

    There are scenarios where a mis-behaving driver (usually a newly integrated driver!) can introduce issues. If the crash happens while the UART is disabled, you won't see any of the output. One method of checking for this type of issue by setting console_suspend to "no":

    echo no > /sys/module/printk/parameters/console_suspend

    Note: With this configuration, the console cannot be used as a wakeup source!

    veera anjaneyulu said:
    =====> here we are not getting uart 0 wakeup message whats the reason we are not getting the message?


    The reason might be that something else to be the reason for the wakeup. 
    This something else might be the attached USB device (disconnect, connect and enumerate).

    Which defconfig file you are using (tisdk_am335x-evm_defconf or multi_v7_defconf)?

    Regards,
    Pavel
  • 0
    Expert 1920 points

    Hi all?

    My requirement is uart0 is my power wake-up source.

    we run sleep command on target board.

    #echo mem > /sys/power/state

    we got below logs.when we press any key from keyboard its waking up .But we are not getting the uart0 is wake up source in the below log

     

    root@am335x-evm:~# echo mem > /sys/power/state
    [ 4583.725496] PM: Syncing filesystems ... done.
    [ 4583.751530] Freezing user space processes ... (elapsed 0.001 seconds) done.
    [ 4583.762435] Freezing remaining freezable tasks ... (elapsed 0.001 seconds) done.

    [ 4583.786863] wlcore: down
    [ 4583.787422] queueing ieee80211 work while going to suspend
    [ 4583.810835] PM: suspend of devices complete after 38.201 msecs
    [ 4583.812679] PM: late suspend of devices complete after 1.803 msecs
    [ 4583.815813] PM: noirq suspend of devices complete after 3.093 msecs
    [ 4583.815826] PM: Successfully put all powerdomains to target state
    [ 4583.836120] PM: noirq resume of devices complete after 20.118 msecs
    [ 4583.838345] PM: early resume of devices complete after 1.961 msecs
    [ 4583.840210] net eth0: initializing cpsw version 1.12 (0)
    [ 4583.840235] net eth0: initialized cpsw ale version 1.4
    [ 4583.846106] net eth0: phy found : id is : 0x7c111
    [ 4583.849596] net eth1: initializing cpsw version 1.12 (0)
    [ 4583.855397] net eth1: phy found : id is : 0x7c111
    [ 4584.168596] wlcore: ERROR firmware boot failed despite 3 retries
    [ 4584.168611] ------------[ cut here ]------------
    [ 4584.169388] WARNING: CPU: 0 PID: 347 at net/mac80211/util.c:1854 ieee80211_reconfig+0x204/0x8e8 [mac80211]()
    [ 4584.173033] ---[ end trace 95e78ee294fd1b2f ]---
    [ 4584.173201] ------------[ cut here ]------------
    [ 4584.173735] WARNING: CPU: 0 PID: 347 at net/mac80211/driver-ops.h:12 drv_remove_interface+0x40/0x70 [mac80211]()
    [ 4584.181080] ---[ end trace 95e78ee294fd1b30 ]---
    [ 4584.183037] dpm_run_callback(): wiphy_resume+0x0/0x64 [cfg80211] returns -110
    [ 4584.183288] PM: Device phy0 failed to resume async: error -110
    [ 4589.042937] dpm_run_callback(): usb_dev_resume+0x0/0x18 returns -110
    [ 4589.043011] PM: Device 1-1 failed to resume async: error -110
    [ 4589.043883] PM: resume of devices complete after 5205.509 msecs
    [ 4589.191756] Restarting tasks ...
    [ 4589.196257] usb 1-1: USB disconnect, device number 2
    wlan0: INTERFACE-DISABLED
    wlan0: INTERFACE-DISABLED
    wlan0: INTERFACE-ENABLED
    Failed to set beacon parameters
    root@am335x-evm:~#
    root@am335x-evm:~# [ 4589.235042] option1 ttyUSB0: GSM modem (1-port) converter now disconnected from ttyUSB0
    [ 4589.258019] option 1-1:1.0: device disconnected
    [ 4589.282651] option1 ttyUSB1: GSM modem (1-port) converter now disconnected from ttyUSB1
    [ 4589.313207] option 1-1:1.1: device disconnected
    [ 4589.326900] option1 ttyUSB2: GSM modem (1-port) converter now disconnected from ttyUSB2
    [ 4589.346758] option 1-1:1.2: device disconnected
    [ 4589.360874] option1 ttyUSB3: GSM modem (1-port) converter now disconnected from ttyUSB3
    [ 4589.379483] option 1-1:1.3: device disconnected
    [ 4589.393701] option1 ttyUSB4: GSM modem (1-port) converter now disconnected from ttyUSB4
    [ 4589.401880] option 1-1:1.4: device disconnected
    [ 4589.423459] qmi_wwan 1-1:1.5 wwan0: unregister 'qmi_wwan' usb-musb-hdrc.0.auto-1, WWAN/QMI device
    [ 4589.742924] usb 1-1: new high-speed USB device number 3 using musb-hdrc
    [ 4589.894923] option 1-1:1.0: GSM modem (1-port) converter detected
    [ 4589.916982] usb 1-1: GSM modem (1-port) converter now attached to ttyUSB0
    [ 4589.927908] option 1-1:1.1: GSM modem (1-port) converter detected
    [ 4589.943821] usb 1-1: GSM modem (1-port) converter now attached to ttyUSB1
    [ 4589.957674] option 1-1:1.2: GSM modem (1-port) converter detected
    [ 4589.967326] usb 1-1: GSM modem (1-port) converter now attached to ttyUSB2
    [ 4589.983895] option 1-1:1.3: GSM modem (1-port) converter detected
    [ 4589.997064] usb 1-1: GSM modem (1-port) converter now attached to ttyUSB3
    [ 4590.007870] option 1-1:1.4: GSM modem (1-port) converter detected
    [ 4590.023668] usb 1-1: GSM modem (1-port) converter now attached to ttyUSB4
    [ 4590.042536] qmi_wwan 1-1:1.5: cdc-wdm0: USB WDM device
    [ 4590.069986] qmi_wwan 1-1:1.5 wwan0: register 'qmi_wwan' at usb-musb-hdrc.0.auto-1, WWAN/QMI device, 22:9b:8b:25:a2:59

    if we disabled uart0 but still we are getting uart0 waking up.But we are not getting the uart0 wakeup source message.,

    Thanks

    veera

     

  • 0
    Expert 1920 points

    Hi All

    1.How to disable uart power wake-up source on target board? with out using no_console_suspend?

    2.If use rtc wakeup source we are not getting rtc wakeup message in our waking up logs.whats the reason we are not getting? same thing uart0 also not giving waking message?

    3.we got below rtc power wakeup logs 

    root@am335x-evm:~# rtcwake -d /dev/rtc0 -m mem -s 5
    wakeup from "mem" at Sat Jan 1 00:01:00 2000
    [ 55.264474] PM: Syncing filesystems ... done.
    [ 55.279499] Freezing user space processes ... (elapsed 0.001 seconds) done.
    [ 55.288739] Freezing remaining freezable tasks ... (elapsed 0.001 seconds) done.
    [ 55.300327] wlcore: down
    [ 55.307021] queueing ieee80211 work while going to suspend
    [ 55.307239] queueing ieee80211 work while going to suspend
    [ 55.317646] PM: suspend of devices complete after 18.703 msecs
    [ 55.319618] PM: late suspend of devices complete after 1.928 msecs
    [ 55.322491] PM: noirq suspend of devices complete after 2.834 msecs
    [ 55.322504] PM: Successfully put all powerdomains to target state
    [ 55.342968] PM: noirq resume of devices complete after 20.288 msecs
    [ 55.345328] PM: early resume of devices complete after 1.916 msecs
    [ 55.347206] net eth0: initializing cpsw version 1.12 (0)
    [ 55.347231] net eth0: initialized cpsw ale version 1.4
    [ 55.352512] net eth0: phy found : id is : 0x7c111
    [ 55.356430] net eth1: initializing cpsw version 1.12 (0)
    [ 55.361675] net eth1: phy found : id is : 0x7c111
    [ 55.903134] wlcore: PHY firmware version: Rev 8.2.0.0.237
    [ 55.991218] wlcore: firmware booted (Rev 8.9.0.0.70)
    [ 60.552987] dpm_run_callback(): usb_dev_resume+0x0/0x18 returns -110
    [ 60.553063] PM: Device 1-1 failed to resume async: error -110
    [ 60.553930] PM: resume of devices complete after 5208.573 msecs
    [ 60.659706] Restarting tasks ...
    [ 60.663196] usb 1-1: USB disconnect, device number 2
    root@am335x-evm:~# [ 60.692998] option1 ttyUSB0: GSM modem (1-port) converter now disconnected from ttyUSB0
    [ 60.719980] option 1-1:1.0: device disconnected
    [ 60.729771] option1 ttyUSB1: GSM modem (1-port) converter now disconnected from ttyUSB1
    [ 60.753294] option 1-1:1.1: device disconnected
    [ 60.766716] option1 ttyUSB2: GSM modem (1-port) converter now disconnected from ttyUSB2
    [ 60.786323] option 1-1:1.2: device disconnected
    [ 60.800435] option1 ttyUSB3: GSM modem (1-port) converter now disconnected from ttyUSB3
    [ 60.818876] option 1-1:1.3: device disconnected
    [ 60.832618] option1 ttyUSB4: GSM modem (1-port) converter now disconnected from ttyUSB4
    [ 60.855126] option 1-1:1.4: device disconnected
    [ 60.865708] qmi_wwan 1-1:1.5 wwan0: unregister 'qmi_wwan' usb-musb-hdrc.0.auto-1, WWAN/QMI device
    [ 61.182949] usb 1-1: new high-speed USB device number 3 using musb-hdrc
    [ 61.335107] option 1-1:1.0: GSM modem (1-port) converter detected
    [ 61.354670] usb 1-1: GSM modem (1-port) converter now attached to ttyUSB0
    [ 61.368536] option 1-1:1.1: GSM modem (1-port) converter detected
    [ 61.378413] usb 1-1: GSM modem (1-port) converter now attached to ttyUSB1
    [ 61.395002] option 1-1:1.2: GSM modem (1-port) converter detected
    [ 61.408008] usb 1-1: GSM modem (1-port) converter now attached to ttyUSB2
    [ 61.418765] option 1-1:1.3: GSM modem (1-port) converter detected
    [ 61.434449] usb 1-1: GSM modem (1-port) converter now attached to ttyUSB3
    [ 61.448285] option 1-1:1.4: GSM modem (1-port) converter detected
    [ 61.458036] usb 1-1: GSM modem (1-port) converter now attached to ttyUSB4
    [ 61.479364] qmi_wwan 1-1:1.5: cdc-wdm0: USB WDM device
    [ 61.506808] qmi_wwan 1-1:1.5 wwan0: register 'qmi_wwan' at usb-musb-hdrc.0.auto-1, WWAN/QMI device, 22:79:66:7d:da:8a

    4.If any firmware changes needed? 

    Any body solve this issue can guide me...

    Thanks 

    veera

  • 0 in reply to veera anjaneyulu
    TI__Guru**** 170625 points

    veera anjaneyulu said:
    1.How to disable uart power wake-up source on target board? with out using no_console_suspend?

    Have you tried with UART_SYSC and WER registers? What values you have there just before start the sleep procedure?

    Also, only UART0 has wake-up capability, if you use another UART for console, there will be no wake-up option.

    veera anjaneyulu said:
    2.If use rtc wakeup source we are not getting rtc wakeup message in our waking up logs.whats the reason we are not getting? same thing uart0 also not giving waking message?

    Starting from PSDK3, the wake up reason is printed only when in RTC-Only mode:

    linux-4.4.12/drivers/soc/ti/pm33xx.c

    static int am33xx_pm_suspend(suspend_state_t suspend_state)
    {

    /* print the wakeup reason */
            if (rtc_only_idle) {
            wakeup_src = rtc_wake_src();
                pm_ops->prepare_rtc_resume();
                pr_info("PM: Wakeup source %s\n", wakeup_src.src);
            }

    }

    While in older SDK, like PSDK2 for example we have:

    linux-4.1.13/drivers/soc/ti/pm33xx.c

    /* print the wakeup reason */
            if (rtc_only_idle) {
                wakeup_src = rtc_wake_src();
                pm_ops->prepare_rtc_resume();
                pr_info("PM: Wakeup source %s\n", wakeup_src.src);
            } else {
                pr_info("PM: Wakeup source %s\n",
                    wkup_m3_request_wake_src());
            }

    veera anjaneyulu said:
    4.If any firmware changes needed? 

    I am not aware of such need.

    Regards,
    Pavel

  • 0 in reply to Pavel Botev
    Expert 1920 points

    Hi Pavel

    1.We passed the below register values before power waking up .

    root@am335x-evm:~# busybox-armv7l devmem 0x44E09054 b 0x09
    root@am335x-evm:~# busybox-armv7l devmem 0x44E0905c b 0x00

    2.Below we are using uart wakeup but its giving rtc wakeup things?why its giving rtc messages?
    root@am335x-evm:~# echo mem > /sys/power/state


    [   23.139328] ****drivers/soc/ti/pm33xx.c am33xx_pm_valid
    [   23.145325] PM: Syncing filesystems ... done.
    [   23.233418] Freezing user space processes ... (elapsed 0.002 seconds) done.
    [   23.242659] Freezing remaining freezable tasks ... (elapsed 0.001 seconds) done.
    [   23.252013] ****drivers/soc/ti/pm33xx.c am33xx_pm_begin
    [   23.258042] ****drivers/soc/ti/pm33xx.c am33xx_pm_begin ---->0

    [   23.276490] wlcore: down
    [   23.277050] queueing ieee80211 work while going to suspend
    [   23.304134] PM: suspend of devices complete after 37.899 msecs
    [   23.305974] PM: late suspend of devices complete after 1.797 msecs
    [   23.308825] PM: noirq suspend of devices complete after 2.812 msecs
    [   23.308838] VEERA:****drivers/soc/ti/pm33xx.c am33xx_pm_enter
    [   23.308838] VEERA:****drivers/soc/ti/pm33xx.c am33xx_pm_suspend
    [   23.308838] PM: Successfully put all powerdomains to target state
    [   23.308838] ***rtc wakeup source===>0 ==================================> my debug print message
    [   23.328948] PM: noirq resume of devices complete after 19.937 msecs
    [   23.331132] PM: early resume of devices complete after 1.931 msecs
    [   23.333129] net eth0: initializing cpsw version 1.12 (0)
    [   23.333154] net eth0: initialized cpsw ale version 1.4
    [   23.338419] net eth0: phy found : id is : 0x7c111
    [   23.342218] net eth1: initializing cpsw version 1.12 (0)
    [   23.347586] net eth1: phy found : id is : 0x7c111
    [   23.882525] wlcore: PHY firmware version: Rev 8.2.0.0.237
    [   23.976003] wlcore: firmware booted (Rev 8.9.0.0.70)

    [   28.532865] dpm_run_callback(): usb_dev_resume+0x0/0x18 returns -110=======>where its coming ?How to solve this issue?my usb modem connected to USB1_DM & USB1_DP pins directly connected to processor.

    [   28.532942] PM: Device 1-1 failed to resume async: error -110=================> how to fix this issue?

    [   28.533803] PM: resume of devices complete after 5202.640 msecs
    [   28.649987] VEERA:****drivers/soc/ti/pm33xx.c am33xx_pm_end
    [   28.655624] Restarting tasks ...
    [   28.659073] usb 1-1: USB disconnect, device number 2
    root@am335x-evm:~#
    root@am335x-evm:~# [   28.704942] option1 ttyUSB0: GSM modem (1-port) converter now disconnected from ttyUSB0
    [   28.737213] option 1-1:1.0: device disconnected
    [   28.752480] option1 ttyUSB1: GSM modem (1-port) converter now disconnected from ttyUSB1
    [   28.770931] option 1-1:1.1: device disconnected
    [   28.785786] option1 ttyUSB2: GSM modem (1-port) converter now disconnected from ttyUSB2
    [   28.807988] option 1-1:1.2: device disconnected
    [   28.822563] option1 ttyUSB3: GSM modem (1-port) converter now disconnected from ttyUSB3
    [   28.844893] option 1-1:1.3: device disconnected
    [   28.859555] option1 ttyUSB4: GSM modem (1-port) converter now disconnected from ttyUSB4
    [   28.877884] option 1-1:1.4: device disconnected
    [   28.888192] qmi_wwan 1-1:1.5 wwan0: unregister 'qmi_wwan' usb-musb-hdrc.0.auto-1, WWAN/QMI device
    [   29.202836] usb 1-1: new high-speed USB device number 3 using musb-hdrc
    [   29.359867] option 1-1:1.0: GSM modem (1-port) converter detected
    [   29.381903] usb 1-1: GSM modem (1-port) converter now attached to ttyUSB0
    [   29.392464] option 1-1:1.1: GSM modem (1-port) converter detected
    [   29.408136] usb 1-1: GSM modem (1-port) converter now attached to ttyUSB1
    [   29.423369] option 1-1:1.2: GSM modem (1-port) converter detected
    [   29.436798] usb 1-1: GSM modem (1-port) converter now attached to ttyUSB2
    [   29.447773] option 1-1:1.3: GSM modem (1-port) converter detected
    [   29.462492] usb 1-1: GSM modem (1-port) converter now attached to ttyUSB3
    [   29.477932] option 1-1:1.4: GSM modem (1-port) converter detected
    [   29.487826] usb 1-1: GSM modem (1-port) converter now attached to ttyUSB4
    [   29.509164] qmi_wwan 1-1:1.5: cdc-wdm0: USB WDM device
    [   29.534411] qmi_wwan 1-1:1.5 wwan0: register 'qmi_wwan' at usb-musb-hdrc.0.auto-1, WWAN/QMI device, ca:b5:67:60:c2:05

    3.If we use rtc wakeup source but still we are not getting rtc wakeup source message reason is rtc_only_idle=====> always 0 ie reason we are not getting the rtc wakeup source print message.

    4.Below highlighted lines  logs  are coming from driver/soc/ti/pm33xx.c. 

    root@am335x-evm:~# rtcwake -d /dev/rtc0 -m mem -s 05
    wakeup from "mem" at Sat Jan  1 00:10:33 2000
    [  623.941562] ****drivers/soc/ti/pm33xx.c am33xx_pm_valid
    [  623.947500] PM: Syncing filesystems ... done.
    [  623.960828] Freezing user space processes ... (elapsed 0.001 seconds) done.
    [  623.971203] Freezing remaining freezable tasks ... (elapsed 0.001 seconds) done.

    [  623.980469] ****drivers/soc/ti/pm33xx.c am33xx_pm_begin
    [  623.986485] ****drivers/soc/ti/pm33xx.c am33xx_pm_begin ---->0

    [  623.998774] wlcore: down
    [  623.999341] queueing ieee80211 work while going to suspend
    [  624.010634] PM: suspend of devices complete after 15.957 msecs
    [  624.013338] PM: late suspend of devices complete after 2.661 msecs
    [  624.016205] PM: noirq suspend of devices complete after 2.831 msecs

    [  624.016219] ****drivers/soc/ti/pm33xx.c am33xx_pm_enter
    [  624.016219] ****drivers/soc/ti/pm33xx.c am33xx_pm_suspend

    [  624.016219] PM: Successfully put all powerdomains to target state

    [  624.016219] ***rtc wakeup source===>0

    [  624.036280] PM: noirq resume of devices complete after 19.876 msecs
    [  624.038576] PM: early resume of devices complete after 2.001 msecs
    [  624.040433] net eth0: initializing cpsw version 1.12 (0)
    [  624.040458] net eth0: initialized cpsw ale version 1.4
    [  624.046368] net eth0: phy found : id is : 0x7c111
    [  624.049797] net eth1: initializing cpsw version 1.12 (0)
    [  624.055591] net eth1: phy found : id is : 0x7c111
    [  624.368400] wlcore: ERROR firmware boot failed despite 3 retries
    [  624.368414] ------------[ cut here ]------------
    [  624.369189] WARNING: CPU: 0 PID: 396 at net/mac80211/util.c:1854 ieee80211_reconfig+0x204/0x8e8 [mac80211]()
    [  624.372840] ---[ end trace a43fb2f9cfde8974 ]---
    [  624.373004] ------------[ cut here ]------------
    [  624.373536] WARNING: CPU: 0 PID: 396 at net/mac80211/driver-ops.h:12 drv_remove_interface+0x40/0x70 [mac80211]()
    [  624.380880] ---[ end trace a43fb2f9cfde8975 ]---
    [  624.382830] dpm_run_callback(): wiphy_resume+0x0/0x64 [cfg80211] returns -110
    [  624.383079] PM: Device phy0 failed to resume async: error -110
    [  629.242744] dpm_run_callback(): usb_dev_resume+0x0/0x18 returns -110
    [  629.242817] PM: Device 1-1 failed to resume async: error -110
    [  629.243685] PM: resume of devices complete after 5205.078 msecs
    [  629.407447] VEERA:****drivers/soc/ti/pm33xx.c am33xx_pm_end
    [  629.413082] Restarting tasks ...
    [  629.417556] usb 1-1: USB disconnect, device number 3
    root@am335x-evm:~# [  629.458850] option1 ttyUSB0: GSM modem (1-port) converter now disconnected from ttyUSB0
    [  629.484676] option 1-1:1.0: device disconnected
    [  629.499325] option1 ttyUSB1: GSM modem (1-port) converter now disconnected from ttyUSB1
    [  629.531582] option 1-1:1.1: device disconnected
    [  629.545817] option1 ttyUSB2: GSM modem (1-port) converter now disconnected from ttyUSB2
    [  629.568495] option 1-1:1.2: device disconnected
    [  629.582386] option1 ttyUSB3: GSM modem (1-port) converter now disconnected from ttyUSB3
    [  629.605103] option 1-1:1.3: device disconnected
    [  629.619042] option1 ttyUSB4: GSM modem (1-port) converter now disconnected from ttyUSB4
    [  629.637707] option 1-1:1.4: device disconnected
    [  629.648131] qmi_wwan 1-1:1.5 wwan0: unregister 'qmi_wwan' usb-musb-hdrc.0.auto-1, WWAN/QMI device
    [  629.962728] usb 1-1: new high-speed USB device number 4 using musb-hdrc
    [  630.115068] option 1-1:1.0: GSM modem (1-port) converter detected
    [  630.134738] usb 1-1: GSM modem (1-port) converter now attached to ttyUSB0
    [  630.148788] option 1-1:1.1: GSM modem (1-port) converter detected
    [  630.158512] usb 1-1: GSM modem (1-port) converter now attached to ttyUSB1
    [  630.175059] option 1-1:1.2: GSM modem (1-port) converter detected
    [  630.187955] usb 1-1: GSM modem (1-port) converter now attached to ttyUSB2
    [  630.198655] option 1-1:1.3: GSM modem (1-port) converter detected
    [  630.214297] usb 1-1: GSM modem (1-port) converter now attached to ttyUSB3
    [  630.228121] option 1-1:1.4: GSM modem (1-port) converter detected
    [  630.237847] usb 1-1: GSM modem (1-port) converter now attached to ttyUSB4
    [  630.259934] qmi_wwan 1-1:1.5: cdc-wdm0: USB WDM device
    [  630.286174] qmi_wwan 1-1:1.5 wwan0: register 'qmi_wwan' at usb-musb-hdrc.0.auto-1, WWAN/QMI device, ca:b5:67:60:c2:05

    5.How we will hard code the value rtc_only_idle=====> 1 from below function

    static int am33xx_pm_begin(suspend_state_t state)
    {
            int ret = -EINVAL;

            pr_info("****%s %s\n",__FILE__,__func__);
            if (state == PM_SUSPEND_MEM && pm_ops->check_off_mode_enable()) {
                    rtc_write_scratch(omap_rtc, RTC_SCRATCH_MAGIC_REG,
                                      rtc_magic_val);
                    rtc_only_idle = 1;
            pr_info(":if===>****%s %s ---->%d \n",__FILE__,__func__,rtc_only_idle);
            } else {
                    rtc_only_idle = 0;
            pr_info(":else===>****%s %s ---->%d \n",__FILE__,__func__,rtc_only_idle);
            }

            cpu_idle_poll_ctrl(true);

            switch (state) {
            case PM_SUSPEND_MEM:
                    ret = m3_ipc->ops->prepare_low_power(m3_ipc, WKUP_M3_DEEPSLEEP);
                    break;
            case PM_SUSPEND_STANDBY:
                    ret = m3_ipc->ops->prepare_low_power(m3_ipc, WKUP_M3_STANDBY);
                    break;
            }

            return ret;
    }


    Thanks

    veera

  • 0 in reply to veera anjaneyulu
    Expert 1920 points

    Hi All,

    Any body solved the above issue? or any body hard coded for power management issue?

    Thanks

    veera

  • 0 in reply to veera anjaneyulu
    TI__Guru**** 170625 points

    veera anjaneyulu said:

    1.We passed the below register values before power waking up .

    root@am335x-evm:~# busybox-armv7l devmem 0x44E09054 b 0x09
    root@am335x-evm:~# busybox-armv7l devmem 0x44E0905c b 0x00

    It seems that the PM linux driver is setting these registers (SYSC and WER) with their previous values (0xD and 0xFF) in the suspend/resume procedure. You will need to track where exactly these two registers (SYSC and WER) are re-configured in the linux kernel and change that.

    veera anjaneyulu said:
    2.Below we are using uart wakeup but its giving rtc wakeup things?why its giving rtc messages?
    root@am335x-evm:~# echo mem > /sys/power/state

    veera anjaneyulu said:
    [   23.308838] ***rtc wakeup source===>0 ==================================> my debug print message

    What are the RTC wakeup things you mean? I see only one debug print message that is added by you.

    veera anjaneyulu said:

    [   28.532865] dpm_run_callback(): usb_dev_resume+0x0/0x18 returns -110=======>where its coming ?How to solve this issue?my usb modem connected to USB1_DM & USB1_DP pins directly connected to processor.

    [   28.532942] PM: Device 1-1 failed to resume async: error -110=================> how to fix this issue?

    It seems to me you have something wrong in your HW or SW regarding this USB modem. On the AM335x TI EVM, it have two USB ports, and I have nothing attached to these ports, and suspend/resume is working fine. Can you test without this USB modem attached to your USB port(s), will be there any improvement? Have you also test with the latest PSDK 3.1?

    veera anjaneyulu said:
    3.If we use rtc wakeup source but still we are not getting rtc wakeup source message reason is rtc_only_idle=====> always 0 ie reason we are not getting the rtc wakeup source print message.

    Do you mean RTC-Only or RTC-DDR?

    Can you provide full console log? On the TI EVM, the RTC-Only mode is working fine with the below command:

    root@am335x-evm:~# rtcwake -d /dev/rtc0 -m standby -s 5

    Regards,
    Pavel

  • 0 in reply to Pavel Botev
    Expert 1920 points

    Hi Pavel,

    we checked WER in drivers/tty/serial/omap-serial.c

    //#define OMAP_UART_WER_MOD_WKUP        0x7F commented by veera
    #define OMAP_UART_WER_MOD_WKUP  0x00 ============================> we changed from above to this.

    SYSC only registered in driver/tty/serial/8250/8250_omap.c file only.

    Still any changes needed give me idea.

    find root@am335x-evm:~# rtcwake -d /dev/rtc0 -m standby -s 5  find below logs.

    root@am335x-evm:~# rtcwake -d /dev/rtc0 -m mem -s 05
    wakeup from "mem" at Sat Jan  1 00:15:37 2000
    [  932.548646] VEERA:****drivers/soc/ti/pm33xx.c am33xx_pm_valid
    [  932.554598] PM: Syncing filesystems ... done.
    [  932.560294] VEERA:====>drivers/base/power/main.c dpm_for_each_dev
    [  932.582443] Freezing user space processes ... (elapsed 0.002 seconds) done.
    [  932.591743] Freezing remaining freezable tasks ... (elapsed 0.001 seconds) done.
    [  932.601180] VEERA:****drivers/soc/ti/pm33xx.c am33xx_pm_begin
    [  932.607171] VEERA:else===>****drivers/soc/ti/pm33xx.c am33xx_pm_begin ---->0
    [  932.645669] wlcore: down
    [  932.646225] queueing ieee80211 work while going to suspend
    [  932.653390] PM: suspend of devices complete after 38.032 msecs
    [  932.655340] PM: late suspend of devices complete after 1.906 msecs
    [  932.658183] PM: noirq suspend of devices complete after 2.803 msecs
    [  932.658195] VEERA:****drivers/soc/ti/pm33xx.c am33xx_pm_enter
    [  932.658195] VEERA:****drivers/soc/ti/pm33xx.c am33xx_pm_suspend
    [  932.658195] PM: Successfully put all powerdomains to target state
    [  932.658195] VEERA:***rtc wakeup source===>0
    [  932.658350] VEERA:====>drivers/base/power/main.c dpm_resume_noirq
    [  932.678437] PM: noirq resume of devices complete after 20.065 msecs
    [  932.679092] VEERA:====>drivers/base/power/main.c device_resume_early
    [  932.679111] VEERA:====>drivers/base/power/main.c device_resume_early
    [  932.679124] VEERA:====>drivers/base/power/main.c device_resume_early
    [  932.679135] VEERA:====>drivers/base/power/main.c device_resume_early
    [  932.679146] VEERA:====>drivers/base/power/main.c device_resume_early
    [  932.679158] VEERA:====>drivers/base/power/main.c device_resume_early
    [  932.679170] VEERA:====>drivers/base/power/main.c device_resume_early
    [  932.679182] VEERA:====>drivers/base/power/main.c device_resume_early
    [  932.679192] VEERA:====>drivers/base/power/main.c device_resume_early
    [  932.679203] VEERA:====>drivers/base/power/main.c device_resume_early
    [  932.679214] VEERA:====>drivers/base/power/main.c device_resume_early
    [  932.679224] VEERA:====>drivers/base/power/main.c device_resume_early
    [  932.679235] VEERA:====>drivers/base/power/main.c device_resume_early
    [  932.679247] VEERA:====>drivers/base/power/main.c device_resume_early
    [  932.679258] VEERA:====>drivers/base/power/main.c device_resume_early
    [  932.679269] VEERA:====>drivers/base/power/main.c device_resume_early
    [  932.679280] VEERA:====>drivers/base/power/main.c device_resume_early
    [  932.679291] VEERA:====>drivers/base/power/main.c device_resume_early
    [  932.679301] VEERA:====>drivers/base/power/main.c device_resume_early
    [  932.679313] VEERA:====>drivers/base/power/main.c device_resume_early
    [  932.679355] VEERA:====>drivers/base/power/main.c device_resume_early
    [  932.679366] VEERA:====>drivers/base/power/main.c device_resume_early
    [  932.679377] VEERA:====>drivers/base/power/main.c device_resume_early
    [  932.679388] VEERA:====>drivers/base/power/main.c device_resume_early
    [  932.679400] VEERA:====>drivers/base/power/main.c device_resume_early
    [  932.679411] VEERA:====>drivers/base/power/main.c device_resume_early
    [  932.679422] VEERA:====>drivers/base/power/main.c device_resume_early
    [  932.679433] VEERA:====>drivers/base/power/main.c device_resume_early
    [  932.679444] VEERA:====>drivers/base/power/main.c device_resume_early
    [  932.679455] VEERA:====>drivers/base/power/main.c device_resume_early
    [  932.679465] VEERA:====>drivers/base/power/main.c device_resume_early
    [  932.679475] VEERA:====>drivers/base/power/main.c device_resume_early
    [  932.679487] VEERA:====>drivers/base/power/main.c device_resume_early
    [  932.679498] VEERA:====>drivers/base/power/main.c device_resume_early
    [  932.679509] VEERA:====>drivers/base/power/main.c device_resume_early
    [  932.679520] VEERA:====>drivers/base/power/main.c device_resume_early
    [  932.679531] VEERA:====>drivers/base/power/main.c device_resume_early
    [  932.679541] VEERA:====>drivers/base/power/main.c device_resume_early
    [  932.679553] VEERA:====>drivers/base/power/main.c device_resume_early
    [  932.679563] VEERA:====>drivers/base/power/main.c device_resume_early
    [  932.679574] VEERA:====>drivers/base/power/main.c device_resume_early
    [  932.679585] VEERA:====>drivers/base/power/main.c device_resume_early
    [  932.679595] VEERA:====>drivers/base/power/main.c device_resume_early
    [  932.679606] VEERA:====>drivers/base/power/main.c device_resume_early
    [  932.679617] VEERA:====>drivers/base/power/main.c device_resume_early
    [  932.679628] VEERA:====>drivers/base/power/main.c device_resume_early
    [  932.679638] VEERA:====>drivers/base/power/main.c device_resume_early
    [  932.679649] VEERA:====>drivers/base/power/main.c device_resume_early
    [  932.679660] VEERA:====>drivers/base/power/main.c device_resume_early
    [  932.679671] VEERA:====>drivers/base/power/main.c device_resume_early
    [  932.679682] VEERA:====>drivers/base/power/main.c device_resume_early
    [  932.679692] VEERA:====>drivers/base/power/main.c device_resume_early
    [  932.679703] VEERA:====>drivers/base/power/main.c device_resume_early
    [  932.679713] VEERA:====>drivers/base/power/main.c device_resume_early
    [  932.679724] VEERA:====>drivers/base/power/main.c device_resume_early
    [  932.679735] VEERA:====>drivers/base/power/main.c device_resume_early
    [  932.679746] VEERA:====>drivers/base/power/main.c device_resume_early
    [  932.679756] VEERA:====>drivers/base/power/main.c device_resume_early
    [  932.679767] VEERA:====>drivers/base/power/main.c device_resume_early
    [  932.679778] VEERA:====>drivers/base/power/main.c device_resume_early
    [  932.679789] VEERA:====>drivers/base/power/main.c device_resume_early
    [  932.679800] VEERA:====>drivers/base/power/main.c device_resume_early
    [  932.679811] VEERA:====>drivers/base/power/main.c device_resume_early
    [  932.679822] VEERA:====>drivers/base/power/main.c device_resume_early
    [  932.679833] VEERA:====>drivers/base/power/main.c device_resume_early
    [  932.679843] VEERA:====>drivers/base/power/main.c device_resume_early
    [  932.679854] VEERA:====>drivers/base/power/main.c device_resume_early
    [  932.679866] VEERA:====>drivers/base/power/main.c device_resume_early
    [  932.679876] VEERA:====>drivers/base/power/main.c device_resume_early
    [  932.679887] VEERA:====>drivers/base/power/main.c device_resume_early
    [  932.679898] VEERA:====>drivers/base/power/main.c device_resume_early
    [  932.679909] VEERA:====>drivers/base/power/main.c device_resume_early
    [  932.679920] VEERA:====>drivers/base/power/main.c device_resume_early
    [  932.679930] VEERA:====>drivers/base/power/main.c device_resume_early
    [  932.679940] VEERA:====>drivers/base/power/main.c device_resume_early
    [  932.679950] VEERA:====>drivers/base/power/main.c device_resume_early
    [  932.679961] VEERA:====>drivers/base/power/main.c device_resume_early
    [  932.679971] VEERA:====>drivers/base/power/main.c device_resume_early
    [  932.679982] VEERA:====>drivers/base/power/main.c device_resume_early
    [  932.679992] VEERA:====>drivers/base/power/main.c device_resume_early
    [  932.680003] VEERA:====>drivers/base/power/main.c device_resume_early
    [  932.680014] VEERA:====>drivers/base/power/main.c device_resume_early
    [  932.680024] VEERA:====>drivers/base/power/main.c device_resume_early
    [  932.680035] VEERA:====>drivers/base/power/main.c device_resume_early
    [  932.680046] VEERA:====>drivers/base/power/main.c device_resume_early
    [  932.680056] VEERA:====>drivers/base/power/main.c device_resume_early
    [  932.680068] VEERA:====>drivers/base/power/main.c device_resume_early
    [  932.680078] VEERA:====>drivers/base/power/main.c device_resume_early
    [  932.680089] VEERA:====>drivers/base/power/main.c device_resume_early
    [  932.680099] VEERA:====>drivers/base/power/main.c device_resume_early
    [  932.680110] VEERA:====>drivers/base/power/main.c device_resume_early
    [  932.680120] VEERA:====>drivers/base/power/main.c device_resume_early
    [  932.680131] VEERA:====>drivers/base/power/main.c device_resume_early
    [  932.680141] VEERA:====>drivers/base/power/main.c device_resume_early
    [  932.680152] VEERA:====>drivers/base/power/main.c device_resume_early
    [  932.680163] VEERA:====>drivers/base/power/main.c device_resume_early
    [  932.680174] VEERA:====>drivers/base/power/main.c device_resume_early
    [  932.680184] VEERA:====>drivers/base/power/main.c device_resume_early
    [  932.680195] VEERA:====>drivers/base/power/main.c device_resume_early
    [  932.680206] VEERA:====>drivers/base/power/main.c device_resume_early
    [  932.680217] VEERA:====>drivers/base/power/main.c device_resume_early
    [  932.680227] VEERA:====>drivers/base/power/main.c device_resume_early
    [  932.680238] VEERA:====>drivers/base/power/main.c device_resume_early
    [  932.680249] VEERA:====>drivers/base/power/main.c device_resume_early
    [  932.680259] VEERA:====>drivers/base/power/main.c device_resume_early
    [  932.680269] VEERA:====>drivers/base/power/main.c device_resume_early
    [  932.680280] VEERA:====>drivers/base/power/main.c device_resume_early
    [  932.680291] VEERA:====>drivers/base/power/main.c device_resume_early
    [  932.680301] VEERA:====>drivers/base/power/main.c device_resume_early
    [  932.680311] VEERA:====>drivers/base/power/main.c device_resume_early
    [  932.680322] VEERA:====>drivers/base/power/main.c device_resume_early
    [  932.680332] VEERA:====>drivers/base/power/main.c device_resume_early
    [  932.680343] VEERA:====>drivers/base/power/main.c device_resume_early
    [  932.680354] VEERA:====>drivers/base/power/main.c device_resume_early
    [  932.680365] VEERA:====>drivers/base/power/main.c device_resume_early
    [  932.680376] VEERA:====>drivers/base/power/main.c device_resume_early
    [  932.680386] VEERA:====>drivers/base/power/main.c device_resume_early
    [  932.680397] VEERA:====>drivers/base/power/main.c device_resume_early
    [  932.680408] VEERA:====>drivers/base/power/main.c device_resume_early
    [  932.680418] VEERA:====>drivers/base/power/main.c device_resume_early
    [  932.680429] VEERA:====>drivers/base/power/main.c device_resume_early
    [  932.680439] VEERA:====>drivers/base/power/main.c device_resume_early
    [  932.680450] VEERA:====>drivers/base/power/main.c device_resume_early
    [  932.680460] VEERA:====>drivers/base/power/main.c device_resume_early
    [  932.680471] VEERA:====>drivers/base/power/main.c device_resume_early
    [  932.680481] VEERA:====>drivers/base/power/main.c device_resume_early
    [  932.680492] VEERA:====>drivers/base/power/main.c device_resume_early
    [  932.680502] VEERA:====>drivers/base/power/main.c device_resume_early
    [  932.680513] VEERA:====>drivers/base/power/main.c device_resume_early
    [  932.680523] VEERA:====>drivers/base/power/main.c device_resume_early
    [  932.680533] VEERA:====>drivers/base/power/main.c device_resume_early
    [  932.680543] VEERA:====>drivers/base/power/main.c device_resume_early
    [  932.680554] VEERA:====>drivers/base/power/main.c device_resume_early
    [  932.680564] VEERA:====>drivers/base/power/main.c device_resume_early
    [  932.680576] VEERA:====>drivers/base/power/main.c device_resume_early
    [  932.680586] VEERA:====>drivers/base/power/main.c device_resume_early
    [  932.680597] VEERA:====>drivers/base/power/main.c device_resume_early
    [  932.680608] VEERA:====>drivers/base/power/main.c device_resume_early
    [  932.680618] VEERA:====>drivers/base/power/main.c device_resume_early
    [  932.680629] VEERA:====>drivers/base/power/main.c device_resume_early
    [  932.680640] VEERA:====>drivers/base/power/main.c device_resume_early
    [  932.680650] VEERA:====>drivers/base/power/main.c device_resume_early
    [  932.680661] VEERA:====>drivers/base/power/main.c device_resume_early
    [  932.680672] VEERA:====>drivers/base/power/main.c device_resume_early
    [  932.680683] VEERA:====>drivers/base/power/main.c device_resume_early
    [  932.680694] VEERA:====>drivers/base/power/main.c device_resume_early
    [  932.680705] VEERA:====>drivers/base/power/main.c device_resume_early
    [  932.680716] VEERA:====>drivers/base/power/main.c device_resume_early
    [  932.680726] VEERA:====>drivers/base/power/main.c device_resume_early
    [  932.680737] VEERA:====>drivers/base/power/main.c device_resume_early
    [  932.680748] VEERA:====>drivers/base/power/main.c device_resume_early
    [  932.680759] VEERA:====>drivers/base/power/main.c device_resume_early
    [  932.680770] VEERA:====>drivers/base/power/main.c device_resume_early
    [  932.680782] VEERA:====>drivers/base/power/main.c device_resume_early
    [  932.680793] VEERA:====>drivers/base/power/main.c device_resume_early
    [  932.680804] VEERA:====>drivers/base/power/main.c device_resume_early
    [  932.680815] VEERA:====>drivers/base/power/main.c device_resume_early
    [  932.680825] VEERA:====>drivers/base/power/main.c device_resume_early
    [  932.680836] VEERA:====>drivers/base/power/main.c device_resume_early
    [  932.680847] VEERA:====>drivers/base/power/main.c device_resume_early
    [  932.680858] VEERA:====>drivers/base/power/main.c device_resume_early
    [  932.680869] VEERA:====>drivers/base/power/main.c device_resume_early
    [  932.680880] VEERA:====>drivers/base/power/main.c device_resume_early
    [  932.680945] VEERA:====>drivers/base/power/main.c device_resume_early
    [  932.680958] VEERA:====>drivers/base/power/main.c device_resume_early
    [  932.680969] VEERA:====>drivers/base/power/main.c device_resume_early
    [  932.680981] VEERA:====>drivers/base/power/main.c device_resume_early
    [  932.680992] VEERA:====>drivers/base/power/main.c device_resume_early
    [  932.681003] VEERA:====>drivers/base/power/main.c device_resume_early
    [  932.681015] VEERA:====>drivers/base/power/main.c device_resume_early
    [  932.681026] VEERA:====>drivers/base/power/main.c device_resume_early
    [  932.681037] VEERA:====>drivers/base/power/main.c device_resume_early
    [  932.681048] VEERA:====>drivers/base/power/main.c device_resume_early
    [  932.681059] VEERA:====>drivers/base/power/main.c device_resume_early
    [  932.681070] VEERA:====>drivers/base/power/main.c device_resume_early
    [  932.681081] VEERA:====>drivers/base/power/main.c device_resume_early
    [  932.681092] VEERA:====>drivers/base/power/main.c device_resume_early
    [  932.681103] VEERA:====>drivers/base/power/main.c device_resume_early
    [  932.681114] VEERA:====>drivers/base/power/main.c device_resume_early
    [  932.681125] VEERA:====>drivers/base/power/main.c device_resume_early
    [  932.681136] VEERA:====>drivers/base/power/main.c device_resume_early
    [  932.681148] VEERA:====>drivers/base/power/main.c device_resume_early
    [  932.681159] VEERA:====>drivers/base/power/main.c device_resume_early
    [  932.681172] VEERA:====>drivers/base/power/main.c device_resume_early
    [  932.681184] VEERA:====>drivers/base/power/main.c device_resume_early
    [  932.681195] VEERA:====>drivers/base/power/main.c device_resume_early
    [  932.681206] VEERA:====>drivers/base/power/main.c device_resume_early
    [  932.681217] VEERA:====>drivers/base/power/main.c device_resume_early
    [  932.681228] VEERA:====>drivers/base/power/main.c device_resume_early
    [  932.681238] VEERA:====>drivers/base/power/main.c device_resume_early
    [  932.681248] VEERA:====>drivers/base/power/main.c device_resume_early
    [  932.681259] VEERA:====>drivers/base/power/main.c device_resume_early
    [  932.681269] VEERA:====>drivers/base/power/main.c device_resume_early
    [  932.681279] VEERA:====>drivers/base/power/main.c device_resume_early
    [  932.681290] VEERA:====>drivers/base/power/main.c device_resume_early
    [  932.681301] VEERA:====>drivers/base/power/main.c device_resume_early
    [  932.681311] VEERA:====>drivers/base/power/main.c device_resume_early
    [  932.681321] VEERA:====>drivers/base/power/main.c device_resume_early
    [  932.681332] VEERA:====>drivers/base/power/main.c device_resume_early
    [  932.681342] VEERA:====>drivers/base/power/main.c device_resume_early
    [  932.681352] VEERA:====>drivers/base/power/main.c device_resume_early
    [  932.681363] VEERA:====>drivers/base/power/main.c device_resume_early
    [  932.681374] VEERA:====>drivers/base/power/main.c device_resume_early
    [  932.681384] VEERA:====>drivers/base/power/main.c device_resume_early
    [  932.681395] VEERA:====>drivers/base/power/main.c device_resume_early
    [  932.681406] VEERA:====>drivers/base/power/main.c device_resume_early
    [  932.681418] VEERA:====>drivers/base/power/main.c device_resume_early
    [  932.681429] VEERA:====>drivers/base/power/main.c device_resume_early
    [  932.681439] VEERA:====>drivers/base/power/main.c device_resume_early
    [  932.681451] VEERA:====>drivers/base/power/main.c device_resume_early
    [  932.681462] VEERA:====>drivers/base/power/main.c device_resume_early
    [  932.681474] VEERA:====>drivers/base/power/main.c device_resume_early
    [  932.681484] VEERA:====>drivers/base/power/main.c device_resume_early
    [  932.681495] VEERA:====>drivers/base/power/main.c device_resume_early
    [  932.681507] VEERA:====>drivers/base/power/main.c device_resume_early
    [  932.681518] VEERA:====>drivers/base/power/main.c device_resume_early
    [  932.681530] VEERA:====>drivers/base/power/main.c device_resume_early
    [  932.681541] VEERA:====>drivers/base/power/main.c device_resume_early
    [  932.681552] VEERA:====>drivers/base/power/main.c device_resume_early
    [  932.681564] VEERA:====>drivers/base/power/main.c device_resume_early
    [  932.681575] VEERA:====>drivers/base/power/main.c device_resume_early
    [  932.681587] VEERA:====>drivers/base/power/main.c device_resume_early
    [  932.681598] VEERA:====>drivers/base/power/main.c device_resume_early
    [  932.681610] VEERA:====>drivers/base/power/main.c device_resume_early
    [  932.681620] VEERA:====>drivers/base/power/main.c device_resume_early
    [  932.681631] VEERA:====>drivers/base/power/main.c device_resume_early
    [  932.681641] VEERA:====>drivers/base/power/main.c device_resume_early
    [  932.681653] VEERA:====>drivers/base/power/main.c device_resume_early
    [  932.681664] VEERA:====>drivers/base/power/main.c device_resume_early
    [  932.681674] VEERA:====>drivers/base/power/main.c device_resume_early
    [  932.681686] VEERA:====>drivers/base/power/main.c device_resume_early
    [  932.681697] VEERA:====>drivers/base/power/main.c device_resume_early
    [  932.681708] VEERA:====>drivers/base/power/main.c device_resume_early
    [  932.681719] VEERA:====>drivers/base/power/main.c device_resume_early
    [  932.681729] VEERA:====>drivers/base/power/main.c device_resume_early
    [  932.681739] VEERA:====>drivers/base/power/main.c device_resume_early
    [  932.681750] VEERA:====>drivers/base/power/main.c device_resume_early
    [  932.681760] VEERA:====>drivers/base/power/main.c device_resume_early
    [  932.681771] VEERA:====>drivers/base/power/main.c device_resume_early
    [  932.681782] VEERA:====>drivers/base/power/main.c device_resume_early
    [  932.681792] VEERA:====>drivers/base/power/main.c device_resume_early
    [  932.681803] VEERA:====>drivers/base/power/main.c device_resume_early
    [  932.681814] VEERA:====>drivers/base/power/main.c device_resume_early
    [  932.681825] VEERA:====>drivers/base/power/main.c device_resume_early
    [  932.681836] VEERA:====>drivers/base/power/main.c device_resume_early
    [  932.681847] VEERA:====>drivers/base/power/main.c device_resume_early
    [  932.681858] VEERA:====>drivers/base/power/main.c device_resume_early
    [  932.681869] VEERA:====>drivers/base/power/main.c device_resume_early
    [  932.682109] VEERA:====>drivers/base/power/main.c device_resume_early
    [  932.682147] VEERA:====>drivers/base/power/main.c device_resume_early
    [  932.682177] VEERA:====>drivers/base/power/main.c device_resume_early
    [  932.682206] VEERA:====>drivers/base/power/main.c device_resume_early
    [  932.682233] VEERA:====>drivers/base/power/main.c device_resume_early
    [  932.682260] VEERA:====>drivers/base/power/main.c device_resume_early
    [  932.682289] VEERA:====>drivers/base/power/main.c device_resume_early
    [  932.682317] VEERA:====>drivers/base/power/main.c device_resume_early
    [  932.682347] VEERA:====>drivers/base/power/main.c device_resume_early
    [  932.682377] VEERA:====>drivers/base/power/main.c device_resume_early
    [  932.682405] VEERA:====>drivers/base/power/main.c device_resume_early
    [  932.682434] VEERA:====>drivers/base/power/main.c device_resume_early
    [  932.682675] VEERA:====>drivers/base/power/main.c device_resume_early
    [  932.682701] VEERA:====>drivers/base/power/main.c device_resume_early
    [  932.682728] VEERA:====>drivers/base/power/main.c device_resume_early
    [  932.682794] VEERA:====>drivers/base/power/main.c device_resume_early
    [  932.682978] VEERA:====>drivers/base/power/main.c device_resume_early
    [  932.683129] VEERA:====>drivers/base/power/main.c device_resume_early
    [  932.683141] VEERA:====>drivers/base/power/main.c device_resume_early
    [  932.683151] VEERA:====>drivers/base/power/main.c device_resume_early
    [  932.683162] VEERA:====>drivers/base/power/main.c device_resume_early
    [  932.683173] VEERA:====>drivers/base/power/main.c device_resume_early
    [  932.683184] VEERA:====>drivers/base/power/main.c device_resume_early
    [  932.683195] VEERA:====>drivers/base/power/main.c device_resume_early
    [  932.683206] VEERA:====>drivers/base/power/main.c device_resume_early
    [  932.683218] VEERA:====>drivers/base/power/main.c device_resume_early
    [  932.683229] VEERA:====>drivers/base/power/main.c device_resume_early
    [  932.683240] VEERA:====>drivers/base/power/main.c device_resume_early
    [  932.683251] VEERA:====>drivers/base/power/main.c device_resume_early
    [  932.683261] VEERA:====>drivers/base/power/main.c device_resume_early
    [  932.683272] VEERA:====>drivers/base/power/main.c device_resume_early
    [  932.683283] VEERA:====>drivers/base/power/main.c device_resume_early
    [  932.683294] VEERA:====>drivers/base/power/main.c device_resume_early
    [  932.683305] VEERA:====>drivers/base/power/main.c device_resume_early
    [  932.683316] VEERA:====>drivers/base/power/main.c device_resume_early
    [  932.683326] VEERA:====>drivers/base/power/main.c device_resume_early
    [  932.683337] VEERA:====>drivers/base/power/main.c device_resume_early
    [  932.683349] VEERA:====>drivers/base/power/main.c device_resume_early
    [  932.683360] VEERA:====>drivers/base/power/main.c device_resume_early
    [  932.683371] VEERA:====>drivers/base/power/main.c device_resume_early
    [  932.683382] VEERA:====>drivers/base/power/main.c device_resume_early
    [  932.683393] VEERA:====>drivers/base/power/main.c device_resume_early
    [  932.683404] VEERA:====>drivers/base/power/main.c device_resume_early
    [  932.683415] VEERA:====>drivers/base/power/main.c device_resume_early
    [  932.683426] VEERA:====>drivers/base/power/main.c device_resume_early
    [  932.683437] VEERA:====>drivers/base/power/main.c device_resume_early
    [  932.683448] VEERA:====>drivers/base/power/main.c device_resume_early
    [  932.683458] VEERA:====>drivers/base/power/main.c device_resume_early
    [  932.683469] VEERA:====>drivers/base/power/main.c device_resume_early
    [  932.683479] VEERA:====>drivers/base/power/main.c device_resume_early
    [  932.683490] VEERA:====>drivers/base/power/main.c device_resume_early
    [  932.683501] VEERA:====>drivers/base/power/main.c device_resume_early
    [  932.683514] VEERA:====>drivers/base/power/main.c device_resume_early
    [  932.683572] VEERA:====>drivers/base/power/main.c device_resume_early
    [  932.683613] VEERA:====>drivers/base/power/main.c device_resume_early
    [  932.683643] VEERA:====>drivers/base/power/main.c device_resume_early
    [  932.683690] VEERA:====>drivers/base/power/main.c device_resume_early
    [  932.683719] VEERA:====>drivers/base/power/main.c device_resume_early
    [  932.683748] VEERA:====>drivers/base/power/main.c device_resume_early
    [  932.683764] VEERA:====>drivers/base/power/main.c device_resume_early
    [  932.683778] VEERA:====>drivers/base/power/main.c device_resume_early
    [  932.683793] VEERA:====>drivers/base/power/main.c device_resume_early
    [  932.683808] VEERA:====>drivers/base/power/main.c device_resume_early
    [  932.683822] VEERA:====>drivers/base/power/main.c device_resume_early
    [  932.683837] VEERA:====>drivers/base/power/main.c device_resume_early
    [  932.683851] VEERA:====>drivers/base/power/main.c device_resume_early
    [  932.683865] VEERA:====>drivers/base/power/main.c device_resume_early
    [  932.683879] VEERA:====>drivers/base/power/main.c device_resume_early
    [  932.683893] VEERA:====>drivers/base/power/main.c device_resume_early
    [  932.683908] VEERA:====>drivers/base/power/main.c device_resume_early
    [  932.683922] VEERA:====>drivers/base/power/main.c device_resume_early
    [  932.683966] VEERA:====>drivers/base/power/main.c device_resume_early
    [  932.684016] VEERA:====>drivers/base/power/main.c device_resume_early
    [  932.684062] VEERA:====>drivers/base/power/main.c device_resume_early
    [  932.684091] VEERA:====>drivers/base/power/main.c device_resume_early
    [  932.684381] VEERA:====>drivers/base/power/main.c device_resume_early
    [  932.684396] VEERA:====>drivers/base/power/main.c device_resume_early
    [  932.684412] VEERA:====>drivers/base/power/main.c device_resume_early
    [  932.684424] VEERA:====>drivers/base/power/main.c device_resume_early
    [  932.684437] VEERA:====>drivers/base/power/main.c device_resume_early
    [  932.684449] VEERA:====>drivers/base/power/main.c device_resume_early
    [  932.684461] VEERA:====>drivers/base/power/main.c device_resume_early
    [  932.684485] PM: early resume of devices complete after 5.609 msecs
    [  932.686515] net eth0: initializing cpsw version 1.12 (0)
    [  932.686546] net eth0: initialized cpsw ale version 1.4
    [  932.691847] net eth0: phy found : id is : 0x7c111
    [  932.695828] net eth1: initializing cpsw version 1.12 (0)
    [  932.701075] net eth1: phy found : id is : 0x7c111
    [  933.243483] wlcore: PHY firmware version: Rev 8.2.0.0.237
    [  933.415361] wlcore: firmware booted (Rev 8.9.0.0.70)
    [  938.002676] dpm_run_callback(): usb_dev_resume+0x0/0x18 [usbcore] returns -110
    [  938.002758] PM: Device 1-1 failed to resume async: error -110
    [  938.003663] PM: resume of devices complete after 5319.147 msecs
    [  940.263859] VEERA:****drivers/soc/ti/pm33xx.c am33xx_pm_end
    [  940.269474] Restarting tasks ...
    [  940.272969] usb 1-1: USB disconnect, device number 2
    wlan0: INTERFACE-DISABLED
    wlan0: INTERFACE-ENABLED
    root@am335x-evm:~# [  940.313368] option1 ttyUSB0: GSM modem (1-port) converter now disconnected from ttyUSB0
    [  940.346748] option 1-1:1.0: device disconnected
    [  940.368209] option1 ttyUSB1: GSM modem (1-port) converter now disconnected from ttyUSB1
    [  940.396559] option 1-1:1.1: device disconnected
    [  940.414297] option1 ttyUSB2: GSM modem (1-port) converter now disconnected from ttyUSB2
    [  940.443910] option 1-1:1.2: device disconnected
    [  940.457296] option1 ttyUSB3: GSM modem (1-port) converter now disconnected from ttyUSB3
    [  940.483927] option 1-1:1.3: device disconnected
    [  940.507262] option1 ttyUSB4: GSM modem (1-port) converter now disconnected from ttyUSB4
    [  940.531113] option 1-1:1.4: device disconnected
    [  940.543754] qmi_wwan 1-1:1.5 wwan0: unregister 'qmi_wwan' usb-musb-hdrc.1.auto-1, WWAN/QMI device
    [  940.872127] usb 1-1: new high-speed USB device number 3 using musb-hdrc
    [  941.036948] option 1-1:1.0: GSM modem (1-port) converter detectedroot@am335x-evm:~# rtcwake -d
    [  941.059005] usb 1-1: GSM modem (1-port) converter now attached to ttyUSB0
    [  941.070028] option 1-1:1.1: GSM modem (1-port) converter detected
    [  941.085829] usb 1-1: GSM modem (1-port) converter now attached to ttyUSB1
    [  941.099916] option 1-1:1.2: GSM modem (1-port) converter detected
    [  941.113322] usb 1-1: GSM modem (1-port) converter now attached to ttyUSB2
    [  941.127087] option 1-1:1.3: GSM modem (1-port) converter detected
    [  941.137004] usb 1-1: GSM modem (1-port) converter now attached to ttyUSB3
    [  941.153765] option 1-1:1.4: GSM modem (1-port) converter detected
    [  941.166954] usb 1-1: GSM modem (1-port) converter now attached to ttyUSB4
    [  941.186346] qmi_wwan 1-1:1.5: cdc-wdm0: USB WDM device

  • 0 in reply to veera anjaneyulu
    TI__Guru**** 170625 points

    veera anjaneyulu said:

    we checked WER in drivers/tty/serial/omap-serial.c

    //#define OMAP_UART_WER_MOD_WKUP        0x7F commented by veera
    #define OMAP_UART_WER_MOD_WKUP  0x00 ============================> we changed from above to this.

    SYSC only registered in driver/tty/serial/8250/8250_omap.c file only.

    Still any changes needed give me idea.

    Try the below modification:

    /drivers/tty/serial/omap-serial.c

    static int serial_omap_startup(struct uart_port *port)

    {

    /* Enable module level wake up */
    //   up->wer = OMAP_UART_WER_MOD_WKUP;
    //    if (up->features & OMAP_UART_WER_HAS_TX_WAKEUP)
    //        up->wer |= OMAP_UART_TX_WAKEUP_EN;

     //   serial_out(up, UART_OMAP_WER, up->wer);

    }

    static void omap_serial_fill_features_erratas(struct uart_omap_port *up)
    {

    case OMAP_UART_REV_52:
            up->errata |= (UART_ERRATA_i202_MDR1_ACCESS |
                    UART_ERRATA_i291_DMA_FORCEIDLE);
          //  up->features |= OMAP_UART_WER_HAS_TX_WAKEUP;
            break;
        case OMAP_UART_REV_63:
            up->errata |= UART_ERRATA_i202_MDR1_ACCESS;
          //  up->features |= OMAP_UART_WER_HAS_TX_WAKEUP;
            break;

    }

    #ifdef CONFIG_PM
    static void serial_omap_restore_context(struct uart_omap_port *up)
    {

    //serial_out(up, UART_OMAP_WER, up->wer);
    }

    static int serial_omap_runtime_suspend(struct device *dev)
    {

    // serial_omap_enable_wakeup(up, true);

    }

    static int serial_omap_suspend(struct device *dev)
    {

    if (device_may_wakeup(dev))
            //serial_omap_enable_wakeup(up, true);

    }

    Regards,
    Pavel

  • 0 in reply to Pavel Botev
    Expert 1920 points

    Hi Povel,

    Thanks for your suggestion. we have done your changes and tried on our custom boards.One custom board we are not getting wakeup through uart its going to deep sleep mode.

    2.An other our custom target board  we run echo mem > /sys/power/state.Its waking automatically after some time?What is the reason ? Any hardware issue or software issue?

    3.But rtc wakeup is working fine on our two custom boards.

    4.By running echo mem > /sys/power/state.   one board is going to deep sleep means not waking up from uart ,I think this is the correct way because of we disabled enable wakeup source right?

    5.An other target board waking up automatically after some times.whats the reason?  

    Thanks 

    veera

  • 0 in reply to veera anjaneyulu
    TI__Guru**** 170625 points

    veera anjaneyulu said:

    Thanks for your suggestion. we have done your changes and tried on our custom boards.One custom board we are not getting wakeup through uart its going to deep sleep mode.

    2.An other our custom target board  we run echo mem > /sys/power/state.Its waking automatically after some time?What is the reason ? Any hardware issue or software issue?

    Are these two boards the same? With the same SW running? If yes, this should be HW issue. Can you provide me full console log with the issue?

    veera anjaneyulu said:
    4.By running echo mem > /sys/power/state.   one board is going to deep sleep means not waking up from uart ,I think this is the correct way because of we disabled enable wakeup source right?

    Yes. Note that the official way to disable UART wake-up is through the no_console_suspend in bootargs or set though sysfs.

    veera anjaneyulu said:
    5.An other target board waking up automatically after some times.whats the reason?  

    There might be various reasons. Need more details here, starting with console log.

    Regards,
    Pavel

  • 0 in reply to Pavel Botev
    Expert 1920 points

    Hi pavel,

    After Resuming SYSC register value always D only if we gave 9.But after resuming/wakeup its value giving D only.How its getting by default D value of the SYSC register.

    Where its coming from the default value.

    WER register we gave 0 in place of 0xff .After waking up WER register value 0x00 only.

    WER is ok but SYSC Why its changing,

    Thanks

    veera

  • 0 in reply to veera anjaneyulu
    TI__Guru**** 170625 points

    Veera,

    UART_SYSC[2] ENAWAKEUP bit is defined and changed in the below files:

    linux-4.4.12/arch/arm/mach-omap2/omap_hwmod_33xx_43xx_ipblock_data.c

    linux-4.4.12/arm/mach-omap2/omap_hwmod.h

    linux-4.4.12/arch/arm/mach-omap2/omap_hwmod.c

    You can try with removing the SYSC_HAS_ENAWAKEUP flag from struct omap_hwmod_class_sysconfig uart_sysc.

    Regards,
    Pavel

  • 0 in reply to Pavel Botev
    Expert 1920 points

    Hi Pavel,

    Thanks for your suggestion.we succed when we changed register values from D to 9 means disable system configuration wakeup in arch/arm/mach-omap2/omap_hwmod.h  file.

    //#define SYSC_HAS_ENAWAKEUP (1 << 2) veera
    #define SYSC_HAS_ENAWAKEUP (0 << 2).

     

    Now we are getting default  value 9 means hardware wakeup disabled right?

    root@am335x-evm:~# busybox-armv7l devmem 0x44E09054
    0x00000009

    Then if we run sleep command

    root@am335x-evm:~# echo mem > /sys/power/state
    [ 359.524089] VEERA:****drivers/soc/ti/pm33xx.c am33xx_pm_valid
    [ 359.529916] PM: Syncing filesystems ... done.
    [ 359.630067] VEERA:====>drivers/base/power/main.c dpm_for_each_dev
    [ 359.646442] Freezing user space processes ... (elapsed 0.001 seconds) done.
    [ 359.655442] Freezing remaining freezable tasks ... (elapsed 0.001 seconds) done.
    [ 359.664751] VEERA:****drivers/soc/ti/pm33xx.c am33xx_pm_begin
    [ 359.670540] VEERA:else===>****drivers/soc/ti/pm33xx.c am33xx_pm_begin ---->0

    now we are not facing automatically power waking up issue its going to deep sleep.

     

    Previous After 5-10 minuts in between we are facing automatically power waking up issue.Now Ok working fine.If we want wakeup from uart how enable.with out changing the register in omap-hwmod.h file.

    If we reverted back means the register value we set 0D But again we are facing automatic power waking up issue.Then how to fix this?

    is There any software bug? or how to fix give me idea.

     

    Thanks 

    veera

     

  • 0 in reply to veera anjaneyulu
    TI__Guru**** 170625 points

    veera anjaneyulu said:
    Now we are getting default  value 9 means hardware wakeup disabled right?

    Yes, 0x9 (b1001) mean wakeup is disabled, UART_SYSC[2] ENAWAKEUP = 0

    I will test this on the AM335x TI EVM. I will enter sleep mode (echo mem) and wait 10 minutes there to see if my EVM will wake-up by spurious/fake UART wake-up event. But I do not think this will happen. This looks like HW malfunction of your custom board. You might check again your design with focus on the UART.

    Does all your custom boards have these spurious/fake UART wake-up events?

    Regards,
    Pavel


  • 0 in reply to Pavel Botev
    Expert 1920 points

    Hi Pavel,

    Thanks for your reply.

    Then how to avoid spurious/fake uart wake up events with software .Any changes needed?

    Thanks

    veera

  • 0 in reply to veera anjaneyulu
    Expert 1920 points

    Hi Pavel,

    we have checked on our automatically waking up custom board and not waking up custom board we probed uart0 voltage levels.voltage levels are same 1.8v .we did not observe nothing changes.

    But behaviour different means after five minuts getting automatically  power waking up issue.ie only difference remaining all functionalities same.

    Thanks 

    veera

  • 0 in reply to veera anjaneyulu
    TI__Guru**** 170625 points

    Veera,


    Let me clarify something. You have custom boards that works fine and custom boards that have fake UART wake-up events?

    Regards,
    Pavel

  • 0 in reply to Pavel Botev
    Expert 1920 points

    Hi pavel,

    Ya we have custom boards that works fine.custom boards does not have fake uart wake-up events.If we found any spuriours/fake events from i ll let you know.

    Thanks

    veera

  • 0 in reply to veera anjaneyulu
    TI__Guru**** 170625 points
    Veera,

    Then this seems to me like a HW problem of your non-working custom board. You should compare your non-working custom board with:
    - your working custom board
    - AM335x TI EVM
    - BeagleBoneBlack board

    Regards,
    Pavel