All of lore.kernel.org
 help / color / mirror / Atom feed
From: Heiko Stuebner <heiko@sntech.de>
To: Dmitry Torokhov <dmitry.torokhov@gmail.com>
Cc: Linus Walleij <linus.walleij@linaro.org>,
	linux-input@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH 1/5] Input: auo-pixcir-ts - drop support for platform data
Date: Wed, 14 Sep 2022 16:40:22 +0200	[thread overview]
Message-ID: <5602073.DvuYhMxLoT@phil> (raw)
In-Reply-To: <20220914141428.2201784-1-dmitry.torokhov@gmail.com>

Am Mittwoch, 14. September 2022, 16:14:24 CEST schrieb Dmitry Torokhov:
> Currently there are no users of auo_pixcir_ts_platdata in the mainline, and
> having it (with legacy gpio numbers) prevents us from converting the driver
> to gpiod API, so let's drop it.
> 
> If, in the future, someone wants to use this driver on non-device tree,
> non-ACPI system, they should use static device properties instead of
> platform data.
> 
> Signed-off-by: Dmitry Torokhov <dmitry.torokhov@gmail.com>

Reviewed-by: Heiko Stuebner <heiko@sntech.de>



      parent reply	other threads:[~2022-09-14 14:40 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-09-14 14:14 [PATCH 1/5] Input: auo-pixcir-ts - drop support for platform data Dmitry Torokhov
2022-09-14 14:14 ` [PATCH 2/5] Input: auo-pixcir-ts - switch to using gpiod API Dmitry Torokhov
2022-09-14 15:04   ` Heiko Stuebner
2022-09-14 15:15     ` Dmitry Torokhov
2022-09-15 13:08   ` Heiko Stuebner
2022-09-18 14:40   ` Linus Walleij
2022-09-14 14:14 ` [PATCH 3/5] Input: auo-pixcir-ts - do not force rising edge interrupt trigger Dmitry Torokhov
2022-09-14 15:05   ` Heiko Stuebner
2022-09-14 14:14 ` [PATCH 4/5] Input: auo-pixcir-ts - switch to using generic device properties Dmitry Torokhov
2022-09-14 15:06   ` Heiko Stuebner
2022-09-14 14:14 ` [PATCH 5/5] dt-bindings: input: auo-pixcir-ts: fix gpio and interrupt properties Dmitry Torokhov
2022-09-14 15:07   ` Heiko Stuebner
2022-09-14 14:40 ` Heiko Stuebner [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=5602073.DvuYhMxLoT@phil \
    --to=heiko@sntech.de \
    --cc=dmitry.torokhov@gmail.com \
    --cc=linus.walleij@linaro.org \
    --cc=linux-input@vger.kernel.org \
    --cc=linux-kernel@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 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.