OrgZephyr/zephyr
OrgZephyr
/
zephyr
mirror of https://github.com/zephyrproject-rtos/zephyr.git
1
0
Fork 0
Code Issues Releases Wiki Activity
zephyr/dts/bindings/usb/usb-controller.yaml

32 lines
799 B
YAML
Raw Normal View History

dts: bindings: Add yaml files for STM32 USB support to DT Add yaml files to DT for initial support of STM32 USB Origin: original Signed-off-by: Yannis Damigos <giannis.damigos@gmail.com>
2017-10-15 23:09:49 +08:00
# Copyright (c) 2018, I-SENSE group of ICCS
# SPDX-License-Identifier: Apache-2.0
yaml: Remove redundant document separators YAML document separators are needed e.g. when doing $ cat doc1.yaml doc2.yaml | <parser> For the bindings, we never parse concatenated documents. Assume we don't for any other .yaml files either. Having document separators in e.g. base.yaml makes !include a bit confusing, since the !included files are merged and not separate documents (the merging is done in Python code though, so it makes no difference for behavior). The replacement was done with $ git ls-files '*.yaml' | \ xargs sed -i -e '${/\s*\.\.\.\s*/d;}' -e 's/^\s*---\s*$//' First pattern removes ... at the end of files, second pattern clears a line with a lone --- on it. Some redundant blank lines at the end of files were cleared with $ git ls-files '*.yaml' | xargs sed -i '${/^\s*$/d}' This is more about making sure people can understand why every part of a binding is there than about removing some text. Signed-off-by: Ulf Magnusson <Ulf.Magnusson@nordicsemi.no>
2019-06-19 06:03:49 +08:00
dts: bindings: Rename usb.yaml to usb-controller.yaml Renaming bindings to consistently be called foo-controller.yaml for controllers and foo-device.yaml for devices (last one mostly makes sense for devices on buses and the like). I was thinking of having a plain foo.yaml be the controller as well, but !include interrupt.yaml reads much worse than !include interrupt-controller.yaml Another advantage of this approach is that no binding changes meaning (which could be risky). It's just adding suffixes to filenames. Signed-off-by: Ulf Magnusson <Ulf.Magnusson@nordicsemi.no>
2019-08-16 16:19:21 +08:00
# Common fields for USB controllers
dts: bindings: Add yaml files for STM32 USB support to DT Add yaml files to DT for initial support of STM32 USB Origin: original Signed-off-by: Yannis Damigos <giannis.damigos@gmail.com>
2017-10-15 23:09:49 +08:00
dts/bindings: Convert bindings to new include syntax Convert from: inherits: !include spi-device.yaml to: include: spi-device.yaml Signed-off-by: Kumar Gala <kumar.gala@linaro.org>
2019-08-22 07:10:12 +08:00
include: base.yaml
dts: bindings: Add yaml files for STM32 USB support to DT Add yaml files to DT for initial support of STM32 USB Origin: original Signed-off-by: Yannis Damigos <giannis.damigos@gmail.com>
2017-10-15 23:09:49 +08:00
usb: cdc_acm: allow to configure CDC ACM UART device from devicetree Add hidden Kconfig option to Kconfig.cdc and allow to configure CDC ACM UART device from devicetree. Signed-off-by: Johann Fischer <johann.fischer@nordicsemi.no>
2021-07-20 18:28:03 +08:00
bus: usb
dts/bindings: Move common properties into a base.yaml Move common properties like 'compatible', 'reg', 'reg-names', 'interrupts', 'interrupt-names', and 'label' into one common base.yaml that all the other yaml's can inherit from. This removes both duplication and inconsistent definition. The device specific yamls just need to say if a property is 'required' or not. NOTE: due to some generation conflicts we did not covert 'soc-nv-flash.yaml' to use base.yaml. Signed-off-by: Kumar Gala <kumar.gala@linaro.org>
2019-06-08 00:12:49 +08:00
properties:
dts: bindings: usb: Add maximum-speed property Add maximum-speed property to usb node. It configures USB controllers to work up to a specific speed. Valid arguments are "super-speed", "high-speed", "full-speed" and "low-speed". Signed-off-by: Yannis Damigos <giannis.damigos@gmail.com>
2018-07-20 01:25:56 +08:00
maximum-speed:
type: string
dts: bindings: Have 'required: true/false' instead of 'category: ...' The 'category: required/optional' setting for properties is just a yes/no thing. Using a boolean makes it clearer, so have 'required: true/false' instead. Print a clear error when 'category:' is used: edtlib.EDTError: please put 'required: true' instead of 'category: required' in 'properties: foo: ...' in test-bindings/sub-node-parent.yaml - 'category' has been removed The old scripts in scripts/dts/ ignore this setting, and only print a warning if 'category: required' in an inherited binding is changed to 'category: optional'. Remove that code, since the new scripts already have the same check. The replacement was done with git ls-files 'dts/bindings/*.yaml' | xargs sed -i \ -e 's/category:\s*required/required: true/' \ -e 's/category:\s*optional/required: false/' dts/binding-template.yaml is updated as well. Signed-off-by: Ulf Magnusson <Ulf.Magnusson@nordicsemi.no>
2019-08-28 06:22:01 +08:00
required: false
dts: bindings: usb: Add maximum-speed property Add maximum-speed property to usb node. It configures USB controllers to work up to a specific speed. Valid arguments are "super-speed", "high-speed", "full-speed" and "low-speed". Signed-off-by: Yannis Damigos <giannis.damigos@gmail.com>
2018-07-20 01:25:56 +08:00
description: Configures USB controllers to work up to a specific
speed. Valid arguments are "super-speed", "high-speed",
"full-speed" and "low-speed". If this is not passed
via DT, USB controllers should use their maximum
hardware capability.
dts: bindings: usb: Add enum to maximum-speed property Add enum to list what values of maximum-speed are exceptable since enum's get represented as strings in DT. This also allows us to generate a code enum to correspond to the string. We also introduce include/dt-bindings/usb/usb.h which is a hand coded definition of the enum. We don't have a great way to generate this right now, however it would be better if we did. Signed-off-by: Kumar Gala <kumar.gala@linaro.org>
2019-05-14 19:53:45 +08:00
enum:
- "low-speed"
- "full-speed"
- "high-speed"
- "super-speed"
dts: bindings: usb: Add maximum-speed property Add maximum-speed property to usb node. It configures USB controllers to work up to a specific speed. Valid arguments are "super-speed", "high-speed", "full-speed" and "low-speed". Signed-off-by: Yannis Damigos <giannis.damigos@gmail.com>
2018-07-20 01:25:56 +08:00
dts: bindings: Add yaml files for STM32 USB support to DT Add yaml files to DT for initial support of STM32 USB Origin: original Signed-off-by: Yannis Damigos <giannis.damigos@gmail.com>
2017-10-15 23:09:49 +08:00
label:
dts: bindings: Have 'required: true/false' instead of 'category: ...' The 'category: required/optional' setting for properties is just a yes/no thing. Using a boolean makes it clearer, so have 'required: true/false' instead. Print a clear error when 'category:' is used: edtlib.EDTError: please put 'required: true' instead of 'category: required' in 'properties: foo: ...' in test-bindings/sub-node-parent.yaml - 'category' has been removed The old scripts in scripts/dts/ ignore this setting, and only print a warning if 'category: required' in an inherited binding is changed to 'category: optional'. Remove that code, since the new scripts already have the same check. The replacement was done with git ls-files 'dts/bindings/*.yaml' | xargs sed -i \ -e 's/category:\s*required/required: true/' \ -e 's/category:\s*optional/required: false/' dts/binding-template.yaml is updated as well. Signed-off-by: Ulf Magnusson <Ulf.Magnusson@nordicsemi.no>
2019-08-28 06:22:01 +08:00
required: true
usb: convert VBUS control to new GPIO API Use DT for VBUS control and convert it to new GPIO API. Signed-off-by: Johann Fischer <j.fischer@phytec.de>
2020-01-23 00:35:22 +08:00
vbus-gpios:
type: phandle-array
required: false
description: Control VBUS via GPIO pin.