From: Dmitry Torokhov <dmitry.torokhov@gmail.com>
To: Joshua Clayton <stillcompiling@gmail.com>
Cc: linux-input@vger.kernel.org
Subject: Re: Connecting input driver to underlying uart
Date: Fri, 17 Jul 2015 16:27:42 -0700 [thread overview]
Message-ID: <20150717232742.GH39282@dtor-ws> (raw)
In-Reply-To: <1466420.W6prjcqLLf@jclayton-pc>
On Fri, Jul 17, 2015 at 04:00:16PM -0700, Joshua Clayton wrote:
> On Wednesday, July 15, 2015 11:22:06 AM you wrote:
> > Hi list,
> > I'm starting work on an input driver.
> > the device is connected to an RS232 uart in my freescale imx6q arm system,
> > which has 2 serial ports, one of which is a console
> >
> > It is not anything like a ps2/at device.
> > How can I get it to take over the uart device? A devicetree entry?
> >
> > I do not understand serio probing, and don't understand if I should use serio
> > for a non ps2 compatible device.
> >
> > Any pointers would be helpful.
> >
> > The input device documentation is great if I can just figure out how to
> > connect it to my hardware.
> >
> >
> I went ahead and converted (parts of) the existing userspace driver.
> Clearly I am missing something. My driver is registered with serio, but serio is not associated with any devices.
> I turned on the SERIO_SERPORT...
> /sys/bus/serio/devices/ is empty.
> I would like it to bind my driver to /dev/ttymxc1 (uart 2 on this system), or its underlying uart.
You need to use inputattach utility to activate serport on the uart of
your choosing and tell it what type of serio port to create.
Thanks.
--
Dmitry
prev parent reply other threads:[~2015-07-17 23:27 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-07-15 18:22 Connecting input driver to underlying uart Joshua Clayton
2015-07-17 23:00 ` Joshua Clayton
2015-07-17 23:27 ` 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=20150717232742.GH39282@dtor-ws \
--to=dmitry.torokhov@gmail.com \
--cc=linux-input@vger.kernel.org \
--cc=stillcompiling@gmail.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