From: "Enrico Weigelt, metux IT consult" <info@metux.net>
To: linux-kernel@vger.kernel.org
Cc: dmitry.torokhov@gmail.com, linux-input@vger.kernel.org
Subject: repost: input: keyboard: gpio-keys-polled: use input name from pdata
Date: Fri, 7 Jun 2019 00:43:08 +0200 [thread overview]
Message-ID: <1559860989-7723-1-git-send-email-info@metux.net> (raw)
Hi,
this patch had already been sent a while ago, and a discussion arised
about whether pdata support should be dropped in favour of of/acpi.
Unfortunately, the open problems - lack of proper of/acpi data and sane
ways to inject this data - remain (theoretically, could be done by writing
special fwnode backends, but that would be a whole project on its own)
and the discussion perished w/o any conclusion.
Until we have a complete and easily replacement for pdata, even for cases
where no oftree/acpi data is available and platform drivers need to be
instantiated directly, pdata structs still need to be maintained.
Therefore I'm resending this pretty trivial patch.
--mtx
next reply other threads:[~2019-06-06 22:43 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-06-06 22:43 Enrico Weigelt, metux IT consult [this message]
2019-06-06 22:43 ` [PATCH] input: keyboard: gpio-keys-polled: use input name from pdata if available Enrico Weigelt, metux IT consult
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=1559860989-7723-1-git-send-email-info@metux.net \
--to=info@metux.net \
--cc=dmitry.torokhov@gmail.com \
--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 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).