All of lore.kernel.org
 help / color / mirror / Atom feed
From: Tomi Valkeinen <tomi.valkeinen@ti.com>
To: Jyri Sarha <jsarha@ti.com>, dri-devel@lists.freedesktop.org
Cc: Darren Etheridge <detheridge@ti.com>, laurent.pinchart@ideasonboard.com
Subject: Re: [PATCH 01/21] drm/tilcdc: disable console switching during pm operations
Date: Mon, 8 Feb 2016 22:00:20 +0200	[thread overview]
Message-ID: <56B8F3D4.5090802@ti.com> (raw)
In-Reply-To: <c7774d3c091ddc47e97f46d4d0e15cb349bda402.1454577570.git.jsarha@ti.com>


[-- Attachment #1.1: Type: text/plain, Size: 708 bytes --]



On 04/02/16 11:30, Jyri Sarha wrote:
> From: Darren Etheridge <detheridge@ti.com>
> 
> The default behavior of consoles during power management operations is: On
> entry to suspend a new console is allocated and switched to. On resume the
> original console is restored.
> 
> However this isn't the observed behavior and the original console is not
> restored. This commit avoids the problem by disabling the switching of
> consoles at suspend/resume. This works because the driver already restores
> all necessary hardware context during such pm operations.

I think this should be dropped, because no one else is doing the same,
and the whole issue seems to be rather unclear.

 Tomi


[-- Attachment #1.2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 819 bytes --]

[-- Attachment #2: Type: text/plain, Size: 160 bytes --]

_______________________________________________
dri-devel mailing list
dri-devel@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/dri-devel

  reply	other threads:[~2016-02-08 20:00 UTC|newest]

Thread overview: 24+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-02-04  9:30 [PATCH 00/21] drm/ticdc: Accumulated fixes over the past couple of years Jyri Sarha
2016-02-04  9:30 ` [PATCH 01/21] drm/tilcdc: disable console switching during pm operations Jyri Sarha
2016-02-08 20:00   ` Tomi Valkeinen [this message]
2016-02-09  9:41     ` Daniel Vetter
2016-02-04  9:30 ` [PATCH 02/21] drm/tilcdc: rewrite pixel clock calculation Jyri Sarha
2016-02-04  9:30 ` [PATCH 03/21] drm/tilcdc: verify fb pitch Jyri Sarha
2016-02-04  9:30 ` [PATCH 04/21] drm/tilcdc: adopt pinctrl support Jyri Sarha
2016-02-04  9:30 ` [PATCH 05/21] drm/tilcdc: fix kernel panic on suspend when no hdmi monitor connected Jyri Sarha
2016-02-04  9:30 ` [PATCH 06/21] drm/tilcdc: make frame_done interrupt active at all times Jyri Sarha
2016-02-04  9:31 ` [PATCH 07/21] drm/tilcdc: disable the lcd controller/dma engine when suspend invoked Jyri Sarha
2016-02-04  9:31 ` [PATCH 08/21] drm/tilcdc: Implement dma-buf support for tilcdc Jyri Sarha
2016-02-04  9:31 ` [PATCH 09/21] drm/tilcdc: fix build error when !CONFIG_CPU_FREQ Jyri Sarha
2016-02-04  9:31 ` [PATCH 10/21] drm/tilcdc: Allocate register storage based on the actual number registers Jyri Sarha
2016-02-04  9:31 ` [PATCH 11/21] drm/tilcdc: cleanup runtime PM handling Jyri Sarha
2016-02-04  9:31 ` [PATCH 12/21] drm/tilcdc: disable crtc on unload Jyri Sarha
2016-02-04  9:31 ` [PATCH 13/21] drm/tilcdc: split reset to a separate function Jyri Sarha
2016-02-04  9:31 ` [PATCH 14/21] drm/tilcdc: remove broken error handling Jyri Sarha
2016-02-04  9:31 ` [PATCH 15/21] drm/tilcdc: cleanup irq handling Jyri Sarha
2016-02-04  9:31 ` [PATCH 16/21] drm/tilcdc: Get rid of complex ping-pong mechanism Jyri Sarha
2016-02-04  9:31 ` [PATCH 17/21] drm/tilcdc: Do not update the next frame buffer close to vertical blank Jyri Sarha
2016-02-04  9:31 ` [PATCH 18/21] drm/tilcdc: Fix interrupt enable/disable code for version 2 tilcdc Jyri Sarha
2016-02-04  9:31 ` [PATCH 19/21] drm/tilcdc: Remove the duplicate LCDC_INT_ENABLE_SET_REG in registers[] Jyri Sarha
2016-02-04  9:31 ` [PATCH 20/21] drm/tilcdc: Add prints on sync lost and FIFO underrun interrupts Jyri Sarha
2016-02-04  9:31 ` [PATCH 21/21] drm/tilcdc: Disable sync lost interrupt if it fires on every frame Jyri Sarha

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=56B8F3D4.5090802@ti.com \
    --to=tomi.valkeinen@ti.com \
    --cc=detheridge@ti.com \
    --cc=dri-devel@lists.freedesktop.org \
    --cc=jsarha@ti.com \
    --cc=laurent.pinchart@ideasonboard.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body. 
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.