- Mar 13, 2024
-
-
Robert Nelson authored
6.1.80-ti-arm64-r33 bb.org_defconfig 6.1 TI Delta: https://github.com/RobertCNelson/ti-linux-kernel/compare/a6174d6c4ff531039c677079321888a9a3f9951c...4d3502a8b8db0395db8ce0c6501795de2ec240c9 BBDTBS: BeagleBoard-DeviceTrees@2da4a657 WIRELESS_REGDB: https://git.kernel.org/pub/scm/linux/kernel/git/wens/wireless-regdb.git/commit/?id=454130065a5857bc0c534d5c52ed17a97b704c36 WPANUSB: beagleconnect/linux/wpanusb@6aa9bf65 Signed-off-by:
Robert Nelson <robertcnelson@gmail.com>
-
Robert Nelson authored
-
Robert Nelson authored
Signed-off-by:
Robert Nelson <robertcnelson@gmail.com>
-
Robert Nelson authored
Signed-off-by:
Robert Nelson <robertcnelson@gmail.com>
-
Ben Hutchings authored
We want to enable use of the Android ashmem and binder drivers to support Anbox, but they should not be built-in as that would waste resources and increase security attack surface on systems that don't need them. Export the currently un-exported symbols they depend on.
-
Ben Hutchings authored
We want to enable use of the Android ashmem and binder drivers to support Anbox, but they should not be built-in as that would waste resources and increase security attack surface on systems that don't need them. - Add a MODULE_LICENSE declaration to ashmem - Change the Makefiles to build each driver as an object with the "_linux" suffix (which is what Anbox expects) - Change config symbol types to tristate Update: In upstream commit 721412ed titled "staging: remove ashmem" the ashmem driver was removed entirely. Secondary commit message: "The mainline replacement for ashmem is memfd, so remove the legacy code from drivers/staging/" Consequently, the ashmem part of this patch has been removed.
-
Ayush Singh authored
Signed-off-by:
Ayush Singh <ayushdevel1325@gmail.com>
-
Vaishnav Achath authored
add of_find_serdev_controller_by_node to obtain a serdev_controller from the device_node, which can help if the serdev_device is not described over device tree and instantiation of the device happens from a different driver, for the same purpose an option to not delete an empty serdev controller is added. Signed-off-by:
Vaishnav M A <vaishnav@beagleboard.org> Signed-off-by:
Ayush Singh <ayushdevel1325@gmail.com>
-
Ayush Singh authored
This externalizes and exports the symbol of_find_spi_controller_by_node() from the SPI core akin to how of_find_i2c_adapter_by_node() is already available. As we will need this also for non-dynamic OF setups, we move it under a CONFIG_OF check. Signed-off-by:
Ayush Singh <ayushdevel1325@gmail.com>
-
Ayush Singh authored
Signed-off-by:
Ayush Singh <ayushdevel1325@gmail.com>
-
Ayush Singh authored
Signed-off-by:
Ayush Singh <ayushdevel1325@gmail.com>
-
Kishon Vijay Abraham I authored
Lets drive Sierra clock output and workaround a TIFS/DM bug for now. Signed-off-by:
Kishon Vijay Abraham I <kishon@ti.com>
-
Jason Kridner authored
-
Ayush Singh authored
Add the Greybus host driver for BeaglePlay board by BeagleBoard.org. The current greybus setup involves running SVC in a user-space application (GBridge) and using netlink to communicate with kernel space. GBridge itself uses wpanusb kernel driver, so the greybus messages travel from kernel space (gb_netlink) to user-space (GBridge) and then back to kernel space (wpanusb) before reaching CC1352. This driver directly communicates with CC1352 (running SVC Zephyr application). Thus, it simplifies the complete greybus setup eliminating user-space GBridge. This driver is responsible for the following: - Start SVC (CC1352) on driver load. - Send/Receive Greybus messages to/from CC1352 using HDLC over UART. - Print Logs from CC1352. - Stop SVC (CC1352) on driver load. Signed-off-by:
Ayush Singh <ayushdevel1325@gmail.com> Link: https://lore.kernel.org/r/20231017101116.178041-3-ayushdevel1325@gmail.com Signed-off-by:
Greg Kroah-Hartman <gregkh@linuxfoundation.org>
-
Ayush Singh authored
Add DT bindings for Texas Instruments Simplelink CC1352P7 wireless MCU BeaglePlay has CC1352P7 co-processor connected to the main AM62 (running Linux) over UART. In the BeagleConnect Technology, CC1352 is responsible for handling 6LoWPAN communication with beagleconnect freedom nodes as well as their discovery. Signed-off-by:
Ayush Singh <ayushdevel1325@gmail.com> Reviewed-by:
Krzysztof Kozlowski <krzysztof.kozlowski@linaro.org> Reviewed-by:
Nishanth Menon <nm@ti.com> Link: https://lore.kernel.org/r/20231017101116.178041-2-ayushdevel1325@gmail.com Signed-off-by:
Greg Kroah-Hartman <gregkh@linuxfoundation.org>
-
Robert Nelson authored
Reference: rpi-6.1.y Signed-off-by:
Robert Nelson <robertcnelson@gmail.com>
-
Robert Nelson authored
Signed-off-by:
Robert Nelson <robertcnelson@gmail.com>
-
Matthijs van Duin authored
"uio" for generic use "ti,pruss-shmem" for backwards compatibility the of_id module parameter is still supported to add another id
-
Matthijs van Duin authored
-
Robert Nelson authored
Reference: v5.10.212 Signed-off-by:
Robert Nelson <robertcnelson@gmail.com>
-
Jason Kridner authored
From https://github.com/statropy/wpanusb
-
Vaishnav Achath authored
IMX390 is a 2.1MP raw (bayer) sensor, the rugged camera module by D3 [1] packages it with an FPDLink-III serializer (DS90UB953) for use with sensor fusion setups using FPDLink-III deserializer boards. Add overlays for the cases when the modules are connected to ports on the DS90UB960 deserializer in fusion EVM when connected to third CSI port in a device like J784S4 or AM69. This helps to enable 12 camera use cases on AM69 SK. 1 - https://www.d3engineering.co/product/designcore-d3rcm-imx390-953-rugged-camera-module/ Signed-off-by:
Vaishnav Achath <vaishnav.a@ti.com> Acked-by:
Jai Luthra <j-luthra@ti.com> Tested-by:
Abhay Chirania <a-chirania@ti.com>
-
Vaishnav Achath authored
Fusion application board [1] can be used to connect multiple FPDLink-III based sensors to TI EVMs. Upto 12x sensors can simultaneously stream over the three CSI RX ports on J784S4/AM69, add an overlay to support the fusion board connected to CSI port 2(CSI_AUX port) on AM69 SK to enable 12 camera applications with AM69 SK. Link: https://svtronics.com/portfolio/evm577pfusion-v1-0-fusion/ [1] Signed-off-by:
Vaishnav Achath <vaishnav.a@ti.com> Acked-by:
Jai Luthra <j-luthra@ti.com> Tested-by:
Abhay Chirania <a-chirania@ti.com>
-
Vaishnav Achath authored
Fusion application board [1] can be used to connect multiple FPDLink-III based sensors to TI EVMs. Upto 8x sensors can simultaneously stream over the two CSI RX ports on J722S EVM. Link: https://svtronics.com/portfolio/evm577pfusion-v1-0-fusion/ [1] Signed-off-by:
Vaishnav Achath <vaishnav.a@ti.com> Acked-by:
Jai Luthra <j-luthra@ti.com> Tested-by:
Abhay Chirania <a-chirania@ti.com>
-
Vaishnav Achath authored
Arducam's UC-A09 is a V3Link "mini" fusion board. [1] It can be used to connect multiple V3Link (and FPD-III) based cameras to TI EVMs using a single 22-pin FFC (4-lane) CSI2 connector. Add an overlay to support it on J722S EVM. [1] https://www.arducam.com/downloads/datasheet/Arducam_V3Link_Datasheet.pdf Signed-off-by:
Vaishnav Achath <vaishnav.a@ti.com> Acked-by:
Jai Luthra <j-luthra@ti.com> Tested-by:
Abhay Chirania <a-chirania@ti.com>
-
Vaishnav Achath authored
Arducam's UC-A09 is a V3Link "mini" fusion board. [1] It can be used to connect multiple V3Link (and FPD-III) based cameras to TI EVMs using a single 22-pin FFC (4-lane) CSI2 connector. Add an overlay to support it on AM69 SK, Also while at it fix the missing symbol export on k3-am69-sk-csi2-fpdlink-fusion overlay. [1] https://www.arducam.com/downloads/datasheet/Arducam_V3Link_Datasheet.pdf Signed-off-by:
Vaishnav Achath <vaishnav.a@ti.com> Acked-by:
Jai Luthra <j-luthra@ti.com> Tested-by:
Abhay Chirania <a-chirania@ti.com>
-
Vaishnav Achath authored
Arducam's UC-A09 is a V3Link "mini" fusion board. [1] It can be used to connect multiple V3Link (and FPD-III) based cameras to TI EVMs using a single 22-pin FFC (4-lane) CSI2 connector. Add an overlay to support it on AM68 SK, Also while at it fix the missing symbol export on k3-am68-sk-fpdlink-fusion overlay. [1] https://www.arducam.com/downloads/datasheet/Arducam_V3Link_Datasheet.pdf Signed-off-by:
Vaishnav Achath <vaishnav.a@ti.com> Acked-by:
Jai Luthra <j-luthra@ti.com> Tested-by:
Abhay Chirania <a-chirania@ti.com>
-
Sinthu Raja authored
Enable support to use Intel Wireless Next-Gen WiFi adapters for AM57x platform. Signed-off-by:
Sinthu Raja <sinthu.raja@ti.com> Reviewed-by:
Udit Kumar <u-kumar1@ti.com>
-
Devarsh Thakkar authored
Re-enable hardware on system resume before resuming the v4l2 m2m jobs so that jobs that were queued prior to system suspend can be resumed back. This helps support scenario to resume back from active use-case where a jpeg encoding use-case was already running before system got suspended. Signed-off-by:
Devarsh Thakkar <devarsht@ti.com>
-
Jayesh Choudhary authored
Add the gpio hog for HDMI_LS_OE for HDMI ESD device TPD12S016PWR. Without this signal pulled up, TPD12S016PWR is unable to pass through the I2C request to HDMI connector which results in EDID not being read. After that fallback mode 1024x768 and smaller resolutions are added as valid modes. Pull up the control pin HDMI_LS_OE to get EDID working. Signed-off-by:
Jayesh Choudhary <j-choudhary@ti.com> Reviewed-by:
Udit Kumar <u-kumar1@ti.com>
-
Jayesh Choudhary authored
Currently, mode_valid hook returns all mode as valid. Add the check for the maximum and minimum pixel clock that the bridge can support while validating a mode. Signed-off-by:
Jayesh Choudhary <j-choudhary@ti.com> Reviewed-by:
Aradhya Bhatia <a-bhatia1@ti.com>
-
- Mar 12, 2024
-
-
Ravi Gunasekaran authored
The VLAN table is a shared memory between the two ports/slices in a ICSSG cluster and this may lead to race condition when the common code paths for both ports are executed in different CPUs. Fix the race condition access by locking the shared memory access. Signed-off-by:
Ravi Gunasekaran <r-gunasekaran@ti.com>
-
Ravi Gunasekaran authored
commit 4322af8c ("net: hsr: Disable promiscuous mode in offload mode") disables promiscuous mode of slave devices while creating an HSR interface. But while deleting the HSR interface, it does not take care of it. It decreases the promiscuous mode count, which eventually enables promiscuous mode on the slave devices when creating HSR interface again. Fix this by not decrementing the promiscuous mode count while deleting the HSR interface when offload is enabled. Fixes: 4322af8c ("net: hsr: Disable promiscuous mode in offload mode") Signed-off-by:
Ravi Gunasekaran <r-gunasekaran@ti.com>
-
Ravi Gunasekaran authored
In HSR mode, the netdev notifier does not take care of the unlinking event of the upper net device. Fix this. Signed-off-by:
Ravi Gunasekaran <r-gunasekaran@ti.com>
-
Ravi Gunasekaran authored
Add support to offload HSR Tx Tag Insertion and Rx Tag Removal and duplicate discard. Support for offloading these features needs ICSSG HSR FW version REL.HSR_1G_01.02.00.01. Steps to offload to HSR Tx Tag Insertion and Rx Tag Removal. ----------------------------------------------------------- Example assuming eth1, eth2 ports of ICSSG1 on AM64-EVM 1) Delete existing HSR interface ip link delete hsr0 2) Bring down the interfaces ip link set eth1 down ip link set eth2 down 3) Configure both interfaces to have same MAC address ip link set dev eth2 address <ETH1_MAC_ADDRESS> 4) Enable HSR offload for both interfaces ethtool -K eth1 hsr-fwd-offload on ethtool -K eth1 hsr-dup-offload on ethtool -K eth1 hsr-tag-ins-offload on ethtool -K eth1 hsr-tag-rm-offload on ethtool -K eth2 hsr-fwd-offload on ethtool -K eth2 hsr-dup-offload on ethtool -K eth2 hsr-tag-ins-offload on ethtool -K eth2 hsr-tag-rm-offload on devlink dev param set platform/icssg1-eth \ name hsr_offload_mode \ value true cmode runtime 5) Bring up the interfaces ip link set eth1 up ip link set eth2 up 6) Create HSR interface and add slave interfaces to it ip link add name hsr0 type hsr slave1 eth1 slave2 eth2 \ supervision 45 version 1 7) Add IP address to the HSR interface ip addr add <IP_ADDR>/24 dev hsr0 8) Bring up the HSR interface ip link set hsr0 up Switching back to Dual EMAC mode: --------------------------------- 1) Delete HSR interface ip link delete hsr0 2) Bring down the interfaces ip link set eth1 down ip link set eth2 down 3) Disable HSR port-to-port offloading mode, packet duplication ethtool -K eth1 hsr-fwd-offload off ethtool -K eth1 hsr-dup-offload off ethtool -K eth1 hsr-tag-ins-offload off ethtool -K eth1 hsr-tag-rm-offload off ethtool -K eth2 hsr-fwd-offload off ethtool -K eth2 hsr-dup-offload off ethtool -K eth2 hsr-tag-ins-offload off ethtool -K eth2 hsr-tag-rm-offload off devlink dev param set platform/icssg1-eth \ name hsr_offload_mode \ value false cmode runtime Note: 1) At the very least, hsr-fwd-offload must be enabled. Without offloading the port-to-port offload, other HSR offloads cannot be enabled. 2) Inorder to enable hsr-tag-ins-offload, hsr-dup-offload must also be enabled as these are tightly coupled in the firmware implementation. Signed-off-by:
Ravi Gunasekaran <r-gunasekaran@ti.com>
-
Ravi Gunasekaran authored
In order to fully to support all the HSR offload features at 1G, more clock cycles are needed. So switch the ICSSG core clock from 250MHz to 333MHz. This switch to 333MHz is applicable for all 3 modes - MAC mode, Switch Mode and HSR Mode and improves performance as well. Performance update in dual mac mode With Core Clk @ 333MHz Tx throughput - 934 Mbps Rx throuhput - 914 Mbps, With core clk @ 250MHz, Tx throughput - 920 Mbps Rx throughput - 706 Mbps The improvement in performance is in alignment with the firmware team's understanding that Rx budget cycle is tight at 250MHz. Signed-off-by:
Ravi Gunasekaran <r-gunasekaran@ti.com>
-
Ravi Gunasekaran authored
With the declarations of struct and enum related to IEP present in .c file, it is not possible to access the structures in other source code files. So move the declarations from icss_iep.c to icss_iep.h. IEP's def_inc is derived from the IEP reference clock. Instead of using hard coded value, use the def_inc as this is safer when changing the reference clock value. Signed-off-by:
Ravi Gunasekaran <r-gunasekaran@ti.com>
-