linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: "H. Nikolaus Schaller" <hns@goldelico.com>
To: Andrey Utkin <andrey_utkin@fastmail.com>
Cc: linux-input@vger.kernel.org, devel@driverdev.osuosl.org,
	kernel-mentors@selenic.com, linux-kernel@vger.kernel.org,
	letux-kernel@openphoenux.org, kernel@pyra-handheld.com,
	Dmitry Torokhov <dmitry.torokhov@gmail.com>,
	Krzysztof Kozlowski <k.kozlowski@samsung.com>,
	Arnd Bergmann <arnd@arndb.de>, Mark Brown <broonie@kernel.org>,
	Daniel Hung-yu Wu <hywu@google.com>,
	Moritz Fischer <moritz.fischer@ettus.com>,
	Geert Uytterhoeven <geert@linux-m68k.org>,
	S Twiss <stwiss.opensource@diasemi.com>,
	Rob Herring <robh@kernel.org>,
	Grant Grundler <grundler@chromium.org>
Subject: Re: [Kernel] Mainlining of Pyra nub joystick driver
Date: Tue, 14 Jun 2016 19:09:50 +0200	[thread overview]
Message-ID: <DAA6B14A-062E-45E9-97DD-18D55480F0A8@goldelico.com> (raw)
In-Reply-To: <20160614170206.GE4820@zver>


> Am 14.06.2016 um 19:02 schrieb Andrey Utkin <andrey_utkin@fastmail.com>:
> 
> On Tue, Jun 14, 2016 at 02:45:23PM +0300, Andrey Utkin wrote:
>> There's a pair of "nub" devices on Pyra handheld PC
>> ...
> 
> Update: found drivers/input/joystick/as5011.c in mainline kernel,
> will look how it works with as5013 hardware.

Before you spend too much time on it, they have not much in
common except the manufacturer and the as501x designation.

Register models (data sheet) are very different.

BR,
Nikolaus

  reply	other threads:[~2016-06-14 17:10 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-06-14 11:45 Mainlining of Pyra nub joystick driver Andrey Utkin
2016-06-14 15:14 ` Arnd Bergmann
2016-06-14 17:02 ` [Kernel] " Andrey Utkin
2016-06-14 17:09   ` H. Nikolaus Schaller [this message]
2016-06-16 19:51     ` Andrey Utkin
2016-06-17 11:20       ` H. Nikolaus Schaller

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=DAA6B14A-062E-45E9-97DD-18D55480F0A8@goldelico.com \
    --to=hns@goldelico.com \
    --cc=andrey_utkin@fastmail.com \
    --cc=arnd@arndb.de \
    --cc=broonie@kernel.org \
    --cc=devel@driverdev.osuosl.org \
    --cc=dmitry.torokhov@gmail.com \
    --cc=geert@linux-m68k.org \
    --cc=grundler@chromium.org \
    --cc=hywu@google.com \
    --cc=k.kozlowski@samsung.com \
    --cc=kernel-mentors@selenic.com \
    --cc=kernel@pyra-handheld.com \
    --cc=letux-kernel@openphoenux.org \
    --cc=linux-input@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=moritz.fischer@ettus.com \
    --cc=robh@kernel.org \
    --cc=stwiss.opensource@diasemi.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).