Some tiny news:
After doing some more experiments, I think the firmware inside the AESS DSP may even be running... The effect of crashing the L3 with pmem can be traced to a read access to an undocumented register inside a register block (Table 8 in the document mentioned below) which controls...
Hi, that is nice.
I did the same with the old PandaES driver recommended by Peter (omap-audio maintainer): https://github.com/omap-audio/linux-audio/tree/next-bnw/ti-audio-next_3.15
Here is my version with some fixes and an addition for a shell script that downloads and builds the matching...
I am happy to share a simple trick from ancient times when the Pyra was developed and I had to take out the battery very often...
Just take s short one-sided adhesive tape and put it like shown on the battery.
Well it doesn't change opening the battery cover.
Same for me, unfortunately. And also no time for working on the AESS subsystem driver.
And I have seen a strange bug in the kernel driver (it stops accepting changes for the threshold values) which deserves more research.
Well, next year comes soon and will be long compared to the days left...
Yes, indeed, it is very specific to the Pyra and the mix of the OMAP5432 and the DDR3L.
Someone more experienced with OMAP5 (or its successors) can certainly help.
According to my last information (but it may have changed) DRAM chips are: Samsung K4B8G1646D-MMK0. It could be helpful or not to...
I'd vote for Risca. As far as I see it was his research and idea to find and use the threshold mechanism. Going beyond that is "just debugging" and "making more user friendly"...
Just a note:
the fix (https://github.com/Risca/pyra_vol_mon/commit/f409d7f9ced10d4f4a48e13d0ff1b141e487bbdd)
to collect subprocess(es) should IMHO be run after, not just before spawning a new execute_callback after a successful read_value_and_update_thresholds().
I.e. one wait() for one fork()...
First test results: threshold calculation seems to be improved, but driver reports -EBUSY after a while, when trying to set threshold values in the driver. May be related to calibration.
E.g.
Failed to enable upper threshold 1149: -16
Failed to enable lower threshold 922: -16
I'm close to some fixes (already improved threshold setting logic) - but unfortuantely I had to upgrade my build host and there is now some issue with the (new) gcc and (old) cross compiler toolchains so that I can not yet recompile the kernel and do further testing until I have fixed the...
Have been testing a little.
1. well, values reported are 0..1250 (converted to mV by the calibration functions) but MAX value default is 2500. So why do we need min and max at all, if the value is the measured mV range (which is known to be based on the adc reference voltage of 1.2V and will not...
Quick note: latest (and full) pyra_vol_mon is now integrated into Letux tree (v6.1-rc6):
https://git.goldelico.com/?p=letux-kernel.git;a=tree;f=Letux/root/pyra_vol_mon;h=091bf7ef5e3d97e49a2e5bfe6d49dbc3e4a816f1;hb=99441d84f2ba3352b265a1f6724e34544eb83770
Haven't tried to run or check for the...
Well, -rc (or "Prepatch") kernels are never "useable" since they are development and integration snapshots and Letux can't be better than Linus... See: https://www.kernel.org/category/releases.html
But v6.1 will likely become the next longterm kernel with long-lasting upstream support which...
Yes, it is the power controller chip which also monitors battery, charger plug-in etc. with the same circuit (just on a different channel). But that is far from being as power hungry as the M4 or A15 cores running background tasks.
So kudos to risca for finding the palmas gpadc threshold feature...
I am a friend of a modular approach...
So one daemon decoding the wheel and calling another tool to do something. And a third mechanism to set this up either on boot or on demand. This seems to be the most flexible approach and would already be reached :)
Yes... some boards also have HDMI audio an there is no reliable way to find the headset/speaker connected sound card.
BTW: it is something I have not yet understood: why the card name is "L15". There is no "L15" in the whole kernel tree... Maybe some magic algorithm.
Well, my old volumed was...
Here is the script (and bug fixes) included: https://git.goldelico.com/?p=letux-kernel.git;a=tree;f=Letux/root/pyra_vol_mon;h=02da7d094d2dbbdd4ad35910369eaa24e078d64a;hb=refs/heads/letux-6.1-rc4
A minor weakness is that the gpadc rarely reports the volume of exactly "$VOL" = 0. Especially if...
Yes it is.. And on the PandaBoard ES. The main hardware differences are that the 5EVM only has a stereo headset output, the PandaES has one more accesible handsfree speaker output and the Pyra has two of them...
I have initially done some development for AESS on the OMAP5 EVM and then switched...
This site uses cookies to help personalise content, tailor your experience and to keep you logged in if you register.
By continuing to use this site, you are consenting to our use of cookies.