From: Robert Jarzmik <robert.jarzmik@free.fr>
To: Dmitry Torokhov <dmitry.torokhov@gmail.com>,
Daniel Mack <daniel@zonque.org>
Cc: linux-input@vger.kernel.org, "Timo Teräs" <timo.teras@iki.fi>,
"Haojian Zhuang" <haojian.zhuang@gmail.com>,
linux-arm-kernel@lists.infradead.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH 0/4] rotary-encoder: use generic device properties
Date: Sat, 23 Jan 2016 19:01:04 +0100 [thread overview]
Message-ID: <87r3h8b2fz.fsf@belgarion.home> (raw)
In-Reply-To: <1453138902-11657-1-git-send-email-dmitry.torokhov@gmail.com> (Dmitry Torokhov's message of "Mon, 18 Jan 2016 09:41:38 -0800")
Dmitry Torokhov <dmitry.torokhov@gmail.com> writes:
> Hi,
>
> This series tries to move the driver away from legacy platform data towards
> using platform-independent way of retrieving both configuration parameters and
> GPIOs (device_property_read_* and gpiod APIs).
>
> This is based on top of 2 Timo's patches converting the driver to use devm* API
> and threaded IRQs. I uploaded all changes into 'rotary-encoder' branch of my
> tree.
>
> I do not have hard ware so please give it a spin, especially on raumfield as it
> uses branch new way of passing platform parameters to the driver.
Hi Dmitry,
>From the pxa architecture point of view, it looks fine to me.
Daniel, I seem to remember you had this raumfeld hardware, would you have the
opportunity to give this serie a try ?
Cheers.
--
Robert
prev parent reply other threads:[~2016-01-23 18:01 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-01-18 17:41 Dmitry Torokhov
2016-01-18 17:41 ` [PATCH 1/4] Input: rotary_encoder - mark PM methods as __maybe_unused Dmitry Torokhov
2016-01-18 17:41 ` [PATCH 2/4] Input: rotary_encoder - convert to use gpiod API Dmitry Torokhov
2016-01-18 17:41 ` [PATCH 3/4] Input: rotary_encoder - use input_set_capability() Dmitry Torokhov
2016-01-18 17:41 ` [PATCH 4/4] Input: rotary_encoder - move away from platform data structure Dmitry Torokhov
2016-01-23 18:01 ` Robert Jarzmik [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=87r3h8b2fz.fsf@belgarion.home \
--to=robert.jarzmik@free.fr \
--cc=daniel@zonque.org \
--cc=dmitry.torokhov@gmail.com \
--cc=haojian.zhuang@gmail.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-input@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=timo.teras@iki.fi \
/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
all inboxes | Powered by JetHome®