| Age | Commit message (Collapse) | Author |
|---|
|
Signed-off-by: Philippe Schenker <philippe.schenker@toradex.com>
|
|
Signed-off-by: Philippe Schenker <philippe.schenker@toradex.com>
|
|
This patch enables both RXC and TXC 2ns dll delay lines on the
KSZ9131 PHY. Both are neede because the i.MX8MM SoC is RGMII v1.3
compliant. This means we need the TXC delay of the PHY.
Related-to: ELB-1299
Signed-off-by: Philippe Schenker <philippe.schenker@toradex.com>
|
|
The RXC delay is provided in both PHYs used (KSZ9031 and KSZ9131)
on the PHY itself so it is not needed on the MAC.
Related-to: ELB-1299
Signed-off-by: Philippe Schenker <philippe.schenker@toradex.com>
|
|
Add CTRL_SLEEP_MOCI required for e.g. the Dahlia carrier board.
Related-to: ELB-2520
Signed-off-by: Marcel Ziswiler <marcel.ziswiler@toradex.com>
|
|
The hardware of verdin has some bypass caps after the switch that
switches power to the sd-card. These caps are resulting in a slow
discharge.
Add off-on-delay to set a minimum off-time of the regulator so it
can fully discharge until it turns on again.
Signed-off-by: Philippe Schenker <philippe.schenker@toradex.com>
|
|
This commit basically deletes the devicetree for V1.0 Apalis iMX8
modules. It includes V1.1 devicetree then and only puts in the
differences and deletes the nodes that are not used in V1.0.
This is done to prevent code duplication and have better overview of
what has changed.
Related-to: ELB-1254
Signed-off-by: Philippe Schenker <philippe.schenker@toradex.com>
|
|
Related-to: ELB-1254
Signed-off-by: Philippe Schenker <philippe.schenker@toradex.com>
|
|
Related-to: ELB-1254
Signed-off-by: Philippe Schenker <philippe.schenker@toradex.com>
|
|
This commit does no code changes it just copies fsl-imx8qm-apalis.dtsi
to fsl-imx8qm-apalis-v1.1.dtsi.
This is done to be able to track changes made between those versions.
Related-to: ELB-1254
Signed-off-by: Philippe Schenker <philippe.schenker@toradex.com>
|
|
Signed-off-by: Philippe Schenker <philippe.schenker@toradex.com>
|
|
Related-to: ELB-2289
Signed-off-by: Philippe Schenker <philippe.schenker@toradex.com>
|
|
Related-to: ELB-2289
Signed-off-by: Philippe Schenker <philippe.schenker@toradex.com>
|
|
Related-to: ELB-2289
Signed-off-by: Philippe Schenker <philippe.schenker@toradex.com>
|
|
Related-to: ELB-2359
Signed-off-by: Philippe Schenker <philippe.schenker@toradex.com>
|
|
Note: there is still backfeeding present at this moment from those pads:
SC_P_ENET0_RGMII_TXD0
SC_P_ENET0_RGMII_TXD1
SC_P_ENET0_RGMII_RXD0
SC_P_ENET0_RGMII_RXD1
Related-to: ELB-1254
Signed-off-by: Philippe Schenker <philippe.schenker@toradex.com>
|
|
Related-to: ELB-1254
Signed-off-by: Philippe Schenker <philippe.schenker@toradex.com>
|
|
Related-to: ELB-1254
Signed-off-by: Philippe Schenker <philippe.schenker@toradex.com>
|
|
Add a 'sleep' pinmuxing which prevents driving RGMII pins and backfeed the
unpowered Ethernet PHY.
When switching the Ethernet PHY supply off, it takes about 400 ms for
the PHY power to go down. So wait a minimum of 500 ms before reenabling
the PHY supply.
Related-to: HAR-2339
Signed-off-by: Max Krummenacher <max.krummenacher@toradex.com>
|
|
After the Ethernet PHY supply is enabled an RC holds the reset asserted
for about 120 ms. Reduce the time waited from 1000 ms to 200 ms which
should account for any possible tolerance.
U-Boot enables the PHY supply, switching it off in Linux with the RGMII
pins allready muxed creates backfeeding, thus set regulator-boot-on.
Related-to: HAR-2339
Signed-off-by: Max Krummenacher <max.krummenacher@toradex.com>
|
|
The driver now checks the fuses for a disabled DSP. Thus enable the DSP
device in the device tree and let the driver decide at run-time if the
DSP can be used or not.
This reverts commit 862886b0c48296d34b0e63d7497fa671e6fe25d7.
Related-to: ELB-1380
Signed-off-by: Max Krummenacher <max.krummenacher@toradex.com>
|
|
toradex_4.14-2.0.x-imx-next
Conflicts:
sound/soc/codecs/sgtl5000.c
|
|
This is the 4.14.159 stable release
Conflicts:
arch/arm/Kconfig.debug
arch/arm/boot/dts/imx7s.dtsi
arch/arm/mach-imx/cpuidle-imx6sx.c
drivers/crypto/caam/caamalg.c
drivers/crypto/mxs-dcp.c
drivers/dma/imx-sdma.c
drivers/input/keyboard/imx_keypad.c
drivers/net/can/flexcan.c
drivers/net/can/rx-offload.c
drivers/net/wireless/ath/ath10k/pci.c
drivers/pci/dwc/pci-imx6.c
drivers/spi/spi-fsl-lpspi.c
drivers/usb/dwc3/gadget.c
|
|
[ Upstream commit 5b78012636f537344bd551934387f5772c38ba80 ]
The gpio line names were set in the pinctrl node instead of the gpio node,
at the time it was merged, it worked, but was obviously wrong.
This patch moves the properties to the gpio nodes.
Fixes: 60795933b709 ("ARM64: dts: meson-gxl-khadas-vim: Add GPIO lines names")
Signed-off-by: Neil Armstrong <narmstrong@baylibre.com>
Signed-off-by: Kevin Hilman <khilman@baylibre.com>
Signed-off-by: Sasha Levin <sashal@kernel.org>
|
|
[ Upstream commit 2165b006b65d609140dafafcb14cce5a4aaacbab ]
The gpio line names were set in the pinctrl node instead of the gpio node,
at the time it was merged, it worked, but was obviously wrong.
This patch moves the properties to the gpio nodes.
Fixes: b03c7d6438bb ("ARM64: dts: meson-gxbb-odroidc2: Add GPIO lines names")
Signed-off-by: Neil Armstrong <narmstrong@baylibre.com>
Signed-off-by: Kevin Hilman <khilman@baylibre.com>
Signed-off-by: Sasha Levin <sashal@kernel.org>
|
|
[ Upstream commit f0783f5edb52af14ecaae6c5ce4f38e0a358f5d8 ]
The gpio line names were set in the pinctrl node instead of the gpio node,
at the time it was merged, it worked, but was obviously wrong.
This patch moves the properties to the gpio nodes.
Fixes: 12ada0513d7a ("ARM64: dts: meson-gxbb-nanopi-k2: Add GPIO lines names")
Signed-off-by: Neil Armstrong <narmstrong@baylibre.com>
Signed-off-by: Kevin Hilman <khilman@baylibre.com>
Signed-off-by: Sasha Levin <sashal@kernel.org>
|
|
[ Upstream commit 11fa9774612decea87144d7f950a9c53a4fe3050 ]
The gpio line names were set in the pinctrl node instead of the gpio node,
at the time it was merged, it worked, but was obviously wrong.
This patch moves the properties to the gpio nodes.
Fixes: 47884c5c746e ("ARM64: dts: meson-gxl-libretech-cc: Add GPIO lines names")
Signed-off-by: Neil Armstrong <narmstrong@baylibre.com>
Signed-off-by: Kevin Hilman <khilman@baylibre.com>
Signed-off-by: Sasha Levin <sashal@kernel.org>
|
|
commit 1e5e929c009559bd7e898ac8e17a5d01037cb057 upstream.
Commit 34993594181d ("arm64: tegra: Enable HDMI on Jetson TX1")
added a regulator for HDMI on the Jetson TX1 platform. This regulator
has an active high enable, but the GPIO specifier for enabling the
regulator incorrectly defines it as active-low. This causes the
following warning to occur on boot ...
WARNING KERN regulator@10 GPIO handle specifies active low - ignored
The fixed-regulator binding does not use the active-low flag from the
gpio specifier and purely relies of the presence of the
'enable-active-high' property to determine if it is active high or low
(if this property is omitted). Fix this warning by setting the GPIO
to active-high in the GPIO specifier which aligns with the presense of
the 'enable-active-high' property.
Fixes: 34993594181d ("arm64: tegra: Enable HDMI on Jetson TX1")
Signed-off-by: Jon Hunter <jonathanh@nvidia.com>
Signed-off-by: Thierry Reding <treding@nvidia.com>
Signed-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
|
|
Use a OV5640 camera driver which works with the i.MX8 MM camera stack.
gst-launch-1.0 v4l2src device='/dev/video0' ! video/x-raw,format=YUY2,width=1920,height=1080,framerate=30/1 ! waylandsink
Signed-off-by: Max Krummenacher <max.krummenacher@toradex.com>
|
|
Signed-off-by: Max Krummenacher <max.krummenacher@toradex.com>
|
|
Ixora board has several differences from the Apalis Evaluation one.
Some important differences are reflected in personalized device-tree files.
Signed-off-by: Oleksandr Suvorov <oleksandr.suvorov@toradex.com>
|
|
This patch adds the device tree to support Toradex Verdin iMX8M Mini a
computer on module which can be used on different carrier boards.
The module consists of an NXP i.MX 8M Mini family SoC, a Rohm BD71847
PMIC, a Gigabit Ethernet PHY, 2 GB of LPDDR4 RAM, an eMMC, an ADC, a
Secure Element, an EEPROM, an RTC, USB host and OTG ports, PCIe and
MIPI-CSI2/DSI interfaces plus optional Bluetooth/Wi-Fi module and CAN
controllers.
Anything that is not self-contained on the module is disabled by
default.
The device tree for the Verdin Development Board includes the module's
device tree and enables the supported peripherals of the carrier board
(the Verdin Development Board supports almost all of them).
Not yet tested:
- all UARTs other than console/debug Verdin UART_3
- push button controller on carrier board
- JTAG
- I2S to Wi-Fi
- I2S to DSI Mezzanine
Not yet working:
- carrier board audio
- MIPI-CSI2
- carrier board power gating
- FTDI control signals and JTAG
Signed-off-by: Max Krummenacher <max.krummenacher@toradex.com>
Signed-off-by: Marcel Ziswiler <marcel.ziswiler@toradex.com>
|
|
This fixes the following device tree compilation issue as introduced by
the previous commit 621db2fdb2e1 ("arm64: dts: apalis-imx8x: add adv7280
to devicetree"):
DTC arch/arm64/boot/dts/freescale/fsl-imx8qxp-apalis-eval.dtb
arch/arm64/boot/dts/freescale/fsl-imx8qxp-apalis-eval.dtb: ERROR
(phandle_references): Reference to non-existent node or label
"adv7280_ep"
Signed-off-by: Marcel Ziswiler <marcel.ziswiler@toradex.com>
|
|
This patch adds the adv7280 to the devicetree and makes changes that
are necessary for parallel-CSI.
Signed-off-by: Philippe Schenker <philippe.schenker@toradex.com>
|
|
Signed-off-by: Philippe Schenker <philippe.schenker@toradex.com>
|
|
Signed-off-by: Philippe Schenker <philippe.schenker@toradex.com>
|
|
This reverts commit c1e7d4fc8c1b9bd599eed9cf848eff3ed9a34637.
Adding pcie_per leads to eventual kernel panics on boot for Apalis
iMX8QM modules.
Related-To: #58016
Signed-off-by: Oleksandr Suvorov <oleksandr.suvorov@toradex.com>
|
|
This reverts commit 81d5c3f7cc7490bde7d388a1a4a23fc38c5b8cae.
Adding pcie_per leads to eventual kernel panics on boot for Apalis
iMX8QM modules.
Related-To: #58016
Signed-off-by: Oleksandr Suvorov <oleksandr.suvorov@toradex.com>
|
|
USB WiFi soldered into Apalis iMX8X module and permamently connect to
usbotg3 via usb 3.0 hub. After system resuming from suspend, WiFi module
fails to communicate via USB interface:
-----------------------------------------------------------
[ 1550.425744] usb usb2: root hub lost power or was reset
[ 1551.756995] usb 2-1: reset SuperSpeed USB device number 2 using cdns-usb3
[ 1552.145771] usb 2-1.1: reset SuperSpeed USB device number 4 using cdns-usb3
[ 1552.196843] usb 2-1.1: PREP_CMD: device in suspended state
[ 1552.202412] usb 2-1.1: mwifiex_usb_disconnect: removing card
[ 1552.208209] usb 2-1.1: info: shutdown mwifiex...
[ 1552.213071] usb 2-1.1: PREP_CMD: device in suspended state
[ 1552.236771] usb 2-1.1: PREP_CMD: device in suspended state
[ 1552.661125] usb 2-1.1:1.0: rebind failed: -517
[ 1552.665648] usb 2-1.1:1.1: rebind failed: -517
[ 1552.670118] usb 2-1.1:1.2: rebind failed: -517
[ 1552.676051] PM: resume devices took 2.276 seconds
[ 1552.681128] OOM killer enabled.
[ 1552.684296] Restarting tasks ...
[ 1552.692860] usb 2-1.1: WLAN FW is active
[ 1552.693897] done.
[ 1552.702695] PM: suspend exit
...
[ 1562.764794] usb 2-1.1: mwifiex_cmd_timeout_func: Timeout cmd id = 0xa9, act = 0x0
[ 1562.772300] usb 2-1.1: num_data_h2c_failure = 0
[ 1562.776865] usb 2-1.1: num_cmd_h2c_failure = 0
[ 1562.781340] usb 2-1.1: is_cmd_timedout = 1
[ 1562.785462] usb 2-1.1: num_tx_timeout = 0
[ 1562.789492] usb 2-1.1: last_cmd_index = 1
[ 1562.793524] usb 2-1.1: last_cmd_id: 00 00 a9 00 00 00 00 00 00 00
[ 1562.799639] usb 2-1.1: last_cmd_act: 00 00 00 00 00 00 00 00 00 00
[ 1562.805842] usb 2-1.1: last_cmd_resp_index = 0
[ 1562.810308] usb 2-1.1: last_cmd_resp_id: 00 00 00 00 00 00 00 00 00 00
[ 1562.816857] usb 2-1.1: last_event_index = 0
[ 1562.821060] usb 2-1.1: last_event: 00 00 00 00 00 00 00 00 00 00
[ 1562.827091] usb 2-1.1: data_sent=0 cmd_sent=1
[ 1562.831470] usb 2-1.1: ps_mode=0 ps_state=0
[ 1562.835700] usb 2-1.1: info: _mwifiex_fw_dpc: unregister device
-----------------------------------------------------------
Enable reset-on-resume feature of usb phy-generic driver fixes this
issue.
Signed-off-by: Oleksandr Suvorov <oleksandr.suvorov@toradex.com>
|
|
USBOTG3 connects to USB Hub placed on SoM. As well as its VBUS enable
signal exports to board X1 connector.
Move a part of usbotg3 node to SoM module too.
Related-to: #57466
Related-to: #55501
Signed-off-by: Oleksandr Suvorov <oleksandr.suvorov@toradex.com>
|
|
Add required pad-wakeup/pad-wakeup-num properties to have
wakeup by gpio key function working.
Signed-off-by: Oleksandr Suvorov <oleksandr.suvorov@toradex.com>
|
|
[ Upstream commit 09bae3b64cb580c95329bd8d16f08f0a5cb81ec9 ]
SPI controller nodes should be named 'spi' rather than 'ssp'. Fixing the
name enables dtc SPI bus checks.
Cc: Chanho Min <chanho.min@lge.com>
Signed-off-by: Rob Herring <robh@kernel.org>
Signed-off-by: Arnd Bergmann <arnd@arndb.de>
Signed-off-by: Sasha Levin <sashal@kernel.org>
|
|
[ Upstream commit e9f0878c4b2004ac19581274c1ae4c61ae3ca70e ]
dtc has new checks for SPI buses. Fix the warnings in node names.
arch/arm64/boot/dts/amd/amd-overdrive.dtb: Warning (spi_bus_bridge): /smb/ssp@e1030000: node name for SPI buses should be 'spi'
arch/arm64/boot/dts/amd/amd-overdrive-rev-b0.dtb: Warning (spi_bus_bridge): /smb/ssp@e1030000: node name for SPI buses should be 'spi'
arch/arm64/boot/dts/amd/amd-overdrive-rev-b1.dtb: Warning (spi_bus_bridge): /smb/ssp@e1030000: node name for SPI buses should be 'spi'
Cc: Brijesh Singh <brijeshkumar.singh@amd.com>
Cc: Suravee Suthikulpanit <suravee.suthikulpanit@amd.com>
Cc: Tom Lendacky <thomas.lendacky@amd.com>
Signed-off-by: Rob Herring <robh@kernel.org>
Signed-off-by: Arnd Bergmann <arnd@arndb.de>
Signed-off-by: Sasha Levin <sashal@kernel.org>
|
|
[ Upstream commit 88a20edf76091ee7f1bb459b89d714d53f0f8940 ]
The microSD card slot in the Sapphire board is not working because of
several issues:
1.- The vmmc power supply is missing in the DTS. It is capable of 3.0V
and has a GPIO-based enable control.
2.- The vqmmc power supply can provide up to 3.3V, but it is capped in
the DTS to just 3.0V because of the vmmc capability. This results in a
conflict from the mmc driver requesting an unsupportable voltage range
from 3.3V to 3.0V (min > max) as reported in dmesg. So, extend the
range up to 3.3V. The hw should be able to stand this 0.3V tolerance.
See mmc_regulator_set_vqmmc in drivers/mmc/core/core.c.
3.- The card detect signal is non-working. There is a known conflict
with jtag, but the workaround in drivers/soc/rockchip/grf.c does not
work. Adding the broken-cd attribute to the DTS fixes the issue.
Signed-off-by: Vicente Bergas <vicencb@gmail.com>
Signed-off-by: Heiko Stuebner <heiko@sntech.de>
Signed-off-by: Sasha Levin <sashal@kernel.org>
|
|
[ Upstream commit 68ecb5c1920c5b98b1e717fd2349fba2ee5d4031 ]
dtc has new checks for SPI buses. The meson dts files have a node named
spi' which causes false positive warnings. As the node is a pinctrl child
node, change the node name to be 'spi-pins' to fix the warnings.
arch/arm64/boot/dts/amlogic/meson-gxbb-nanopi-k2.dtb: Warning (spi_bus_bridge): /soc/periphs@c8834000/pinctrl@4b0/spi: incorrect #address-cells for SPI bus
Cc: Carlo Caione <carlo@caione.org>
Cc: Kevin Hilman <khilman@baylibre.com>
Cc: linux-amlogic@lists.infradead.org
Signed-off-by: Rob Herring <robh@kernel.org>
Signed-off-by: Kevin Hilman <khilman@baylibre.com>
Signed-off-by: Sasha Levin <sashal@kernel.org>
|
|
[ Upstream commit b7eb0e26cc4a212fde09144cd49d4103170d2b9e ]
There is actually several different libretech board with the CC suffix
so the model name is not appropriate here. Update to something more
specific
Reported-by: Da Xue <da@lessconfused.com>
Signed-off-by: Jerome Brunet <jbrunet@baylibre.com>
Signed-off-by: Kevin Hilman <khilman@baylibre.com>
Signed-off-by: Sasha Levin <sashal@kernel.org>
|
|
[ Upstream commit bcdb578a5f5b4aea79441606ab7f0a2e076b4474 ]
The pin is GPIO4-D1 not GPIO1-D1, see schematic, page 15 for reference.
Signed-off-by: Vicente Bergas <vicencb@gmail.com>
Signed-off-by: Heiko Stuebner <heiko@sntech.de>
Signed-off-by: Sasha Levin <sashal@kernel.org>
|
|
[ Upstream commit 6ff7705da8806de45ca1490194f0b4eb07725804 ]
On p2180 sdmmc4 is powered from a fixed 1.8 V regulator.
Signed-off-by: Aapo Vienamo <avienamo@nvidia.com>
Reviewed-by: Mikko Perttunen <mperttunen@nvidia.com>
Signed-off-by: Thierry Reding <treding@nvidia.com>
Signed-off-by: Sasha Levin <sashal@kernel.org>
|
|
[ Upstream commit 480f58cdbe392d4387a2193b6131a277e0111dd0 ]
According to the NanoPi-A64 schematics, DCDC1 is connected to a voltage
rail named "VDD_SYS_3.3V". All users seem to expect 3.3V here: the
Ethernet PHY, the uSD card slot, the camera interface and the GPIO pins
on the headers.
Fix up the voltage on the regulator to lift it up to 3.3V.
Signed-off-by: Andre Przywara <andre.przywara@arm.com>
Acked-by: Maxime Ripard <maxime.ripard@bootlin.com>
Signed-off-by: Chen-Yu Tsai <wens@csie.org>
Signed-off-by: Sasha Levin <sashal@kernel.org>
|
|
[ Upstream commit 93366b49a35f3a190052734b3f32c8fe2535b53f ]
The Olinuxino board uses DDR3L chips which are supposed to be driven
with 1.35V. The reset default of the AXP is properly set to 1.36V.
While technically the chips can also run at 1.5 volts, changing the
voltage on the fly while booting Linux is asking for trouble. Also
running at a lower voltage saves power.
So fix the DCDC5 value to match the actual board design.
Signed-off-by: Andre Przywara <andre.przywara@arm.com>
Tested-by: Martin Lucina <martin@lucina.net>
Acked-by: Maxime Ripard <maxime.ripard@bootlin.com>
Signed-off-by: Chen-Yu Tsai <wens@csie.org>
Signed-off-by: Sasha Levin <sashal@kernel.org>
|
