In order to address the warnings about the naming convention for keys,
this commit renames the 'power' key to 'power-button' in the vicut1-12inch
device tree source file. The warning in question is as follows:
arch/arm/boot/dts/imx6q-vicut1.dtb: gpio-keys: 'power' does not match
any of the regexes:
'^(button|event|key|switch|(button|event|key|switch)-[a-z0-9-]+|[a-z0-9-]+-(button|event|key|switch))$',
'pinctrl-[0-9]+'
The referenced warning originates from the following schema:
Documentation/devicetree/bindings/input/gpio-keys.yaml
Signed-off-by: Oleksij Rempel <o.rempel@pengutronix.de>
Signed-off-by: Shawn Guo <shawnguo@kernel.org>
Fix USB-related warnings in prtrvt, prtvt7, prti6q and prtwd2 device trees
by disabling unused usbphynop1 and usbphynop2 USB PHYs and providing proper
configuration for the over-current detection. This fixes the following
warnings with the current kernel:
usb_phy_generic usbphynop1: dummy supplies not allowed for exclusive requests
usb_phy_generic usbphynop2: dummy supplies not allowed for exclusive requests
imx_usb 2184200.usb: No over current polarity defined
By the way, fix over-current detection on usbotg port for prtvt7, prti6q
and prtwd2 boards. Only prtrvt do not have OC on USB OTG port.
Signed-off-by: Oleksij Rempel <o.rempel@pengutronix.de>
Signed-off-by: Shawn Guo <shawnguo@kernel.org>
USB over-current detection is supported on this board. So, activate it.
Signed-off-by: Oleksij Rempel <o.rempel@pengutronix.de>
Signed-off-by: Shawn Guo <shawnguo@kernel.org>
USB over-current detection is supported on this board. So, activate it
and fixes the following kernel warnings:
imx_usb 2184200.usb: No over current polarity defined
Signed-off-by: Oleksij Rempel <o.rempel@pengutronix.de>
Signed-off-by: Shawn Guo <shawnguo@kernel.org>
The imx6qp-prtwd3 board supports USB over current detection on the USB
OTG port, however, it was previously disabled in the device tree. This
commit enables the over current detection by changing the device tree
setting from 'disable-over-current' to 'over-current-active-low'. This
could potentially protect the USB port from damage due to over current
situations.
Signed-off-by: Oleksij Rempel <o.rempel@pengutronix.de>
Signed-off-by: Shawn Guo <shawnguo@kernel.org>
Fix USB-related warnings in imx6dl prtmvt device tree by disabling
unused usbphynop1 and usbphynop2 USB PHYs and over-current detection
which is not supported on USB h1 port. This fixes the following warnings
with the current kernel:
usb_phy_generic usbphynop1: dummy supplies not allowed for exclusive requests
usb_phy_generic usbphynop2: dummy supplies not allowed for exclusive requests
imx_usb 2184200.usb: No over current polarity defined
By the way, fix over-current detection on usbotg port.
Signed-off-by: Oleksij Rempel <o.rempel@pengutronix.de>
Signed-off-by: Shawn Guo <shawnguo@kernel.org>
Fix USB-related warnings in imx6dl alti6p device tree by disabling
unused usbphynop1 and usbphynop2 USB PHYs and properly configuring
over-current detection on related ports. This fixes the following
warnings with the current kernel:
usb_phy_generic usbphynop1: dummy supplies not allowed for exclusive requests
usb_phy_generic usbphynop2: dummy supplies not allowed for exclusive requests
imx_usb 2184200.usb: No over-current polarity defined
Signed-off-by: Oleksij Rempel <o.rempel@pengutronix.de>
Signed-off-by: Shawn Guo <shawnguo@kernel.org>
This patch addresses several USB-related warnings in the device tree for
the imx6dl vicut1 system. Specifically, it disables the unused
usbphynop1 and usbphynop2 USB PHYs, and disables unsupported
over-current detection. This action mitigates the following kernel
warnings:
usb_phy_generic usbphynop1: dummy supplies not allowed for exclusive requests
usb_phy_generic usbphynop2: dummy supplies not allowed for exclusive requests
imx_usb 2184200.usb: No over-current polarity defined
Signed-off-by: Oleksij Rempel <o.rempel@pengutronix.de>
Signed-off-by: Shawn Guo <shawnguo@kernel.org>
Kernel v6.3-rc1 prints errors due to missing trip points in thermal
zones. These errors indicate a lack of critical temperature threshold
settings, causing warnings at boot. To silence these errors, this patch
introduces trip points into the thermal zones of several imx6dl based
devices.
The following devices are updated:
- plym2m
- prtvt7
- victgo
- vicut1
These devices are automotive grade and expected to operate up to 105C.
An exception is the plym2m, an industrial grade device, which is
certified to work up to 85C.
The added trip points act as alert thresholds but do not trigger any
actions except warnings. This behavior is by design, as these devices
should maintain their performance until the end, without any thermal
throttling.
Signed-off-by: Oleksij Rempel <o.rempel@pengutronix.de>
Signed-off-by: Shawn Guo <shawnguo@kernel.org>
This commit adds the 'over-current-active-low' flag to the USB OTG node
in the imx6dl-lanmcu device tree. This flag is necessary because the
hardware signals over-current conditions by pulling the line low.
Without this flag, the kernel could misinterpret an over-current
condition, leading to unexpected behavior.
Signed-off-by: Oleksij Rempel <o.rempel@pengutronix.de>
Signed-off-by: Shawn Guo <shawnguo@kernel.org>
In the imx6dl-lanmcu system, the usbh2 and usbh3 interfaces are not in
use. However, the related USB PHY nodes (usbphynop1 and usbphynop2) are
enabled by default in the imx6qdl.dtsi file, which can lead to confusion
and potential resource mismanagement.
This commit explicitly disables these unused USB PHY nodes in the
imx6dl-lanmcu device tree, aligning the configuration more accurately
with the actual hardware setup.
Signed-off-by: Oleksij Rempel <o.rempel@pengutronix.de>
Signed-off-by: Shawn Guo <shawnguo@kernel.org>
This commit addresses a misconfiguration in the prtwd2 device tree
source. Specifically, the ENET MDIO and MDC pins were mistakenly
assigned to the Ethernet block, while they are actually used by the I2C4
interface.
Signed-off-by: Robin van der Gracht <robin@protonic.nl>
Signed-off-by: Oleksij Rempel <o.rempel@pengutronix.de>
Signed-off-by: Shawn Guo <shawnguo@kernel.org>
This touchscreen does not seem to be inverted in any axis, so remove these
DT properties.
Signed-off-by: David Jander <david@protonic.nl>
Signed-off-by: Oleksij Rempel <o.rempel@pengutronix.de>
Signed-off-by: Shawn Guo <shawnguo@kernel.org>
This commit changes the default brightness level of the backlight on the
prtvt7 device from 20 to 65, roughly equivalent to 75% of the maximum
brightness level defined in the "brightness-levels" property.
The adjustment provides a more optimal default brightness for the
device, improving the overall user experience.
Signed-off-by: Robin van der Gracht <robin@protonic.nl>
Signed-off-by: Oleksij Rempel <o.rempel@pengutronix.de>
Signed-off-by: Shawn Guo <shawnguo@kernel.org>
According to Documentation/devicetree/bindings/sound/fsl,ssi.txt
'fsl,mode' should be specified for AC97 mode only.
The 'fsl,ssi' documentation doesn't say anything about specifying
'sound-dai-cells' so we'll remove that as well.
Signed-off-by: Robin van der Gracht <robin@protonic.nl>
Signed-off-by: Oleksij Rempel <o.rempel@pengutronix.de>
Signed-off-by: Shawn Guo <shawnguo@kernel.org>
Devicetree node names should be generic. Use 'eeprom' as node name
to avoid devicetree check warning from at24.yaml.
Signed-off-by: Fabio Estevam <festevam@denx.de>
Reviewed-by: Krzysztof Kozlowski <krzysztof.kozlowski@linaro.org>
Signed-off-by: Shawn Guo <shawnguo@kernel.org>
As documented in pfuze100.yaml, the correct name for the regulator is
"coin", so change it to fix the following DT check warning:
imx6ul-ccimx6ulsbcexpress.dtb: pmic@8: regulators: 'vcoin' does not match any of the regexes:
Signed-off-by: Fabio Estevam <festevam@denx.de>
Signed-off-by: Shawn Guo <shawnguo@kernel.org>
Devicetree node names should be generic. Use 'pmic' as node name
to avoid devicetree check warning from pfuze100.yaml.
Signed-off-by: Fabio Estevam <festevam@denx.de>
Reviewed-by: Krzysztof Kozlowski <krzysztof.kozlowski@linaro.org>
Signed-off-by: Shawn Guo <shawnguo@kernel.org>
According to Documentation/devicetree/bindings/sound/imx-audmux.yaml,
there must be a "mux-" prefix in the audmux port nodes.
Add the "mux-" prefix to avoid devicetree schema warnings.
Signed-off-by: Fabio Estevam <festevam@denx.de>
Signed-off-by: Shawn Guo <shawnguo@kernel.org>
Describe the SD1_VSELECT pad, which is necessary to allow UHS modes.
Also, to support higher SD card speed modes, describe the 100MHz and
200MHz SD card pinctrl entries.
Suggested-by: Ye Li <ye.li@nxp.com>
Signed-off-by: Fabio Estevam <festevam@denx.de>
Signed-off-by: Shawn Guo <shawnguo@kernel.org>
Improve the devicetree description by adding the SD card regulator
that is controlled via GPIO5_2.
Signed-off-by: Fabio Estevam <festevam@denx.de>
Signed-off-by: Shawn Guo <shawnguo@kernel.org>
The DSA framework has got more picky about always having a phy-mode
for the CPU port. The Vybrid FEC is a Fast Ethrnet using RMII.
Additionally, the cpu label has never actually been used in the
binding, so remove it.
Lastly, for DSA links between switches, add a fixed-link node
indicating the expected speed/duplex of the link.
Signed-off-by: Andrew Lunn <andrew@lunn.ch>
Signed-off-by: Shawn Guo <shawnguo@kernel.org>
'vmcc-supply' is not a valid property.
Use 'vmmc-supply' supply instead.
Signed-off-by: Fabio Estevam <festevam@denx.de>
Signed-off-by: Shawn Guo <shawnguo@kernel.org>
The 'clock-names' property is not a valid property for wdog.
Remove it to fix the following DT check warning:
vf610-zii-ssmb-dtu.dtb: watchdog@4003e000: Unevaluated properties are not allowed ('clock-names' was unexpected)
From schema: /Documentation/devicetree/bindings/watchdog/fsl-imx-wdt.yaml
Signed-off-by: Fabio Estevam <festevam@denx.de>
Signed-off-by: Shawn Guo <shawnguo@kernel.org>
The 'clock-names' property is not a valid property for wdog.
Remove it to fix the following DT check warning:
watchdog@53fdc000: Unevaluated properties are not allowed ('clock-names' was unexpected)
From schema: Documentation/devicetree/bindings/watchdog/fsl-imx-wdt.yaml
Signed-off-by: Fabio Estevam <festevam@denx.de>
Signed-off-by: Shawn Guo <shawnguo@kernel.org>
The 'num-chipselects' property is not a valid property for ecspi.
Remove it to fix the following DT check warning:
spi@30630000: Unevaluated properties are not allowed ('num-chipselects' was unexpected)
From schema: Documentation/devicetree/bindings/spi/fsl-imx-cspi.yaml
Signed-off-by: Fabio Estevam <festevam@denx.de>
Signed-off-by: Shawn Guo <shawnguo@kernel.org>
The 'rs485-rts-active-high' property is not a valid property and is not
documented anywhere.
Remove it to fix the following DT schema warning:
serial@21f0000: Unevaluated properties are not allowed ('rs485-rts-active-high' was unexpected)
Signed-off-by: Fabio Estevam <festevam@denx.de>
Signed-off-by: Shawn Guo <shawnguo@kernel.org>
Pass Ethernet aliases, so that the bootloader can properly pass MAC address
to Linux.
This fixes the problem of getting a random MAC address for eth1 in Linux.
Signed-off-by: Fabio Estevam <festevam@denx.de>
Signed-off-by: Shawn Guo <shawnguo@kernel.org>
Use pinctrl-0 for pinctrl_rfkill to fix the following
'make CHECK_DTBS=y imx7d-smegw01.dtb' warning:
regulator-wlan-rfkill: 'pinctrl-0' is a dependency of 'pinctrl-names'
Signed-off-by: Fabio Estevam <festevam@denx.de>
Signed-off-by: Shawn Guo <shawnguo@kernel.org>
Pass 'gpr' to the pinctrl groups to fix the following
'make CHECK_DTBS=y imx7d-smegw01.dtb' warning:
pinctrl@30330000: 'rfkillrp', 'usbotg1', 'usbotg1-pwr', 'usbotg1-pwr-gpio' do not match any of the regexes: 'grp$', 'pinctrl-[0-9]+'
From schema: Documentation/devicetree/bindings/pinctrl/fsl,imx7d-pinctrl.yaml
Signed-off-by: Fabio Estevam <festevam@denx.de>
Signed-off-by: Shawn Guo <shawnguo@kernel.org>
Remove the unneeded #address-cells/#size-cells from sram@0 to fix
the following 'make CHECK_DTBS=y imx7d-smegw01.dtb' warning:
sram@0: Unevaluated properties are not allowed ('#address-cells', '#size-cells' were unexpected)
From schema: Documentation/devicetree/bindings/mtd/microchip,mchp48l640.yaml
Signed-off-by: Fabio Estevam <festevam@denx.de>
Signed-off-by: Shawn Guo <shawnguo@kernel.org>
Remove the invalid #address-cells and #size-cells nodes from
the fan-controller.
Signed-off-by: Tim Harvey <tharvey@gateworks.com>
Signed-off-by: Shawn Guo <shawnguo@kernel.org>
Remove the invalid #address-cells and #size-cells nodes from
the fan-controller.
Signed-off-by: Tim Harvey <tharvey@gateworks.com>
Signed-off-by: Shawn Guo <shawnguo@kernel.org>
i.MX6SX has an LVDS controller that is connected to the eLCDIF.
Add support for it.
Signed-off-by: Fabio Estevam <festevam@denx.de>
Signed-off-by: Shawn Guo <shawnguo@kernel.org>
usdhc1 and usdhc3 node name contain underscores, so replace the
'_' by '-'.
Signed-off-by: Haibo Chen <haibo.chen@nxp.com>
Signed-off-by: Shawn Guo <shawnguo@kernel.org>
This adds support for a COTS monitor connected to X17.
4k monitors can be used, but are limited to 1080p.
Signed-off-by: Alexander Stein <alexander.stein@ew.tq-group.com>
Signed-off-by: Shawn Guo <shawnguo@kernel.org>
The OCOTP node should have address/size-cells so the cells can have unit
address:
imx7ulp-evk.dtb: efuse@410a6000: '#address-cells' is a required property
imx7ulp-evk.dtb: efuse@410a6000: '#size-cells' is a required property
Signed-off-by: Krzysztof Kozlowski <krzysztof.kozlowski@linaro.org>
Reviewed-by: Peng Fan <peng.fan@nxp.com>
Signed-off-by: Shawn Guo <shawnguo@kernel.org>
This fixes the warnings:
pca953x 3-0020: supply vcc not found, using dummy regulator
pca953x 3-0021: supply vcc not found, using dummy regulator
pca953x 3-0022: supply vcc not found, using dummy regulator
at24 3-0051: supply vcc not found, using dummy regulator
Signed-off-by: Alexander Stein <alexander.stein@ew.tq-group.com>
Signed-off-by: Shawn Guo <shawnguo@kernel.org>
According to fsl,imx-gpc.yaml the General Power Control requires
a ipg clock and a Power Gating Control node. So add them to fix
the dtbs_check warnings on i.MX6UL boards:
gpc@20dc000: 'clocks' is a required property
gpc@20dc000: 'clock-names' is a required property
gpc@20dc000: 'pgc' is a required property
Suggested-by: Jacky Bai <ping.bai@nxp.com>
Signed-off-by: Stefan Wahren <stefan.wahren@i2se.com>
Signed-off-by: Shawn Guo <shawnguo@kernel.org>
Currently the dtbs_check generates warnings like this:
$nodename:0: 'dma-apbh@110000' does not match '^dma-controller(@.*)?$'
So fix all affected dma-apbh node names.
Signed-off-by: Stefan Wahren <stefan.wahren@i2se.com>
Signed-off-by: Shawn Guo <shawnguo@kernel.org>
The DSA framework has got more picky about always having a phy-mode
for the CPU port. Add a phy-mode based on what the SoC ethernet is
using. For RGMII mode, have the switch add the delays.
Additionally, the cpu label has never actually been used in the
binding, so remove it.
Lastly add a fixed-link node indicating the expected speed/duplex of
the link to the SoC.
Signed-off-by: Andrew Lunn <andrew@lunn.ch>
Reviewed-by: Vladimir Oltean <vladimir.oltean@nxp.com>
Signed-off-by: Shawn Guo <shawnguo@kernel.org>
The DSA framework has got more picky about always having a phy-mode
for the CPU port. The imx51 Ethernet supports MII, and RMII. Set the
switch phy-mode based on how the SoC Ethernet port has been
configured.
Additionally, the cpu label has never actually been used in the
binding, so remove it.
Signed-off-by: Andrew Lunn <andrew@lunn.ch>
Reviewed-by: Vladimir Oltean <vladimir.oltean@nxp.com>
Signed-off-by: Shawn Guo <shawnguo@kernel.org>
As stated in Documentation/devicetree/bindings/spi/spi-gpio.yaml,
'gpio-miso', 'gpio-mosi' and 'gpio-sck' are deprecated properties.
Use the recommeded 'miso-gpios', 'mosi-gpios' and 'sck-gpios' instead.
Signed-off-by: Fabio Estevam <festevam@denx.de>
Signed-off-by: Shawn Guo <shawnguo@kernel.org>
As stated in Documentation/devicetree/bindings/spi/spi-gpio.yaml,
'gpio-miso', 'gpio-mosi' and 'gpio-sck' are deprecated properties.
Use the recommeded 'miso-gpios', 'mosi-gpios' and 'sck-gpios' instead.
Signed-off-by: Fabio Estevam <festevam@denx.de>
Signed-off-by: Shawn Guo <shawnguo@kernel.org>
As stated in Documentation/devicetree/bindings/spi/spi-gpio.yaml,
'gpio-miso', 'gpio-mosi' and 'gpio-sck' are deprecated properties.
Use the recommeded 'miso-gpios', 'mosi-gpios' and 'sck-gpios' instead.
Signed-off-by: Fabio Estevam <festevam@denx.de>
Signed-off-by: Shawn Guo <shawnguo@kernel.org>
As stated in Documentation/devicetree/bindings/spi/spi-gpio.yaml,
'gpio-miso', 'gpio-mosi' and 'gpio-sck' are deprecated properties.
Use the recommeded 'miso-gpios', 'mosi-gpios' and 'sck-gpios' instead.
Signed-off-by: Fabio Estevam <festevam@denx.de>
Signed-off-by: Shawn Guo <shawnguo@kernel.org>
As stated in Documentation/devicetree/bindings/spi/spi-gpio.yaml,
'gpio-miso', 'gpio-mosi' and 'gpio-sck' are deprecated properties.
Use the recommeded 'miso-gpios', 'mosi-gpios' and 'sck-gpios' instead.
Signed-off-by: Fabio Estevam <festevam@denx.de>
Signed-off-by: Shawn Guo <shawnguo@kernel.org>
As stated in Documentation/devicetree/bindings/spi/spi-gpio.yaml,
'gpio-mosi' and 'gpio-sck' are deprecated properties.
Use the recommeded 'mosi-gpios' and 'sck-gpios' instead.
Signed-off-by: Fabio Estevam <festevam@denx.de>
Signed-off-by: Shawn Guo <shawnguo@kernel.org>
