From: jorge.ramirez-ortiz@linaro.org (Jorge Ramirez-Ortiz)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH 0/3] DT labels for connector device mapping
Date: Thu, 10 Dec 2015 16:36:19 -0500 [thread overview]
Message-ID: <5669F053.4080509@linaro.org> (raw)
In-Reply-To: <1449782473-20880-1-git-send-email-robh@kernel.org>
On 12/10/2015 04:21 PM, Rob Herring wrote:
> Having a common connector interface across different platforms can be
> problematic for determining which SOC device is connected to which
> connector pins. The standard DT property "label" is intended to provide
> a human readable name for a device and can be used to provide this
> information. Then userspace can can read the label to determine the
> device mapping. For example:
>
> for f in $(ls -d /sys/class/tty/tty*); do
> label=$(cat $f/device/of_node/label)
> if [ "$label" = "LS-UART1" ]; then
> # you've found UART1, so do something with it.
> # $f/dev is the major:minor for the /dev node
> fi
> done
>
> This series adds labels on hikey and dragonboard 410c devices for the
> low speed and high speed connectors. Not tested at all.
should we then use the line-name property on the GPIOs to have a common naming
convention across all 96Boards boards?
next prev parent reply other threads:[~2015-12-10 21:36 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-12-10 21:21 [PATCH 0/3] DT labels for connector device mapping Rob Herring
2015-12-10 21:21 ` [PATCH 1/3] arm64: dts: apq8016-sbc: enable UART0 on LS connector Rob Herring
2015-12-10 21:21 ` [PATCH 2/3] arm64: dts: apq8016-sbc: add label properties for UART, I2C, and SPI Rob Herring
2015-12-11 23:14 ` Kevin Hilman
2015-12-10 21:21 ` [PATCH 3/3] arm64: dts: hikey: add label properties to UARTs Rob Herring
2015-12-10 21:36 ` Jorge Ramirez-Ortiz [this message]
2015-12-11 0:00 ` [PATCH 0/3] DT labels for connector device mapping Rob Herring
2015-12-22 19:25 ` Olof Johansson
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=5669F053.4080509@linaro.org \
--to=jorge.ramirez-ortiz@linaro.org \
--cc=linux-arm-kernel@lists.infradead.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).