in section 2.2.2 of devicetree spec v0.2, there is a moderately
lengthy list of recommended (but not mandatory) node names, but i
notice the use of a few other node names that might warrant inclusion
in that list. first, there is a *single* use of the node name
"nor-flash" here:
arm64/boot/dts/hisilicon/hip05-d02.dts: nor-flash@0,0 {
but a single usage doesn't really warrant official approval.
next, there is usage of both "spiflash" and "spi-flash", but
"spi-flash" is clearly the dominant form (searching under arch/):
$ grep -r spi-flash@ * | wc -l
38
$ grep -r spiflash@ * | wc -l
1
so is "spi-flash" a recommended node name to be added to that list?
(neither of them is in the list at present.)
a few other node names i noticed in my travels, none of which are in
that list:
video@...
qos@...
vram@...
gadget@...
video-scaler@...
also, while the approved list contains "usb-phy", there is a fair
bit of just "ubsphy" -- is that equally acceptable?
the list also contains "usb-hub", of which there is all of one
example:
arm/boot/dts/exynos5410-odroidxu.dts: usb3503: usb-hub@8 {
finally, i notice a few instances of the node name "mtd_dataflash"
under arm/boot/dts (using an underscore instead of the ubiquitous
hyphen):
at91rm9200ek.dts: mtd_dataflash@0 {
at91sam9260ek.dts: mtd_dataflash@0 {
at91sam9261ek.dts: mtd_dataflash@0 {
at91sam9263ek.dts: mtd_dataflash@0 {
at91sam9g20ek_common.dtsi: mtd_dataflash@0 {
at91sam9m10g45ek.dts: mtd_dataflash@0 {
at91sam9rlek.dts: mtd_dataflash@0 {
usb_a9263.dts: mtd_dataflash@0 {
i'm sure there's more, just curious if any of this merits updating
section 2.2.2 of the spec.
rday
--
========================================================================
Robert P. J. Day Ottawa, Ontario, CANADA
http://crashcourse.ca/dokuwiki
Twitter: http://twitter.com/rpjday
LinkedIn: http://ca.linkedin.com/in/rpjday
========================================================================
--
To unsubscribe from this list: send the line "unsubscribe devicetree-spec" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
