Hi Samuel Thanks for your detail insights, its really helpful for further debug. here is my observation on my target. Could you please check is it helpfull for triage.
ARISC firmware loaded successfully in kernel , pfb for logs in both kernel and u-boot. uboot: [ 1.144]set arisc reset to de-assert state [ 1.248][ARISC] :arisc initialize [ 1.275][ARISC] :arisc para ok [SCP] :sunxi-arisc driver begin startup 2 [SCP] :arisc version: [v0.2.17.1] [SCP] :sunxi-arisc driver v1.10 is starting [ 1.288][ARISC] :sunxi-arisc driver startup succeeded kernel: bpi-m64-lcd5:/sys/devices/soc.0/arisc.2 # dmesg | grep arisc [ 0.342420] [ARISC] :sunxi-arisc driver v1.10 [ 0.360645] [ARISC] :sunxi-arisc driver v1.10 startup succeeded but i can see that in kernel none ldo on during stand by. bpi-m64-lcd5:/sys/devices/soc.0/arisc.2 # cat sst_power_real_info power info: enable 0x0 regs 0x0 power consume 0mw these power on during standby: axp:(null) these power off during standby: axp:dc5ldo,dcdc1,dcdc2,dcdc3,dcdc4,dcdc5,aldo1,aldo2,eldo1,eldo2,eldo3,dldo1,dldo2,dldo3,dldo4,dc1sw,aldo3,io0ldo,io1ldo Could you please suggest any way to fix this issue?? I dont find any dram refresh parameters in dtsi file. Your help will be really appreciated. Regards Pune On Monday, 13 January 2020 10:19:42 UTC+5:30, Samuel Holland wrote: > > Allwinner sun8i/sun50i SoCs (A31 and newer) have two interrupt > controllers: GIC and R_INTC. GIC does not support wakeup, and is > inaccessible from the ARISC (power management coprocessor). R_INTC > controls the NMI pin, and provides 16-32 IRQs to the ARISC. The first 16 > of these correspond 1:1 to a block of GIC IRQs starting with the NMI. > > This series replaces the existing chained irqchip driver used only to > control the NMI, with a stacked irqchip driver that also provides wakeup > capability for those 16 IRQs. The idea is that we preconfigure the > ARISC's IRQ controller, and then it knows to wake up as soon as it > receives an IRQ. > > I went back and forth about updating the existing driver versus writing > a new one. The NMI-only control on sun7i (A20) and sun9i (A80) is > missing MASK_REG, so it would need a different irq_chip definition. And > the only benefit it would get is the chained->stacked conversion, since > there's no separate coprocessor to see the IRQs during suspend. So > ultimately I went with a new driver. It may be useful to separately do > the chained->stacked conversion on the sunxi-nmi driver as well. > > Patch 1 adds the new driver. > Patch 2 adds wakeup capability. > Remaining patches update the DT+bindings to use R_INTC where beneficial > > With appropriate firmware, this series allows waking from RTC and NMI > (power button, plugging in USB, etc.). Wake from Port L GPIO interrupts > (gpio-keys, wifi, etc.) requires some patches to the pinctrl driver. > > Samuel Holland (9): > irqchip/sun6i-r: Switch to a stacked irqchip driver > irqchip/sun6i-r: Add wakeup support > dt-bindings: irq: Add a compatible for the H3 R_INTC > ARM: dts: sunxi: h3/h5: Add r_intc node > ARM: dts: sunxi: h3/h5: Move wakeup-capable IRQs to r_intc > ARM: dts: sunxi: a83t: Move wakeup-capable IRQs to r_intc > arm64: dts: allwinner: a64: Move wakeup-capable IRQs to r_intc > arm64: dts: allwinner: h6: Fix indentation of IR node > arm64: dts: allwinner: Move wakeup-capable IRQs to r_intc > > .../allwinner,sun7i-a20-sc-nmi.yaml | 3 + > arch/arm/boot/dts/sun8i-a83t.dtsi | 9 +- > arch/arm/boot/dts/sunxi-h3-h5.dtsi | 20 +- > arch/arm/mach-sunxi/Kconfig | 1 + > arch/arm64/Kconfig.platforms | 1 + > arch/arm64/boot/dts/allwinner/sun50i-a64.dtsi | 11 +- > arch/arm64/boot/dts/allwinner/sun50i-h6.dtsi | 33 ++- > drivers/irqchip/Makefile | 1 + > drivers/irqchip/irq-sun6i-r.c | 273 ++++++++++++++++++ > drivers/irqchip/irq-sunxi-nmi.c | 26 +- > 10 files changed, 329 insertions(+), 49 deletions(-) > create mode 100644 drivers/irqchip/irq-sun6i-r.c > > -- > 2.23.0 > > -- You received this message because you are subscribed to the Google Groups "linux-sunxi" group. To unsubscribe from this group and stop receiving emails from it, send an email to linux-sunxi+unsubscr...@googlegroups.com. To view this discussion on the web, visit https://groups.google.com/d/msgid/linux-sunxi/120d1c98-b7d7-4ebf-a95e-03c413961758%40googlegroups.com.
