Age | Commit message (Collapse) | Author |
|
RESET and CONNECT come out of reset with pull downs enabled. Keep
that in the pin muxing.
These pins are switched to output during the hub configuration and then
controlled as needed. The datasheet specifically states that CONNECT
must not be driven when RESET is low, so keeping the pull downs is
less likely to violate the spec.
The INT pin has an external pull up, so keeping the pull down makes
the system draw more power.
Related-to: ELB-2702
Signed-off-by: Max Krummenacher <max.krummenacher@toradex.com>
|
|
Related-to: ELB-2529
Signed-off-by: Philippe Schenker <philippe.schenker@toradex.com>
|
|
Related-to: ELB-2324
Signed-off-by: Max Krummenacher <max.krummenacher@toradex.com>
|
|
This unifies node names and adds a reference to the sound node.
Related-to: ELB-2324
Signed-off-by: Max Krummenacher <max.krummenacher@toradex.com>
|
|
The write protect switch is not connected. Specify that to get rid of:
mmc1: host does not support reading read-only switch, assuming write-enable
Signed-off-by: Max Krummenacher <max.krummenacher@toradex.com>
|
|
Add Colibri SODIMM numbers as GPIO line names on module level. The GPIO
lines with a name are all available on the SODIMM edge connector of the
Colibri iMX7 module and therefore a customer might use it as a GPIO. The
Toradex Evaluation Board has the SODIMM numbers printed on the silk-
screen. This allows a customer to quickly control a GPIO on a pin-header
by using the name printed next to it.
Putting the GPIO line name on module level makes sure that a customer
gets a reasonable default. If more meaningful names are available on a
custom carrier board, the user can overwrite the line names in a carrier
board level device tree.
The eMMC based modules share all GPIO names except two GPIOs on bank 6
which are not available on the raw NAND devices. Hence overwrite GPIO
line names of bank 6 in the eMMC specific device tree file.
Signed-off-by: Stefan Agner <stefan.agner@toradex.com>
Reviewed-by: Philippe Schenker <philippe.schenker@toradex.com>
Signed-off-by: Shawn Guo <shawnguo@kernel.org>
(cherry picked from commit 119c98f16e704e4c85522f6e22c9c819c21c4128)
Related-to: ELB-2309
Signed-off-by: Philippe Schenker <philippe.schenker@toradex.com>
|
|
The 2nd CAN controller is not assembled in the standard SKUs.
Thus disable it and prevent unneeded probing and kernel output.
Signed-off-by: Max Krummenacher <max.krummenacher@toradex.com>
|
|
The DSI to other display technologies bridges are modules. Currently two
bridges are enabled in the device tree, HDMI and LVDS. However using the
module with the LVDS bridge requires further changes to the device tree.
Thus disable it and prevent unneeded probing and kernel output.
Signed-off-by: Max Krummenacher <max.krummenacher@toradex.com>
|
|
Signed-off-by: Max Krummenacher <max.krummenacher@toradex.com>
|
|
With out this, the suspend sequence will stop and the system resumes
immediately.
Signed-off-by: Max Krummenacher <max.krummenacher@toradex.com>
|
|
The iomuxc pinctrl-0 property is set with pinctrl nodes muxed for
potential user space use in the module specific device tree.
In order to keep them copy the full list here and amend the additional
pinctrl_uart24_forceoff.
Signed-off-by: Max Krummenacher <max.krummenacher@toradex.com>
|
|
I understood this property as I could reset something that is on this
USB controller. This was a wrong understanding and the property
reset-gpio is meant to reset the IP inside the SoC.
Remove this for fixing the USB issue.
Related-to: ELB-2592
Signed-off-by: Philippe Schenker <philippe.schenker@toradex.com>
|
|
Fixes: d4d419f1b24e
apalis/colibri_imx6/-imx6ull/_imx7/-imx8/8x_defconfig: config refresh
Signed-off-by: Philippe Schenker <philippe.schenker@toradex.com>
|
|
Implicitly disable HDMI audio on the module level as it is disabled by
default in imx6qdl.dtsi. It can be enabled on the carrier board level
(e.g. imx6q-apalis-eval.dts, imx6q-apalis-ixora.dts,
imx6q-apalis-ixora-v1.1.dts or imx6q-apalis-ixora-v1.2.dts) if required.
Signed-off-by: Marcel Ziswiler <marcel.ziswiler@toradex.com>
|
|
Enable WIRELESS_EXT and WEXT_PRIV options for the backported
rtl81288eu driver.
Related-to: ELB-2388
Signed-off-by: Oleksandr Suvorov <oleksandr.suvorov@toradex.com>
|
|
Disabling all wireless drivers and cfg80211 module makes able
to completely avoid interferences with backported drivers.
Related-to: ELB-2388
Signed-off-by: Oleksandr Suvorov <oleksandr.suvorov@toradex.com>
|
|
Enable WIRELESS_EXT and WEXT_PRIV options as needed for the backported
rtl81288eu driver.
Related-to: ELB-2388
Signed-off-by: Oleksandr Suvorov <oleksandr.suvorov@toradex.com>
|
|
Disabling all wireless drivers and cfg80211 module makes able
to completely avoid interferences with backported drivers.
Related-to: ELB-2388
Signed-off-by: Oleksandr Suvorov <oleksandr.suvorov@toradex.com>
|
|
As suggested by the reference manual in a note in chapter 13.2
this commit disables the keeper and enables a 100k pull-down on the
adc pins.
Related-to: ELB-2690
Signed-off-by: Philippe Schenker <philippe.schenker@toradex.com>
|
|
There are some unstable drivers in the kernel.
The stable versions of these drivers present in backported-5.4 package.
Remove duplicated mwifiex_sdio and mwifiex_usb.
Related-to: ELB-2388
Signed-off-by: Oleksandr Suvorov <oleksandr.suvorov@toradex.com>
|
|
There are some unstable drivers in the kernel.
The stable versions of these drivers present in backported-5.4 package.
Remove unstable rtl8188eu, mwifiex_sdio, mwifiex_usb.
Related-to: ELB-2388
Signed-off-by: Oleksandr Suvorov <oleksandr.suvorov@toradex.com>
|
|
Related-to: ELB-2684
Signed-off-by: Philippe Schenker <philippe.schenker@toradex.com>
|
|
Further clean-up modularising it some more.
BTW: Changing BT_MRVL, BT_MRVL_SDIO, CFG80211 and MAC80211 to modules
will make it co-exist with our latest backports efforts.
Related-to: ELB-2388
Signed-off-by: Marcel Ziswiler <marcel.ziswiler@toradex.com>
|
|
The driver mwifiex_sdio stucks after the wifi firmware crash.
Enabling asynchronous interrupts processing in sdio driver
fixes this issue and allows the mwifiex_sdio driver to be reloaded
and continue operates successfully.
Related-to: ELB-2596
Signed-off-by: Oleksandr Suvorov <oleksandr.suvorov@toradex.com>
|
|
Signed-off-by: Marcel Ziswiler <marcel.ziswiler@toradex.com>
|
|
The driver mwifiex_sdio stucks after the wifi firmware crash.
Enabling asynchronous interrupts processing in sdio driver
fixes this issue and allows the mwifiex_sdio driver to be reloaded
and continue operates successfully.
Works better with the driver from the backported-5.4 package.
Related-to: ELB-2596
Signed-off-by: Oleksandr Suvorov <oleksandr.suvorov@toradex.com>
|
|
Refresh kernel configs adding some more USB as well as PCIe options
where applicable plus synchronise some more accross all modules.
Signed-off-by: Marcel Ziswiler <marcel.ziswiler@toradex.com>
|
|
Some comments made it through. SPI is tested that it works and those
comments are no longer necessary-
Signed-off-by: Philippe Schenker <philippe.schenker@toradex.com>
|
|
There is a hardware issue with the clock lines. It barely works
with 200MHz with SD-Cards but not with SDIO cards. Therefore put
a safe value in there until the hardware issue is resolved
Related-to: ELB-1974
Related-to: HAR-3252
Signed-off-by: Philippe Schenker <philippe.schenker@toradex.com>
|
|
use of rgmii-id instead of rgmii to denote use of rxc and txc delay on the phy.
Related-to: ELB-2581
Signed-off-by: Philippe Schenker <philippe.schenker@toradex.com>
|
|
Until now a PHY-fixup in mach-imx set our rgmii timing correctly. For
the PHY KSZ9131 there is no PHY-fixup in mach-imx. To support this PHY
too, use rgmii-id.
For the now used KSZ9031 nothing will change, as rgmii-id is only
implemented and supported by the KSZ9131.
Signed-off-by: Philippe Schenker <philippe.schenker@toradex.com>
Signed-off-by: David S. Miller <davem@davemloft.net>
(cherry picked from commit 1b68480b945e51ba879496d3f9ff5a5addd82007)
We have a PHY-fixup in our downstream Linux. However this patch makes
anyway sense to apply as it documents the rgmii mode properly and
won't brake anything.
Related-to: ELB-2581
Signed-off-by: Philippe Schenker <philippe.schenker@toradex.com>
|
|
This reverts commit 118d904a302114b323e3464bceab64bfc26868e2.
There is now a mainline solution for that. Drop this solution in favor
of the upstream one. We will use "rgmii-id" tag now to declare that
delays.
Related-to: ELB-2581
Signed-off-by: Philippe Schenker <philippe.schenker@toradex.com>
|
|
Add support of non-wifi Toradex Verdin iMX8MM module
on the Development board.
Related-to: ELB-2322
Signed-off-by: Oleksandr Suvorov <oleksandr.suvorov@toradex.com>
|
|
Add the mark of wi-fi version of Toradex Verdin iMX8MM module
to a devicetree file name.
Related-to: ELB-2322
Signed-off-by: Oleksandr Suvorov <oleksandr.suvorov@toradex.com>
|
|
Split the common devicetree file to two layers:
- Toradex Verdin iMX8MM WB;
- Toradex Verdin Development board.
Related-to: ELB-2322
Signed-off-by: Oleksandr Suvorov <oleksandr.suvorov@toradex.com>
|
|
Move the on-module Wi-Fi part of a Toradex Verdin iMX8MM module
to a separate file.
Related-to: ELB-2322
Signed-off-by: Oleksandr Suvorov <oleksandr.suvorov@toradex.com>
|
|
Fix the minor code formatting issue.
Related-to: ELB-2322
Signed-off-by: Oleksandr Suvorov <oleksandr.suvorov@toradex.com>
|
|
The mwifiex Wi-Fi driver in kernel-4.14-2.3.x-imx works unstable.
The same driver in backports-5.4 works well.
Backports-5.4 requires the undocumented build option CRYPTO_HASH_INFO.
This option is selected by enabled ASYMMETRIC_PUBLIC_KEY_SUBTYPE.
This makes able to build and use the Wi-Fi driver mwifiex_sdio, that works
stable unlike the original driver in 4.14-2.3.x-imx.
Related-to: ELB-2388
Signed-off-by: Oleksandr Suvorov <oleksandr.suvorov@toradex.com>
|
|
The mwifiex Wi-Fi driver in kernel-4.14-2.3.x-imx works unstable.
The same driver in backports-5.4 works well.
Backports-5.4 requires the undocumented build option CRYPTO_HASH_INFO.
This option is selected by enabled ASYMMETRIC_PUBLIC_KEY_SUBTYPE.
This makes able to build and use the Wi-Fi driver mwifiex_sdio, that works
stable unlike the original driver in 4.14-2.3.x-imx.
Related-to: ELB-2388
Signed-off-by: Oleksandr Suvorov <oleksandr.suvorov@toradex.com>
|
|
Out-of-the-box the analogue camera adapter fails detecting with the
following error:
[ 6.503046] adv7280 2-0021: adv7280_probe:Analog Device adv7280 not detected -6!
Unfortunately, the camera seems to be held in reset due to the BL_ON pin
not being serviced.
Fix this by hogging the camera_nreset aka BL_ON pin to output high.
Related-to: ELB-2580
Signed-off-by: Marcel Ziswiler <marcel.ziswiler@toradex.com>
|
|
Related-to: ELB-2316
Signed-off-by: Philippe Schenker <philippe.schenker@toradex.com>
|
|
The dprX_channelY, pixel-combiner and prgX nodes need to be enabled
to use the g2d functionality.
Thus move those nodes into the common fsl-imx8qxp-colibri-eval-v3.dtsi, so that
fsl-imx8qxp-colibri-eval-v3.dts also gets them enabled.
Signed-off-by: Max Krummenacher <max.krummenacher@toradex.com>
|
|
Add CTRL_WAKE1_MICO# as a wakeup source.
Signed-off-by: Max Krummenacher <max.krummenacher@toradex.com>
|
|
Commit 833f2cbf7091 ("ARM: dts: imx6: change the core clock of spdif")
changed many more clocks than only the SPDIF core clock as stated in
the commit message.
The MLB clock has been added and this causes SPDIF regression as
reported by Xavi Drudis Ferran and also in this forum post:
https://forum.digikey.com/thread/34240
The MX6Q Reference Manual does not mention that MLB is a clock related
to SPDIF, so change it back to a dummy clock to restore SPDIF
functionality.
Thanks to Ambika for providing the fix at:
https://community.nxp.com/thread/387131
Fixes: 833f2cbf7091 ("ARM: dts: imx6: change the core clock of spdif")
Cc: <stable@vger.kernel.org> # 4.4.x
Reported-by: Xavi Drudis Ferran <xdrudis@tinet.cat>
Signed-off-by: Fabio Estevam <fabio.estevam@nxp.com>
Tested-by: Xavi Drudis Ferran <xdrudis@tinet.cat>
Signed-off-by: Shawn Guo <shawnguo@kernel.org>
(cherry picked from commit f065e9e4addd75c21bb976bb2558648bf4f61de6)
This fix was correct, but overwritten by commit 833f2cbf7091099baee28136dc68678e974c0ac5.
MLB (Media Local Bus) Clock is in fact not related to SPDIF according to the MX6Q Reference
Manual. Tested playback and record on pulseaudio with 44.1kHz samples.
Signed-off-by: Gerard Salvatella <gerard.salvatella@toradex.com>
Acked-by: Max Krummenacher <max.krummenacher@toradex.com>
(cherry picked from commit 58e5313d36b969029d76b1ef45d3224c8557af75)
|
|
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>
|
|
The MAC of the i.MX6 SoC is compliant with RGMII v1.3. The KSZ9131 PHY
is like KSZ9031 adhering to RGMII v2.0 specification. This means the
MAC should provide a delay to the TXC line. Because the i.MX6 MAC does
not provide this delay this has to be done in the PHY.
This patch adds by default ~1.4ns delay to the TXC line. This should
be good for all boards that have all RGMII signals routed with the
same length.
The KSZ9131 has relatively high tolerances on skew registers from
MMD 2.4 to MMD 2.8. Therefore the new DLL-based delay of 2ns is used
and then as little as possibly subtracted from that so we get more
accurate delay. This is actually needed because the i.MX6 SoC has
an asyn skew on TXC from -100ps to 900ps.
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>
|