devicetree.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Sylvain Rochet <sylvain.rochet@finsecur.com>
To: Dmitry Torokhov <dmitry.torokhov@gmail.com>
Cc: "devicetree@vger.kernel.org" <devicetree@vger.kernel.org>,
	"linux-input@vger.kernel.org" <linux-input@vger.kernel.org>,
	Daniel Mack <daniel@caiaq.de>, Johan Hovold <jhovold@gmail.com>
Subject: Re: Correct property to use for wake up support on rotary encoders
Date: Mon, 12 Oct 2015 18:42:49 +0200	[thread overview]
Message-ID: <20151012164248.GA11780@gradator.net> (raw)
In-Reply-To: <CAKdAkRSAYRr8PqcmzVCmGy89dedo_aybJq-2FhPzF1CFYy0GYg@mail.gmail.com>

Hi Dmitry,

On Mon, Oct 12, 2015 at 09:29:16AM -0700, Dmitry Torokhov wrote:
> On Mon, Oct 12, 2015 at 9:09 AM, Sylvain Rochet
> <sylvain.rochet@finsecur.com> wrote:
> >
> > Several month ago I proposed a patch[1][2] to add wake up support to
> > rotary encoders[3].
> >
> > Among all the properties currently used in Linux kernels device trees,
> > we have three recognisable patterns for wake up support:
> >  - driver-name,wakeup
> >  - linux,wakeup
> >  - wakeup-source
> >
> > We don't know which one to use, could you tell which one we should use
> > for GPIO rotary encoders ?
> 
> Please use "wakeup-source", we've been trying to standardize on it.

Thank you Dmitry for this fast answer. I will respin shortly then.

Sylvain

      reply	other threads:[~2015-10-12 16:42 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-10-12 16:09 Correct property to use for wake up support on rotary encoders Sylvain Rochet
2015-10-12 16:29 ` Dmitry Torokhov
2015-10-12 16:42   ` Sylvain Rochet [this message]

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=20151012164248.GA11780@gradator.net \
    --to=sylvain.rochet@finsecur.com \
    --cc=daniel@caiaq.de \
    --cc=devicetree@vger.kernel.org \
    --cc=dmitry.torokhov@gmail.com \
    --cc=jhovold@gmail.com \
    --cc=linux-input@vger.kernel.org \
    /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;
as well as URLs for NNTP newsgroup(s).