Age | Commit message (Collapse) | Author |
|
Correct ldo1/ldo2 voltage as below:
ldo1 --NVCC_SNVS_1V8
ldo2 --VDD_SNVS_0V8
Signed-off-by: Robin Gong <yibin.gong@nxp.com>
Reviewed-by: Jacky Bai <ping.bai@nxp.com>
(cherry picked from commit 6e1db954c1261c9a8a40f7c4e33f03173c4d05b6)
(cherry picked from commit 8574922dd583141a332be58fe1656ee05c9e5dd4)
|
|
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>
|
|
memory
Need flush outer cache after zero CMA allocated memory on arm32 platform.
Change-Id: Ieaa7c62bf65e4490f904d68bed1fa16fb7c5d8fa
Signed-off-by: Richard Liu <xuegang.liu@nxp.com>
Reviewed-by: Bing Song <bing.song@nxp.com>
(cherry picked from commit 9e51da339eb290f35eb79d9acc0ea147d8bdf0cf)
|
|
ION CMA memory default is cacheable, need flush cache after memset(),
else cache and physical memory not sync may cause problem.
Issue case:
VPU Video playback or GPU render have dirty line issue.
Root cause:
ION CMA allocate cacheable buffer and do memset(), some data still in cache
not in physical memory, VPU or GPU write the buffer with physical address,
or user call ion_mmap() to map the buffer through pgprot_writecombine() as
no-cache and write the buffer, later some CPU cache access trigger cache
flush, previous memset() data go to physical memory as dirty data.
Change-Id: I82b4cb61bbe6cffc687d452f9f81c1e35914d2f1
Signed-off-by: Richard Liu <xuegang.liu@nxp.com>
(cherry picked from commit 5d360f25f3523311b5f478b7b1c7bc9020cfda58)
|
|
Fixes: d4d419f1b24e
apalis/colibri_imx6/-imx6ull/_imx7/-imx8/8x_defconfig: config refresh
Signed-off-by: Philippe Schenker <philippe.schenker@toradex.com>
|
|
kfifo memory size must roundup to power-of-two if it is
allocated by driver. Because kfifo elements size will
roundup to power-of-two in kfifo_init(), must guarantee
allocated memory is enough.
Signed-off-by: Shijie Qin <shijie.qin@nxp.com>
Reviewed-by: ming_qian <ming.qian@nxp.com>
(cherry picked from commit c900bb4cd98efc43dddfb18d96c8af358e804481)
|
|
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>
|
|
The config option WIRELESS_EXT and WEXT_PRIV use to build external
drivers, such as backports. Make these options storable in config file
to be able to set them independently.
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>
|
|
This reverts commit dc1f576a8423568cb16eb077f7406c08affec9ec.
This patch breaks dma for HDMI-Audio. So reverting it.
Signed-off-by: Philippe Schenker <philippe.schenker@toradex.com>
Conflicts:
drivers/dma/imx-sdma.c
|
|
Backport of the upstreamed and not merged patch [1].
It fixes the crash like [2].
If we disconnect a device before completing the connection, connection
will no longer be available in connection list, thus conn will be NULL.
[1] https://www.spinics.net/lists/linux-bluetooth/msg70764.html
[2]
[ 4960.112410] Unable to handle kernel NULL pointer dereference at virtual address 0000001a
[ 4961.120795] Mem abort info:
[ 4961.128933] Exception class = DABT (current EL), IL = 32 bits
[ 4961.140189] SET = 0, FnV = 0
[ 4961.148719] EA = 0, S1PTW = 0
[ 4961.157065] Data abort info:
[ 4961.165047] ISV = 0, ISS = 0x00000004
[ 4961.173975] CM = 0, WnR = 0
[ 4961.181934] user pgtable: 4k pages, 48-bit VAs, pgd = ffff80084f467000
[ 4961.193579] [000000000000001a] *pgd=0000000000000000
[ 4961.201942] Internal error: Oops: 96000004 [#1] PREEMPT SMP
[ 4961.210271] Modules linked in: veth xt_nat xt_tcpudp ipt_MASQUERADE nf_nat_masquerade_ipv4 iptable_nat nf_conntrack_ipv4 nf_defrag_ipv4 nf_nat_ipv4 xt_addrtype iptable_filter ip_tables xt_conntrack x_tables nf_nat nf_conntrack libcrc32c br_netfilter bridge stp overlay crc32_ce crct10dif_ce mwifiex_pcie mwifiex cdc_acm galcore(O)
[ 4961.255701] Process kworker/u13:0 (pid: 12632, stack limit = 0xffff00002e5e8000)
[ 4961.268662] CPU: 3 PID: 12632 Comm: kworker/u13:0 Tainted: G O 4.14.159-4.0.0-devel+git.fff496c2a1bd #1
[ 4961.284881] Hardware name: Toradex Apalis iMX8QM/QP on Apalis Evaluation Board (DT)
[ 4961.298330] Workqueue: hci0 hci_rx_work
[ 4961.307903] task: ffff80084faa8d80 task.stack: ffff00002e5e8000
[ 4961.319611] PC is at hci_connect_le_scan_cleanup+0x14/0x128
[ 4961.330986] LR is at create_le_conn_complete+0xec/0x108
Signed-off-by: Thomas Gagneret <tgagneret@xxxxxxxxxxx>
Signed-off-by: Oleksandr Suvorov <oleksandr.suvorov@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>
|
|
This is a temporary workround for the case when:
-SWIOTLB is used for DMA bounce buffering AND
-data to be DMA-ed is mapped DMA_FROM_DEVICE and device only partially
overwrites the "original" data AND
-it's expected that the "original" data that was not overwritten
by the device to be untouched
As discussed in upstream, the proper fix should be:
-either an extension of the DMA API OR
-a workaround in the device driver (considering these cases are rarely
met in practice)
Since both alternatives are not trivial (to say the least),
add a workaround for the few cases matching the error conditions
listed above.
Link: https://lore.kernel.org/lkml/VI1PR0402MB348537CB86926B3E6D1DBE0A98070@VI1PR0402MB3485.eurprd04.prod.outlook.com/
Link: https://lore.kernel.org/lkml/20190522072018.10660-1-horia.geanta@nxp.com/
Signed-off-by: Horia Geantă <horia.geanta@nxp.com>
Reviewed-by: Valentin Ciocoi Radulescu <valentin.ciocoi@nxp.com>
Reviewed-by: Iuliana Prodan <iuliana.prodan@nxp.com>
|
|
The incorrect traversal of the scatterlist, during the linearization phase
lead to computing the hash value of the wrong input buffer.
New implementation uses scatterwalk_map_and_copy()
to address this issue.
Fixes: 15b59e7c3733 ("crypto: mxs - Add Freescale MXS DCP driver")
Signed-off-by: Rosioru Dragos <dragos.rosioru@nxp.com>
Acked-by: Horia Geantă <horia.geanta@nxp.com>
Signed-off-by: Leonard Crestez <leonard.crestez@nxp.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>
|
|
The KSZ9131 provides DLL controlled delays on RXC and TXC lines. This
patch makes use of those delays. The information which delays should
be enabled or disabled comes from the interface names, documented in
ethernet-controller.yaml:
rgmii: Disable RXC and TXC delays
rgmii-id: Enable RXC and TXC delays
rgmii-txid: Enable only TXC delay, disable RXC delay
rgmii-rxid: Enable onlx RXC delay, disable TXC delay
Signed-off-by: Philippe Schenker <philippe.schenker@toradex.com>
Signed-off-by: David S. Miller <davem@davemloft.net>
(cherry picked from commit bd734a742d5533fb9190ecd8cf25befc1f759a5b)
Replace phy_modify_mmd with phy_read_mmd and phy_write_mmd.
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>
|
|
This reverts commit 4bdc5d8f4f1e6ec472074a6a4fc2e2061cdb1c8d.
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>
|
|
This reverts commit f49da0d7dbf67030f7e12a94fd18a7f1a0b845e0.
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>
|
|
Based on imx_4.1x kernel, enable the PCIEB on i.MX8QM MEK baseboard.
Regarding to the base board HW limitation(two Disable#) are not
connected. Only the standard PCIe EP device is supported on PCIEB port.
Signed-off-by: Richard Zhu <hongxing.zhu@nxp.com>
(cherry picked from commit d0331d84e5a14d6e2520d04540d1e893d75bd678)
|
|
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>
|
|
Suggest to use vmalloc for fifo entity.
Then use kfifo_init to init the fifo structure.
Then we do not have to require contiguous memory from buddy,
especially in a high pressure of memory resource.
Signed-off-by: Ming Qian <ming.qian@nxp.com>
(cherry picked from commit 0cd3c661b95ecb273da5ee76fe7353ab7abd38c9)
|
|
Signed-off-by: Wojciech Slenska <wojciech.slenska@gmail.com>
Signed-off-by: Philippe Schenker <philippe.schenker@toradex.com>
Signed-off-by: Stefan Agner <stefan.agner@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>
|
|
Make Epson RX8130 device tree and ACPI aware.
Fixes: ee0981be7704 ("rtc: ds1307: Add support for Epson RX8130CE")
Signed-off-by: Bastian Stender <bst@pengutronix.de>
Signed-off-by: Alexandre Belloni <alexandre.belloni@free-electrons.com>
(cherry picked from commit 47dd47292828a552d62d0e68b7cd6bdc99d9e0aa)
|
|
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>
|