- Nov 30, 2023
-
-
Robert Nelson authored
6.1.46-ti-rt-r13 bb.org_defconfig TI SDK: 09.01.00.003 6.1 TI Delta: https://github.com/RobertCNelson/ti-linux-kernel/compare/37f154cc9ceeee52ff63ffbe8b44d295a1fc708b...7d494fe58c8e5d41a6bd886c9a628a7fff5763f9 BBDTBS: https://git.beagleboard.org/beagleboard/BeagleBoard-DeviceTrees/-/commit/55d7cdc4d6aa77211033ae2fdb8b0c7217ba3939 RT: patch-6.1.46-rt14.patch.xz WIRELESS_REGDB: https://git.kernel.org/pub/scm/linux/kernel/git/sforshee/wireless-regdb.git/commit/?id=991b1ef696b7a034a5bf001cf31ab7735888c6e1 KSMBD: https://github.com/cifsd-team/ksmbd/commit/7dec4e9aa879132a92d730aedaebfff130e2963f TI_AMX3_CM3: http://git.ti.com/gitweb/?p=processor-firmware/ti-amx3-cm3-pm-firmware.git;a=commit;h=fb484c5e54f2e31cf0a338d2927a06a2870bcc2c WPANUSB: https://git.beagleboard.org/beagleconnect/linux/wpanusb/-/commit/6aa9bf65b9d88a2c9a111e7b4aed03de2be9413d Signed-off-by:
Robert Nelson <robertcnelson@gmail.com>
-
Robert Nelson authored
-
Robert Nelson authored
Signed-off-by: -
Robert Nelson authored
Signed-off-by: -
Jason Kridner authored -
Robert Nelson authored
Signed-off-by: -
Jason Kridner authored
Original Commit : https://github.com/beagleboard/linux/commit/8884f22a6b3a5217177c2f843e5c83d613bc6676 Signed-off-by:
Jason Kridner <jkridner@beagleboard.org>
-
Robert Nelson authored
This reverts commit 2b038e78 . Signed-off-by:
-
Robert Nelson authored
#<Daulity> is there a kernel option to not reset gpio state at linux boot ? #<zmatt> Daulity: the kernel does not reset any gpio unless explicitly requested to by a driver #<zmatt> though by default if cape-universal is enabled then a gpio-of-helper device gets set up which configures all gpios as input... though that is normally the state they are in anyway after reset #<zmatt> Daulity: why? are you setting gpios in u-boot? #<Daulity> yes u-boot sets a few gpio's before it boots the kernel they get reset to a certain state not certain if u-boot or linux kernel #<Daulity> was just wondering #<zmatt> the annoying bit is that this isn't really fixable by applying an overlay on top of cape-universal due the the limitations of overlays and the fact that status="disabled"; doesn't work on individual gpios of a gpio-of-helper device node #<zmatt> so your options are to modify the cape-universal overlay or disable cape-universal entirely and use an overlay to declare/export gpios (with initialization of your choice) #<Daulity> i see #<zmatt> (or fix the gpio-of-helper drivers to respect the status property of individual gpios... which is probably a 2-line patch) #<zmatt> *driver #<zmatt> interesting, if CONFIG_OF_KOBJ=n then nodes with non-okay status property don't even get deserialized, however in practice CONFIG_OF_KOBJ is always y (specifically, it is only n in kernels that lack sysfs support) #<zmatt> yeah it's definitely a 2-line fix #<zmatt> https://pastebin.com/f8V8pz1V #<Daulity> thanks :) #<zmatt> rcn-ee: can you include that patch? that way overlays can disable cape-universal's gpio export for individual gpios used by the overlay #<zmatt> e.g. &ocp { cape-universal { P9_14 { status = "disabled"; }; }; }; #<zmatt> Daulity: you can use that in an overlay and then if you still want the gpio exported you can just declare your own gpio-of-helper ... unfortunately it doesn't support exporting a gpio without initializing it, but at least you can choose *how* to initialize it (input, output-low, output-high) and whether or not linux userspace is allowed to change the direction of the gpio Signed-off-by:
-
Robert Nelson authored
Signed-off-by: -
Robert Nelson authored
hack: gpiolib: yes we have drivers stomping on each other, we need to find a better way to share gpio... Signed-off-by: -
Robert Nelson authored
Authors: Pantelis Antoniou <panto@antoniou-consulting.com> Charles Steinkuehler <charles@steinkuehler.net> Jason Kridner <jdk@ti.com> Robert Nelson <robertcnelson@gmail.com> Tobias Müller <Tobias_Mueller@twam.info> Matthijs van Duin <matthijsvanduin@gmail.com> This patch was derived from 19 commits: https://github.com/RobertCNelson/linux-dev/tree/35e301ae8436e9f56f65bf1a7440021eda42f948/patches/drivers/ti/gpio Signed-off-by:
-
Robert Nelson authored
Authors: Pantelis Antoniou <panto@antoniou-consulting.com> Charles Steinkuehler <charles@steinkuehler.net> Jason Kridner <jdk@ti.com> Robert Nelson <robertcnelson@gmail.com> Tobias Müller <Tobias_Mueller@twam.info> Matthijs van Duin <matthijsvanduin@gmail.com> This patch was derived from 19 commits: https://github.com/RobertCNelson/linux-dev/tree/35e301ae8436e9f56f65bf1a7440021eda42f948/patches/drivers/ti/gpio Signed-off-by:
-
frost authored
-
bigguiness@gmail.com authored
------=_Part_422_1349561576.1515022447432 Content-Type: text/plain; charset="UTF-8" Hello all, The TI touch screen driver does not work _right_ with the libts-bin package in the jessie image. $ cat /etc/dogtag BeagleBoard.org Debian Image 2018-01-01 $ lsb_release -a No LSB modules are available. Distributor ID: Debian Description: Debian GNU/Linux 8.10 (jessie) Release: 8.10 Codename: jessie $ dpkg -l | grep libts-bin ii libts-bin 1.14-1rcnee0~jessie+20171122 armhf touch screen library utilities $ sudo ts_calibrate ts_setup: No such file or directory It is possible to make it work by setting the TSLIB_TSDEVICE environment variable: $ sudo su # export TSLIB_TSDEVICE=/dev/input/event2 # ts_calibrate But, that's a bit of a pain since the environment variable always needs to be set in order to use the touchscreen. It appears that this version of the utilities uses the INPUT_PROP_DIRECT propbit to automatically detect which /dev/input/event device is the touchscreen. It looks like the following is the only change needed to make it work. Unfortunately, I don't have currently have a way to build a custom kernel for the BeagleBone in order to test it. If there is anyone that could I would appreciate it. Regards, Hartley -
Robert Nelson authored
This reverts commit 3c9dc275 . Signed-off-by:
-
Robert Nelson authored
Signed-off-by: -
Robert Nelson authored
Signed-off-by: -
Robert Nelson authored
Signed-off-by: -
Robert Nelson authored
Reference: v6.1.64 Signed-off-by: -
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.202 Signed-off-by: -
-
-
-
Robert Nelson authored
patch-6.1.46-rt14.patch.xz Signed-off-by: -
-
Jason Kridner authored
From https://github.com/statropy/wpanusb
-
-
- Nov 02, 2023
-
-
Brandon Brnich authored
Wave5 has option to connect device to on-chip SRAM through secondary AXI. This allows for storing temporal buffers on a per stream basis leading to the reduction of memory traffic. Signed-off-by:
Brandon Brnich <b-brnich@ti.com> Reviewed-by:
Jai Luthra <j-luthra@ti.com>
-
Prasanth Babu Mantena authored
Add OPP table to the dt node, which has multiple frequency points with highest and lowest operating frequencies. The frequencies are opted based on the HSDIV value and divider of the PLL. Signed-off-by:
Prasanth Babu Mantena <p-mantena@ti.com> Acked-by:
-
Prasanth Babu Mantena authored
Add OPP table to two instances of wave5, with multiple frequency points, with highest and lowest operating frequencies. The frequencies are opted based on the HSDIV value and divider of the PLL. Signed-off-by:
-
Prasanth Babu Mantena authored
Add OPP table to vpu dt node, which has multiple frequency points with highest and lowest operating frequencies. The frequencies are opted based on the HSDIV value and divider of the PLL. Signed-off-by:
-
Prasanth Babu Mantena authored
Support for OPP table is added to the driver. Driver can now select the frequency from the available operational frequencies from the OPP table and run at the frequency that is required for the Pixel rate that the IP is handling. The Operating frequency adjusts to higher values when multiple instances are initialized asynchronously and vice-versa. When no instance is running, the frequency is set to the lowest operational frequency of the OPP table. Signed-off-by:
-
Prasanth Babu Mantena authored
Added support for runtime suspend and resume. The device when probed will issue vpu to go into sleep mode. Whenever an instance is running, then the vpu is wake up and runs to max frequency. Signed-off-by:
-
Bryan Brattlof authored
Add the bootph-all property to the sdhci0 node so uboot's build scripts will include the node into the device tree blobs for its SPL builds. This will enable booting via eMMC on the SK boards. Signed-off-by:Bryan Brattlof <bb@ti.com>
-
Bryan Brattlof authored
There are a few extra properties needed to probe TI's MMC controllers with a 8bit width. Add these needed properties. Signed-off-by: -
Judith Mendez authored
Rename k3-am625-sk-rpi-hdr-pwm.dtso to k3-am625-sk-pwm.dtso since this overlay only enables PWM. Reviewed-by:
Judith Mendez <jm@ti.com>
-
Judith Mendez authored
Add overlays which enable RPI header with GPIOs and PWM using eHRPWM modules on the following platforms: - AM62-SK - AM62A-SK - AM62P-SK Reviewed-by:
-
