summaryrefslogtreecommitdiffstats
path: root/Documentation/devicetree/bindings/ufs/mediatek,ufs.yaml
diff options
context:
space:
mode:
authorSean Anderson <sean.anderson@seco.com>2022-03-03 23:35:42 +0100
committerThierry Reding <thierry.reding@gmail.com>2022-04-22 18:21:10 +0200
commitf643490e1bf941600f6105e4d27c49054fb6d562 (patch)
tree9df1ad98bdc36adecd31e2de8553a13eb61c55b8 /Documentation/devicetree/bindings/ufs/mediatek,ufs.yaml
parentpwm: atmel-tcb: Drop duplicated tracking of per-channel data (diff)
downloadlinux-f643490e1bf941600f6105e4d27c49054fb6d562.tar.xz
linux-f643490e1bf941600f6105e4d27c49054fb6d562.zip
dt-bindings: pwm: Add Xilinx AXI Timer
This adds a binding for the Xilinx LogiCORE IP AXI Timer. This device is a "soft" block, so it has some parameters which would not be configurable in most hardware. This binding is usually automatically generated by Xilinx's tools, so the names and values of some properties should be kept as they are, if possible. In addition, this binding is already in the kernel at arch/microblaze/boot/dts/system.dts, and in user software such as QEMU. The existing driver uses the clock-frequency property, or alternatively the /cpus/timebase-frequency property as its frequency input. Because these properties are deprecated, they have not been included with this schema. All new bindings should use the clocks/clock-names properties to specify the parent clock. Because we need to init timer devices so early in boot, we determine if we should use the PWM driver or the clocksource/clockevent driver by the presence/absence, respectively, of #pwm-cells. Because both counters are used by the PWM, there is no need for a separate property specifying which counters are to be used for the PWM. Signed-off-by: Sean Anderson <sean.anderson@seco.com> Reviewed-by: Rob Herring <robh@kernel.org> Signed-off-by: Thierry Reding <thierry.reding@gmail.com>
Diffstat (limited to 'Documentation/devicetree/bindings/ufs/mediatek,ufs.yaml')
0 files changed, 0 insertions, 0 deletions