mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: David Heidelberg <david@ixit.cz>
To: Bjorn Andersson <andersson@kernel.org>,
	Alexander Wilhelm <alexander.wilhelm@westermo.com>,
	Thorsten Leemhuis <regressions@leemhuis.info>
Cc: Konrad Dybcio <konradybcio@kernel.org>,
	linux-arm-msm@vger.kernel.org, linux-kernel@vger.kernel.org,
	regressions@lists.linux.dev
Subject: Re: [PATCH v5 0/3] soc: qcom: extend interface for big endian support
Date: Mon, 24 Aug 2026 01:36:38 +0200	[thread overview]
Message-ID: <959d32b7-592f-48ce-a7a2-c2cf4b0cb44a@ixit.cz> (raw)
In-Reply-To: <aa6kLwNxoCIvquBT@FUE-ALEWI-WINX>

On 09/03/2026 11:42, Alexander Wilhelm wrote:
> On Mon, Mar 09, 2026 at 11:30:42AM +0100, Thorsten Leemhuis wrote:
>> On 2/14/26 20:26, Bjorn Andersson wrote:
>>> On Wed, Jan 21, 2026 at 09:22:07AM +0100, David Heidelberg wrote:
>>>> 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:
>>>> [...]
>>>> 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.
>>>
>>> #regzbot ^introduced: fe099c387e06
>>
>> Looks like nothing much has happened since then – or was there some
>> progress or even a solution I missed?
> 
> The current proposal is that the driver side should always use `u32` for
> all `DATA_LEN` fields. Most drivers already follow this, and Bjorn has
> proposed the patch for the one that was using a different type, and it has
> already been applied.
> 
> Check:
> [1/1] remoteproc: sysmon: Correct subsys_name_len type in QMI request
>        commit: da994db94e60f9a9411108ddf4d1836147ad4c9c

So I assume we can drop:

  - soc: qcom: qmi: Fix "invalid data length" in encoder
  - soc: qcom: qmi: Avoid splatting the "length" destination field

we carry, right?

Thanks
David>
> 
> Best regards
> Alexander Wilhelm


  reply	other threads:[~2026-08-23 23:36 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-11-19 10:40 Alexander Wilhelm
2025-11-19 10:40 ` [PATCH v5 1/3] soc: qcom: check QMI basic element error codes Alexander Wilhelm
2025-11-19 10:40 ` [PATCH v5 2/3] soc: qcom: fix QMI encoding/decoding for basic elements Alexander Wilhelm
2025-11-19 10:40 ` [PATCH v5 3/3] soc: qcom: preserve CPU endianness for QMI_DATA_LEN Alexander Wilhelm
2026-01-16 21:39 ` [PATCH v5 0/3] soc: qcom: extend interface for big endian support Bjorn Andersson
2026-01-21  8:22 ` David Heidelberg
2026-01-21  9:07   ` Alexander Wilhelm
2026-01-21  9:27     ` Dmitry Baryshkov
2026-01-21 10:34       ` Alexander Wilhelm
2026-01-27 13:29     ` Konrad Dybcio
2026-02-14 19:26   ` Bjorn Andersson
2026-03-09 10:30     ` Thorsten Leemhuis
2026-03-09 10:42       ` Alexander Wilhelm
2026-08-23 23:36         ` David Heidelberg [this message]
2026-08-31  7:40           ` Alexander Wilhelm

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=959d32b7-592f-48ce-a7a2-c2cf4b0cb44a@ixit.cz \
    --to=david@ixit.cz \
    --cc=alexander.wilhelm@westermo.com \
    --cc=andersson@kernel.org \
    --cc=konradybcio@kernel.org \
    --cc=linux-arm-msm@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=regressions@leemhuis.info \
    --cc=regressions@lists.linux.dev \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox

all inboxes | Powered by JetHome®