On 08:49-20231215, Marcel Ziswiler wrote: > On Thu, 2023-12-14 at 14:10 -0600, b...@ti.com wrote: > > On December 14, 2023 thus sayeth Marcel Ziswiler: > > > Hi Apurva > > > > > > Thanks! > > > > > > On Wed, 2023-12-06 at 18:07 +0530, Apurva Nandan wrote: > > > > Hello Everyone! > > > > > > > > This series will introduce basic support (SD and UART) support for Texas > > > > Instruments J784S4 EVM. > > > > > > For the whole series: > > > > > > Tested-by: Marcel Ziswiler <marcel.ziswi...@toradex.com> > > > > > > However, one thing I noticed is that with upstream TF-A I do get the > > > following errors: > > > > > > NOTICE: BL31: v2.10.0 (release):v2.10.0-76-g02091541d > > > NOTICE: BL31: Built : 18:13:08, Dec 14 2023 > > > ERROR: Failed to get response (-19) > > > ERROR: Transfer send failed (-19) > > > ERROR: Unable to query firmware capabilities (-19) > > > > > > While with latest TF-A from downstream TI BSP (both 9.0 and 9.1 use the > > > same versin) I do not get any > > > errors: > > > > > > NOTICE: BL31: v2.9(release):v2.9.0-614-gd7a7135d3 > > > NOTICE: BL31: Built : 18:40:38, Dec 14 2023 > > > > > > > What version of TIFS are you running? Not getting a response usually > > means firmware is dead or we're not using the right thread to talk. > > Yeah, sorry. I was always running the latest from the ti-linux-firmware > branch: > > SYSFW ABI: 3.1 (firmware rev 0x0009 '9.1.2--v09.01.02 (Kool Koala)') > > So, it is really TF-A which seems to cause the issue.
Actually not TFA either (TFA complains correctly). we have an internal ticket that is in the middle of getting fixed for TIFS and PDK to enable this. a bit of history: A new api TISCI_MSG_QUERY_FW_CAPS[1] was introduced to help determine which version of firmware combination supports what features (such as Low power, etc). This allows for consistent TFA/Kernel implementation that can dynamically detect platforms (since LPM also involved a bit of firmware handshaking for board specific details - PMIC control and the like). This API is as fundamental as version message API that all firmware are supposed to implement. unfortunately the defconfig option for that API wasn't properly implemented for various firmware components correctly. - impacted chips are: j721e, j7200, j721s2/am68, j784s4/am69. Other K3 processor firmware have it implemented correctly. The latest 9.1.8--v09.01.08 has the bug as well - but hopefully should be fixed and released soon-ish. [1] https://software-dl.ti.com/tisci/esd/latest/2_tisci_msgs/general/core.html#tisci-msg-query-fw-caps -- Regards, Nishanth Menon Key (0xDDB5849D1736249D) / Fingerprint: F8A2 8693 54EB 8232 17A3 1A34 DDB5 849D 1736 249D
