On Fri, 20 Nov 2015, Jon Hunter wrote:
>
> On 19/11/15 14:23, Jon Hunter wrote:
> > The as3722 device is registered as an irqchip and the as3722-rtc interrupt
> > is one of it's interrupt sources. When using the as3722-rtc as a wake-up
> > device from suspend, the following is seen:
> >
> >
On 19/11/15 14:23, Jon Hunter wrote:
> The as3722 device is registered as an irqchip and the as3722-rtc interrupt
> is one of it's interrupt sources. When using the as3722-rtc as a wake-up
> device from suspend, the following is seen:
>
> PM: Syncing filesystems ... done.
> Freezing user
On 19/11/15 14:23, Jon Hunter wrote:
> The as3722 device is registered as an irqchip and the as3722-rtc interrupt
> is one of it's interrupt sources. When using the as3722-rtc as a wake-up
> device from suspend, the following is seen:
>
> PM: Syncing filesystems ... done.
> Freezing user
On Fri, 20 Nov 2015, Jon Hunter wrote:
>
> On 19/11/15 14:23, Jon Hunter wrote:
> > The as3722 device is registered as an irqchip and the as3722-rtc interrupt
> > is one of it's interrupt sources. When using the as3722-rtc as a wake-up
> > device from suspend, the following is seen:
> >
> >
The as3722 device is registered as an irqchip and the as3722-rtc interrupt
is one of it's interrupt sources. When using the as3722-rtc as a wake-up
device from suspend, the following is seen:
PM: Syncing filesystems ... done.
Freezing user space processes ... (elapsed 0.001 seconds) done.
The as3722 device is registered as an irqchip and the as3722-rtc interrupt
is one of it's interrupt sources. When using the as3722-rtc as a wake-up
device from suspend, the following is seen:
PM: Syncing filesystems ... done.
Freezing user space processes ... (elapsed 0.001 seconds) done.
6 matches
Mail list logo