[PATCH v6 00/17] Introduce initial TI's J784S4 and AM69 support

[Andrew Davis]

On 12/15/23 2:51 AM, Marcel Ziswiler wrote:
> On Thu, 2023-12-14 at 14:28 -0600, Andrew Davis wrote:
>> On 12/14/23 2:10 PM, bb at 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.ziswiler at 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.
>>>
>>
>> In this case the early versions of TIFS/DM for J784S4/AM69 had
>> a bug where the "query firmware capabilities" API was left disabled.
>> This is fixed in the next version of firmware, this error message
>> is harmless today anyway (no LPM yet).
> 
> No, 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 here.
> 

When I said "fixed in the next version" I meant the next to
be released, as in not yet out (I'd guess out in a week or so).
Sorry for any confusion here.

I added support for this new API to TF-A only recently,
which is why the old TF-A versions don't print this error.
Nishanth gives more details in the other thread, but as
said this error is harmless and will go away in with
the next firmware update.

Andrew

>> Andrew
> 
> Cheers
> 
> Marcel