- 11 May, 2020 12 commits
-
-
Samuel Holland authored
This arch_timer property was added in commit c950ca8c ("clocksource/drivers/arch_timer: Workaround for Allwinner A64 timer instability") but I omitted the device tree binding documentation. Now `make dtbs_check` prints the following warning for all A64 boards: timer: 'allwinner,erratum-unknown1' does not match any of the regexes: 'pinctrl-[0-9]+' Resolve this by documenting the erratum property. Signed-off-by:
Samuel Holland <samuel@sholland.org> Signed-off-by:
Rob Herring <robh@kernel.org>
-
Johan Jonker authored
A test with the command below gives this error: arch/arm64/boot/dts/rockchip/px30-evb.dt.yaml: usb@ff300000: 'power-domains' does not match any of the regexes: 'pinctrl-[0-9]+' With the conversion to yaml it also filters things in a node that are used by other drivers like 'power-domains' for Rockchip px30 usb nodes, so add them to 'dwc2.yaml'. make ARCH=arm64 dtbs_check DT_SCHEMA_FILES=Documentation/devicetree/bindings/usb/dwc2.yaml Signed-off-by:
Johan Jonker <jbx6244@gmail.com> Signed-off-by:
-
Johan Jonker authored
A test with the command below gives this error: arch/arm64/boot/dts/rockchip/px30-evb.dt.yaml: gpu@ff400000: '#cooling-cells', 'power-domains' do not match any of the regexes: 'pinctrl-[0-9]+' With the conversion to yaml it also filters things in a node that are used by other drivers like '#cooling-cells' and 'power-domains' for Rockchip px30 gpu nodes, so add them to 'arm,mali-bifrost.yaml'. make ARCH=arm64 dtbs_check DT_SCHEMA_FILES=Documentation/devicetree/bindings/gpu/ arm,mali-bifrost.yaml Signed-off-by:
-
Lad Prabhakar authored
Sort the items in the compatible string list in increasing number of SoC. Signed-off-by:
Lad Prabhakar <prabhakar.mahadev-lad.rj@bp.renesas.com> Reviewed-by:
Sergei Shtylyov <sergei.shtylyov@cogentembedded.com> Reviewed-by:
Geert Uytterhoeven <geert+renesas@glider.be> Signed-off-by:
-
Masahiro Yamada authored
arch/arm/boot/dts/uniphier-ref-daughter.dtsi has compatible = "microchip,24lc128", "atmel,24c128"; and 'make ARCH=arm dtbs_check' warns this: eeprom@50: compatible: ['microchip,24lc128', 'atmel,24c128'] is not valid under any of the given schemas (Possible causes of the failure) Microchip 24LC128 is the device used on this board, and I see it in https://www.microchip.com/wwwproducts/en/24LC128Signed-off-by:
Masahiro Yamada <yamada.masahiro@socionext.com> Signed-off-by:
-
Anson Huang authored
Convert the i.MX7ULP watchdog binding to DT schema format using json-schema. Signed-off-by:
Anson Huang <Anson.Huang@nxp.com> Signed-off-by:
-
Anson Huang authored
Convert the i.MX watchdog binding to DT schema format using json-schema. Signed-off-by:
-
Anson Huang authored
Convert the MXS OCOTP binding to DT schema format using json-schema. Signed-off-by:
-
Anson Huang authored
Convert the i.MX IIM binding to DT schema format using json-schema. Signed-off-by:
-
Anson Huang authored
Convert the i.MX OCOTP binding to DT schema format using json-schema. Signed-off-by:
-
Anson Huang authored
Convert the i.MX GPIO binding to DT schema format using json-schema. Signed-off-by:
-
Anson Huang authored
Convert the i.MX8MM thermal binding to DT schema format using json-schema Signed-off-by:
Amit Kucheria <amit.kucheria@linaro.org> Signed-off-by:
-
- 05 May, 2020 1 commit
-
-
Yoshihiro Shimoda authored
Convert Renesas VMSA-Compatible IOMMU bindings documentation to json-schema. Note that original documentation doesn't mention renesas,ipmmu-vmsa for R-Mobile APE6. But, R-Mobile APE6 is similar to the R-Car Gen2. So, renesas,ipmmu-r8a73a4 belongs the renesas,ipmmu-vmsa section. Signed-off-by:
Yoshihiro Shimoda <yoshihiro.shimoda.uh@renesas.com> Reviewed-by:
-
- 04 May, 2020 11 commits
-
-
Mauro Carvalho Chehab authored
- Add a SPDX header; - Adjust document and section titles; - Mark literal blocks as such; - Add it to bindings/index.rst. Signed-off-by:
Mauro Carvalho Chehab <mchehab+huawei@kernel.org> Signed-off-by:
-
Mauro Carvalho Chehab authored
- Add a SPDX header; - Adjust document and section titles; - Mark literal blocks as such; - Add it to bindings/index.rst. Signed-off-by:
-
Mauro Carvalho Chehab authored
This file only requires a properly-formatted title to be recognized as a ReST file. As there will be more files under bindings/ that will be included at the documentation body, add a new index.rst file there. Signed-off-by:
-
Mauro Carvalho Chehab authored
- Add a SPDX header; - Adjust document title; - Some whitespace fixes and new line breaks; - Mark literal blocks as such; - Add it to devicetree/index.rst. Signed-off-by:
-
Mauro Carvalho Chehab authored
- Add a SPDX header; - Adjust document and section titles; - Adjust numerated list markups; - Some whitespace fixes and new line breaks; - Mark literal blocks as such; - Add it to devicetree/index.rst. Signed-off-by:
-
Mauro Carvalho Chehab authored
- Add a SPDX header; - Adjust document title; - Add it to devicetree/index.rst. Signed-off-by:
-
Mauro Carvalho Chehab authored
- Add a SPDX header; - Add a document title; - Some whitespace fixes and new line breaks; - Add it to devicetree/index.rst. Signed-off-by:
-
Mauro Carvalho Chehab authored
The devicetree.org doesn't host the Device_Tree_Usage page anymore. So, fix the link to point to a new address. Signed-off-by:
-
Mauro Carvalho Chehab authored
- Add a SPDX header; - Adjust document title; - Use footnoote markups; - Some whitespace fixes and new line breaks; - Mark literal blocks as such; - Add it to devicetree/index.rst. Signed-off-by:
Lee Jones <lee.jones@linaro.org> Signed-off-by:
-
Mauro Carvalho Chehab authored
There are some device tree documentation under Documentation/devicetree. Add a top index file for it and add the already-existing ReST file on it. Signed-off-by:
-
Frank Rowand authored
The overlay implementation details in the compiled (DTB) file are now properly implemented by the dtc compiler and should no longer be hard coded in the source file. Signed-off-by:
Frank Rowand <frank.rowand@sony.com> Reviewed-by:
-
- 03 May, 2020 9 commits
-
-
Andre Przywara authored
The Calxeda system registers are a collection of MMIO register controlling several more general aspects of the SoC. Beside for some power management tasks this node is also somewhat abused as the container for the clock nodes. Add a binding in DT schema format using json-schema. Signed-off-by:
Andre Przywara <andre.przywara@arm.com> Signed-off-by:
-
Andre Przywara authored
Convert the generic IPMI controller bindings to DT schema format using json-schema. The device_type property is deprecated for most node per the DT spec, but at least the Linux driver matches on it, so I keep it in. The Linux driver parses for some additional and optional properties, but there are no in-tree users. Let's allow extra properties to cover any other users. Signed-off-by:
-
Andre Przywara authored
Convert the Calxeda DDR memory controller binding to DT schema format using json-schema. Although this technically covers the whole DRAM controller, the intention to use it only for error reporting and mapping fault addresses to DRAM chips. Signed-off-by:
-
Andre Przywara authored
Convert the L2-ECC controller binding to DT schema format using json-schema. This is indented to be just used for error reporting. Signed-off-by:
-
Andre Przywara authored
Convert the Calxeda ComboPHY binding to DT schema format using json-schema. There is no driver in the Linux kernel matching the compatible string, but the nodes are parsed by the SATA driver, which links to them using its port-phys property. Signed-off-by:
-
Andre Przywara authored
Convert the Calxeda XGMAC Ethernet device binding to DT schema format using json-schema. Signed-off-by:
-
Andre Przywara authored
Convert the Calxeda Highbank SATA controller binding to DT schema format using json-schema. Signed-off-by:
-
Andre Przywara authored
Convert the Calxeda clock bindings to DT schema format using json-schema. This just covers the actual PLL and divider clock nodes. In the actual DTs they are somewhat unconnected (no ranges or bus compatible) children of the sregs node, but for the actual clock bindings this is not relevant. One oddity is that the addresses are relative to the parent node, without that being pronounced using a ranges property. But this is too late to fix now. Signed-off-by:
Stephen Boyd <sboyd@kernel.org> Signed-off-by:
-
Rob Herring authored
json-schema versions draft7 and earlier have a weird behavior in that any keywords combined with a '$ref' are ignored (silently). The correct form was to put a '$ref' under an 'allOf'. This behavior is now changed in the 2019-09 json-schema spec and '$ref' can be mixed with other keywords. The json-schema library doesn't yet support this, but the tooling now does a fixup for this and either way works. This has been a constant source of review comments, so let's change this treewide so everyone copies the simpler syntax. Scripted with ruamel.yaml with some manual fixups. Some minor whitespace changes from the script. Signed-off-by:
Maxime Ripard <mripard@kernel.org> Acked-by:
Vinod Koul <vkoul@kernel.org> Acked-by:
Mark Brown <broonie@kernel.org> Acked-by:
Alexandre Belloni <alexandre.belloni@bootlin.com> Acked-by: Wolfram Sang <wsa@the-dreams.de> # for I2C Reviewed-by:
Linus Walleij <linus.walleij@linaro.org> Acked-by: Jonathan Cameron <Jonathan.Cameron@huawei.com> #for-iio Reviewed-by: Stephen Boyd <sboyd@kernel.org> # clock Signed-off-by:
-
- 01 May, 2020 2 commits
-
-
Rob Herring authored
The dtschema package must be somewhat up to date as the tools and meta-schema checks are still evolving. Implement a version check, so this can be enforced. This will help ensure new schema submissions get checked against the latest meta-schemas. Reviewed-by:
Masahiro Yamada <masahiroy@kernel.org> Signed-off-by:
-
Lubomir Rintel authored
Some fixes were done during the conversion: Slightly better examples. The original example was for an OMAP serial port, which is not even described by this binding, but by omap_serial.txt instead. Added compatible strings, that were used, byt not documented: andestech,uart16550, cavium,octeon-3860-uart, fsl,16550-FIFO64, nvidia,tegra186-uart, nvidia,tegra194-uart, nxp,lpc1850-uart, opencores,uart16550-rtlsvn105, ralink,mt7620a-uart, ralink,rt3052-uart, ralink,rt3883-uart and xlnx,xps-uart16550-2.00.b. Removed "serial" compatible string. It's redundant with the node name (which, in OFW, serves the same purpose as the compatible string). Signed-off-by:
Lubomir Rintel <lkundrak@v3.sk> [robh: allow additional properties. clocks/clock-frequency can be optional on original 8250 series with standard clocks] Signed-off-by:
-
- 30 Apr, 2020 2 commits
-
-
Lubomir Rintel authored
These ports are compatible with NS8250 and handled by the same driver. Get rid of the extra document that fails to document the properties that are actually supported. Signed-off-by:
-
Rob Herring authored
-
- 28 Apr, 2020 3 commits
-
-
Nicolas Saenz Julienne authored
When creating a consumer/supplier relationship between two devices, make sure the supplier node is actually active. Otherwise this will create a link relationship that will never be fulfilled. This, in the worst case scenario, will hang the system during boot. Note that, in practice, the fact that a device-tree represented consumer/supplier relationship isn't fulfilled will not prevent devices from successfully probing. Fixes: a3e1d1a7 ("of: property: Add functional dependency link from DT bindings") Signed-off-by:
Nicolas Saenz Julienne <nsaenzjulienne@suse.de> Reviewed-by:
Saravana Kannan <saravanak@google.com> Signed-off-by:
-
Nicolas Saenz Julienne authored
Upon adding a new device from a DT node, we scan its properties and its children's properties in order to create a consumer/supplier relationship between the device and the property provider. That said, it's possible for some of the node's children to be disabled, which will create links that'll never be fulfilled. To get around this, use the for_each_available_child_of_node() function instead of for_each_available_node() when iterating over the node's children. Fixes: d4387cd1 ("of: property: Create device links for all child-supplier depencencies") Signed-off-by:
-
Saravana Kannan authored
When of_link_to_phandle() was implemented initially, there was no way to tell if device_link_add() was failing because the supplier device hasn't been parsed yet, hasn't been added yet, the links were creating a cycle, etc. Some of these were transient errors that'd go away at a later point. However, with the current set of improved checks, if device_link_add() fails, it'll only be for permanent errors like cycles or out-of-memory errors. Also, with the addition of DL_FLAG_SYNC_STATE_ONLY flag [1] to device links, all the valid dependency cycles due to "proxy" device links (needed for correctness of sync_state() device callback) will never fail device_link_add() due to cycles. So, continuing to retry failing device links (by returning -EAGAIN) is no longer useful. At worst, it prevents platforms from setting fw_devlink=on (or better) because it prevents proper boot up. So, let's not do that anymore. [1] - https://lore.kernel.org/lkml/20191028220027.251605-1-saravanak@google.com/ Cc: Nicolas Saenz Julienne <nsaenzjulienne@suse.de> Cc: Greg Kroah-Hartman <gregkh@linuxfoundation.org> Signed-off-by:
-
