All of lore.kernel.org
 help / color / mirror / Atom feed
From: olof@lixom.net (Olof Johansson)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH 0/3] DT labels for connector device mapping
Date: Tue, 22 Dec 2015 11:25:55 -0800	[thread overview]
Message-ID: <20151222192555.GR30172@localhost> (raw)
In-Reply-To: <1449782473-20880-1-git-send-email-robh@kernel.org>

On Thu, Dec 10, 2015 at 03:21:10PM -0600, 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.
> 
> BTW, there are no platform maintainers listed for these files. Setting 
> them should be enforced for the dts files as DT maintainers mainly 
> review binding docs, not dts files.
> 
> Rob
> 
> Rob Herring (3):
>   arm64: dts: apq8016-sbc: enable UART0 on LS connector
>   arm64: dts: apq8016-sbc: add label properties for UART, I2C, and SPI
>   arm64: dts: hikey: add label properties to UARTs

Applied all 3 to next/dt64.


-Olof

WARNING: multiple messages have this Message-ID (diff)
From: Olof Johansson <olof-nZhT3qVonbNeoWH0uzbU5w@public.gmane.org>
To: Rob Herring <robh-DgEjT+Ai2ygdnm+yROfE0A@public.gmane.org>
Cc: Bintian Wang
	<bintian.wang-hv44wF8Li93QT0dZR+AlfA@public.gmane.org>,
	Andy Gross <agross-sgV2jX0FEOL9JmXXK+q4OQ@public.gmane.org>,
	arm-DgEjT+Ai2ygdnm+yROfE0A@public.gmane.org,
	devicetree-u79uwXL29TY76Z2rM5mHXA@public.gmane.org,
	linux-arm-kernel-IAPFreCvJWM7uuMidbF8XUB+6BGkLq7r@public.gmane.org,
	Grant Likely
	<grant.likely-QSEj5FYQhm4dnm+yROfE0A@public.gmane.org>,
	Srinivas Kandagatla
	<srinivas.kandagatla-QSEj5FYQhm4dnm+yROfE0A@public.gmane.org>,
	Jorge Ramirez-Ortiz
	<jorge.ramirez-ortiz-QSEj5FYQhm4dnm+yROfE0A@public.gmane.org>
Subject: Re: [PATCH 0/3] DT labels for connector device mapping
Date: Tue, 22 Dec 2015 11:25:55 -0800	[thread overview]
Message-ID: <20151222192555.GR30172@localhost> (raw)
In-Reply-To: <1449782473-20880-1-git-send-email-robh-DgEjT+Ai2ygdnm+yROfE0A@public.gmane.org>

On Thu, Dec 10, 2015 at 03:21:10PM -0600, 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.
> 
> BTW, there are no platform maintainers listed for these files. Setting 
> them should be enforced for the dts files as DT maintainers mainly 
> review binding docs, not dts files.
> 
> Rob
> 
> Rob Herring (3):
>   arm64: dts: apq8016-sbc: enable UART0 on LS connector
>   arm64: dts: apq8016-sbc: add label properties for UART, I2C, and SPI
>   arm64: dts: hikey: add label properties to UARTs

Applied all 3 to next/dt64.


-Olof

--
To unsubscribe from this list: send the line "unsubscribe devicetree" in
the body of a message to majordomo-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html

  parent reply	other threads:[~2015-12-22 19:25 UTC|newest]

Thread overview: 16+ 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 ` 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   ` 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-10 21:21   ` Rob Herring
2015-12-11 23:14   ` Kevin Hilman
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:21   ` Rob Herring
2015-12-10 21:36 ` [PATCH 0/3] DT labels for connector device mapping Jorge Ramirez-Ortiz
2015-12-10 21:36   ` Jorge Ramirez-Ortiz
2015-12-11  0:00   ` Rob Herring
2015-12-11  0:00     ` Rob Herring
2015-12-22 19:25 ` Olof Johansson [this message]
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=20151222192555.GR30172@localhost \
    --to=olof@lixom.net \
    --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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.