From: Mathieu Poirier <email@example.com>
To: Dmitry Torokhov <firstname.lastname@example.org>
Cc: email@example.com, firstname.lastname@example.org,
Subject: Re: [PATCH v2] drivers/tty: Folding Android's keyreset driver in sysRQ
Date: Fri, 31 Aug 2012 15:52:00 -0600 [thread overview]
Message-ID: <email@example.com> (raw)
On 12-08-30 05:01 PM, Dmitry Torokhov wrote:
> Hi Matthieu,
> On Thu, Aug 30, 2012 at 04:30:54PM -0600, firstname.lastname@example.org wrote:
>> From: "Mathieu J. Poirier" <email@example.com>
>> This patch adds keyreset functionality to the sysrq driver. It
>> allows certain button/key combinations to be used in order to
>> trigger device resets.
>> The first time the key-combo is detected a work function that syncs
>> the filesystems is scheduled and the kernel rebooted. If all the keys
>> are released and then pressed again, it calls panic. Reboot on panic
>> should be set for this to work. A platform device that specify a
>> reset key-combo should be added to the board file to trigger the
> Why do we need to involve a platform device and not use, for example, a module
> parameter, that could be set up from userspace?
The platform device comes from the original design and was included to
minimise the amount of changes in code that make use of the current
I am definitely willing to explore the possibility of adding module
parameter to complement the platform data but again, to avoid impacting
board code I'm in favour of keeping the platform data/device - get back
to me if you disagree.
Thinking back on this it may be better to call 'platform_driver_probe'
rather than 'platform_driver_register'. That way one wouldn't have to
instantiate a platform_device.
> Also, why do we need reset_fn() and not simply invoke SysRq-B handler
> that should call ctrl_alt_del() for us?
The reset_fn() gives an implementer the chance of calling some custom
function before the reset sequence is started and in my opinion should
stay. On the flip side I'm not sure that I understand what you mean by
"SysRq-B handler" - are you talking about the "sysrq_reboot_op" ?
Please expand on that ?
Thanks for the review and comments,
next prev parent reply other threads:[~2012-08-31 21:52 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-08-30 22:30 [PATCH v2] drivers/tty: Folding Android's keyreset driver in sysRQ mathieu.poirier
2012-08-30 23:01 ` Dmitry Torokhov
2012-08-31 21:52 ` Mathieu Poirier [this message]
2012-08-31 22:02 ` Alan Cox
2012-08-31 22:41 ` Dmitry Torokhov
2012-08-31 22:57 ` Mathieu Poirier
2012-08-31 23:22 ` Dmitry Torokhov
2012-09-04 21:53 ` Mathieu Poirier
2012-09-04 22:01 ` Alan Cox
2012-08-31 22:51 ` Mathieu Poirier
2012-09-01 19:18 ` Colin Cross
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:
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
* 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;
as well as URLs for NNTP newsgroup(s).