lists.openwall.net   lists  /  announce  owl-users  owl-dev  john-users  john-dev  passwdqc-users  yescrypt  popa3d-users  /  oss-security  kernel-hardening  musl  sabotage  tlsify  passwords  /  crypt-dev  xvendor  /  Bugtraq  Full-Disclosure  linux-kernel  linux-netdev  linux-ext4  linux-hardening  linux-cve-announce  PHC 
Open Source and information security mailing list archives
 
Hash Suite: Windows password security audit tool. GUI, reports in PDF.
[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20180523180052.GP98604@atomide.com>
Date:   Wed, 23 May 2018 11:00:52 -0700
From:   Tony Lindgren <tony@...mide.com>
To:     Andy Shevchenko <andy.shevchenko@...il.com>
Cc:     Sebastian Andrzej Siewior <bigeasy@...utronix.de>,
        Andy Shevchenko <andriy.shevchenko@...ux.intel.com>,
        Petr Mladek <pmladek@...e.com>,
        Sergey Senozhatsky <sergey.senozhatsky@...il.com>,
        Steven Rostedt <rostedt@...dmis.org>,
        Linux Kernel Mailing List <linux-kernel@...r.kernel.org>,
        Greg Kroah-Hartman <gregkh@...uxfoundation.org>,
        Jiri Slaby <jslaby@...e.com>,
        "open list:SERIAL DRIVERS" <linux-serial@...r.kernel.org>,
        Arnd Bergmann <arnd@...db.de>
Subject: Re: [PATCH v1 0/3] console, serial8250: Disable PM and DMA ops

* Andy Shevchenko <andy.shevchenko@...il.com> [180522 21:54]:
> On Thu, May 17, 2018 at 10:48 PM, Tony Lindgren <tony@...mide.com> wrote:
> > * Andy Shevchenko <andy.shevchenko@...il.com> [180517 16:38]:
> >> On Thu, May 17, 2018 at 4:48 PM, Tony Lindgren <tony@...mide.com> wrote:
> >> > * Sebastian Andrzej Siewior <bigeasy@...utronix.de> [180516 10:49]:
> 
> >> > The idea breaking PM seems silly to me considering that we've had
> >> > it working for years already.
> >>
> >> Same question  / note. World is much more complex than just being OMAP.
> >
> > Sorry but you are making assumptions about hardware being powered on
> > all the time.
> 
> Nope, other way around. The so called "support" _prevents_ our
> hardware to go to sleep.

Hmm sorry now I'm all confused what issues you're having.

I thought you said earlier the issue was that you wanted to keep
the console enabled all the time and never idle?

Regards,

Tony

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ