All of lore.kernel.org
 help / color / mirror / Atom feed
From: Jiri Kosina <jikos@kernel.org>
To: Roderick Colenbrander <roderick@gaikai.com>
Cc: Bastien Nocera <hadess@hadess.net>,
	Cameron Gutman <aicommander@gmail.com>,
	linux-input@vger.kernel.org,
	Benjamin Tissoires <benjamin.tissoires@redhat.com>
Subject: Re: Method to power off HID device from driver?
Date: Thu, 19 Jan 2017 14:37:40 +0100 (CET)	[thread overview]
Message-ID: <alpine.LSU.2.20.1701191436220.25515@cbobk.fhfr.pm> (raw)
In-Reply-To: <CANndSKkeMtLp6S2MRXFHTrdyUnVQ7HqwyKB2F-pqbgJFPh8A9w@mail.gmail.com>

On Mon, 9 Jan 2017, Roderick Colenbrander wrote:

> From the sounds of it various others are interested in the ability to
> trigger a device disconnect as well. Since I don't think any of us
> have a good enough understanding of the HID / input frameworks, I'm
> adding Benjamin and Jiri. Maybe they have some good ideas on how to
> tackle this.

Well, this really depends on the low-level (transport, as we call it in 
HID) driver.

USB, for example, has it's own runtime power management, and the devices 
auto-suspend and auto-resume themselves almost automatically without too 
many specific generic code requirements.

What is the hardware transport we're talking about here?

-- 
Jiri Kosina
SUSE Labs


  reply	other threads:[~2017-01-19 13:37 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-12-02  2:05 Method to power off HID device from driver? Roderick Colenbrander
2016-12-07  0:25 ` Roderick Colenbrander
2016-12-07  3:20   ` Cameron Gutman
2016-12-07 21:21     ` Roderick Colenbrander
2016-12-08  3:39     ` Bastien Nocera
2017-01-10  2:28       ` Roderick Colenbrander
2017-01-19 13:37         ` Jiri Kosina [this message]
2017-01-19 13:42           ` Bastien Nocera
     [not found]             ` <CANndSKkp+wYjp4DpWX5VK7MLWEn60tgcc5QX=r87gPQJKvkoPg@mail.gmail.com>
2017-01-19 16:26               ` Bastien Nocera
2017-01-19 18:07                 ` Roderick Colenbrander
2017-01-24  9:47                   ` Bastien Nocera
2017-01-24 15:29                     ` Roderick Colenbrander

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.LSU.2.20.1701191436220.25515@cbobk.fhfr.pm \
    --to=jikos@kernel.org \
    --cc=aicommander@gmail.com \
    --cc=benjamin.tissoires@redhat.com \
    --cc=hadess@hadess.net \
    --cc=linux-input@vger.kernel.org \
    --cc=roderick@gaikai.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.