mailarchive of the ptxdist mailing list
 help / color / mirror / Atom feed
From: Juergen Borleis <jbe@pengutronix.de>
To: oselas@community.pengutronix.de
Cc: ptxdist@pengutronix.de, "Alejandro Vázquez" <vazlup@gmail.com>
Subject: Re: [ptxdist] Create alias for device event
Date: Fri, 26 Feb 2016 10:26:55 +0100	[thread overview]
Message-ID: <201602261026.56012.jbe@pengutronix.de> (raw)
In-Reply-To: <CAEt18EW_qgvRDY3=9LZCA8kmQgYHr=EbcxLXAd6TW798e_QeUw@mail.gmail.com>

Hi Alejandro,

On Thursday 25 February 2016 22:31:00 Alejandro Vázquez wrote:
> In my /dev/input I have some device (touchscreen, gpios, etc) and I want to
> know if it's posible create a alias for a device event automatically with
> ptxdist to identify devices faster. Also I have the problem that if I add a
> new device, it  change the order of device event.
> This has taken up an issue with tslib for the order change.

Its more a OSELAS-Community related question than PTXdist specific. So I
forward it.

Take a look into the Mini2440 BSP which has the same issue:

$ cat configs/platform-friendlyarm-mini2440/projectroot/lib/udev/rules.d/10-mini2440.rules
#
# some Mini2440 related settings, due to the kernel enumerates them differently from time to time
#
SUBSYSTEMS=="input", KERNEL=="event[0-9]*", KERNELS=="input[0-9]*", ATTRS{name}=="gpio-keys", SYMLINK+="input/buttons"
SUBSYSTEMS=="input", KERNEL=="event[0-9]*", KERNELS=="input[0-9]*", ATTRS{name}=="S3C24XX TouchScreen", SYMLINK+="input/touchscreen"
SUBSYSTEMS=="input", KERNEL=="event[0-9]*", KERNELS=="input[0-9]*", ATTRS{name}=="pwm-beeper", SYMLINK+="input/beeper"

You must do it in this way, due to the kernel brings up the drivers
concurrently. So there is no guarantee of the device order even
if you do not add new devices!

Regards,
Juergen

-- 
Pengutronix e.K.                              | Juergen Borleis             |
Industrial Linux Solutions                    | http://www.pengutronix.de/  |

_______________________________________________
ptxdist mailing list
ptxdist@pengutronix.de

      reply	other threads:[~2016-02-26  9:26 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-02-25 21:31 Alejandro Vázquez
2016-02-26  9:26 ` Juergen Borleis [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=201602261026.56012.jbe@pengutronix.de \
    --to=jbe@pengutronix.de \
    --cc=oselas@community.pengutronix.de \
    --cc=ptxdist@pengutronix.de \
    --cc=vazlup@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