linux-input.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Dmitry Torokhov <dmitry.torokhov@gmail.com>
To: Linus Walleij <linus.walleij@linaro.org>
Cc: Tony Lindgren <tony@atomide.com>, linux-input@vger.kernel.org
Subject: Re: [PATCH 4/4] Input: as5011 - Convert to GPIO descriptor
Date: Tue, 12 Dec 2023 23:13:42 -0800	[thread overview]
Message-ID: <ZXlZptEFE3DWyURm@google.com> (raw)
In-Reply-To: <20231129-descriptors-input-v1-4-9433162914a3@linaro.org>

On Wed, Nov 29, 2023 at 02:51:48PM +0100, Linus Walleij wrote:
> This driver does not have any in-tree users but is passing a
> legacy GPIO number through platform data.
> 
> Convert it to use a GPIO descriptor, new users or outoftree
> users can easily be implemented using GPIO descriptor tables
> or software nodes.
> 
> Signed-off-by: Linus Walleij <linus.walleij@linaro.org>

Applied, thank you.

-- 
Dmitry

      reply	other threads:[~2023-12-13  7:13 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-11-29 13:51 [PATCH 0/4] Convert some input drivers to use GPIO descriptors Linus Walleij
2023-11-29 13:51 ` [PATCH 1/4] Input: navpoint - Convert to use GPIO descriptor Linus Walleij
2023-12-13  7:13   ` Dmitry Torokhov
2023-11-29 13:51 ` [PATCH 2/4] Input: tca6416-keypad - Drop unused include Linus Walleij
2023-12-13  7:13   ` Dmitry Torokhov
2023-11-29 13:51 ` [PATCH 3/4] Input: omap-keypad - Drop optional GPIO support Linus Walleij
2023-11-30 12:15   ` Tony Lindgren
2023-12-13  7:10   ` Dmitry Torokhov
2023-12-13  8:19     ` Linus Walleij
2023-11-29 13:51 ` [PATCH 4/4] Input: as5011 - Convert to GPIO descriptor Linus Walleij
2023-12-13  7:13   ` Dmitry Torokhov [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=ZXlZptEFE3DWyURm@google.com \
    --to=dmitry.torokhov@gmail.com \
    --cc=linus.walleij@linaro.org \
    --cc=linux-input@vger.kernel.org \
    --cc=tony@atomide.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;
as well as URLs for NNTP newsgroup(s).