On Mon, 22 May 2017 16:55:15 +0200 Andrew Lunn <andrew@xxxxxxx> wrote: > On Sun, May 21, 2017 at 02:48:55PM +0200, Ralph Sennhauser wrote: > > Now that we use the reference for the USB3.0 port update the node > > name and labels for the phy and vbus to match the label used by > > armada-38x.dtsi. > > > > Signed-off-by: Ralph Sennhauser <ralph.sennhauser@xxxxxxxxx> > > > > --- > > > > Notes: > > > > Going by documentation regulator-name is only of informative > > nature so changing it should be a non issue. > > Does the regulator name appear in /sys somewhere? To differentiate between node-name and regulator-name property I changed the regulator name to usb3_1-vbus-regulator-name # find /sys -name *usb3_1-vbus* /sys/kernel/debug/regulator/usb3_1-vbus-regulator-name /sys/devices/platform/usb3_1-vbus /sys/firmware/devicetree/base/soc/internal-regs/pinctrl@18000/usb3_1-vbus-pins /sys/firmware/devicetree/base/usb3_1-vbus /sys/bus/platform/devices/usb3_1-vbus /sys/bus/platform/drivers/reg-fixed-voltage/usb3_1-vbus So yes, however, only under /sys/kernel/debug and more importantly not under /sys/class which would be covered by Documentation/ABI/testing/sysfs-class-regulator. How the description is worded in regulator.txt [1] under optional properties, "regulator-name: A string used as a descriptive name for regulator outputs" doesn't give the impression its considered part of the ABI implicitly either, well, as you know this might just be my lack of English skill. As I was uncertain and still am not under the impression this to be an issue I decided to change it and leave a note so it doesn't make it in unnoticed and can be discussed / clarified. Changing the node name has a similar impact but the same can be said for gpio_keys vs gpio-keys which got your Reviewed-by already. The new name would better match some recent dts additions beside being the more obvious choice with the related changes. [1] Documentation/devicetree/bindings/regulator/regulator.txt Ralph -- To unsubscribe from this list: send the line "unsubscribe devicetree" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html