Re: [PATCH v5 0/3] soc: qcom: extend interface for big endian support

[David Heidelberg]

On 19/11/2025 11:40, Alexander Wilhelm wrote:
> Currently, the QMI interface only works on little endian systems due to how
> it encodes and decodes data. Most QMI related data structures are defined
> in CPU native order and do not use endian specific types.
>
> Add support for endian conversion of basic element types in the QMI
> encoding and decoding logic. Fix the handling of QMI_DATA_LEN fields to
> ensure correct interpretation on big endian systems. These changes are
> required to allow QMI to operate correctly across architectures with
> different endianness.
> ---

Hello,

I recently (next-20260119) started receiving errors on Pixel 3:

[   21.158943] ipa 1e40000.ipa: received modem running event
[   21.164616] qmi_encode: Invalid data length
[   21.168930] qcom_q6v5_pas remoteproc-adsp: failed to send subsystem event
[   21.175844] qmi_encode: Invalid data length
[   21.180494] qcom_q6v5_pas remoteproc-cdsp: failed to send subsystem event
[   21.187467] qmi_encode: Invalid data length
[   21.191772] qcom-q6v5-mss 4080000.remoteproc: failed to send 
subsystem event
[   21.199088] qmi_encode: Invalid data length
[   21.203360] qcom-q6v5-mss 4080000.remoteproc: failed to send 
subsystem event
[   21.210636] remoteproc remoteproc0: remote processor 
4080000.remoteproc is now up

Since it's not well tested, I believe there could be problem with 
configuration, but after reverting this series, no errors pop up.

I would believe maybe these errors was previously hidden, but just to be 
sure asking here.

Thanks
David

[...]--
David Heidelberg