- 19 Oct, 2021 10 commits
-
-
Mauro Carvalho Chehab authored
Changeset 63f8e9e0 ("dt-bindings: mtd: Convert mtd-physmap to DT schema") renamed: Documentation/devicetree/bindings/mtd/arm-versatile.txt and: Documentation/devicetree/bindings/mtd/cypress,hyperflash.txt to: Documentation/devicetree/bindings/mtd/mtd-physmap.yaml. Update their cross-references accordingly. Fixes: 63f8e9e0 ("dt-bindings: mtd: Convert mtd-physmap to DT schema") Acked-by:
Miquel Raynal <miquel.raynal@bootlin.com> Signed-off-by:
Mauro Carvalho Chehab <mchehab+huawei@kernel.org> Signed-off-by:
Rob Herring <robh@kernel.org> Link: https://lore.kernel.org/r/cdf3891ef686eca67c6072da8c1d027eedc1ef3e.1634630486.git.mchehab+huawei@kernel.org
-
Mauro Carvalho Chehab authored
Changeset 5d1c5594 ("dt-bindings: net: brcm,unimac-mdio: convert to the json-schema") renamed: Documentation/devicetree/bindings/net/brcm,unimac-mdio.txt to: Documentation/devicetree/bindings/net/brcm,unimac-mdio.yaml. Update its cross-reference accordingly. Fixes: 5d1c5594 ("dt-bindings: net: brcm,unimac-mdio: convert to the json-schema") Signed-off-by:
Florian Fainelli <f.fainelli@gmail.com> Signed-off-by:
-
Mauro Carvalho Chehab authored
Changeset 7da6ebf5 ("dt-bindings: arm: Convert Gemini boards to YAML") renamed: Documentation/devicetree/bindings/arm/gemini.txt to: Documentation/devicetree/bindings/arm/gemini.yaml. Update its cross-reference accordingly. Fixes: 7da6ebf5 ("dt-bindings: arm: Convert Gemini boards to YAML") Signed-off-by:
-
Mauro Carvalho Chehab authored
The file name: Documentation/devicetree/bindings/media/imx8-jpeg.yaml should be, instead: Documentation/devicetree/bindings/media/nxp,imx8-jpeg.yaml. Update its cross-reference accordingly. Fixes: be157db0 ("media: Add maintainer for IMX jpeg v4l2 driver") Fixes: b16ed1e6 ("media: dt-bindings: Add bindings for i.MX8QXP/QM JPEG driver") Reviewed-by:
Mirela Rabulea <mirela.rabulea@nxp.com> Signed-off-by:
-
Mauro Carvalho Chehab authored
The file name: Documentation/devicetree/bindings/display/intel,ixp46x-rng.yaml should be, instead: Documentation/devicetree/bindings/rng/intel,ixp46x-rng.yaml. Update its cross-reference accordingly. Fixes: cca061b0 ("hw_random: ixp4xx: Add DT bindings") Reviewed-by:
Linus Walleij <linus.walleij@linaro.org> Signed-off-by:
-
Mauro Carvalho Chehab authored
Changeset 5a9652f6 ("dt-bindings: arm: keystone: Convert ti,sci to json schema") renamed: Documentation/devicetree/bindings/arm/keystone/ti,sci.txt to: Documentation/devicetree/bindings/arm/keystone/ti,sci.yaml. Update its cross-reference accordingly. Fixes: 5a9652f6 ("dt-bindings: arm: keystone: Convert ti,sci to json schema") Reviewed-by:
Nishanth Menon <nm@ti.com> Signed-off-by:
-
Mauro Carvalho Chehab authored
Changeset 8df65d4a ("dt-bindings: convert rtc/faraday,ftrtc01 to yaml") renamed: Documentation/devicetree/bindings/rtc/faraday,ftrtc010.txt to: Documentation/devicetree/bindings/rtc/faraday,ftrtc010.yaml. Update its cross-reference accordingly. Fixes: 8df65d4a ("dt-bindings: convert rtc/faraday,ftrtc01 to yaml") Reviewed-by:
-
Mauro Carvalho Chehab authored
Changeset 810e4441 ("dt-bindings: aspeed-i2c: Convert txt to yaml format") renamed: Documentation/devicetree/bindings/i2c/i2c-aspeed.txt to: Documentation/devicetree/bindings/i2c/aspeed,i2c.yaml. Update its cross-reference accordingly. Fixes: 810e4441 ("dt-bindings: aspeed-i2c: Convert txt to yaml format") Signed-off-by:
-
Mauro Carvalho Chehab authored
Changeset b7705ba6 ("dt-bindings: interrupt-controller: Convert ARM VIC to json-schema") renamed: Documentation/devicetree/bindings/interrupt-controller/arm,vic.txt to: Documentation/devicetree/bindings/interrupt-controller/arm,vic.yaml. Update its cross-reference accordingly. Fixes: b7705ba6 ("dt-bindings: interrupt-controller: Convert ARM VIC to json-schema") Reviewed-by:
Sudeep Holla <sudeep.holla@arm.com> Signed-off-by:
-
Mauro Carvalho Chehab authored
Changeset 89a5bf0f ("dt-bindings: reserved-memory: ramoops: Convert txt bindings to yaml") renamed: Documentation/devicetree/bindings/reserved-memory/ramoops.txt to: Documentation/devicetree/bindings/reserved-memory/ramoops.yaml. Update the cross-references accordingly. Fixes: 89a5bf0f ("dt-bindings: reserved-memory: ramoops: Convert txt bindings to yaml") Signed-off-by:
David Heidelberg <david@ixit.cz> Signed-off-by:
-
- 18 Oct, 2021 12 commits
-
-
Krzysztof Kozlowski authored
Convert the Marvell NCI NFC controller to DT schema format. Signed-off-by:
Krzysztof Kozlowski <krzysztof.kozlowski@canonical.com> Link: https://lore.kernel.org/r/20211011073934.34340-9-krzysztof.kozlowski@canonical.comSigned-off-by:
-
Krzysztof Kozlowski authored
Convert the TI TRF7970A NFC to DT schema format. Signed-off-by:
-
Krzysztof Kozlowski authored
Convert the ST NCI (ST21NFCB) NFC controller to DT schema format. Changes during bindings conversion: 1. Add a new required "reg" property for SPI binding, because SPI child devices use it as chip-select. 2. Drop the "clock-frequency" property during conversion because it is a property of I2C bus controller, not I2C slave device. It was also never used by the driver. Signed-off-by:
-
Krzysztof Kozlowski authored
Convert the ST ST95HF NFC controller to DT schema format. Signed-off-by:
-
Krzysztof Kozlowski authored
Convert the ST ST21NFCA NFC controller to DT schema format. Changes during bindings conversion: 1. Add a new required "interrupts" property, because it was missing in the old bindings by mistake. 2. Drop the "clock-frequency" property during conversion because it is a property of I2C bus controller, not I2C slave device. It was also never used by the driver. Signed-off-by:
-
Krzysztof Kozlowski authored
Convert the NXP PN532 NFC controller to DT schema format. Drop the "clock-frequency" property during conversion because it is a property of I2C bus controller, not I2C slave device. It was also never used by the driver. Signed-off-by:
-
Krzysztof Kozlowski authored
NXP PN547 NFC controller seems to be compatible with the NXP NCI and there already DTS files using two compatibles. Signed-off-by:
-
Krzysztof Kozlowski authored
Convert the NXP NCI NFC controller to DT schema format. Drop the "clock-frequency" property during conversion because it is a property of I2C bus controller, not I2C slave device. It was also never used by the driver. Signed-off-by:
-
David Heidelberg authored
Convert Elan touchpad documentation to the YAML syntax. Reviewed-by:
Dmitry Osipenko <digetx@gmail.com> Signed-off-by:
-
Maxime Ripard authored
The Silead GSL1680 Touchscreen Controller is supported by Linux thanks to its device tree binding. Now that we have the DT validation in place, let's convert the device tree bindings for that driver over to a YAML schema. Cc: Dmitry Torokhov <dmitry.torokhov@gmail.com> Cc: linux-input@vger.kernel.org Signed-off-by:
Maxime Ripard <maxime@cerno.tech> Link: https://lore.kernel.org/r/20211015073006.8939-1-maxime@cerno.techSigned-off-by:
-
Sergio Paracuellos authored
Add device tree bindings for palmbus controller present in all the MIPS ralink based SoCs. Signed-off-by:
Sergio Paracuellos <sergio.paracuellos@gmail.com> Link: https://lore.kernel.org/r/20211016203323.9165-1-sergio.paracuellos@gmail.comSigned-off-by:
-
David Heidelberg authored
Convert ramoops driver to the YAML syntax. Signed-off-by:
-
- 15 Oct, 2021 1 commit
-
-
Maxime Ripard authored
The Omnivision OV5640 is supported by Linux thanks to its device tree binding. Now that we have the DT validation in place, let's convert the device tree bindings for that driver over to a YAML schema. Cc: linux-media@vger.kernel.org Cc: Mauro Carvalho Chehab <mchehab@kernel.org> Cc: Steve Longerbeam <slongerbeam@gmail.com> Signed-off-by:
-
- 13 Oct, 2021 2 commits
-
-
Rob Herring authored
'reg' is the standard property for defining register banks/addresses. Add it to use for the register address and deprecate 'offset'. This also allows for using standard node names with unit-addresses. However, since it is quite possible to have multiple nodes at the same register address, allow for the unit-address to optionally have the bit offset. The unit-address format is '@<reg address>[,<bit offset>]'. This matches the format recently added for nvmem binding which has the same issue. Cc: Pavel Machek <pavel@ucw.cz> Cc: Linus Walleij <linus.walleij@linaro.org> Cc: linux-leds@vger.kernel.org Signed-off-by:
-
Rob Herring authored
Convert the register-bit-led binding to DT schema format. As the example just repeats nearly identical nodes, trim it down to a few nodes and use some documented values for 'linux,default-trigger'. Cc: Linus Walleij <linus.walleij@linaro.org> Cc: Pavel Machek <pavel@ucw.cz> Cc: linux-leds@vger.kernel.org Signed-off-by:
-
- 12 Oct, 2021 6 commits
-
-
Maxime Ripard authored
The ESP8089 Wireless Chip is supported by Linux (through an out-of-tree driver) thanks to its device tree binding. Now that we have the DT validation in place, let's convert the device tree bindings for that driver over to a YAML schema. Cc: "David S. Miller" <davem@davemloft.net> Cc: de Goede <hdegoede@redhat.com> Cc: Jakub Kicinski <kuba@kernel.org> Cc: Kalle Valo <kvalo@codeaurora.org> Cc: linux-wireless@vger.kernel.org Cc: netdev@vger.kernel.org Reviewed-by:
-
Maxime Ripard authored
Even though both the driver and the device trees all use the allwinner,sun8i-r40-gmac compatible, we documented the compatible as allwinner,sun8i-r40-emac in the binding. Let's fix this. Cc: Alexandre Torgue <alexandre.torgue@st.com> Cc: "David S. Miller" <davem@davemloft.net> Cc: Giuseppe Cavallaro <peppe.cavallaro@st.com> Cc: Jakub Kicinski <kuba@kernel.org> Cc: Jose Abreu <joabreu@synopsys.com> Cc: netdev@vger.kernel.org Reviewed-by:
Jernej Skrabec <jernej.skrabec@gmail.com> Reviewed-by:
-
Maxime Ripard authored
additionalProperties prevent any property not explicitly defined in the binding to be used. Yet, some serial properties like max-speed are valid and validated through the serial/serial.yaml binding. Even though the ideal solution would be to use unevaluatedProperties instead, it's not pratical due to the way the bus bindings have been described. Let's add max-speed to remove the warning. Cc: Alistair Francis <alistair@alistair23.me> Cc: "David S. Miller" <davem@davemloft.net> Cc: Jakub Kicinski <kuba@kernel.org> Cc: netdev@vger.kernel.org Cc: Vasily Khoruzhick <anarsoul@gmail.com> Reviewed-by:
Alistair Francis <alistair@alistair23.me> Reviewed-by:
-
Maxime Ripard authored
The original binding was mentioning that valid values for the clocks and clock-names property were one or two clocks from extclk, txco and lpo, with extclk being deprecated in favor of txco. However, the current binding lists a valid array as extclk, txco and lpo, with either one or two items. While this looks similar, it actually enforces that all the device trees use either ["extclk"], or ["extclk", "txco"]. That doesn't make much sense, since the two clocks are said to be equivalent, with one superseeding the other. lpo is also not a valid clock anymore, and would be as the third clock of the list, while we could have only this clock in the previous binding (and in DTs). Let's rework the clock clause to allow to have either: - extclk, and mark it a deprecated - txco alone - lpo alone - txco, lpo While ["extclk", "lpo"] wouldn't be valid, it wasn't found in any device tree so it's not an issue in practice. Similarly, ["lpo", "txco"] is still considered invalid, but it's generally considered as a best practice to fix the order of clocks. Cc: "David S. Miller" <davem@davemloft.net> Cc: Jakub Kicinski <kuba@kernel.org> Cc: netdev@vger.kernel.org Reviewed-by:
-
Sergio Paracuellos authored
Add binding documentation for Mediatek's SDRAM memory controller present on MT7621 SoC. Signed-off-by:
-
Chukun Pan authored
The clocks in the example use 'SCLK_DDRCLK', which does not exist in the rk3399-cru.h, correct it to 'SCLK_DDRC'. Ref: commit 7fbdfcd6 ("clk: rockchip: add SCLK_DDRC id for rk3399 ddrc") Fixes: c1ceb8f7 ("Documentation: bindings: add dt documentation for rk3399 dmc") Signed-off-by:
Chukun Pan <amadeus@jmu.edu.cn> Link: https://lore.kernel.org/r/20211001150024.18672-1-amadeus@jmu.edu.cnSigned-off-by:
-
- 08 Oct, 2021 2 commits
-
-
Shubhrajyoti Datta authored
Add a clocking node for xilinx udc. Signed-off-by:
Shubhrajyoti Datta <shubhrajyoti.datta@xilinx.com> Signed-off-by:
-
Rob Herring authored
Merge fixes to avoid binding schema warnings. Signed-off-by:
-
- 06 Oct, 2021 1 commit
-
-
Zev Weiss authored
When CONFIG_OF_KOBJ was introduced in commit b56b5528 ("of: make kobject and bin_attribute support configurable") and #ifdef-ed versions of these declarations got added, the originals didn't get removed. Fixes: b56b5528 ("of: make kobject and bin_attribute support configurable") Signed-off-by:
Zev Weiss <zev@bewilderbeest.net> Link: https://lore.kernel.org/r/20211006061943.8472-1-zev@bewilderbeest.netSigned-off-by:
-
- 04 Oct, 2021 5 commits
-
-
Simon Glass authored
Add missing hyphens and reword one sentence for clarity. Signed-off-by:
Simon Glass <sjg@chromium.org> Reviewed-by:
Randy Dunlap <rdunlap@infradead.org> Link: https://lore.kernel.org/r/20211003124936.1.Idc7beddc77250bca0cfb5912b56be719d9073bc4@changeidSigned-off-by:
-
Gavin Shan authored
There is no device node for the empty NUMA node. However, the corresponding NUMA node ID and distance map is still valid in "numa-distance-map-v1" compatible device node. This fetches the NUMA node ID and distance map for these empty NUMA node from "numa-distance-map-v1" compatible device node. Signed-off-by:
Gavin Shan <gshan@redhat.com> Link: https://lore.kernel.org/r/20210927064119.127285-3-gshan@redhat.comSigned-off-by:
-
Gavin Shan authored
The empty memory nodes, where no memory resides in, are allowed. The NUMA node IDs are still valid and parsed, but memory may be added to them through hotplug afterwards. Currently, QEMU fails to boot when multiple empty memory nodes are specified. It's caused by device-tree population failure and duplicated memory node names. The device-tree specification doesn't provide how empty NUMA nodes are handled. Besides, I finds difficulty to get where this case is documented. So lets add a section for empty memory nodes to cover it in NUMA binding document. Signed-off-by:
-
Rob Herring authored
Drop another redundant maxItems that snuck into w1-gpio binding. If a property has an 'items' list, then a 'minItems' or 'maxItems' with the same size as the list is redundant and can be dropped. Note that is DT schema specific behavior and not standard json-schema behavior. The tooling will fixup the final schema adding any unspecified minItems/maxItems. Fixes: dd2c898b ("dt-bindings: w1: Convert 1-Wire GPIO binding to a schema") Cc: Daniel Mack <zonque@gmail.com> Signed-off-by:
-
Geert Uytterhoeven authored
make dtbs_check: arch/arm64/boot/dts/qcom/sdm850-lenovo-yoga-c630.dt.yaml: bridge@2c: reg:0:0: 45 was expected According to the datasheet, the I2C address can be either 0x2c or 0x2d, depending on the ADDR control input. Fixes: e3896e6d ("dt-bindings: drm/bridge: Document sn65dsi86 bridge bindings") Signed-off-by:Geert Uytterhoeven <geert+renesas@glider.be> Reviewed-by:
Kieran Bingham <kieran.bingham@ideasonboard.com> Link: https://lore.kernel.org/r/08f73c2aa0d4e580303357dfae107d084d962835.1632486753.git.geert+renesas@glider.beSigned-off-by:
-
- 01 Oct, 2021 1 commit
-
-
Rob Herring authored
Another round of removing redundant minItems/maxItems from new schema in the recent merge window. If a property has an 'items' list, then a 'minItems' or 'maxItems' with the same size as the list is redundant and can be dropped. Note that is DT schema specific behavior and not standard json-schema behavior. The tooling will fixup the final schema adding any unspecified minItems/maxItems. Cc: "David S. Miller" <davem@davemloft.net> Cc: Jakub Kicinski <kuba@kernel.org> Cc: Evgeniy Polyakov <zbr@ioremap.net> Cc: Marek Vasut <marex@denx.de> Cc: Joakim Zhang <qiangqing.zhang@nxp.com> Cc: dri-devel@lists.freedesktop.org Cc: netdev@vger.kernel.org Cc: linux-arm-kernel@lists.infradead.org Signed-off-by:
-
