- 15 Oct, 2019 1 commit
-
-
Benjamin Gaignard authored
Convert the STM32 display binding to DT schema format using json-schema. Split the original bindings in two yaml files: - one for display controller (ltdc) - one for DSI controller Signed-off-by:
Benjamin Gaignard <benjamin.gaignard@st.com> [robh: drop maxItems from phy-dsi-supply] Signed-off-by:
Rob Herring <robh@kernel.org>
-
- 14 Oct, 2019 6 commits
-
-
Benjamin Gaignard authored
Convert the STM32 timer binding to DT schema format using json-schema Signed-off-by:
-
Benjamin Gaignard authored
Convert the STM32 thermal binding to DT schema format using json-schema Signed-off-by:
-
Benjamin Gaignard authored
Convert the STM32 dcmi binding to DT schema format using json-schema Signed-off-by:
-
Benjamin Gaignard authored
Convert the STM32 cec binding to DT schema format using json-schema Signed-off-by:
-
Benjamin Gaignard authored
Convert the STM32 hwspinlock binding to DT schema format using json-schema Signed-off-by:
-
Rob Herring authored
Regulator '*-supply' properties are always a single phandle, so 'maxItems: 1' or a $ref is not necessary. All that's needed is either 'true' or an optional 'description'. Following this clean-up, the meta-schema will enforce this pattern. There's one case in tree with 'innolux,n156bge-l21' having 2 phandles. This appears to be a mistake or abuse of simple-panel as it's 2 different voltage rails connected to 'power-supply'. Cc: Neil Armstrong <narmstrong@baylibre.com> Cc: Kevin Hilman <khilman@baylibre.com> Cc: Jonathan Cameron <jic23@kernel.org> Cc: Krzysztof Kozlowski <krzk@kernel.org> Cc: Kishon Vijay Abraham I <kishon@ti.com> Cc: Liam Girdwood <lgirdwood@gmail.com> Cc: Mark Brown <broonie@kernel.org> Cc: linux-iio@vger.kernel.org Acked-by: Jonathan Cameron <Jonathan.Cameron@huawei.com> # for iio Signed-off-by:
-
- 11 Oct, 2019 4 commits
-
-
Rob Herring authored
DT bindings are moving to using a json-schema based schema format instead of freeform text. Add a checkpatch.pl check to encourage using the schema for new bindings. It's not yet a requirement, but is progressively being required by some maintainers. Cc: Andy Whitcroft <apw@canonical.com> Cc: Joe Perches <joe@perches.com> Signed-off-by: -
Rob Herring authored
Fix the errors in the RiscV CPU DT schema: Documentation/devicetree/bindings/riscv/cpus.example.dt.yaml: cpu@0: 'timebase-frequency' is a required property Documentation/devicetree/bindings/riscv/cpus.example.dt.yaml: cpu@1: 'timebase-frequency' is a required property Documentation/devicetree/bindings/riscv/cpus.example.dt.yaml: cpu@0: compatible:0: 'riscv' is not one of ['sifive,rocket0', 'sifive,e5', 'sifive,e51', 'sifive,u54-mc', 'sifive,u54', 'sifive,u5'] Documentation/devicetree/bindings/riscv/cpus.example.dt.yaml: cpu@0: compatible: ['riscv'] is too short Documentation/devicetree/bindings/riscv/cpus.example.dt.yaml: cpu@0: 'timebase-frequency' is a required property The DT spec allows for 'timebase-frequency' to be in 'cpu' or 'cpus' node and RiscV requires it in /cpus node, so make it disallowed in cpu nodes. Fixes: 4fd669a8 ("dt-bindings: riscv: convert cpu binding to json-schema") Cc: Palmer Dabbelt <palmer@sifive.com> Cc: Albert Ou <aou@eecs.berkeley.edu> Cc: linux-riscv@lists.infradead.org Acked-by:
Paul Walmsley <paul.walmsley@sifive.com> Signed-off-by:
-
Martin Kaiser authored
Move the native-mode setting inside the display-timing node. Outside of display-timing, it is ignored. Signed-off-by:
Martin Kaiser <martin@kaiser.cx> Signed-off-by:
-
Martin Kaiser authored
Move the native-mode setting inside the display-timing node. Outside of display-timing, it is ignored. Signed-off-by:
-
- 10 Oct, 2019 5 commits
-
-
Maciej Falkowski authored
Document clocks macros with their description from 'Documentation/devicetree/bindings/sound/samsung-i2s.txt' Signed-off-by:
Maciej Falkowski <m.falkowski@samsung.com> Signed-off-by:
Marek Szyprowski <m.szyprowski@samsung.com> Reviewed-by:
Krzysztof Kozlowski <krzk@kernel.org> Signed-off-by:
-
Simon Horman authored
Convert Real Time Clock for Renesas SH and ARM SoCs bindings documentation to json-schema. Also name bindings documentation file according to the compat string being documented. Also correct syntax error in interrupts field in example. Signed-off-by:
Simon Horman <horms+renesas@verge.net.au> Reviewed-by:
Ulrich Hecht <uli+renesas@fpond.eu> Acked-by:
Alexandre Belloni <alexandre.belloni@bootlin.com> Signed-off-by:
-
Krzysztof Kozlowski authored
Convert Samsung Exynos Security SubSystem (SSS) and SlimSSS hardware crypto accelerator bindings to DT schema format using json-schema. Signed-off-by:
-
Krzysztof Kozlowski authored
Convert Samsung Exynos SROM controller bindings to DT schema format using json-schema. Signed-off-by:
-
Krzysztof Kozlowski authored
Convert Samsung Exynos Pseudo Random Number Generator bindings to DT schema format using json-schema. Signed-off-by:
-
- 09 Oct, 2019 3 commits
-
-
Bartosz Golaszewski authored
arch/arm/boot/dts/at91-dvk_som60.dt.yaml uses the compatible string 'giantec,gt24c32a' for an at24 EEPROM with a fallback to 'atmel,24c32'. Add this model as a special case to the binding document. Reported-by:
Bartosz Golaszewski <bgolaszewski@baylibre.com> Signed-off-by:
-
Bartosz Golaszewski authored
Convert the binding document for at24 EEPROMs from txt to yaml. The compatible property uses a regex pattern to address all the possible combinations of "vendor,model" strings. Signed-off-by:
-
Robin Murphy authored
Since the "dma-ranges" property is only valid for a node representing a bus, of_dma_get_range() currently assumes the node passed in is a leaf representing a device, and starts the walk from its parent. In cases like PCI host controllers on typical FDT systems, however, where the PCI endpoints are probed dynamically the initial leaf node represents the 'bus' itself, and this logic means we fail to consider any "dma-ranges" describing the host bridge itself. Rework the logic such that of_dma_get_range() also works correctly starting from a bus node containing "dma-ranges". While this does mean "dma-ranges" could incorrectly be in a device leaf node, there isn't really any way in this function to ensure that a leaf node is or isn't a bus node. Signed-off-by:
Robin Murphy <robin.murphy@arm.com> [robh: Allow for the bus child node to still be passed in] Signed-off-by:
Nicolas Saenz Julienne <nsaenzjulienne@suse.de> Tested-by:
-
- 08 Oct, 2019 9 commits
-
-
Rob Herring authored
of_pci_range_parser_one() has a bug when parsing dma-ranges. When it translates the parent address (aka cpu address in the code), 'ranges' is always being used. This happens to work because most users are just 1:1 translation. Cc: Robin Murphy <robin.murphy@arm.com> Tested-by:
-
Rob Herring authored
'dma-ranges' frequently exists without parent nodes having 'dma-ranges'. While this is an error for 'ranges', this is fine because DMA capable devices always have a translatable DMA address. Also, with no 'dma-ranges' at all, the assumption is that DMA addresses are 1:1 with no restrictions unless perhaps the device itself has implicit restrictions. Cc: Robin Murphy <robin.murphy@arm.com> Tested-by:
-
Rob Herring authored
The functions for parsing 'dma-ranges' ranges are buggy and fail to handle several conditions. Add new tests for of_dma_get_range() and for_each_of_pci_range(). With this test, we get 5 new failures which are fixed in subsequent commits: OF: translation of DMA address(0) to CPU address failed node(/testcase-data/address-tests/device@70000000) FAIL of_unittest_dma_ranges_one():798 of_dma_get_range failed on node /testcase-data/address-tests/device@70000000 rc=-22 OF: translation of DMA address(10000000) to CPU address failed node(/testcase-data/address-tests/bus@80000000/device@1000) FAIL of_unittest_dma_ranges_one():798 of_dma_get_range failed on node /testcase-data/address-tests/bus@80000000/device@1000 rc=-22 OF: translation of DMA address(0) to CPU address failed node(/testcase-data/address-tests/pci@90000000) FAIL of_unittest_dma_ranges_one():798 of_dma_get_range failed on node /testcase-data/address-tests/pci@90000000 rc=-22 FAIL of_unittest_pci_dma_ranges():851 for_each_of_pci_range wrong CPU addr (d0000000) on node /testcase-data/address-tests/pci@90000000 FAIL of_unittest_pci_dma_ranges():861 for_each_of_pci_range wrong CPU addr (ffffffffffffffff) on node /testcase-data/address-tests/pci@90000000 Cc: Robin Murphy <robin.murphy@arm.com> Tested-by:
-
Robin Murphy authored
In some cases such as PCI host controllers, we may have a "parent bus" which is an OF leaf node, but still need to correctly parse ranges from the point of view of that bus. For that, factor out variants of the "#addr-cells" and "#size-cells" parsers which do not assume they have a device node and thus immediately traverse upwards before reading the relevant property. Signed-off-by:
Geert Uytterhoeven <geert+renesas@glider.be> Tested-by:
-
Robin Murphy authored
Much like for address translation, when checking for DMA coherence we should be sure to walk up the DMA hierarchy, rather than the MMIO one, now that we can accommodate them being different. Signed-off-by:
-
Robin Murphy authored
Add of_get_next_dma_parent() helper which is similar to __of_get_dma_parent(), but can be used in iterators and decrements the ref count on the prior parent. Signed-off-by:
-
Robin Murphy authored
If we failed to translate a DMA address, at least show the offending address rather than the uninitialised contents of the destination argument. Signed-off-by:
Christoph Hellwig <hch@lst.de> Signed-off-by:
-
Rob Herring authored
of_dma_get_range() is only used within the DT core code, so remove the export and move the header declaration to the private header. Cc: Robin Murphy <robin.murphy@arm.com> Reviewed-by:
-
Rob Herring authored
of_find_matching_node_by_address() is unused, so remove it. Cc: Robin Murphy <robin.murphy@arm.com> Reviewed-by:
-
- 07 Oct, 2019 1 commit
-
-
Rob Herring authored
-
- 04 Oct, 2019 5 commits
-
-
Krzysztof Kozlowski authored
Include generic watchdog DT schema bindings in Amlogic GXBB Watchdog bindings. Signed-off-by:
-
Krzysztof Kozlowski authored
The Samsung SoC watchdog driver always required providing a clock (either through platform data or from DT). However when bindings were added in commit 9487a9cc ("watchdog: s3c2410: Add support for device tree based probe"), they missed the requirement of clock. Signed-off-by:
-
Krzysztof Kozlowski authored
Convert Samsung S3C/S5P/Exynos watchdog bindings to DT schema format using json-schema. Signed-off-by:
-
Yoshihiro Kaneko authored
Convert Renesas R-Car Timer Pulse Unit PWM Controller bindings documentation to json-schema. Signed-off-by:
Yoshihiro Kaneko <ykaneko0929@gmail.com> Reviewed-by:
-
Yoshihiro Kaneko authored
Convert Renesas R-Car PWM Timer Controller bindings documentation to json-schema. Signed-off-by:
-
- 02 Oct, 2019 5 commits
-
-
Maxime Ripard authored
The binding has a typo where resets-names should read reset-names, which in turn leads to a warning when the example is validated, since reset-names is being used, and the binding prevent the usage of any property that isn't described. Fixes: 088e88be ("dt-bindings: phy: add binding for the Lantiq VRX200 and ARX300 PCIe PHYs") Signed-off-by:
Maxime Ripard <mripard@kernel.org> Signed-off-by:
-
Maxime Ripard authored
The example contains an SPI bus and device, but doesn't have the appropriate size and address cells size. This creates a DTC warning when the example is compiled since the default ones will not match what the device uses. Let's add them to remove that warning. Fixes: f7356e47 ("dt-bindings: iio: adc: ad7192: Add binding documentation for AD7192") Signed-off-by:
-
Maxime Ripard authored
The AD7192 binding describes two regulator properties, avdd-supply and dvdd-supply, but describes it as a constant string that must be avdd and dvdd. This is wrong since a *-supply property is actually a phandle, and results in warnings when the example is validated (or any device tree using that device, for that matter). Let's remove that requirement. Fixes: f7356e47 ("dt-bindings: iio: adc: ad7192: Add binding documentation for AD7192") Signed-off-by:
-
Maxime Ripard authored
The linux,rc-map-name property is described using an enum, yet a value has been put in that enum twice, resulting in a warning. Let's fix that. Fixes: 7c31b9d6 ("media: dt-bindings: media: Add YAML schemas for the generic RC bindings") Signed-off-by:
-
Maxime Ripard authored
The fsl,dsp binding requires a memory-region, yet its example doesn't have one which results in a warning. Let's add a memory-region phandle to the example. Fixes: 7db2f2df ("dt-bindings: dsp: fsl: Add DSP core binding support") Signed-off-by:
Daniel Baluta <daniel.baluta@nxp.com> Signed-off-by:
-
- 01 Oct, 2019 1 commit
-
-
Maciej Falkowski authored
Convert Samsung 2D Graphics Accelerator to newer dt-schema format Signed-off-by:
-
