From: Scot Doyle <lkml14@scotdoyle.com>
To: Jean-Philippe Brucker <jean-philippe.brucker@arm.com>
Cc: linux-fbdev@vger.kernel.org,
Jean-Christophe Plagniol-Villard <plagnioj@jcrosoft.com>,
Tomi Valkeinen <tomi.valkeinen@ti.com>,
Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
Pavel Machek <pavel@ucw.cz>, Thierry Reding <treding@nvidia.com>,
stable@vger.kernel.org
Subject: Re: [PATCH] fbcon: set a default value to blink interval
Date: Mon, 15 Feb 2016 21:12:43 +0000 [thread overview]
Message-ID: <alpine.DEB.2.10.1602151500060.14844@laptop> (raw)
In-Reply-To: <1455561693-28615-1-git-send-email-jean-philippe.brucker@arm.com>
On Mon, 15 Feb 2016, Jean-Philippe Brucker wrote:
> Since commit 27a4c827c34ac4256a190cc9d24607f953c1c459
> fbcon: use the cursor blink interval provided by vt
>
> two attempts have been made at fixing a possible hang caused by
> cursor_timer_handler. That function registers a timer to be triggered at
> "jiffies + fbcon_ops.cur_blink_jiffies".
...
> Instead of patching all possible paths that lead to this case one at a
> time, fix the issue at the source and initialise cur_blink_jiffies to
> 200ms when allocating fbcon_ops. This was its default value before
> aforesaid commit. fbcon_cursor or fbcon_init will refine this value
> downstream.
>
> Signed-off-by: Jean-Philippe Brucker <jean-philippe.brucker@arm.com>
> Cc: <stable@vger.kernel.org> # v4.2
I agree with the approach and the patch works on my x86_64.
Tested-by: Scot Doyle <lkml14@scotdoyle.com>
next prev parent reply other threads:[~2016-02-15 21:12 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-02-15 18:41 [PATCH] fbcon: set a default value to blink interval Jean-Philippe Brucker
2016-02-15 21:12 ` Scot Doyle [this message]
2016-02-26 11:21 ` Tomi Valkeinen
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=alpine.DEB.2.10.1602151500060.14844@laptop \
--to=lkml14@scotdoyle.com \
--cc=gregkh@linuxfoundation.org \
--cc=jean-philippe.brucker@arm.com \
--cc=linux-fbdev@vger.kernel.org \
--cc=pavel@ucw.cz \
--cc=plagnioj@jcrosoft.com \
--cc=stable@vger.kernel.org \
--cc=tomi.valkeinen@ti.com \
--cc=treding@nvidia.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox