- Jun 29, 2023
-
-
Robert Nelson authored
6.1.33-ti-rt-r6 bb.org_defconfig TI SDK: 09.00.00.004 6.1 TI Delta: https://github.com/RobertCNelson/ti-linux-kernel/compare/1ada48a6cf0b8b731b835b9f1e1e4af89f8fb791...2b6f5746de558d954e42749b898fcdb4227dce5a BBDTBS: https://git.beagleboard.org/beagleboard/BeagleBoard-DeviceTrees/-/commit/51f0e9ebb723252b8a5920873997fa4879c04291 RT: patch-6.1.33-rt11.patch.xz WIRELESS_REGDB: https://git.kernel.org/pub/scm/linux/kernel/git/sforshee/wireless-regdb.git/commit/?id=9dc0800cdd7aeeae273b983973a1749f73008291 KSMBD: https://github.com/cifsd-team/ksmbd/commit/11aa06fbc7307b3ff68ebbdb96d42484d9b5ae6a 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 BCFSERIAL: https://git.beagleboard.org/beagleconnect/linux/bcfserial/-/commit/db467023bd136c97c2e13c3a8b9e41dbdfafbc66 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
already default on BBB/X15, just calculated on every bootup Signed-off-by: -
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
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.186 Signed-off-by: -
-
-
-
Robert Nelson authored
patch-6.1.33-rt11.patch.xz Signed-off-by: -
-
Robert Nelson authored
Signed-off-by: -
-
Jason Kridner authored
From https://github.com/statropy/wpanusb
-
-
- Jun 22, 2023
-
-
Nishanth Menon authored
System enters no_irq stage in multiple usage modes, one of them being in suspend operations. However similar situations arise in case of attempts at poweroff, restart etc. Lets just use system_state to determine if we are in a situation (a bit aggressive use , perhaps) to see if we need to use polling mode. While at this, just drop the unused is_suspending state variable and related helpers. Reviewed-by:
Dhruva Gole <d-gole@ti.com> Tested-by:
Francesco Dolcini <francesco@dolcini.it> Reported-by:
Wadim Egorov <w.egorov@phytec.de> Signed-off-by:
Nishanth Menon <nm@ti.com> Tested-by:
Vibhore Vardhan <vibhore@ti.com>
-
Nishanth Menon authored
commit 68dd81a7 upstream. Similar to commit 3308a31c ("arm64: dts: ti: k3-am62: Add general purpose timers for am62"), there are 12 general purpose timers on am62a7 split between 8 in main and 4 in mcu domains. The 4 in mcu domain do not have interrupts that are routable to a53. We configure the timers with the 25 MHz input clock by default as the 32.768 kHz clock may not be wired on the device. We leave the MCU domain timers clock mux unconfigured, and mark the MCU domain timers reserved. The MCU domain timers are likely reserved by the software for the ESM module. Signed-off-by:
-
Vibhore Vardhan authored
This overlay forces maximum clock rates for A53 and C7x on AM62A7-SK Rev E3 board. It is meant only to be used for boards that have VDD_CORE at 0.85V. Please note that AM62A7-SK Board revisions E1 and E2 do not meet this requirement. The overlay adds the 1.4 GHz OPP for A53 cores and disables all the lower OPPs. It also overrides the clock rate for C7x to 1 GHz. Any other boards based on this design should verify that they have the right silicon variant and the right power tree before booting with this overlay. Signed-off-by: -
Devarsh Thakkar authored
Remove job_ready callback since v4l2 m2m core already ensures to queue the job only if non-zero buffers are available at capture and output queue and that criteria suffices the driver. This also removes the check for hardware busy flag as it was causing a hang issue in multistream scenario where userspace queues the buffer which triggers the job_ready callback and the job is not queued ever since the hardware was busy and userspace has queued all the buffers. The hardware busy check as such is not required for queuing the job since the e5010_hw* functions already take care of polling the busy flag and ensuring that registers are only programmed when hardware is not busy, hence remove the now unused function e5010_hw_is_busy too. While at it, remove extra traversal for e5010_dev struct wherever possible for dynamic debug prints. Fixes: 99572119 ("media: platform: img: Add E5010 JPEG Encoder driver") Signed-off-by:
Devarsh Thakkar <devarsht@ti.com> Reviewed-by:
Darren Etheridge <detheridge@ti.com>
-
Devarsh Thakkar authored
- In case of any error during device_run, skip further programming in device_run, reset the hardware and return back the buffers with state marked as error. - When output address error irq occur, it means that output bitstream write exceeds the output buffer size, in this case remaining part of output bitstream is no longer written to memory and so mark the corresponding buffers as VB_STATE_ERROR. - Use userpsace provided pixel format for output queue While at it, - Add v4l2 dynamic debug prints to detect failure scenarioes - Refactor and cleanup code to, - Send EOS event without wrapper - Rename relevant functions, update return value as used - Remove buffer checkes in job_ready as v4l2 framework checks already for non-zero buffers. Fixes: 99572119 ("media: platform: img: Add E5010 JPEG Encoder driver") Signed-off-by: -
Devarsh Thakkar authored
Fixes below warning reported by test bot: >> e5010-jpeg-enc.c:1443:13: warning: variable 'bytesperline_64div' set but not used [-Wunused-but-set-variable] 1443 | u32 bytesperline_64div; variable 'bytesperline_64div' set but not used Closes: https://lore.kernel.org/oe-kbuild-all/202306110416.Ot1Gzxko-lkp@intel.com/ Reported-by:kernel test robot <lkp@intel.com> Signed-off-by:
-
Devarsh Thakkar authored
Remove spinlock while sending encoder start command since the v4l2 ioctls are serialized by v4l2 core with driver provided lock and no explicit locking is needed in this case. While at it, also return correct error value in case of failure. Signed-off-by:
-
