- 09 Oct, 2019 2 commits
-
-
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:
Bartosz Golaszewski <bgolaszewski@baylibre.com> [robh: rework compatible schema, fix missing allOf for $ref, fix errors in example] Signed-off-by:
Rob Herring <robh@kernel.org> [Bartosz: added comments explaining the compatible property] 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 <krzk@kernel.org> Acked-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:
Simon Horman <horms+renesas@verge.net.au> Signed-off-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 18 commits
-
-
Maciej Falkowski authored
Convert Samsung 2D Graphics Accelerator to newer dt-schema format Signed-off-by:
Maciej Falkowski <m.falkowski@samsung.com> Reviewed-by:
-
Maciej Falkowski authored
Convert Samsung Image Scaler to newer dt-schema format. Signed-off-by:
Marek Szyprowski <m.szyprowski@samsung.com> Reviewed-by:
-
Simon Horman authored
Convert Renesas Bus State Controller (BSC) bindings documentation to json-schema. Signed-off-by:
-
Simon Horman authored
Convert Simple Power-Managed Bus bindings documentation to json-schema. As a side effect of this change only simple-pm-bus is used in example. A follow-up patch will provide an example for the separately documented Renesas Bus State Controller (BSC) that uses "renesas,bsc-sh73a0" and "renesas,bsc" compat strings. Signed-off-by:
-
Krzysztof Kozlowski authored
Make the examples in Exynos Multi Core Timer bindings more readable and bring them closer to real DTS by using defines for interrupt flags. Fix also GIC interrupt type in example for Exynos4412 (from SPI to PPI). Suggested-by:
-
Krzysztof Kozlowski authored
Convert Samsung Exynos Soc Multi Core Timer bindings to DT schema format using json-schema. Signed-off-by:
-
Christoph Hellwig authored
If of_setup_earlycon we should keep on iterating earlycon options instead of breaking out of the loop. Signed-off-by:
-
Krzysztof Kozlowski authored
Convert Samsung Exynos Power Management Unit (PMU) bindings to DT schema format using json-schema. Signed-off-by:
-
Krzysztof Kozlowski authored
Convert Samsung Exynos System Registers (SYSREG) bindings to DT schema format using json-schema. Signed-off-by:
-
Yoshihiro Kaneko authored
Convert Renesas Interrupt Controller bindings documentation to json-schema. Signed-off-by:
-
Maciej Falkowski authored
Convert Samsung Exynos IOMMU H/W, System Memory Management Unit to newer dt-schema format. Signed-off-by:
Andrzej Hajda <a.hajda@samsung.com> Signed-off-by:
-
Krzysztof Kozlowski authored
Commit fafb37cf ("iio: exyno-adc: use syscon for PMU register access") changed the Exynos ADC driver so the PMU syscon phandle is required instead of second register address space. The bindings were not updated so fix them now. Signed-off-by:
Jonathan Cameron <Jonathan.Cameron@huawei.com> Signed-off-by:
-
Krzysztof Kozlowski authored
Convert Samsung Exynos Analog to Digital Converter bindings to DT schema format using json-schema. This is a direct conversion of existing bindings so it also copies the existing error in the bindings regarding the requirement of two register address ranges for certain compatibles. The inconsistency in binding was caused by commit fafb37cf ("iio: exyno-adc: use syscon for PMU register access"). Signed-off-by:
-
Krzysztof Kozlowski authored
Convert Samsung S3C/Exynos Real Time Clock bindings to DT schema format using json-schema. Signed-off-by:
-
Krzysztof Kozlowski authored
Convert Samsung Exynos Chipid bindings to DT schema format using json-schema. Signed-off-by:
-
Krzysztof Kozlowski authored
Add missing documentation of ARMv8 Samsung Exynos7 SoC based boards bindings. Signed-off-by:
-
Krzysztof Kozlowski authored
Add missing documentation of Samsung S5Pv210 SoC based boards bindings. Signed-off-by:
-
Krzysztof Kozlowski authored
Convert Samsung S5P and Exynos SoC bindings to DT schema format using json-schema. This is purely conversion of already documented bindings so it does not cover all of DTS in the Linux kernel (few S5P/Exynos and all S3C are missing). Signed-off-by:
-
