- Jun 02, 2021
-
-
Robert Nelson authored
5.10.35-ti-r6 bb.org_defconfig 5.10 TI Delta: https://github.com/RobertCNelson/ti-linux-kernel/compare/72d727fe733f2610e937a063bcebedce329948ec...aff37a0ce2ca958599fcc7303a68e357f1f2c796 AUFS: https://github.com/sfjro/aufs5-standalone/commit/304f28d3c932b1b999393b04dcf380180418e409 BBDTBS: https://github.com/beagleboard/BeagleBoard-DeviceTrees/commit/19bb614e0290035cdf06cc6f37b20080d6843fa3 TI_AMX3_CM3: http://git.ti.com/gitweb/?p=processor-firmware/ti-amx3-cm3-pm-firmware.git;a=commit;h=fb484c5e54f2e31cf0a338d2927a06a2870bcc2c WPANUSB: https://github.com/statropy/wpanusb/commit/251f0167545bf2dcaa3cad991a59dbf5ab05490a WIRELESS_REGDB: https://git.kernel.org/pub/scm/linux/kernel/git/sforshee/wireless-regdb.git/commit/?id=04f3e5411b1cdc59292775e7b8e05a5d35ea4a80 Signed-off-by:
Robert Nelson <robertcnelson@gmail.com>
-
Robert Nelson authored
-
http://gfnd.rcn-ee.org:8080Robert Nelson authored
Signed-off-by: -
Robert Nelson authored
Signed-off-by: -
Robert Nelson authored
already default on BBB/X15, just calcuated everybootup Signed-off-by: -
Robert Nelson authored
Signed-off-by: -
Thomas Petazzoni authored
In commit 92af4fc6 ("usb: musb: Fix suspend with devices connected for a64"), the logic to support the MUSB_QUIRK_B_DISCONNECT_99 quirk was modified to only conditionally schedule the musb->irq_work delayed work. This commit badly breaks ECM Gadget on AM335X. Indeed, with this commit, one can observe massive packet loss: $ ping 192.168.0.100 ... 15 packets transmitted, 3 received, 80% packet loss, time 14316ms Reverting this commit brings back a properly functioning ECM Gadget. An analysis of the commit seems to indicate that a mistake was made: the previous code was not falling through into the MUSB_QUIRK_B_INVALID_VBUS_91, but now it is, unless the condition is taken. Changing the logic to be as it was before the problematic commit *and* only conditionally scheduling musb->irq_work resolves the regression: $ ping 192.168.0.100 ... 64 packets transmitted, 64 received, 0% packet loss, time 64475ms Fixes: 92af4fc6 ("usb: musb: Fix suspend with devices connected for a64") Signed-off-by:
Thomas Petazzoni <thomas.petazzoni@bootlin.com> Cc: stable@vger.kernel.org
-
Jason Kridner authoredOriginal Commit : https://github.com/beagleboard/linux/commit/8884f22a6b3a5217177c2f843e5c83d613bc6676 Signed-off-by:
Jason Kridner <jkridner@beagleboard.org>
-
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:
-
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: -
Will Eccles authored
When CONFIG_PM is not enabled, the function davinci_mdio_update_dt_from_phymask is not defined. This patch fixes this so that the build does not fail with CONFIG_PM disabled. Signed-off-by:Will Eccles <will@eccles.dev>
-
Jay at Control Module Industries authored
I have encountered the same issue(s) on A6A boards. I couldn't find a patch, so I wrote this patch to update the device tree in the davinci_mdio driver in the 3.15.1 tree, it seems to correct it. I would welcome any input on a different approach. https://groups.google.com/d/msg/beagleboard/9mctrG26Mc8/SRlnumt0LoMJ v4.1-rcX: added hack around CONFIG_OF_OVERLAY v4.2-rc3+: added if (of_machine_is_compatible("ti,am335x-bone")) so we do not break dual ethernet am335x devices Signed-off-by:
-
Robert Nelson authored
Signed-off-by: -
Robert Nelson authored
This reverts commit 956b200a . 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: v5.10.41 Signed-off-by: -
Robert Nelson authored
Reference: v5.13-rc4 Signed-off-by: -
Robert Nelson authored
Reference: v5.12.8 Signed-off-by: -
Robert Nelson authored
Reference: v5.12.8 Signed-off-by: -
-
-
-
Jason Kridner authored
From https://github.com/statropy/wpanusb
-
-
-
Robert Nelson authored
Signed-off-by: -
Robert Nelson authored
Signed-off-by: -
Robert Nelson authored
Signed-off-by: -
Robert Nelson authored
Signed-off-by:
-
- Jun 01, 2021
-
-
LCPD Auto Merger authored
TI-Feature: rpmsg TI-Branch: rpmsg-ti-linux-5.10.y-intg * 'rpmsg-ti-linux-5.10.y-intg' of git://git.ti.com/rpmsg/rpmsg : HACK: irqchip/irq-pruss-intc: Fix processing of IEP interrupts irqchip/irq-pruss-intc: Fix listed IRQ type in /proc/interrupts irqchip/irq-pruss-intc: Fix enabling of intc events Signed-off-by:
LCPD Auto Merger <lcpd_integration@list.ti.com>
-
git://git.ti.com/rpmsg/rpmsgSuman Anna authored
Merge branch 'rpmsg-ti-linux-5.10.y' of git://git.ti.com/rpmsg/rpmsg into rpmsg-ti-linux-5.10.y-intg Signed-off-by:
Suman Anna <s-anna@ti.com>
-
git://git.ti.com/rpmsg/remoteprocSuman Anna authored
Pull in the updated remoteproc feature branch that fixes couple of issues in the PRUSS INTC irqchip driver. The patches mitigate some spurious interrupts towards MPU before the IRQs are requested, fix the PRUSS interrupt types printed in /proc/interrupts, and provide a workaround for IEP timer events towards proper PPS functionality. * 'rproc-linux-5.10.y' of git://git.ti.com/rpmsg/remoteproc : HACK: irqchip/irq-pruss-intc: Fix processing of IEP interrupts irqchip/irq-pruss-intc: Fix listed IRQ type in /proc/interrupts irqchip/irq-pruss-intc: Fix enabling of intc events Signed-off-by:
-
- May 28, 2021
-
-
Suman Anna authored
It was discovered that IEP capture/compare IRQs (event #7 on all SoCs and event #56 on K3 SoCs) are always triggered twice when PPS is generated and CMP hit event detected by IEP. An example of the problem is: pruss_intc_irq_handler generic_handle_irq handle_level_irq mask_ack_irq -> IRQ 7 masked and asked in INTC, but it's not yet cleared on HW level handle_irq_event() <threaded on RT> icss_iep_cap_cmp_handler() -> IRQ 7 is actually processed in HW irq_finalize_oneshot() unmask_irq() pruss_intc_irq_unmask() -> IRQ 7 status is still observed as set The solution is to actually ack these IRQs from pruss_intc_irq_unmask() after the IRQ source is cleared in HW. NOTE: 1. The current solution provides a decent generic framework to scale for any additional events that might be discovered in the future. 2. The solution can be reworked using soc_device_attributes() if a per-SoC solution is desired. The current solution applies to all SoCs accounting for single IEP on non-K3 SoCs and for 2 IEPs on all K3 SoCs. Signed-off-by:Grygorii Strashko <grygorii.strashko@ti.com> Signed-off-by:
-
