- Aug 11, 2022
-
-
Vaishnav Achath authored
export serdev id table to the module header. Signed-off-by:
Vaishnav M A <vaishnav@beagleboard.org>
-
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>
-
Vaishnav Achath authored
Signed-off-by:
Vaishnav M A <vaishnav@beagleboard.org>
-
Vaishnav Achath authored
Signed-off-by:
Vaishnav M A <vaishnav@beagleboard.org>
-
Ricardo Ribalda authored
This patch allows file2alias to generate the proper module headers to support serdev modalias drivers. Eg: root@qt5022:~# modinfo serdev:ttydev | grep alias alias: serdev:ttydev_serdev alias: serdev:ttydev root@qt5022:~# cat /lib/modules/4.16.0-qtec-standard/modules.alias | grep serdev alias serdev:ttydev_serdev serdev_ttydev alias serdev:ttydev serdev_ttydev Signed-off-by:
Ricardo Ribalda Delgado <ricardo.ribalda@gmail.com>
-
Ricardo Ribalda authored
Currently,a serdev device driver can only be used with devices that are nodes of a device tree, or are part of the ACPI table.id_table will be used for devices that are not part of the device tree nor the ACPI table (example: device on greybus gbphy created uart). corresponding modalias field is introduced to name the driver to be used with the device, required device(s) that are neither described by device tree nor ACPI table. serdev_device_uevent is also extended for modalias devices. Signed-off-by:
Ricardo Ribalda Delgado <ricardo.ribalda@gmail.com>
-
Vaishnav Achath authored
This Patch series is an update to the mikroBUS driver with support for serdev devices and fixed regulator. RFC v1 Patch : https://lkml.org/lkml/2020/7/24/518 . The mikrobus driver is updated to add mikrobus ports from device-tree overlays, the debug interfaces for adding mikrobus ports through sysFS is removed, and the driver considers the extended usage of mikrobus port pins from their standard purposes. change log: v2: support for adding mikroBUS ports from DT overlays, remove debug sysFS interface for adding mikrobus ports, consider extended pin usage/deviations from mikrobus standard specifications, use greybus CPort protocol enum instead of new protcol enums Fix cases of wrong indendation, ignoring return values, freeing allocated resources in case of errors and other style suggestions in v1 review. Signed-off-by:
Vaishnav M A <vaishnav@beagleboard.org>
-
Jason Kridner authored
-
Robert Nelson authored
This reverts commit 956b200a . Signed-off-by:
Robert Nelson <robertcnelson@gmail.com>
-
Robert Nelson authored
Signed-off-by:
Robert Nelson <robertcnelson@gmail.com>
-
Robert Nelson authored
Signed-off-by:
Robert Nelson <robertcnelson@gmail.com>
-
Robert Nelson authored
Reference: v5.15.60 Signed-off-by:
Robert Nelson <robertcnelson@gmail.com>
-
Robert Nelson authored
Reference: v5.15.60 Signed-off-by:
Robert Nelson <robertcnelson@gmail.com>
-
Robert Nelson authored
Reference: v5.10.136 Signed-off-by:
Robert Nelson <robertcnelson@gmail.com>
-
Robert Nelson authored
Signed-off-by:
Robert Nelson <robertcnelson@gmail.com>
-
Robert Nelson authored
Signed-off-by:
Robert Nelson <robertcnelson@gmail.com>
-
Jason Kridner authored
From https://github.com/statropy/wpanusb
-
Robert Nelson authored
Signed-off-by:
Robert Nelson <robertcnelson@gmail.com>
-
Robert Nelson authored
Signed-off-by:
Robert Nelson <robertcnelson@gmail.com>
-
Robert Nelson authored
Signed-off-by:
Robert Nelson <robertcnelson@gmail.com>
-
Robert Nelson authored
Signed-off-by:
Robert Nelson <robertcnelson@gmail.com>
-
Robert Nelson authored
Signed-off-by:
Robert Nelson <robertcnelson@gmail.com>
-
Lucas Weaver authored
The following has been done in this commit: 1) Add new nodes definitions for enabling all 6 EHRPWM instances 2) Add rules to disable all the instances for non SK platforms 3) Add rules to enable instances 2 and 3 for the SK platform 4) Add mux settings for enabling channel A from instances 2 and 3 for the RPi extension header on the SK platform
-
Prashanth Kumar Amai authored
v4l:vxd-dec:Flushing all the IO buffers and releasing all the held buffers while joing v4l2 job_abort. This patch does the fulsh operation by releasing all the locked up buffers in the driver. It throws the v4l2 harmless traces while trying to re-release the released buffers. Signed-off-by:
Prashanth Kumar Amai <prashanth.amai@ti.com>
-
Sinthu Raja authored
Add DTB overlay file with pin mux details for RPi expansion header defaulting to GPIO mode Signed-off-by:
Sinthu Raja <sinthu.raja@ti.com>
-
Andrew F. Davis authored
This is driver allows user-space to attach a DMA-BUF and receive back its CPU physical address. This is a temporary solution to allow CMEM like functionality from allocated buffers. This is a hack and this will be removed when proper solutions are implemented. Signed-off-by:
Andrew F. Davis <afd@ti.com> Signed-off-by:
Gowtham Tammana <g-tammana@ti.com>
-
Gowtham Tammana authored
Driver allowing user-space attaching of dmabuf fd's returning CPU physical addresses. The reasoning for making this act like a regular device described by DT is so the virtual device that binds the buffer can be made to act as if it is out on a bus or behind an IOMMU, for example. Add this binding here. This is a hack and marked as such. Signed-off-by:
Gowtham Tammana <g-tammana@ti.com>
-
Keerthy authored
Signed-off-by:
Keerthy <j-keerthy@ti.com>
-
Lucas Weaver authored
Confine the memory map changes into a separate rtos-memory-map.dts which describes the common memory map for all RTOS remoteprocs. vision-apps.dtbo uses this and also disables capture and display related peripherals from Linux so that it can be used by RTOS. edgeai-apps.dtbo expects these devices to be owned by linux, so it uses the rtos-memory-map customization only. Signed-off-by:
Nikhil Devshatwar <nikhil.nd@ti.com>
-
Texas Instruments Auto Merger authored
TI-Feature: platform_base TI-Branch: platform-ti-linux-5.10.y * 'platform-ti-linux-5.10.y' of ssh://bitbucket.itg.ti.com/lcpdpublicdom/platform : misc: sram: dma-heap-export: Make our dma_buf_ops static HACK: dma-buf: heaps: carveout: Make our dma_buf_ops static HACK: dma-buf: heaps: carveout: Add support for cached carveout heaps Signed-off-by:
Texas Instruments Auto Merger <lcpd_integration@list.ti.com>
-
Texas Instruments Auto Merger authored
TI-Feature: connectivity TI-Branch: connectivity-ti-linux-5.10.y * 'connectivity-ti-linux-5.10.y' of ssh://bitbucket.itg.ti.com/lcpdpublicdom/connectivity : arm64: dts: ti: Disable UHS speed modes on MMCSD1 instance dmaengine: ti: k3-udma: Reset UDMA_CHAN_RT byte counters to prevent overflow phy: ti: phy-j721e-wiz: stop name conflict if multiple serdes are initialized Signed-off-by:
Texas Instruments Auto Merger <lcpd_integration@list.ti.com>
-
- Aug 10, 2022
-
-
Instabilities were observed on a few SD cards when UHS speed modes were enabled. Therefore, disable UHS modes by adding the tag no-1-8-v tag, in sdhci1 device tree node. Signed-off-by:
Aswath Govindraju <a-govindraju@ti.com> Signed-off-by:
Vignesh Raghavendra <vigneshr@ti.com> Tested-by:
Bryan Brattlof <bb@ti.com>
-
UDMA_CHAN_RT_*BCNT_REG stores the real-time channel bytecount statistics. These registers are 32-bit hardware counters and the driver uses these counters to monitor the operational progress status for a channel, when transferring more than 4GB of data it was observed that these counters overflow and completion calculation of a operation gets affected and the transfer hangs indefinitely. This commit adds changes to decrease the byte count for every complete transaction so that these registers never overflow and the proper byte count statistics is maintained for ongoing transaction by the RT counters. Earlier uc->bcnt used to maintain a count of the completed bytes at driver side, since the RT counters maintain the statistics of current transaction now, the maintenance of uc->bcnt is not necessary. Signed-off-by:
Vaishnav Achath <vaishnav.a@ti.com> Signed-off-by:
Vignesh Raghavendra <vigneshr@ti.com>
-
When multiple serdes instances are initialized the first will succeed but additional will conflict over clocks names and probing fails. Signed-off-by:
Matt Ranostay <mranostay@ti.com> Signed-off-by:
Vignesh Raghavendra <vigneshr@ti.com>
-