From: Stepan Moskovchenko <stepanm@codeaurora.org>
To: Grant Likely <grant.likely@secretlab.ca>
Cc: Rob Herring <robherring2@gmail.com>,
devicetree-discuss@lists.ozlabs.org,
David Brown <davidb@codeaurora.org>,
Daniel Walker <dwalker@fifo99.com>,
Bryan Huntsman <bryanh@codeaurora.org>,
Russell King <linux@arm.linux.org.uk>,
linux-arm-msm@vger.kernel.org,
linux-arm-kernel@lists.infradead.org,
linux-kernel@vger.kernel.org
Subject: Re: [RFC] dt/platform: Use cell-index for device naming if available
Date: Tue, 04 Dec 2012 18:34:59 -0800 [thread overview]
Message-ID: <50BEB2D3.7000101@codeaurora.org> (raw)
In-Reply-To: <20121120161957.7CE973E102F@localhost>
On 11/20/2012 8:19 AM, Grant Likely wrote:
> What if instead we added something like OF_ALIASES to the uevent
> attribute? Then userspace would have access to all the aliases for a
> device. Heck, even a shell script can parse the uevent attribute. There
> is also precedence for exporting OF data using a uevent. This is from
> the versatile device tree support:
>
> # cat /sys/devices/amba.0/uevent
> OF_NAME=amba
> OF_FULLNAME=/amba
> OF_COMPATIBLE_0=arm,amba-bus
> OF_COMPATIBLE_N=1
> MODALIAS=of:NambaT<NULL>Carm,amba-bus
This sounds like a good idea. I have just sent out a new patch to do
this. I followed the OF_COMPATIBLE uevent convention for listing the
aliases, but I can follow another convention if someone objects.
Steve
--
The Qualcomm Innovation Center, Inc. is a member of Code Aurora Forum,
hosted by The Linux Foundation
WARNING: multiple messages have this Message-ID (diff)
From: stepanm@codeaurora.org (Stepan Moskovchenko)
To: linux-arm-kernel@lists.infradead.org
Subject: [RFC] dt/platform: Use cell-index for device naming if available
Date: Tue, 04 Dec 2012 18:34:59 -0800 [thread overview]
Message-ID: <50BEB2D3.7000101@codeaurora.org> (raw)
In-Reply-To: <20121120161957.7CE973E102F@localhost>
On 11/20/2012 8:19 AM, Grant Likely wrote:
> What if instead we added something like OF_ALIASES to the uevent
> attribute? Then userspace would have access to all the aliases for a
> device. Heck, even a shell script can parse the uevent attribute. There
> is also precedence for exporting OF data using a uevent. This is from
> the versatile device tree support:
>
> # cat /sys/devices/amba.0/uevent
> OF_NAME=amba
> OF_FULLNAME=/amba
> OF_COMPATIBLE_0=arm,amba-bus
> OF_COMPATIBLE_N=1
> MODALIAS=of:NambaT<NULL>Carm,amba-bus
This sounds like a good idea. I have just sent out a new patch to do
this. I followed the OF_COMPATIBLE uevent convention for listing the
aliases, but I can follow another convention if someone objects.
Steve
--
The Qualcomm Innovation Center, Inc. is a member of Code Aurora Forum,
hosted by The Linux Foundation
next prev parent reply other threads:[~2012-12-05 2:35 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-11-10 0:48 [RFC] dt/platform: Use cell-index for device naming if available Stepan Moskovchenko
2012-11-10 0:48 ` Stepan Moskovchenko
2012-11-11 2:32 ` Rob Herring
2012-11-11 2:32 ` Rob Herring
2012-11-11 17:49 ` Grant Likely
2012-11-11 17:49 ` Grant Likely
2012-11-12 1:45 ` Stepan Moskovchenko
2012-11-12 1:45 ` Stepan Moskovchenko
2012-11-12 1:45 ` Stepan Moskovchenko
2012-11-13 2:48 ` Stepan Moskovchenko
2012-11-13 2:48 ` Stepan Moskovchenko
2012-11-15 16:10 ` Grant Likely
2012-11-15 16:10 ` Grant Likely
2012-11-15 16:10 ` Grant Likely
2012-11-16 2:46 ` Stepan Moskovchenko
2012-11-16 2:46 ` Stepan Moskovchenko
2012-11-17 3:29 ` Stepan Moskovchenko
2012-11-17 3:29 ` Stepan Moskovchenko
2012-11-20 16:19 ` Grant Likely
2012-11-20 16:19 ` Grant Likely
2012-12-05 2:34 ` Stepan Moskovchenko [this message]
2012-12-05 2:34 ` Stepan Moskovchenko
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=50BEB2D3.7000101@codeaurora.org \
--to=stepanm@codeaurora.org \
--cc=bryanh@codeaurora.org \
--cc=davidb@codeaurora.org \
--cc=devicetree-discuss@lists.ozlabs.org \
--cc=dwalker@fifo99.com \
--cc=grant.likely@secretlab.ca \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-arm-msm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux@arm.linux.org.uk \
--cc=robherring2@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 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.