- Mar 23, 2021
-
-
Robert Nelson authored
5.4.93-ti-rt-r25 bb.org_defconfig 5.4 TI Delta: https://github.com/RobertCNelson/ti-linux-kernel/compare/b26f403d01870360392f2fe778304d3a8cba0bef...ca222ae72ea37d74141ed53deaa0a07263ef34e8 AUFS: https://github.com/sfjro/aufs5-standalone/commit/062b2393e4fae30efc066061087a8b9747528609 BBDTBS: https://github.com/beagleboard/BeagleBoard-DeviceTrees/commit/ec89792253910a98538e5354994d5a6be2cd9fd9 CAN-ISOTP: https://github.com/hartkopp/can-isotp/commit/b312dbd5e720833cb69bc65af3670a52dd1e93ca RT: patch-5.4.93-rt51.patch.xz TI_AMX3_CM3: http://git.ti.com/gitweb/?p=processor-firmware/ti-amx3-cm3-pm-firmware.git;a=commit;h=fb484c5e54f2e31cf0a338d2927a06a2870bcc2c WIREGUARD: https://git.zx2c4.com/WireGuard/commit/edad0d6e99e5133b1e8e865d727a25fff6399cb4 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
Reference: v5.10.25 Signed-off-by: -
Andrzej Hajda authored
During probe every time driver gets resource it should usually check for error printk some message if it is not -EPROBE_DEFER and return the error. This pattern is simple but requires adding few lines after any resource acquisition code, as a result it is often omitted or implemented only partially. dev_err_probe helps to replace such code sequences with simple call, so code: if (err != -EPROBE_DEFER) dev_err(dev, ...); return err; becomes: return dev_err_probe(dev, err, ...); Signed-off-by:
Andrzej Hajda <a.hajda@samsung.com> Reviewed-by:
Rafael J. Wysocki <rafael@kernel.org> Reviewed-by:
Mark Brown <broonie@kernel.org> Reviewed-by:
Andy Shevchenko <andy.shevchenko@gmail.com> Link: https://lore.kernel.org/r/20200713144324.23654-2-a.hajda@samsung.com Signed-off-by:
Greg Kroah-Hartman <gregkh@linuxfoundation.org>
-
Jason Kridner authored -
-
Robert Nelson authored
already default on BBB/X15, just calcuated everybootup 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:
-
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
Signed-off-by: -
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:
-
Pantelis Antoniou authored
-
Robert Nelson authored
Signed-off-by: -
Robert Nelson authored
This reverts commit 956b200a . Signed-off-by:
-
Robert Nelson authored
Signed-off-by: -
Dimitar Dimitrov authored
PRU IRAM addresses need to be masked before being handled to remoteproc. This is due to PRU Binutils' lack of separate address spaces for IRAM and DRAM. Signed-off-by:Dimitar Dimitrov <dinuxbg@gmail.com>
-
Robert Nelson authored
Signed-off-by: -
Robert Nelson authored
Signed-off-by: -
Robert Nelson authored
Signed-off-by: -
Ting-Ying Li authored
Commit 6c219b00 ("brcmfmac: disable packet filtering in promiscuous mode") adds brcmf_configure_arp_nd_offload() configuration according to promiscuous mode in _brcmf_set_multicast_list(). It will always enable arp/nd offload when the device is not in promiscuous mode without considering the interface role. Enabling ARP offload for STA/SAP concurent mode has caused the AP interface to send ARP responses with incorrect mac address. Remove the arp/nd offload setting line as a workaround for now. Signed-off-by:
Ting-Ying Li <tingying.li@cypress.com> Signed-off-by:
Chi-hsien Lin <chi-hsien.lin@cypress.com>
-
Ting-Ying Li authored
Some firmware does not support disabling "ap_isolate" via iovar. Therefore, get iovar "ap_isolate" value after setting to determine whether fmac driver should turn on host-based packet forwarding. Signed-off-by:
-
Jia-Shyr Chuang authored
- Support packet forwarding mechanism on fmac driver for some special usages on PCIE. Please ref to JIRA. - Fixed BE/VI priority issue when pumping iperf - Fix for linux coding style Signed-off-by:
Jia-Shyr Chuang <joseph.chuang@cypress.com> Signed-off-by:
-
Chi-Hsien Lin authored
AOS is a part of the SDIOD core that becomes active when the rest of SDIOD is sleeping to keep SDIO bus alive responding to reduced set of commands. Transaction between AOS and SDIOD is not protected, and if cmd 52 is received in AOS and in the middle of response state changed from AOS to SDIOD, response is corrupted and it causes to SDIO Host controller to hang. Signed-off-by:
Wright Feng <wright.feng@cypress.com> Signed-off-by:
-
Chi-Hsien Lin authored
AOS is a part of the SDIOD core that becomes active when the rest of SDIOD is sleeping to keep SDIO bus alive responding to reduced set of commands. Transaction between AOS and SDIOD is not protected, and if cmd 52 is received in AOS and in the middle of response state changed from AOS to SDIOD, response is corrupted and it causes to SDIO Host controller to hang. Signed-off-by:
-
Chi-Hsien Lin authored
AOS is a part of the SDIOD core that becomes active when the rest of SDIOD is sleeping to keep SDIO bus alive responding to reduced set of commands. Transaction between AOS and SDIOD is not protected, and if cmd 52 is received in AOS and in the middle of response state changed from AOS to SDIOD, response is corrupted and it causes to SDIO Host controller to hang. Signed-off-by: -
Madhan Mohan R authored
With the addition of skb_orphan in the datapath, though the throughput increases in TX path, it introduces an issue by removing the flowcontrol from upper layer and allowing more data to flow for different access category. This workaround is to disable using skb_orphan when running multi-stream data. This change will not be required in linux 4.15 and later versions. We only use this feature when Linux version is less than 4.16.0. Signed-off-by:
Raveendran Somu <raveendran.somu@cypress.com> Signed-off-by:
-
Wright Feng authored
Linux 3.6 introduces TSQ which has a per socket threshold for TCP Tx packet to reduce latency. In fcmode 1/2, host driver enqueues skb in hanger and TCP doesn't push new skb frees until host frees the skb when receiving fwstatus event. So using skb_orphan before sending skb to bus will make the skb removing the ownership of socket. With this patch, we got better throughput in fcmode 1/2. We only call skb_orphan when Linux version is less than 4.16.0. Tested 43455 TCP throughput in 20 MHz bandwidth with/without this patch. fcmode 0: 59.5 / 59.6 (Mbps) fcmode 1: 59.3 / 23.4 (Mbps) fcmode 2: 59.6 / 21.5 (Mbps) Signed-off-by:
-
Pramod Prakash authored
802.1d defines 0,3 for BE and 1,2 for BK. In pcie dongles, 0 & 3 are mapped to 0 and 1,2 are mapped to 1. This change corrects this mapping, so that BE & BK are given access precedence accordingly by pcie dongles. Signed-off-by:
Pramod Prakash <pramod.prakash@cypress.com> Signed-off-by:
-
Wright Feng authored
Linux 3.6 introduces TSQ which has a per socket threshold for TCP Tx packet to reduce latency. In flow control mode , host driver enqueues skb in hanger and TCP doesn't push new skb frees until host frees the skb when receiving fwstatus event. So set pacing shift 8 to send them as a single large aggregate frame to the bus layer. 43455 TX TCP throughput in FC mode 2 on Linux 5.4.18 sk_pacing_shift : Throughput 10: 190 Mbps 9: 216 Mbps 8: 233 Mbps (Max throughput) 7: 233 Mpbs Signed-off-by:
-
Able Liao authored
Ignore FW event if the event's BSSID is different form the BSSID of the currently connected AP. Check interface state is connected or not, if state is not connected that can ignore link down event. Signed-off-by:
Able Liao <Able.Liao@cypress.com> Signed-off-by:
-
Madhan Mohan R authored
To do a clean reset of the chip during rmmod brcmfmac, program the PmuWatchdogCounter register. When a watchdog reset occurs, the PMU, backplane and all of the cores in the chip are reset. Signed-off-by:
Madhan Mohan R <madhanmohan.r@cypress.com> Signed-off-by:
-
David Weng authored
Device is left in non-responding state when unloading driver in non-DS1 state if it ever enters DS1 at least once. It leaves that state only after a hard reset or power cycle 43012. Signed-off-by:
David Weng <david.weng@cypress.com> [Merge from 4.14.77 to 5.4.18] Signed-off-by:
-
Nitin Bhaskar authored
After entering ULP, issuing rmmod does not put chip in sane state because of which next insmod fails. Fix includes writing into few LHL, PMU registers. Signed-off-by:
Nitin Bhaskar <niti@cypress.com> [Merge from 4.14.77 to 5.4.18] Signed-off-by:
-
Praveen Babu C authored
In deep sleep mode (DS1) ARM is off and once exit trigger comes than mailbox Interrupt comes to host and whole reinitiation should be done in the ARM to start TX/RX. Also fix below issus for DS1 exit: 1. Sent Tx Control frame only after firmware redownload complete (check F2 Ready before sending Tx Control frame to Firmware) 2. intermittent High DS1 TX Exit latency time (almost 3sec) ==> This is fixed by skipping host Mailbox interrupt Multiple times (ulp state mechanism) 3. RX GlOM save/restore in Firmware 4. Add ULP event enable & event_msgs_ext iovar configuration in FMAC 5. Add ULP_EVENT_RECV state machine for sbwad support 6. Support 2 Byte Shared memory read for DS1 Exit HUDI implementation Signed-off-by:
Praveen Babu C <pucn@cypress.com> Signed-off-by:
Naveen Gupta <nagu@cypress.com> [Merge from 4.14.77 to 5.4.18; set BRCMF_SDIO_MAX_ACCESS_ERRORS to 20] Signed-off-by:
-
Double Lo authored
Support 54591 PCIE device. Signed-off-by:
Double Lo <double.lo@cypress.com> Signed-off-by:
-
